Fibre Channel (SAN)

New Contributor
Posts: 3
Registered: ‎11-23-2011

Software Bootup Failure:Bringup timed out

[ Edited ]



Map file at LBA sector 0x183e10 ##

Booting image at 00400000 ... Image Name: Linux-

Image Type: PowerPC Linux Multi-File Image (uncompressed) Data Size: 4269595 Bytes = 4.1 MB

Load Address: 00000000 Entry Point: 00000000

Contents: Image 0: 3190917 Bytes = 3 MB Image 1: 1078663 Bytes = 1 MB ##

Current stack ends at 0x1FAEEBE8 => set upper limit to 0x00C00000 ##

initrd at 0x0070B0D4 ... 0x0081265A (len=1078663=0x107587)

Loading Ramdisk to 1f9e6000, end 1faed587 ... OK

initrd_start = 1f9e6000, initrd_end = 1faed587 ##

Transferring control to Linux (at address 00000000) ...

Installing Linux 2.6 Kernel

Attempting to find a root file system on hda2...

INIT: version 2.78 booting Bypassing firmware validation. ---

Partition /dev/hda1 is inconsistent. --- Its content will be restored to be the same as that of /dev/hda2. ---

Please check the version and re-load firmware if necessary after the system boots up.

INIT: Entering runlevel: 3

Starting Fabric OS Services... FIPS off, RRD... Found 2(threshold 5) abnormal reboots within 3000 seconds window(threshold) rscmon_service: started thread! rscmon_service: started thread! sys_chip_init: class 0 max 24 Done ethsw_ha_enabled = 1 uptime: 4293889611; sup_qid: 0 .

Fabric OS (*********)

********* console login: 2014/01/08-16:11:47, [HAM-1004], 7966, CHASSIS, INFO, Brocade300, Processor rebooted - Software Bootup Failure:Bringup timed out

SNMP Research EMANATE/Lite Agent Version Copyright 1989-2006

SNMP Research, Inc.


After login no command can be used

*                                                            *
* Fabric OS has detected frequent switch reboot condition.   *
* Following actions can be taken to recover the switch:      *
* - remove or replace any problem blades (if applicable to   *
*   platform).                                               *
* - use supportsave to collect supportsave data.             *
*                                                            *
sysmodAttach open failed: No such device or address
fabsys device open: No such device or address
Raslog Module Initialisation failed rc=-1
fabsys device open: No such device or address


debchafsw01:root> help
Error in retriving the chassis info.



Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook