>On Mon, 2002-09-16 at 15:26, Florian Hinzmann wrote:
>> > On Mon, 2002-09-16 at 12:17, Florian Hinzmann wrote:
>> >> kernel: hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
>> >> kernel: hdb: read_intr: error=0x10 { SectorIdNotFound }, LBAsect=97567071, high=5, lo
>> >> kernel: hdb: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
>> >
>> > Which is the drive reporting a physical media error
>>
>> Which seems to exist only while using the named combinations of DMA access
>> and kernel versions. While using i.e. 2.4.19 without DMA I can access the same data,
>> dd the whole disk to /dev/null or run badblock checks without finding
>> any physical media errors.
>>
>> 2.4.19 should complain, too, if there is a physical error indeed, right?
>
>The "sectoridnotfound" return is from the drive. That makes it very hard
>to believe it isnt a physical error
It might be a seek beyond end-of-media error as well (see ATA spec for
error reporting in this case: either ABRT or IDNF shall be set)!
Ciao,
Dani
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/