Dell Brocade 825 Brocade Adapters Troubleshooting Guide - Page 44

UEFI boot problems, System will not boot over SAN or on local disk in Legacy BIOS mode

Page 44 highlights

2 General adapter problems Action: If you are installing the brocade_driver_linux_.tar.gz driver package, the driver module compiles on the system during installation. If driver build errors result when you install the package, verify that the appropriate distribution kernel development packages are installed on your host system for the currently running kernel. These packages should include the gcc compiler and the kernel sources. If these are not installed, you will need to install them through your Linux OS Software Management tools or reinstall the operating system before you can continue the driver installation. Be sure to "install everything" including the developer library options. UEFI boot problems This section describes problems that may occur when using the Brocade adapter and unified extensible firmware interface (UEFI) for booting a host system from a remote storage device (boot over SAN). Possible causes and recommended actions to help resolve the problems are provided. System will not boot over SAN or on local disk in Legacy BIOS mode On some IBM UEFI based systems, Hard Disk 0 is not present after Legacy Only option in boot manager and system will not boot as local disk or over SAN. Possible Cause: Hard Disk are not present in the boot manager list. Action: Follow these steps: 1. Press F1 to enter System Setup during early phase of booting. 2. Select Boot Manager and press Enter. 3. Select Add Boot Option and press Enter. 4. Select Legacy Only and press Enter. 5. Press Esc to return to Boot Manager. 6. Select Change Boot Order and press Enter. 7. Select the existing Boot Order and press Enter. 8. Select Legacy Only and press the + key to promote the boot order to a position above the local device that contains the operating system (typically, this would be above Hard Disk 0). Press Enter. 9. Confirm that Hard Disk 'x' is present in the list. If not, return to step 3 and add Hard Disks to the boot order. 10. Select Commit Changes and press Enter. 11. Press Esc to return to Boot Manager. 12. Select Reset System and press Enter. Host not booting from remote LUN If the host system where the adapter is installed does not boot from the remote boot LUN, refer to the following descriptions of possible causes and recommended actions to help resolve the problem. Possible Cause: Boot over SAN is not configured correctly. 20 Brocade Adapters Troubleshooting Guide 53-1002145-01

  • 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

20
Brocade Adapters Troubleshooting Guide
53-1002145-01
General adapter problems
2
Action:
If you are installing the brocade_driver_linux_<versions>.tar.gz driver package, the driver
module compiles on the system during installation. If driver build errors result when you install the
package, verify that the appropriate distribution kernel development packages are installed on your
host system for the currently running kernel. These packages should include the gcc compiler and
the kernel sources. If these are not installed, you will need to install them through your Linux OS
Software Management tools or reinstall the operating system before you can continue the driver
installation. Be sure to “install everything” including the developer library options.
UEFI boot problems
This section describes problems that may occur when using the Brocade adapter and unified
extensible firmware interface (UEFI) for booting a host system from a remote storage device (boot
over SAN). Possible causes and recommended actions to help resolve the problems are provided.
System will not boot over SAN or on local disk in Legacy BIOS mode
On some IBM UEFI based systems,
Hard Disk 0
is not present after
Legacy Only
option in boot
manager and system will not boot as local disk or over SAN.
Possible Cause: Hard Disk
are not present in the boot manager list.
Action:
Follow these steps:
1.
Press F1 to enter
System Setup
during early phase of booting.
2.
Select
Boot Manager
and press Enter.
3.
Select
Add Boot Option
and press Enter.
4.
Select
Legacy Only
and press Enter.
5.
Press Esc to return to Boot Manager.
6.
Select
Change Boot Order
and press Enter.
7.
Select the existing
Boot Order
and press Enter.
8.
Select
Legacy Only
and press the + key to promote the boot order to a position above the local
device that contains the operating system (typically, this would be above Hard Disk 0). Press
Enter.
9.
Confirm that Hard Disk ‘x’ is present in the list. If not, return to
step 3
and add
Hard Disks
to
the boot order.
10. Select
Commit Changes
and press Enter.
11.
Press Esc to return to Boot Manager.
12. Select
Reset System
and press Enter.
Host not booting from remote LUN
If the host system where the adapter is installed does not boot from the remote boot LUN, refer to
the following descriptions of possible causes and recommended actions to help resolve the
problem.
Possible Cause:
Boot over SAN is not configured correctly.