OK. Now I really am at a loss for words. I experienced my first FAILURE
message this morning when trying to fdisk my last newly formatted 160GB
drive. The second fdisk would start to write, my screen would fill with
WRITE_DMA WARNINGS and FAILURES. That was with another drive on the same
Well, it's a week later and I've been trying some things. I don't want
to get in to too much complicated detail, but I've now got the following
disk setup:
Primary Master - 200GB 7200RPM
Secondary Master - TDK VeloCD CD Burner
Secondary Slave - Sony DRU500A
RAID0 Master - 160GB 7200RPM
RAID0
Wesley Will wrote:
I can try to pull the data off one of my other drives, maybe the 60GB,
then format that and try to dump backjust to see if that one copies
back OK with no DMA errors.
Very good idea. This is an excellent plan, especially if you already have
the hardware.
Okay, well
Mark Kane wrote:
[ ... ]
My drives are like this
PRIMARY IDE:
Master - 160GB
Slave - 60GB
SECONDARY IDE:
Master: TDK VeloCD CD Burner
Slave: Sony DRU500A DVD Burner
I never put optical drives on the same channel as hard drives.
I was going to give Maxtor a call on the 80GB when I thought the
Okay well I tried another test. I left the 160GB on the primary IDE
channel, took out both optical drives, and put the 60GB on the secondary
IDE channel by itself.
I copied the data over again. No errors this time. I checksummed the
data, and everything is OK.
Chuck Swiger wrote:
Without
Mark Kane [EMAIL PROTECTED] writes:
This is a brand new motherboard. Giga-Byte GA-K8NS Pro. FreeBSD
5.4-RELEASE (amd64).
I was also doing some searching around and found a list post about
FreeBSD 5 and DMA write problems:
I've got a GA-K8NSC-939 running 5.4-R (i386) with two 80GB using
I had a disk that was giving the same errors so at the time I just
disabled DMA (in loader.conf, hw.ata.ata_dma=0) but I still wanted
to fix it..
so yesterday..
the drive was set as primary (ad2) but I switched it to slave (ad3).
it seems fine now.
clayton
On 8/7/05, Gary W. Swearingen [EMAIL
Wesley Will wrote:
It almost assuredly means that the drive electronics are failing. The mag
bubble is likely still intact but the controller isn't capable of keeping
up with that data rate any longer. It could (easily) be an overheating
issue causing the degradation of performance. These
