"Jack L. Stone" <[EMAIL PROTECTED]> 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. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
