Getting ZFS pools back.
asomers at freebsd.org
Sun Apr 29 14:40:52 UTC 2018
So your kernel couldn't find the pool. That might be due to a GEOM module
that wasn't loaded but should've been (were you using gmirror or geli or
something?). Or you might've accidentally destroyed the pool. It would
still show up in "zdb -l", albeit in the destroyed state. Or you might've
accidentally destroyed the partition. If the pool had resided on the
disk's last partition, then "zdb -l /dev/ada0" still would've seen the
label, since there's a copy of the label at the end of the device. But if
you've reused the disk, then there's no way to know for sure.
On Sun, Apr 29, 2018 at 8:29 AM, Willem Jan Withagen <wjw at digiware.nl>
> On 28/04/2018 20:43, Richard Yao wrote:
>> What is the output of ‘zpool import‘ with no arguments?
> If I boot thru aa mem-stick....
> # zpool import
> So, empty line
> In the mean time I rebuild the system.
> Was able to retreive the data by a convoluted incantation of
> 'zpool import -fmNF' or something like that.
> Made a full backup, and started fresh.
> On Apr 28, 2018, at 11:42 AM, Willem Jan Withagen <wjw at digiware.nl> wrote:
>>> I had this server crash on me, and first it just complained about not
>>> being able to boot because it could not find the guid.
>>> Now I cannot even import the pools any longer.
>>> Althoug zdb -l /dev/ada0 still gives me data that indicates that there
>>> should be a ZFS pool on that partition.
>>> Any suggestions on how to get the pools/data back online?
>>> Help would be highly appreciated, since restoring it from backups is
>>> going to quite some work.
>>> freebsd-hackers at freebsd.org mailing list
>>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at f
> freebsd-hackers at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
More information about the freebsd-fs