HP Elite Dragonfly 13.5 Maintenance and Service Guide - Page 117

No boot to operating system (no read-write error), Read-write error

Page 117 highlights

Table 6-46 Issues, possible causes, and fixes (continued) Items Procedures 7. Test with a verified working hard drive. If it is still not recognized, the system board is faulty. NOTE: If the drive is seen in BIOS and Diagnostics, try a secure erase before replacing a drive as this might resolve related issues. No boot to operating system (no read-write error) Use this information to troubleshoot issues with booting to the operating system. Table 6-47 Issues, possible causes, and fixes Items Procedures Symptoms Possible causes ● POST error message: Boot Device Operating system, loose connection, faulty hard drive, BIOS configuration, Secure Boot. not found (3F0) Troubleshooting steps ● Hang when booting to operating system 1. Verify whether Secure Boot is enabled in BIOS. Secure Boot prevents legacy boot devices from starting the computer, including bootable CDs and DVDs. For more information, see http://support.hp.com/us-en/document/c03653226. 2. Reset BIOS to default. Be sure that BIOS Boot Mode in Boot Option is set up properly for bootable device and its operating system (for example, UEFI Native for Windows 8). Another example, choosing Legacy Boot Order for an UEFI device causes "Boot Device not found (3F0)" error. 3. Verify hard drive connection and flex cable. Reseat connection. For multiple storage devices, keep the primary drive with the operating system and remove other devices. 4. Use PC Hardware Diagnostics tool to test. Record failure code and have the hard drive replaced. 5. If there is no error, reinstall the operating system using HP Restore. 6. Test with a verified working operating system hard drive, if available. Note If there is a hard drive POST error message, see POST error messages and user actions on page 116. Read-write error Use this information to troubleshoot read and write errors. Table 6-48 Issues, possible causes, and fixes Items Procedures Symptoms Possible causes ● POST error message (for Loose connection, faulty hardware. example, error code 301) Troubleshooting steps ● Hang when working on data, files, documents 1. Perform a hard reset (8. Hard reset on page 68). 108 Chapter 6 Troubleshooting guide

  • 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
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172

Table 6-46
Issues, possible causes, and fixes
(continued)
Items
Procedures
7.
Test with a verified working hard drive. If it is still not recognized, the system board is
faulty.
NOTE:
If the drive is seen in BIOS and Diagnostics, try a secure erase before replacing a
drive as this might resolve related issues.
No boot to operating system (no read-write error)
Use this information to troubleshoot issues with booting to the operating system.
Table 6-47
Issues, possible causes, and fixes
Items
Procedures
Symptoms
POST error message: Boot Device
not found (3F0)
Hang when booting to operating
system
Possible causes
Operating system, loose connection, faulty hard drive, BIOS configuration, Secure Boot.
Troubleshooting steps
1.
Verify whether Secure Boot is enabled in BIOS. Secure Boot prevents legacy boot
devices from starting the computer, including bootable CDs and DVDs. For more
information, see
us-
en/
document/
c03653226
.
2.
Reset BIOS to default. Be sure that BIOS
Boot Mode
in
Boot Option
is set up properly for
bootable device and its operating system (for example, UEFI Native for Windows 8).
Another example, choosing
Legacy Boot Order
for an UEFI device causes "Boot Device
not found (3F0)" error.
3.
Verify hard drive connection and flex cable. Reseat connection. For multiple storage
devices, keep the primary drive with the operating system and remove other devices.
4.
Use PC Hardware Diagnostics tool to test. Record failure code and have the hard drive
replaced.
5.
If there is no error, reinstall the operating system using HP Restore.
6.
Test with a verified working operating system hard drive, if available.
Note
If there is a hard drive POST error message, see
POST error messages and user actions
on
page
116
.
Read-write error
Use this information to troubleshoot read and write errors.
Table 6-48
Issues, possible causes, and fixes
Items
Procedures
Symptoms
POST error message (for
example, error code 301)
Hang when working on data, files,
documents
Possible causes
Loose connection, faulty hardware.
Troubleshooting steps
1.
Perform a hard reset (
8. Hard reset
on page
68
).
108
Chapter 6
Troubleshooting guide