Dell PowerConnect Brocade 825 Brocade Adapters Troubleshooting Guide - Page 46

Driver and operating system installation failure on boot LUN

Get Dell PowerConnect Brocade 825 PDF manuals and user guides View all Dell PowerConnect Brocade 825 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 46 highlights

2 General adapter problems "29" is the device handle, and will be different in most systems. More than one Brocade adapter may display. b. Use the EFI shell dh command to display additional information about each Brocade adapter. This will include any attached Fibre Channel disk devices. For example, you would enter the following for the HBA or Fabric Adapter port configured in HBA mode with device handle 29: Shell> dh -d 29 The following displays: 29: PciIo ScsiPassThruExt BusSpecificDriverOverride DevPath (..P0A08,300)/Pci(0|0)/Pci(0|0)) ... Managed by : Drv[25] : Brocade Fibre Channel Adapter Bus Driver Drv[26] : SCSI Bus Driver ... Child Controllers : Child[70] : SCSI Disk Device Child[71] : SCSI Disk Device Child[72] : SCSI Disk Device The SCSI Disk Devices under "Child Controllers" are the LUNs that the Fibre Channel adapter can access. c. If an expected Fibre Channel attached disk does not appear in the "dh -d" list for a Brocade adapter, check the cabling, the adapter's link status LEDs, and the Fibre Channel switch configuration. NOTE The Brocade adapter port may have been disabled with the EFI shell drvcfg command. Use the drvcfg -s shell command to check the enabled status and configuration of the port, including the requested speed. After entering drafted -s, select the appropriate adapter from the Adapter List screen and press Enter to view and modify port properties. Driver and operating system installation failure on boot LUN Installation fails when installing drivers with the driver update disk (DUD) and an installing operating system to a remote LUN being used for booting over SAN. Possible Cause: The appropriate driver update disk (DUD) may not have been used for the host operating system and platform. For example, if the brocade_adapter_rhel53_x86_64 DUD is used during RHEL 5.3 x86 installation, installation will fail. Action: Download the appropriate DUD for your host platform from the Brocade adapters website using the following steps. 1. Go to the adapters website at www.brocade.com/adapters. 2. Navigate to the adapters Downloads page. 3. Select your operating system from the Downloads list to display appropriate downloads. 4. Download the dud from the "Driver Update Disk (DUDs)" area. 22 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
22
Brocade Adapters Troubleshooting Guide
53-1002145-01
General adapter problems
2
“29” is the device handle, and will be different in most systems. More than one Brocade
adapter may display.
b.
Use the EFI shell
dh
command to display additional information about each Brocade
adapter. This will include any attached Fibre Channel disk devices. For example, you would
enter the following for the HBA or Fabric Adapter port configured in HBA mode with device
handle 29:
Shell> dh -d 29
The following displays:
29: PciIo ScsiPassThruExt BusSpecificDriverOverride DevPath
(..P0A08,300)/Pci(0|0)/Pci(0|0))
...
Managed by :
Drv[25] : Brocade Fibre Channel Adapter Bus Driver
Drv[26] : SCSI Bus Driver
...
Child Controllers
:
Child[70] : SCSI Disk Device
Child[71] : SCSI Disk Device
Child[72] : SCSI Disk Device
The SCSI Disk Devices under “Child Controllers” are the LUNs that the Fibre Channel
adapter can access.
c.
If an expected Fibre Channel attached disk does not appear in the “dh -d” list for a
Brocade adapter, check the cabling, the adapter’s link status LEDs, and the Fibre Channel
switch configuration.
NOTE
The Brocade adapter port may have been disabled with the EFI shell
drvcfg
command. Use the
drvcfg -s
shell command to check the enabled status and configuration of the port, including
the requested speed. After entering
drafted -s
, select the appropriate adapter from the
Adapter
List
screen and press
Enter
to view and modify port properties.
Driver and operating system installation failure on boot LUN
Installation fails when installing drivers with the driver update disk (DUD) and an installing
operating system to a remote LUN being used for booting over SAN.
Possible Cause:
The appropriate driver update disk (DUD) may not have been used for the host
operating system and platform. For example, if the brocade_adapter_rhel53_x86_64 DUD is used
during RHEL 5.3 x86 installation, installation will fail.
Action:
Download the appropriate DUD for your host platform from the Brocade adapters website
using the following steps.
1.
Go to the adapters website at
www.brocade.com/adapters
.
2.
Navigate to the adapters
Downloads
page.
3.
Select your operating system from the
Downloads
list to display appropriate downloads.
4.
Download the dud from the “Driver Update Disk (DUDs)” area.