Hello all,
On Thursday, I shutdown my SuSE Linux 6.2 system (kernel 2.2.12) to
reboot into Windows. As it was shutting down it hung just after
unmounting the filesystems, giving me several error messages about not
being able to reboot (which I was too stupid to write down). I did a
reset and booted into Windows. When I tried to reboot my linux system,
lilo started up and the kernel began to load. Just after the line, "INIT
version 2.76 booting" the system goes into a loop printing out:
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=157529
sector=157466
end_request: I/O error, dev 16:01 (hdc) sector 157466
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=157531
sector=157468
end_request: I/O error, dev 16:01 (hdc) sector 157468
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=157534
sector=157471
end_request: I/O error, dev 16:01 (hdc) sector 157471
I am able to boot using tomsrtbt disk and using the Slackware 4.0 system
I have installed on another drive. I used e2fsck from tomsrtbt disk and
from the Slackware system to do filesystem checks. Here is the result of
the last one I did:
dragoon:~# e2fsck -f /dev/hdc1
e2fsck 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
Pass 1: Checking inodes, blocks, and sizes
Error reading block 78753 (Attempt to read block from filesystem resulted
in short read) while reading indirect blocks of inode 8451. Ignore
error<y>? yes
Error reading block 2121747 (Attempt to read block from filesystem
resulted in short read) while doing inode scan. Ignore error<y>? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/hdc1: 100331/602112 files (1.8% non-contiguous), 1912482/2407072
blocks
dragoon:~#
While checking dmesg on the slackware system after having mounted
/dev/hdc1 to /mnt, I noticed that this had been appended to dmesg's
output:
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=157569,
sector=157506end_request: I/O error, dev 16:01 (hdc), sector 157506
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=4243557,
sector=4243494
end_request: I/O error, dev 16:01 (hdc), sector 4243494
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=4243557,
sector=4243494
end_request: I/O error, dev 16:01 (hdc), sector 4243494
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=157569,
sector=157506end_request: I/O error, dev 16:01 (hdc), sector 157506
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=4243557,
sector=4243494
end_request: I/O error, dev 16:01 (hdc), sector 4243494
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=4243557,
sector=4243494
end_request: I/O error, dev 16:01 (hdc), sector 4243494
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=157569,
sector=157506end_request: I/O error, dev 16:01 (hdc), sector 157506
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=4243557,
sector=4243494
end_request: I/O error, dev 16:01 (hdc), sector 4243494
hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x40 { UncorrectableError }, LBAsect=4243557,
sector=4243494
end_request: I/O error, dev 16:01 (hdc), sector 4243494
dragoon:~#
The drive in question is a Western Digital AC32500H, 2.5 GB IDE drive.
My question you all is, is there someway of fixing this? Can I get my
system back? Is the drive hosed? (Obviously it is not working properly;
I am referring to the relative severity of the errors.)
Cheers,
Sean
T. Sean (Theo) Schulze
[EMAIL PROTECTED] [EMAIL PROTECTED]
*****************************************************
There is, however, a limit at which forbearance ceases
to be a virtue. -- Edmund Burke
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
