Re: ATA and msdosfs problems / corruption

[Soren Schmidt]

It seems Wes Morgan wrote:
 
 ad0: ST32140A/08.08.04 ATA-? disk at ata0 as master
 ad0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S
 ad0: 16 secs/int, 0 depth queue, DMA
 ad1: WDC AC418000D/J78OA30K ATA-4 disk at ata0 as slave 
 ad1: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S
 ad1: 16 secs/int, 31 depth queue, DMA
 
 The motherboard is fairly old and does not support ATA/66 etc, and the
 drive with the fat fs has been rock solid so I doubt it has suddenly gone
 bad. I'd like to test this with DMA turned off, what flags will disable
 that?

OK, I'd like to see the rest of the dmesg, from a verbose at best, before
saying anything conclusive, but it looks like the Seagate dont like DMA.

There are currently no flags to control the DMA/PIO behavior, the driver
relies on the hardware to tell the truth. This might change though...


-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

ATA and msdosfs problems / corruption

[Wes Morgan]

When attempting to copy a large file over to a FAT partition, I had these
errors pop up:

Nov 27 16:26:59 volatile /kernel: ata0-master: ad_timeout: lost disk contact - 
resetting
Nov 27 16:28:17 volatile /kernel: ata0: resetting devices .. WARNING: WAIT_READY 
active=ATA_ACTIVE_ATA
Nov 27 16:28:17 volatile /kernel: done
Nov 27 16:28:18 volatile /kernel: ta0-master: ad_timeout: lost disk contact - resetting
Nov 27 16:28:18 volatile /kernel: ata0: resetting devices .. done
Nov 27 16:28:18 volatile /kernel: ata0-master: ad_timeout: lost disk contact - 
resetting
Nov 27 16:28:18 volatile /kernel: ata0: resetting devices .. done
Nov 27 16:28:18 volatile /kernel: ata0-master: ad_timeout: lost disk contact - 
resetting
Nov 27 16:28:19 volatile /kernel: ata0: resetting devices .. done
Nov 27 16:28:19 volatile /kernel: ata0-master: ad_timeout: lost disk contact - 
resetting
Nov 27 16:28:19 volatile /kernel: ata0: resetting devices .. done


The errors continue until the system either panicked and rebooted or just
plain rebooted, I was not at the console. However, the FAT volume was 
corrupted along with the boot loader (grub) overwritten to some
extent. I'm not 100% sure if it was just the partition table or the entire
volume. Next, I cvsup'd and built new kernel+modules, and the same error
happened, but there was no reboot and a couple new error showed up:

Nov 27 18:24:33 volatile /kernel: ad0: HARD WRITE error blk# 1912525 status=51 error=10

This error occurred for several different blocks.
The two drives are identified as:

ad0: ST32140A/08.08.04 ATA-? disk at ata0 as master
ad0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 0 depth queue, DMA
ad1: WDC AC418000D/J78OA30K ATA-4 disk at ata0 as slave 
ad1: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S
ad1: 16 secs/int, 31 depth queue, DMA

The motherboard is fairly old and does not support ATA/66 etc, and the
drive with the fat fs has been rock solid so I doubt it has suddenly gone
bad. I'd like to test this with DMA turned off, what flags will disable
that?

-- 
   _ __ ___   ___ ___ ___
  Wesley N Morgan   _ __ ___ | _ ) __|   \
  [EMAIL PROTECTED]   _ __ | _ \._ \ |) |
  FreeBSD: The Power To Serve  _ |___/___/___/
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message