02-10-2005 09:56 AM
I have a CE-560 that just a while ago worked just fine. It had CDN V3-0-2. I decided to load ACNS 4. When I booted the device I got this message below-
Now I set the device to then boot to flash, hoping I could just recover the OS from there. But regardless of whether I select "None", "Flash", or "Diag" it still boots to the hard drive. If the flash image is gone, I have no idea how a device could just lose a flash image like this. More importantly how the device could have been corrupted.
LI
LILLOO bboooott::
LLooaaddiinngg lliinnuuxx......................................
Linux version 2.2.16-3 (root@porky.devel.redhat.com) (gcc version egcs-2.91.66 1
9990314/Linux (egcs-1.1.2 release)) #1 Mon Jun 19 19:11:44 EDT 2000
relocating initrd image:
initrd_start:0xc0f9c000 initrd_end:0xc0fff81b
mem_start:0xc027d000 mem_end:0xe0000000
initrd_size:0x0006381b dest:0xdff9c000
Detected 598412 kHz processor.
Console: colour *CGA 80x25
Calibrating delay loop... 1192.76 BogoMIPS
Memory: 516744k/524288k available (1036k kernel code, 420k reserved, 5624k data,
64k init, 0k bigmem)
Dentry hash table entries: 262144 (order 9, 2048k)
Buffer cache hash table entries: 524288 (order 9, 2048k)
Page cache hash table entries: 131072 (order 7, 512k)
VFS: Diskquotas version dquot_6.4.0 initialized
Pentium-III serial number disabled.
CPU: Intel Pentium III (Coppermine) stepping 03
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch (rgooch@atnf.csiro.au)
PCI: PCI BIOS revision 2.10 entry at 0xea39c
PCI: Using configuration type 1
PCI: Probing PCI hardware
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
TCP: Hash tables configured (ehash 524288 bhash 65536)
Initializing RT netlink socket
Starting kswapd v 1.5
Detected PS/2 Mouse Port.
Serial driver version 4.27 with<4>keyboard: Too many NACKs -- noisy kbd cable?
keyboard: Too many NACKs -- noisy kbd cable?
MANY_PORTS MULTIPORT SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
apm: BIOS not found.
Real Time Clock Driver v1.09
RAM disk driver initialized: 16 RAM disks of 4096K size
PIIX4: IDE controller on PCI bus 00 dev 39
PIIX4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:pio, hdd:pio
hd0: C/H/S=50127/232/176 from BIOS ignored
hd1: C/H/S=50127/232/176 from BIOS ignored
hd0: C/H/S=50127/232/176 from BIOS ignored
hd1: C/H/S=50127/232/176 from BIOS ignored
hd0: C/H/S=50127/232/176 from BIOS ignored
hd1: C/H/S=50127/232/176 from BIOS ignored
Floppy drive(s): fd0 is 1.44M, fd1 is 1.44M
FDC 0 is a post-1991 82077
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
raid5: MMX detected, trying high-speed MMX checksum routines
pII_mmx : 1331.214 MB/sec
p5_mmx : 1398.270 MB/sec
8regs : 1027.938 MB/sec
32regs : 576.072 MB/sec
using fastest function: p5_mmx (1398.270 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
RAMDISK: Compressed image found at block 0
autodetecting RAID arrays
autorun ...
... autorun DONE.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
autodetecting RAID arrays
autorun ...
... autorun DONE.
kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
VFS: Cannot open root device 08:06
Kernel panic: VFS: Unable to mount root fs on 08:06
02-16-2005 08:11 AM
To the best of my knowledge, for sometimes it takes several reboots for the unit to operate normally and upgrade to latest version, Please check with the following URL.
http://www.cisco.com/warp/public/117/mnl_upgrade_cdn_acns.html
http://www.cisco.com/univercd/cc/td/doc/product/webscale/webcache/ce25/config25/chap2.htm#xtocid2264
02-16-2005 09:52 AM
Sure enough that was the case. After rebooting several times I finally got it to boot well enough that I could re-install the software
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide