HP EliteDesk 800 G5 Maintenance and Service Guide - Page 84

File Backup Program, Hard Drive

Page 84 highlights

Disk transaction problem. Cause Either the directory structure is bad or there is a problem with a file. Solution In Windows 10, type file in the taskbar search box, and then select File Explorer from the list of applications. In the left column, expand This PC, right-click on a drive, select Properties, and then select the Tools tab. Under Error checking click Check. Drive not found (identified). Cause Cable could be loose. The system may not have automatically recognized a newly installed device. The device is attached to a SATA port that has been hidden in Computer Setup. Drive responds slowly immediately after power-up. Solution Check cable connections. See reconfiguration directions in the Solving hardware installation problems on page 85 section. If the system still does not recognize the new device, check to see if the device is listed within Computer Setup. If it is listed, the probable cause is a driver problem. If it is not listed, the probable cause is a hardware problem. If this is a newly installed drive, run the Computer Setup utility and try adding a POST delay under Advanced > Boot Options. Run the Computer Setup utility and ensure Device Available is selected for the device's SATA port in Advanced > Port Options. Run Computer Setup and increase the POST Delay in Advanced > Boot Options. Nonsystem disk/NTLDR missing message. Cause Solution The system is trying to start from the hard drive but the hard drive may have been damaged. ▲ Perform Drive Protection System (DPS) testing in system ROM. System files missing or not properly installed. 1. Insert bootable media and restart the computer. 2. Boot to the windows installation media and select the recovery option. If only a restore kit is available, then select the File Backup Program option, and then restore the system. 3. Install system files for the appropriate operating system. Hard drive boot has been disabled in Computer Setup. Run the Computer Setup utility and enable the hard drive entry in the Advanced > Boot Options list. Bootable hard drive is not attached as first in a multiple hard drive If attempting to boot from a hard drive, ensure it is attached to configuration. the system board dark blue SATA connector. Bootable hard drive is not listed first in the Boot Order. Run the Computer Setup utility and select Advanced > Boot Options and ensure the bootable hard drive is listed immediately under the Hard Drive entry. 74 Chapter 5 Troubleshooting without diagnostics

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151

Disk transaction problem.
Cause
Solution
Either the directory structure is bad or there is a problem with a
file.
In Windows 10, type
file
in the taskbar search box, and then
select
File Explorer
from the list of applications. In the left
column, expand
This PC
, right-click on a drive, select
Properties
,
and then select the
Tools
tab. Under
Error checking
click
Check
.
Drive not found (identified).
Cause
Solution
Cable could be loose.
Check cable connections.
The system may not have automatically recognized a newly
installed device.
See reconfiguration directions in the
Solving hardware installation
problems
on page
85
section. If the system still does not
recognize the new device, check to see if the device is listed within
Computer Setup. If it is listed, the probable cause is a driver
problem. If it is not listed, the probable cause is a hardware
problem.
If this is a newly installed drive, run the Computer Setup utility
and try adding a POST delay under
Advanced
>
Boot Options
.
The device is attached to a SATA port that has been hidden in
Computer Setup.
Run the Computer Setup utility and ensure
Device Available
is
selected for the device's SATA port in
Advanced
>
Port Options
.
Drive responds slowly immediately after power-up.
Run Computer Setup and increase the POST Delay in
Advanced
>
Boot Options
.
Nonsystem disk/NTLDR missing message.
Cause
Solution
The system is trying to start from the hard drive but the hard
drive may have been damaged.
Perform Drive Protection System (DPS) testing in system
ROM.
System files missing or not properly installed.
1.
Insert bootable media and restart the computer.
2.
Boot to the windows installation media and select the
recovery option. If only a restore kit is available, then select
the
File Backup Program
option, and then restore the
system.
3.
Install system files for the appropriate operating system.
Hard drive boot has been disabled in Computer Setup.
Run the Computer Setup utility and enable the hard drive entry in
the
Advanced
>
Boot Options
list.
Bootable hard drive is not attached as first in a multiple hard drive
configuration.
If attempting to boot from a hard drive, ensure it is attached to
the system board dark blue SATA connector.
Bootable hard drive is not listed first in the Boot Order.
Run the Computer Setup utility and select
Advanced
>
Boot
Options
and ensure the bootable hard drive is listed immediately
under the
Hard Drive
entry.
74
Chapter 5
Troubleshooting without diagnostics