On Wed, 2002-06-12 at 21:13, Tom Allison wrote: > devfs: v1.10 (20020120) Richard Gooch > devfs: boot_options: 0x0
No matter what else is a problem, the above is also very much a problem. Just say no to devfs. It mucks with device things in ways that cause exactly the sort of problem you have. When you get this "VFS: Unable to mount root fs on ..." error, this generally means that the kernel was told root (the /) is on /dev/hdaX when in fact, it is on /dev/hdaY (Y != X). Note how devfs can contribute to this, as root may really be on /dev/ide/bus/0/part/1 or whatever sillyness it forces. Regardless of devfs, boot with some sort of rescue disk (you do have a rescue disk... right?), run fdisk to figure out where the partitions containing root really are, modify /etc/lilo.conf (and /etc/fstab to reflect reality), and rerun lilo. If you use grub, well, sorry, cant help here (but same basic concept). > pty: 256 Unix98 ptys configured > Serial driver version 5.05c > RQ SERIAL_PCI enabled > ttyS00 at 0x03f8 (irq = 4)... > ttyS02 at 0x03e8 (irq - 4)... > block: 128 slots per queue, batch=32 > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > Cronyx Ltd, Synchronous PPP and CISCO HDLC > Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak. > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP, IGMP > IP: routing cache hash table of 1024 buckets, 8Kbytes > TCP: Hash tables configured (established 8192 bind 8192) > Linux IP multicast router 0.06 plus PIM-SM > request_module[block-major-3]: Root fs is not mounted > VFS: Cannot open root device "302" or 03:02 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 03:02 > -------------------------------------------------------- > I replace the RAM with 128M stick that has worked in the past and I get: > -----------------------[dmesg]---------------------------- > [ posting only the differences between the previous entry] > TCP: Hash tables configured (established 8192 bind 8192) > Linux IP multicast router 0.06 plus PIM-SM > RAMDISK: cramfs filesystem found at block 0 > RAMDISK: Loading 2700 blocks [1 disk] into ram disk... / > done > Freeing initrd memory: 2700k freed > VFS: Mounted root (cramfs filesystem). > [and the rest goes on from there] > > I'm thinking that there is some sort of problem in creating a RAMDISK > from cramfs... -- Joe Landman, email: [EMAIL PROTECTED] web : http://scientificappliance.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
