Problem With Bcm400 rls 4.0 boot

[supportbcm]

Hello everyone,

i have a faulty disk rls 3.6 on a bcm 400.
I bought a disk 4.0 rls and an upgrade kit 3.6 to 4.0 for keycode migration.
My Bios version is 02.03.50.
I plug the disk rls 4.0 to the bcm and i try to boot, this is the log from my try:

---------------------
Linux version 2.4.22-ncgl-10.12.1.0 (root@zcarh0xk.ca.nortel.com) (gcc version 3
.3.1) #2 Mon Mar 27 11:25:35 EST 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e4c00 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000fe80000 (usable)
BIOS-e820: 000000000fe80000 - 0000000010000000 (reserved)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
user-defined physical RAM map:
user: 0000000000000000 - 000000000009f800 (usable)
user: 000000000009f800 - 00000000000a0000 (reserved)
user: 00000000000e4c00 - 0000000000100000 (reserved)
user: 0000000000100000 - 000000000fe80000 (usable)
254MB LOWMEM available.
On node 0 totalpages: 65152
zone(0): 4096 pages.
zone(1): 61056 pages.
zone(2): 0 pages.
DMI not present.
Kernel command line: rw root=/dev/hda5 nmi_watchdog=1 mem=260608K
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
Initializing CPU#0
Detected 1196.404 MHz processor.
Calibrating delay loop... 2385.51 BogoMIPS
Memory: 254520k/260608k available (1884k kernel code, 5700k reserved, 606k data,
96k init, 0k highmem)
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
dump: Registering dump compression type 0x0
dump: mbank[0]: type:1, phys_addr: 0 ... fe7ffff
dump: Crash dump driver initialized.
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 256K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Celeron(TM) CPU 1200MHz stepping 04
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
testing NMI watchdog ... OK.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 1196.3751 MHz.
..... host bus clock speed is 99.6979 MHz.
cpu: 0, clocks: 996979, slice: 498489
CPU0<T0:996976,T1:498480,D:7,S:498489,C:996979>
PCI: PCI BIOS revision 2.10 entry at 0xfd93b, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
Unknown bridge resource 2: assuming transparent
PCI: Using IRQ router PIIX [8086/2450] at 00:1f.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x0
NTFS driver v1.1.22 [Flags: R/W]
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en
abled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10f
RAMDISK driver initialized: 16 RAM disks of 5000K size 1024 blocksize
loop: loaded (max 8 devices)
Intel(R) PRO/100 Network Driver - version 2.3.38
Copyright (c) 2004 Intel Corporation

PCI: Found IRQ 9 for device 01:09.0
e100: eth0: Intel(R) PRO/100 Network Connection
Hardware receive checksums enabled

