CRC Read errors

[sLydE]

I'm running a web/ftp/samba/mail server from my house using fedora core 2. last night, i just installed a new hard drive, cdrom and did a fresh install of fedora core 2. I bought the brand new hard drive, because i was getting some CRC read errors while trying to transfer large files to the former hard drive. So, now, when trying to copy my music collection from a windows box to the server, i get the same errors once again. I searched around, and saw that it could be a few things: the hard drive is bad, the cable is bad, the motherboard is bad, or the dma settings are out of whack. Well, seeing as i've used 2 different hard drives, the most recent brand new, and i've switched cables a few times, it must be either the motherboard or the dma settings. Anyone know where i can configure these settings before i decide that it's a motherboard problem? here are my specs:

p3 800mhz
768mb pc133 ram
ati radeon 7200
aopen ax34 mobo
brand new 120gb western digital hd w/8mb cache setup as hda w/80-pin ide cable
some cd-rom drive, an internal zip drive, and a 10/100 ethernet card
450w power supply (only about a year old)

any help would be greatly appreciated
edit: forgot to mention that the web/ftp/mail servers are setup fine, it's just trying to transfer the files over for samba share where i encounter the problems.

[sLydE]

here is the exact error i'm getting:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }

if this gives you some more information, great, i need to know what's up with this...

[Ned]

I bought the brand new hard drive, because i was getting some CRC read errors while trying to transfer large files to the former hard drive. So, now, when trying to copy my music collection from a windows box to the server, i get the same errors once again.

I have no idea if this is related to your problem, but it's worth noting.

I've had issues copying LARGE files within windows, either from partition to partition, disk to disk or over a windows file sharing netowrk. I first noticed it with large ghost images and more recently with CD iso images. Probelm seems to occur when using explorer to drag and drop files. I've not tested over a samba network but I would expect the same.

I found a simple solution to be to map the drive to a drive letter in windows (if a remote drive) and to use the verify (/V) switch with the dos copy command from a dos shell/command prompt. With the verify switch, large files would copy correctly every time (although it's a lot slower).

So basically it was a Windows Explorer problem. Like I said, this may not be your problem, but it's worth a try and worth knowing about. It's easy to test with md5sum and a linux iso image of known checksum.

Ned

[sLydE]

that's a good idea, i'm going to try it and get back to you. i was using explorer to drag and drop previously. thanks

edit: sorry, that didn't work, does anyone else have any suggestions? i'm going dig further on the net to see if i can find something. thanks in advance

edit2: i feel bad double posting, so i will just edit this post. i used this command:
hdparm -X34 /dev/hda
and everything now works alright, no more read errors!

[Ned]

Glad you got it sorted :)

Ned

[PsyGhost]

Check the memory for errors. Fedora's CD had memtest86 built in it.