Date: Fri, 4 Aug 2000 11:36:04 -0500 From: "Alejandro Ramirez" <ales@megared.net.mx> To: "Soren Schmidt" <sos@freebsd.dk> Cc: <freebsd-questions@freebsd.org> Subject: ATA33 Problem ??? Message-ID: <021001bffe32$152db480$02c134c8@megared.net.mx> References: <200008031744.TAA73057@freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Soren,
I have a PII-266 with 4 Quantum Fireball disks running FreeBSD
4.1-RELEASE, and its working as a veryloaded squid cache engine, suddenly it
stopped working and this messages hit the console:
Aug 3 13:29:33 cache3 /kernel: ad2: WRITE command timeout - resetting
Aug 3 13:29:33 cache3 /kernel: ata1: resetting devices .. done
Aug 3 13:56:16 cache3 /kernel: ad4: HARD WRITE ERROR blk#
6881408ata2-master: WARNING: WAIT_READY active=ATA_ACTIVE_ATA
Aug 3 13:56:16 cache3 /kernel: ad4: HARD WRITE ERROR blk# 6881408 status=11
error=02
Aug 3 13:56:16 cache3 /kernel: ad4: DMA problem fallback to PIO mode
Aug 3 13:56:16 cache3 /kernel: ad4: HARD WRITE ERROR blk# 6881424 status=11
error=02
Aug 3 13:56:16 cache3 /kernel: ad4: HARD WRITE ERROR blk# 6881440 status=11
error=02
Aug 3 13:56:16 cache3 /kernel: ad4: HARD WRITE ERROR blk# 6946864 status=11
error=02
Aug 3 13:56:16 cache3 /kernel: ad4: HARD READ ERROR blk# 8275008 status=19
error=02
Aug 3 13:56:16 cache3 /kernel: ad4: timeout waiting for DRQ
What Im asking to you its that if the ad4 disk really have bad blocks, and I
have to change it as soon as posible, or could be something else???
Actually I have booted the system with a DOS floppy, used fdisk to erase the
BSD slice, and to create a DOS partition, also used format to create a C
partition, with no bad blocks reported, also I isued chkdsk to the disk with
the same result, no bad blocks reported, after that I used DOS Scandisk to
check the disk and isued a complete surface check of the disk with the same
result no bad sectors at all, could this be caused by the Promise card,
actually just ad4 reported this, and ad6 its also in the Promise Card, and
it has not presented this problem at all, coul this be some kind of bug???,
remember that its working as a very loaded squid cache server (8,000 users
simultaneously cable modem connected).
BTW this is the configuration reported at boot time:
atapci0: <Intel PIIX4 ATA33 controller> port 0x1060-0x106f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
atapci1: <Promise ATA33 controller> port
0x1040-0x105f,0x1474-0x1477,0x1078-0x107f,0x1074-0x1077,0x1080-0x1087 irq 9
at device 16.0 on pci0
ata2: at 0x1080 on atapci1
ata3: at 0x1078 on atapci1
ad0: 6149MB <QUANTUM FIREBALL ST6.4A> [13328/15/63] at ata0-master using
UDMA33
ad2: 6149MB <QUANTUM FIREBALL ST6.4A> [13328/15/63] at ata1-master using
UDMA33
ad4: 6149MB <QUANTUM FIREBALL ST6.4A> [13328/15/63] at ata2-master using
UDMA33
ad6: 6149MB <QUANTUM FIREBALL ST6.4A> [13328/15/63] at ata3-master using
UDMA33
Mounting root from ufs:/dev/ad0s1a
P.S. If you need more info just tell me, actually this is a test machine, if
you need an account for testing, I can certanly provide it.
Thanks...
Ales
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?021001bffe32$152db480$02c134c8>