Date: Sat, 5 Dec 2009 19:15:26 +0000 From: Baldur Gislason <baldur@foo.is> To: freebsd-fs@freebsd.org Subject: Re: ZFS and reordering drives Message-ID: <20091205191526.GR73250@gremlin.foo.is> In-Reply-To: <20091205190641.GQ73250@gremlin.foo.is> References: <20091205170400.GM73250@gremlin.foo.is> <8555674.871260033069220.JavaMail.root@zimbra> <20091205184112.GP73250@gremlin.foo.is> <5da0588e0912051052p25fb743ele098ed9cb9de8fa0@mail.gmail.com> <20091205190641.GQ73250@gremlin.foo.is>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok. I'm starting to think that all hope is lost and I just have to rebuild the pool. I moved the drive to a different sata port, which let me start the system with the drive attached and import the pool in degraded mode, but when I try to do a replace, no luck. root@enigma:~# zpool replace zirconium 10805584276324217146 ad16 cannot replace 10805584276324217146 with ad16: device is too small Baldur On Sat, Dec 05, 2009 at 07:06:41PM +0000, Baldur Gislason wrote: > I did that already, I figured out that the labels are > found at the beginnin and the end of the disk. Overwriting the first > and last megabytes of the disk has given the result that zdb -l finds no label > on the disk but even after removing the cache file and rebooting, zpool still > insists the disk is a part of the pool and won't import the pool when it's attached. > > Baldur > > > On Sat, Dec 05, 2009 at 01:52:08PM -0500, Rich wrote: > > My suggestion would be to plug in the faulty drive in another machine > > (or this machine with the pool not imported, it's mostly academic), > > zero the entire drive, and then reboot with all the drives in. > > > > It can hardly attempt to import a label it can't find. > > > > - Rich > > > > On Sat, Dec 5, 2009 at 1:41 PM, Baldur Gislason <baldur@foo.is> wrote: > > > I have managed to import the pool in degraded mode, however I am having problems > > > getting it back into normal operating mode. > > > I can detach the drive either by pulling the sata cable or by using atacontrol > > > but I don't have any ways of reattaching the drive to a running system. > > > Running atacontrol attach on the ata channel after detaching it just gives an error, > > > running atacontrol reinit on the ata channel after reconnecting the physically disconnected > > > drive doesn't find the drive. > > > And there doesn't seem to be any option in zpool to forcefully destroy a device in a zpool1, > > > forcefully degrading the pool, and the pool refuses to cooperate when the drive is attached. > > > I even tried putting the drive on a USB->SATA controller but zpool wouldn't let me replace > > > it that way, saying it was too small. > > > What to do, what to do? > > > > > > Baldur > > > > > > On Sat, Dec 05, 2009 at 11:11:09AM -0600, James R. Van Artsdalen wrote: > > >> This is beyond what I know - someone else will need to step in. > > >> > > >> If it's a raidz1 with one bad disk you can probably just unplug the bad disk and import the pool DEGRADED (due to the missing disk). > > >> > > >> ----- Original Message ----- > > >> From: "Baldur Gislason" <baldur@foo.is> > > >> To: freebsd-fs@freebsd.org > > >> Sent: Saturday, December 5, 2009 11:04:00 AM > > >> Subject: Re: ZFS and reordering drives > > >> > > >> Ok. Running zdb -l on the four drives seems to indicate that one of them > > >> has some label issues. > > >> http://foo.is/~baldur/brokenzfs/ > > >> ad4, ad6 and ad20 all have identical labels, only differences are the ids of the disk > > >> holding the label, as expected. > > >> root@enigma:~# diff ad4.label ad6.label > > >> 12c12 > > >> < guid=12923783381249452341 > > >> --- > > >> > guid=972519640617937764 > > >> 61c61 > > >> < guid=12923783381249452341 > > >> --- > > >> > guid=972519640617937764 > > >> 110c110 > > >> < guid=12923783381249452341 > > >> --- > > >> > guid=972519640617937764 > > >> 159c159 > > >> < guid=12923783381249452341 > > >> --- > > >> > guid=972519640617937764 > > >> root@enigma:~# diff ad4.label ad20.label > > >> 12c12 > > >> < guid=12923783381249452341 > > >> --- > > >> > guid=10715749107930065182 > > >> 61c61 > > >> < guid=12923783381249452341 > > >> --- > > >> > guid=10715749107930065182 > > >> 110c110 > > >> < guid=12923783381249452341 > > >> --- > > >> > guid=10715749107930065182 > > >> 159c159 > > >> < guid=12923783381249452341 > > >> --- > > >> > guid=10715749107930065182 > > >> > > >> ad18 has a somewhat broken label. Label 0 and 1 exist identical to the labels on the rest > > >> label 2 and 3 are broken or nonexistant. > > >> -------------------------------------------- > > >> LABEL 2 > > >> -------------------------------------------- > > >> failed to unpack label 2 > > >> -------------------------------------------- > > >> LABEL 3 > > >> -------------------------------------------- > > >> failed to unpack label 3 > > >> > > >> How should I go about recovering this? > > >> > > >> Baldur > > >> > > >> On Sat, Dec 05, 2009 at 04:39:44PM +0000, Baldur Gislason wrote: > > >> > Ok. The pool that was degraded imported cleanly but the pool that went > > >> > unavailable won't import. > > >> > If it is of any significance, I did change the BIOS disk controller settings > > >> > from IDE to AHCI and then back to IDE before I noticed this pool was gone. > > >> > > > >> > root@enigma:~# zpool import zirconium > > >> > cannot import 'zirconium': invalid vdev configuration > > >> > > > >> > pool: zirconium > > >> > id: 16708799643457239163 > > >> > state: UNAVAIL > > >> > status: The pool is formatted using an older on-disk version. > > >> > action: The pool cannot be imported due to damaged devices or data. > > >> > config: > > >> > > > >> > zirconium UNAVAIL insufficient replicas > > >> > raidz1 UNAVAIL corrupted data > > >> > ad4 ONLINE > > >> > ad6 ONLINE > > >> > ad18 ONLINE > > >> > ad20 ONLINE > > >> > > > >> > How do I go about debugging this? > > >> > > > >> > Baldur > > >> > > > >> > > > >> > On Sat, Dec 05, 2009 at 11:33:33AM -0500, Gary Corcoran wrote: > > >> > > James R. Van Artsdalen wrote: > > >> > > > Baldur Gislason wrote: > > >> > > >> When I plugged them back in they didn't go in the right order > > >> > > >> and now both of my pools are broken. > > >> > > > zpool.cache is broken. Rename /boot/zfs/zpool.cache so that ZFS won't > > >> > > > load it, then import the pools manually. (a reboot might be needed > > >> > > > before the import; not sure). > > >> > > > > >> > > If one were booting from ZFS, would you be out of luck (since you wouldn't > > >> > > be able to access the zpool.cache before booting), or is there a way > > >> > > around this problem? Just wondering, I've avoided booting from ZFS so far. > > >> > > > > >> > > > The problem is that ZFS is recording the boot-time assigned name > > >> > > > (/dev/ad0) in the cache. I'm hoping to get GEOM to put the disk serial > > >> > > > number in /dev, i.e., /dev/serialnum/5LZ958QL. If you created the pool > > >> > > > using serial numbers then the cache would always work right. > > >> > > > > >> > > Is there any way today, to avoid using the boot assigned drive name (e.g. > > >> > > /dev/ad2) when creating the zpool? Again just wondering, I don't need > > >> > > a solution this year... > > >> > > > > >> > > Thanks, > > >> > > Gary > > >> > > > > >> > > > > >> > > _______________________________________________ > > >> > > freebsd-fs@freebsd.org mailing list > > >> > > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > >> > > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > >> > _______________________________________________ > > >> > freebsd-fs@freebsd.org mailing list > > >> > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > >> > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > >> _______________________________________________ > > >> freebsd-fs@freebsd.org mailing list > > >> http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > >> To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > > _______________________________________________ > > > freebsd-fs@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > > > > > > > > > > -- > > > > my US geograpy is lousy...lol so's mine and I live here Make no little > > plans; they have no ma... > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091205191526.GR73250>