Date: Sat, 5 Dec 2009 16:39:44 +0000 From: Baldur Gislason <baldur@foo.is> To: freebsd-fs@freebsd.org Subject: Re: ZFS and reordering drives Message-ID: <20091205163943.GL73250@gremlin.foo.is> In-Reply-To: <4B1A8B5D.6050808@rcn.com> References: <20091205152757.GK73250@gremlin.foo.is> <4B1A830D.3090900@jrv.org> <4B1A8B5D.6050808@rcn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091205163943.GL73250>