My 30G drive has a / (root) partition (currently /dev/hdb2) and a /boot
partition (currently /dev/hdb1). I couldn't get LILO to start properly when I
installed it on my 30G drive so I've switched to GRUB. (I'll switch back to
LILO if need be and I get good advice.) I can get GRUB to start my kernel
but my kernel panics when trying to mount file systems. Here is a transcript
of the kernel output:
attempt to access beyond end of device
03:42: rw=0, want=1, liimt=1
EXT2-fs: unable to read superblock
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0
attempt to access beyond end of device
03:42: rw=0, want=33, limit=1
isofs_read_super: bread failed, dev=03:42, iso_blknum=16, block=32
Kernel panic: VFS: Unable to mount root fs on 03:42
When I switch everything back to the way it was this kernel can be started
without a problem.
In switching the drives' master/slave status around I have (of course) done
the following:
* changed jumper settings on both drives
* edited /etc/fstab on the 30G drive (the one I want to boot as master).
* modified the bios settings (got bios to autodetect drives in new
configuration).
Why does my kernel panic? How do I fix the problem so that I can boot the
linux kernel on my 30G drive when the drive is configured as master instead
of slave?
Please help,
Jeff
-- =============================================================================== I never saw a wild thing sorry for itself. A small bird will drop frozen dead from a bough without ever having felt sorry for itself. -- "Self-Pity" by David Herbert Lawrence (1885-1930) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/