From owner-freebsd-questions Fri Aug 4 9:37: 9 2000 Delivered-To: freebsd-questions@freebsd.org Received: from unix.megared.net.mx (megamail.megared.com.mx [200.52.207.52]) by hub.freebsd.org (Postfix) with ESMTP id 7C35D37B8E5 for ; Fri, 4 Aug 2000 09:37:04 -0700 (PDT) (envelope-from ales@megared.net.mx) Received: from ales (ales.corp.megared.net.mx [200.52.193.2]) by unix.megared.net.mx (8.9.3/8.9.3) with SMTP id LAA66441; Fri, 4 Aug 2000 11:34:24 -0500 (CDT) (envelope-from ales@megared.net.mx) Message-ID: <021001bffe32$152db480$02c134c8@megared.net.mx> From: "Alejandro Ramirez" To: "Soren Schmidt" Cc: References: <200008031744.TAA73057@freebsd.dk> Subject: ATA33 Problem ??? Date: Fri, 4 Aug 2000 11:36:04 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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: port 0x1060-0x106f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 atapci1: 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 [13328/15/63] at ata0-master using UDMA33 ad2: 6149MB [13328/15/63] at ata1-master using UDMA33 ad4: 6149MB [13328/15/63] at ata2-master using UDMA33 ad6: 6149MB [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