PCI: Found IRQ 7 for device 01:08.0
e100: eth1: Intel(R) PRO/100 Network Connection
Hardware receive checksums enabled

Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
C-ICH: IDE controller at PCI slot 00:1f.1
C-ICH: chipset revision 0
C-ICH: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1880-0x1887, BIOS settings: hdaMA, hdbio
hda: ST380215A, ATA DISK drive
blk: queue c03b3a40, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 39876480 sectors (20417 MB) w/2048KiB Cache, CHS=2482/255/63, UDMA(33)
Partition check:
/dev/ide/host0/bus0/target0/lun0:hda: dma_intr: status=0x51 { DriveReady SeekCo
mplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
end_request: I/O error, dev 03:00 (hda), sector 0
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
unable to read partition table
SCSI subsystem driver Revision: 1.00
PROMISE SATA150 Series Linux Driver v1.00.0.10
pdc-ultra:[warning] No valid cards found
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
dump: Registering dump compression type 0x1
dump: Registering dump compression type 0x2
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
host/usb-uhci.c: $Revision: 1.275 $ time 11:25:32 Mar 27 2006
host/usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 11 for device 00:1f.2
host/usb-uhci.c: USB UHCI at I/O 0x18a0, IRQ 11
host/usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
usb.c: registered new driver acm
acm.c: v0.21:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
Initializing IPsec netlink socket
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Cannot open root device "hda5" or 03:05
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:05

---------------------------

do you have any idea about my problem?

Thanks in advance!!

 

[Firebird Scrambler]

What is the status of the LED's on the BCM?. Can you ping the default IP LAN 1 AND 2 address's (assuming that you have used a new day one BCM 400 image?)

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[supportbcm]

thanx firebird for your quick response!

When the log stop all the led exept hd led are flashing.
ican't ping ip Lan1&2.
I have a brand new hd rls 4.0 from Nortel.

 

[cook1082]

Does this have something to do with the MSC card not being at 4.0? You did not upgrade this your just droping a HD in to it and the MSC is still at 3.6 plus when you r/p a HD you have to INI it. Try using the serial port to access it.

 

[supportbcm]

the only think that i can do from the serial port is to view all the above log...
the last line of the log is..
Kernel panic: VFS: Unable to mount root fs on 03:05
then i can't do anything!

 

[gberger]

I think you're missing the Bios Update.

Here's the patch notes;

Software Update Name: BCM.R400.nnn-BIOS

Applicable H/W Platforms: BCM200, BCM400, SRG200 1.5, SRG400 1.5

Applicable S/W Platforms: BCM 4.0, SRG 1.5 based on BCM 4.0

Category: GEN

Installation Recommendations:
This BIOS should be installed on a BCM 200/400 or SRG 1.5 which has been upgraded from an
earlier release to BCM 4.0 via a hard drive replacement. The installation is done with a
bootable CD containing the BIOS. The iso file in this update must be burned to the CD as a
bootable image.

The update contains installation instructions


Components & Versions:
fdstd288.iso


Dependencies:
Required updates:
BCM.R400.GA

Updates should be applied in the following order:

- BCM.R400.GA applied by hard disk replacement
- BIOS upgrade

Product Dependencies: None

Size: 3.2 MB

System Impact:
Time to apply approximately 25 Minutes

Does update application force reboot: Yes, 2 reboots

Other impacts: All services are unavailable during the patch process.

Limitations: Power failure during application of this patch may result in a failure
that requires replacement of the BFT to resolve.

 

[supportbcm]

I already have Bios Version 02.03.50
and when i try to run the bios update by image fdstd288.iso...
i take fault at installing version 02.03.50!
seems to try to overwrite the same version 02.03.50

but idon't have alive HD 3.6 or 3.7 to apply the the first update
that you mention below..

Updates should be applied in the following order:

- BCM.R400.GA applied by hard disk replacement
- BIOS upgrade

 

[MikeDThePhoneGuy]

I have done this before and if you are replacing a 3.6 h/d with a 4.0 h/d you don't need to do anything except plug it into the BCM and power it up. The MSC doesn't care what it has attached it will boot as a 4.0. The upgrade keycode then just needs to be activated in KRS to have AVAYA update the existing keycodes to the 4.0 format so that they can be re-installed.
I would make sure that you have the jumper in the master position on the new 4.0 h/d (furthest from the power, closest to the data cable) then I would check that all the cables from the h/d to the backplane are tight and try a reboot. I have also found in the past that I needed to reseat the MSC card in the BFT, you could try that as well. Good luck!

 

[pkellow]

Don't the drive errors give the game away??

Partition check: /dev/ide/host0/bus0/target0/lun0:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }ide0: reset: successhda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }ide0: reset: successhda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }end_request: I/O error, dev 03:00 (hda), sector 0hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }hda: dma_intr: error=0x84 { DriveStatusError BadCRC }ide0: reset: success unable to read partition table

and

VFS: Cannot open root device "hda5" or 03:05Please append a correct "root=" boot optionKernel panic: VFS: Unable to mount root fs on 03:05


The drive might be 'new' however it doesn't look happy. Try the HDD on another bcm if you have one. You could also try 'seatools' and connect the HDD to a PC and try testing it further.

 

[supportbcm]

Thanks Paul for your reply!

If i plug the disk to pc it must be boot?