Re: Is this a bad, bad sign? (harddisk problem?)
umm.. that looks as if you file system is corrupted.. that usually
happens when someone turned off your computer or something equally
horrible.. when that happened to me, next time i rebooted my
MBR thought i had like 6 disk partitions.. i didn't :) in any case,
my file system was trash and i couldn't clean it with 'fsck'..
i probably went the cheezy way and reinstalled Linux -- but then again
some ppl can't do that because they are running networked computers
that ppl actually use :)
-------------------------------------------------------------------------------
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
|* struong@quake.digitaldune.net *|
||* http://quake.digitaldune.net/~struong *||
|* --==SbL==-- *|
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
-------------------------------------------------------------------------------
On Sun, 4 May 1997, Sam Ockman wrote:
> Found this on terminal 7, probably came from X.... Is it a bad, bad thing,
> or just somewhat bad?
>
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=2356919,
> sector=1280358
> end_request: I/O error, dev 03:03, sector 1280358
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=2357025,
> sector=1280474
> end_request: I/O error, dev 03:03, sector 1280474
> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=2357025,
> sector=1280476
> end_request: I/O error, dev 03:03, sector 1280476
>
> Thanks,
> Sam
>
>
> --
> TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
> debian-user-request@lists.debian.org .
> Trouble? e-mail to templin@bucknell.edu .
>
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: