Re: ad0: WARNING - removed from configuration (atacontrol and gmirror relationship?)
On Nov 27, 2007, at 8:24 PM, [EMAIL PROTECTED] wrote: On Nov 27, 2007 7:03 PM, Josh Paetzel <[EMAIL PROTECTED]> wrote: On Tuesday 27 November 2007 01:08:49 pm [EMAIL PROTECTED] wrote: Why was the device removed completely? Can I simply do this? (want to be sure as this box is remote) gmirror forget data atacontrol attach ata0 gmirror insert data ad0 IDE devices generally aren't hot swappable, so you're going to have to take the box down to replace the failed drive (that's why it detached from the bus). Once you do that you can rebuild the gmirror. I don't want to hot swap...I want to get the existing bad drive back into the mirror and see how long it lasts before gmirror breaks again. Can I use atacontrol to get the drive back in the system? Thanks, Andy You can, only if the two drives are on different channels. If you have ad0 and ad1, you're probably out of luck. - Eric F Crist Secure Computing Networks ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad0: WARNING - removed from configuration (atacontrol and gmirror relationship?)
On Nov 27, 2007 7:03 PM, Josh Paetzel <[EMAIL PROTECTED]> wrote: > On Tuesday 27 November 2007 01:08:49 pm [EMAIL PROTECTED] wrote: > > Why was the device removed completely? > > > > > > Can I simply do this? (want to be sure as this box is remote) > > > > gmirror forget data > > > > atacontrol attach ata0 > > > > gmirror insert data ad0 > > IDE devices generally aren't hot swappable, so you're going to have to > take > the box down to replace the failed drive (that's why it detached from the > bus). Once you do that you can rebuild the gmirror. > I don't want to hot swap...I want to get the existing bad drive back into the mirror and see how long it lasts before gmirror breaks again. Can I use atacontrol to get the drive back in the system? Thanks, Andy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad0: WARNING - removed from configuration (atacontrol and gmirror relationship?)
On Tuesday 27 November 2007 01:08:49 pm [EMAIL PROTECTED] wrote: > This just happened on my server: > > Nov 22 03:21:11 sockeye kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 > retries left) LBA=28892960 > Nov 22 03:21:11 sockeye kernel: ad0: WARNING - removed from configuration > Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Device gm0s1: provider ad0 > disconnected. > Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=6). > ad0[WRITE(offset=13881704448, length=12288)] > Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=6). > ad0[WRITE(offset=14795718656, length=2048)] > Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=6). > ad0[WRITE(offset=770891776, length=16384)] > Nov 22 03:21:11 sockeye kernel: ata0-master: FAILURE - WRITE_DMA timed out > Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=5). > ad0[WRITE(offset=14793195520, length=2048)] > > Now the ad0 Master drive no longer exists: > > -su-2.05b$ sudo atacontrol list > ATA channel 0: > Master: no device present > Slave: acd0 ATA/ATAPI revision 5 > ATA channel 1: > Master: ad2 ATA/ATAPI revision 6 > Slave: ad3 ATA/ATAPI revision 6 > > > What is the relationship between atacontrol and gmirror? > > > Why was the device removed completely? > > > Can I simply do this? (want to be sure as this box is remote) > > gmirror forget data > > atacontrol attach ata0 > > gmirror insert data ad0 IDE devices generally aren't hot swappable, so you're going to have to take the box down to replace the failed drive (that's why it detached from the bus). Once you do that you can rebuild the gmirror. -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB signature.asc Description: This is a digitally signed message part.
ad0: WARNING - removed from configuration (atacontrol and gmirror relationship?)
This just happened on my server: Nov 22 03:21:11 sockeye kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=28892960 Nov 22 03:21:11 sockeye kernel: ad0: WARNING - removed from configuration Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Device gm0s1: provider ad0 disconnected. Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=6). ad0[WRITE(offset=13881704448, length=12288)] Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=6). ad0[WRITE(offset=14795718656, length=2048)] Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=6). ad0[WRITE(offset=770891776, length=16384)] Nov 22 03:21:11 sockeye kernel: ata0-master: FAILURE - WRITE_DMA timed out Nov 22 03:21:11 sockeye kernel: GEOM_MIRROR: Request failed (error=5). ad0[WRITE(offset=14793195520, length=2048)] Now the ad0 Master drive no longer exists: -su-2.05b$ sudo atacontrol list ATA channel 0: Master: no device present Slave: acd0 ATA/ATAPI revision 5 ATA channel 1: Master: ad2 ATA/ATAPI revision 6 Slave: ad3 ATA/ATAPI revision 6 What is the relationship between atacontrol and gmirror? Why was the device removed completely? Can I simply do this? (want to be sure as this box is remote) gmirror forget data atacontrol attach ata0 gmirror insert data ad0 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
