Brocade Troubleshooting and Diagnostics Guide v6.1.0 (53-1000853-01, June 2008)

40 Fabric OS Troubleshooting and Diagnostics Guide
53-1000853-01
Firmware download issues
5
Symptom You receive a BadRootDev error message.
Probable cause and recommended action
You perform a firmwaredownload on a 3900 or 4100 (a single-bladed/4.x switch). During the
firmwaredownload process the boot environment variables are incorrectly set and causes a
BadRootDev error message to appear.
You can find the information contained in the examples below in the output from the supportShow
command.
Example of normal boot environment variable
/sbin/bootenv:
AutoLoad=yes
ENET_MAC=006069900E8C
InitTest=MEM()
LoadIdentifiers=Fabric Operating System;Fabric Operating System
OSBooted=MEM()0xF0000000
OSLoadOptions=quiet;quiet
OSLoader=MEM()0xF0000000;MEM()0xF0800000
OSRootPartition=hda2;hda1
SkipWatchdog=yes
The following boot environment variable example shows what it looks like when a firmware
upgrade has occurred but not a proper reboot. This environment variable is temporarily placed
there by the firmware upgrade process. To fix this issue, you can reboot the switch. If the problem
persists, contact your switch support provider.
Example of switch needing a reboot
Example of BadRootDev environment variable
This environment variable will need to be removed before continuing:
/sbin/bootenv:
AutoLoad=yes
AutoLoadTimeout=0
ENET_MAC=006069906014
LoadIdentifiers=IDE w/ XFS;IDE w/ XFS & NFS Root
OSLoadOptions=quiet;quiet
OSLoader=MEM()0xF0800000;MEM()0xF0000000
OSRootPartition=hda2;hda1
SkipWatchdog=yes
SoftUpgrade=commit
Upgrade=/dev/hda2
/sbin/bootenv:
AutoLoad=yes
BadRootDev=hda2
ENET_MAC=00051e3411ad
InitTest=MEM()
LoadIdentifiers=Fabric Operating System;Fabric Operating System
OSBooted=MEM()0xF0000000
OSLoadOptions=quiet;quiet
OSLoader=MEM()0xF0000000;MEM()0xF0800000
OSRootPartition=hda1;hda2
SkipWatchdog=yes