Date: Thu, 19 Sep 2002 15:04:40 -0500 From: "Jack L. Stone" <jackstone@sage-one.net> To: Lowell Gilbert <freebsd-questions-local@be-well.no-ip.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Server Lockups during Backups ad0 to ad1 Message-ID: <3.0.5.32.20020919150440.00e8d428@mail.sage-one.net> In-Reply-To: <44sn07wb3i.fsf@be-well.ilk.org> References: <3.0.5.32.20020916122857.0117d8b8@mail.sage-one.net> <3.0.5.32.20020916122857.0117d8b8@mail.sage-one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 11:50 AM 9.18.2002 -0400, Lowell Gilbert wrote: >"Jack L. Stone" <jackstone@sage-one.net> writes: > >> Am running FreeBSD 4.5-RELEASE > >Updating might help; there are some changes to the ATA code which I >think *might* be relevant. Don't do that first, though; it could >certainly compound your problems. > >> BTW, the BIOS doesn't even show the ad1 IDE on first reboot, which takes a >> hard switch reset. Tnen a complete power down/power up to bring the ad1 HD >> in the BIOS back....OUCH! Is scary for this server which is not very old. > >[...] > >> ============================================================================== >> Sep 16 10:38:23 sage-one /kernel: ad1: WRITE command timeout tag=0 serv=0 - >> resetting >> Sep 16 10:40:07 sage-one /kernel: ata0: resetting devices .. done >> Sep 16 10:40:07 sage-one /kernel: ad1: WRITE command timeout tag=0 serv=0 - >> resetting >> Sep 16 10:40:07 sage-one /kernel: ata0: resetting devices .. done > >This looks like the drive is going out to lunch. > >> Sep 16 10:40:07 sage-one /kernel: ad1s1f: hard error writing fsbn 23516351 >> of 5466688-5466943 (ad1s1 bn 23516351; cn 1463 tn >> 210 sn 26)ata0-slave: timeout waiting for command=ef s=01 e=04 > >This looks like an actual media problem on the drive. > >> Sep 16 10:40:07 sage-one /kernel: ad1: timeout waiting for DRQ - resetting >> Sep 16 10:40:07 sage-one /kernel: ata0: resetting devices .. done >> Sep 16 10:40:07 sage-one /kernel: ad1: timeout waiting for DRQ - resetting >> Sep 16 10:40:07 sage-one /kernel: ata0: resetting devices .. done >> Sep 16 10:40:07 sage-one /kernel: swap_pager: indefinite wait buffer: >> device: #ad/0x20001, blkno: 392, size: 4096 > >The drive seems to have gone away... > >I'd recommend starting by replacing the ad1 drive, if possible. > >Good luck. > The ad1 drive WAS the problem. Using for a while in another machine showed same symptoms. DRATS! It was a brand-new drive and so has been dangerously flaky (defective) from the start when installed several months ago. Fortunately, the ad0 identical drive was okay.... no more QUANTUM FIREBALLS for me! Again, thanks for all help....!!! Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net 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?3.0.5.32.20020919150440.00e8d428>