Basically, if my /boot/vmlinuz image exceeds a certain size (the limit seems be somewhere around 900000 bytes), the following occurs on boot:
hdc6: bad access: block=2, count=2 end_request: I/O error, dev 16:06 (hdc), sector 2 EXT3-fs: Unable to read superblock hdc6: bad access: block=2, count=2 end_request: I/O error, dev 16:06 (hdc), sector 2 EXT2-fs: Unable to read superblock hdc6: bad access: block=0, count=1 end_request: I/O error, dev 16:06 (hdc), sector 0 NTFS: Reading super block failed Kernel panic: VFS: Unable to mount root fs on 16:06 While some googling revealed that I'm certainly not the only one being hit by this particular type of kernel panic, I found no solutions that seemed applicable to my situation. This has happened with 2.4.19, 2.4.20-pre10, and now 2.4.20-ck1, all compiled from kernel.org sources (ck1 from http://members.optusnet.com.au/ckolivas/kernel/). I have not tested any 2.4-kernel prior to 2.4.19. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
