On Mon, 12 Aug 1996, Douglas Bates wrote:
> `dmesg' shows a lot of messages about two sectors on my disk. For
> example
> hda: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=1097170,
> sector=48787
> hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> hda: read_in
Gerry Jensen <[EMAIL PROTECTED]> writes:
> I have a 1.5g Maxtor hard drive. My motherboard has the Intel Triton
> chipset. Do we have anything in common here? I'm currently running
> 2.0.11 but have had this with other 2.0.x kernels as well.
Aha. I've been having this problem and I have a 1.
On Mon, 12 Aug 1996, Douglas Bates wrote:
> `dmesg' shows a lot of messages about two sectors on my disk. For
> example
> hda: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=1097170,
> sector=48787
> hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
...
>
> Shoul
Douglas Bates <[EMAIL PROTECTED]> writes:
> `dmesg' shows a lot of messages about two sectors on my disk.
From: Michael Harnois <[EMAIL PROTECTED]>
> Oh, thank God! I'm not the only one! I thought my disk was dying!
Maybe it is. Read the man page for "e2fsck", and look for the "-c"
flag. Read the
Douglas Bates <[EMAIL PROTECTED]> writes:
>
> `dmesg' shows a lot of messages about two sectors on my disk.
Oh, thank God! I'm not the only one! I thought my disk was dying!
`dmesg' shows a lot of messages about two sectors on my disk. For
example
hda: read_intr: error=0x01 { AddrMarkNotFound }, LBAsect=1097170, sector=48787
hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=1097170,
6 matches
Mail list logo
