hda: dma_intr: error=0x84 { DriveStatusError BadCRC }

neilloffhagen · n00b Joined: 06 Dec 2003 Posts: 23

Hi

Had some problems after running etc-update and overwriting files that i guess should have been left alone. Have since sortd it all (I think) and am booting into KDe okay again. But as the PC boots get the following errors:

dickbn · n00b Joined: 01 Sep 2003 Posts: 26

i don't think they are serious. it looks like a filesystem / physical disk problem. maybe a filesystem-fix could help.

Jazz · Posted: Tue Dec 09, 2003 10:11 pm Post subject:

No, perhaps if i'm not completely wrong.. u have attached another hdd to your system, or is it that you just got one hdd and still you're getting this error ??

Also post which kernel do you use, cuz in the 2.6 kernel there is an option to fix these messages..

in 2.6 kernel.. goto Drivers --> ATA/ATAPI/MFM/RLL support ---> Use multi-mode by default

Please include it in the kernel [*], that might solve your problem...

do let me know if it does,

Bye.
Jassi

neilloffhagen · n00b Joined: 06 Dec 2003 Posts: 23

Appreciate your responce.

Do you mean use e2fsck or fsck? Was going to try fsck, but got the message:

neilloffhagen · n00b Joined: 06 Dec 2003 Posts: 23

Hi,

I'm running kernel:

dickbn · n00b Joined: 01 Sep 2003 Posts: 26

try to boot your system without mounting the partition (for example by booting to another linux-system or booting the live-cd) and then do the filesystem-check again.

Jazz · Posted: Wed Dec 10, 2003 1:02 am Post subject:

Well then is there any multimode thingy in the 2.4 kernel that you're running ??

cuz its help specified spcefically that if you had errors then use this by default...

Directly from kernel halp pages :-

northern · Posted: Thu Dec 11, 2003 6:59 pm Post subject:

Did you get this fixed ?

Cos I've been having the same problem since installing gentoo (never had this problem on any other linux distro in about 6 years)

Here's my error:

Ateo · Posted: Thu Dec 25, 2003 7:59 am Post subject:

invaderzim · Posted: Fri Dec 26, 2003 7:43 pm Post subject:

These errors are harmless. But they can cause your drive to lose DMA mode sometimes. So you might have to do hdparm -d1 /dev/hd? once in a while if they keep coming up. Try using new IDE cables too. I'm starting to question my use of Rounded IDE cables.

talwaar2 · n00b Joined: 08 Dec 2003 Posts: 4

I used to get these errors on random occassions which would cause a hard lock almost every day (Hence i would not take these errors lightly) I seriously thought that my harddisk was going to crash. I looked up as much information about as I could regarding these errors on the forums and concluded that either :
1. harddisk is about to crash.
2. IDE cables are too long or faulty.
3. hdparm settings are messed up.
4. A combination of the above.

As it turns out, hdparm settings seemed fine and I tried all possible combinations of the settings but still got the hard locks ( Check if hdparm is added in rc-update and then the settings in /etc/conf.d/hdparm ). Since none of that worked hence I backed up my data and had the bright idea to attach the harddisk to a shorter IDE cable and have never had a problem since...infact, by testing the hd transfer rate using hdparm -tT /dev/hdXX before and after, it has made a 5 mb/s difference in the buffered disk reads. So, incase all software tinkering fails, check cables first and foremost !