How can I help solve this problem? What has changed in 2.1.106 to
create this problem? Are we spending too much time on spelling
errors and file system architectures, and not enough time on fixing
new bugs that are creeping into the system?? :-)
=S.Coffin
scoffin@netcom.com
/**************************************************************/
To: linux-kernel@vger.rutgers.edu
Subject: 2.1.106 boot failure ??
I got the following boot-time message twice recently with 2.1.106,
in about 20 successful boots. Never had this before with any previous kernel.
I have made no config changes since 2.1.8x, 2.1.9x. 2.1.10x, etc etc.
Any comments appreciated....
ps= machine is PPro 200, 2940 SCSI controller, boot disk is 4.2 GB on sda
=S.Coffin
scoffin@netcom.com
=================================================================
Partition check:
sda: scsidisk I/O Error: dev 08:00, sector 0
unable to read partition table
Drive not ready. Make sure there is a disk in the drive
sda: read capacity failed.
sda: status=1, message=00, host=0, driver=28
sda: extended sense code=2
sda: block size assumed to be 512 bytes, disk size 1GB
sda: scsidisk I/O Error: dev 08:00, sector 0
unable to read partition table
VFS: cannot open root device 08:02
Kernel panic: VFS: unable to mount root fs on 08:02
=================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu