Fixing vdev name
Alexander at leidinger.net
Wed Sep 19 19:05:15 UTC 2018
Quoting David Chisnall <theraven at freebsd.org> (from Wed, 19 Sep 2018
> Hello the list,
> I have a VM that uses ZFS with a pair of striped devices. The first
> is a partition on the root disk, created by the installer. When
> this was too small, I added another device (da1) and told the pool
> to expand to use it (no redundancy, because the underlying storage
> for the VM images provides that). After a reboot, I can no longer
> boot the system. Booting from the install CD and attempting to
> import the pool, it correctly identifies da0p4 as one of the
> devices, but gives me a long number instead of da1.
This means ZFS doesn't see the other device (or more correctly no
device with the ZFS meta-data on the device which matches what the
pool wants to see as the second vdev).
Do you see the second disk from non-ZFS tools? Does the partition info
look OK there (if you partitioned it before giving it to ZFS)? Does
the geometry/size look correct?
> How do I fix this so that the pool again points to da1?
As a side note, it doesn't matter if it is da1 or something else (e.g.
/dev/gpt/<volid> or whatever), as long as it is a geom provider
instead of the uuid of the device like it seems to be the case right
http://www.Leidinger.net Alexander at Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org netchild at FreeBSD.org : PGP 0x8F31830F9F2772BF
More information about the freebsd-fs