Volker Kuhlmann wrote:
> Incidentally, I don't think that much of the badblocks program. They all
> can't really work properly. I ran it with -w and it didn't find
> anything. Yet, if I deliberately read certain blocks, the kernel keeps
> on reporting
>
> dma_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
> dma_intr: error=0x01 { AddrMarkNotFound }, LBAsect=
Did some googling.... question have you turned on S.M.A.R.T. for your
hard drive in the BIOS if you have the option?
Or it could simply be a DMA problem that goes away if you turn off DMA
for that drive... I suppose it could even be a motherboard problem
rather than a hard drive problem.
However I have had another thought, I'm not sure if it would be possible
as I haven't had much low-level linux programming experience, but
someone here might know if you could erase the file, and then
specifically allocate the faulty blocks to a 'dud' file. Or specify the
"supposedly bad" blocks to badblocks?
