I got this set of errors while my machine was booting:

login: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }

Is this due to forgetting to unmount the drive the last itme I was logged in? Just curious, thanks.

this looks more like a faulty HDD. Get your HDD checked.

Cheers

Subhasis

I believe I have seen reports of those errors being present when the DMA controller is not working 100% with linux.

IIRC, the users who got these errors reported that their machines still booted and worked fine. The error in their case seemed to be a slight compatibility issue between their particular DMA controller and linux.

Sorry for the vague answer, if you Google a bit I think you'll see some reference to what I am talking about.

Just wanted to be sure you didn't throw out your hard drive just because of those errors, since the HDD might not actually be at fault.

Unfortunately, I did have a hard drive failure over the weekend and lost a lot of data (sigh). Anyway, the drive that failed was not the drive that Linux was on. (The machine was a dual boot which I have since had to rebuild.) It was a dual boot Linux/Windows XP machine with one 10GB drive as my Linux drive and two other 10GB drives fro Windows. Would I still be seeing the same errors regardless of whether the failed drive was the Linux drive or not?

All the errors you posted referred to the "hdd" device (which I THINK is generally the slave-drive on the secondary IDE channel...I may be wrong on that).

That may very well be one of the Windows drives. I believe at bootup time that linux will poke around and see what's on the ide bus. It may very well be throwing those hdd DMA errors when it's trying to interrogate the failed Windows drive.

187807, U are absolutely right.

-Subhasis

I thought that as well, but it was the secondary on first IDE channel that failed. hdd, or what Linux refers to as "hard drive d" was fine. I think it actually would have been hdb that crashed...

0perat0r,

no matter which drive has failed, Linux will probe all hardware while booting. Hence, the DMA errors at bootup.

-Subhasis