Unable to import degraded zpool

[Linda Kateley]

I would have tried omnios for this.. much closer to nexenta.

If you can import the pool, sometimes I can just run zpool online on the 
UNAVAIL drive and have it pop in..

Linda


On 1/4/17 12:13 PM, Arthur Ramsey wrote:
> Hello,
>
> I had 2 pools on Nexenta 4.  One pool caused Nexenta to boot loop, so 
> I decided to install FreeNAS 9.10.2.  No idea why it starting acting 
> up: no changes were made nor was a scrub started.  I've previously 
> migrated pools from Nexenta 4 to FreeNAS 9.3 without issue.  FreeNAS 
> reported one of the pools reported as corrupted though all disks were 
> online, which is the pool that was causing the boot loop I think.  I 
> recreated that pool since the data was more easily replaceable.  I had 
> another pool that reported as online, but it failed to import with a 
> missing disk error and dmesg had errors about incompatible mediasize.  
> One disk was shown with the blkdev name (daXXpX) in the zfs import 
> output and zdb -l revealed what I thought was a label for an old pool, 
> so I did a zpool labelclear on it; however, it still failed to import 
> with the same error and as expected now reported as degraded.  I then 
> tried FreeNAS 9.3.1 and got the same missing disk error, but nothing 
> interesting in dmesg: http://pastebin.com/w0VBcCfy, 
> http://pastebin.com/NH0uyULV.  No combination of -f, -F, -n, -N, -X, 
> -T or -o readonly=on will import the pool on FreeNAS 9.3.1, FreeNAS 
> 9.10.2, OpenIndiana Hipster or Ubuntu 16.04.1.  On FreeNAS, I had 
> vfs.zfs.recover=1 and vfs.zfs.debug=1.  A memory test passed on the 
> machine and the recreated pool seemed to work OK, but I tried moving 
> the pool's disks to a known good machine running FreeNAS 9.3 and I had 
> the same result.
>
> # zpool import
>    pool: xensr
>      id: 17993649064102742628
>   state: DEGRADED
>  status: The pool was last accessed by another system.
>  action: The pool can be imported despite missing or damaged devices.  
> The
>         fault tolerance of the pool may be compromised if imported.
>    see: http://illumos.org/msg/ZFS-8000-EY
>  config:
>
>         xensr                                           DEGRADED
>           mirror-0                                      DEGRADED
>             gptid/f3ececf5-a319-9266-b870-bc3259f24b68  ONLINE
>             5862692444503195050                         UNAVAIL cannot 
> open
>           mirror-1                                      ONLINE
>             mfisyspd6p1                                 ONLINE
>             gptid/7cbacbcb-30f8-b5cd-a569-c92eea865edd  ONLINE
>           mirror-3                                      ONLINE
>             mfisyspd5p1                                 ONLINE
>             mfisyspd4p1                                 ONLINE
>           mirror-4                                      ONLINE
>             mfisyspd3p1                                 ONLINE
>             mfisyspd1p1                                 ONLINE
>         cache
>           12574043822818177481
>         spares
>           11626098521560667599
>         logs
>           mirror-2                                      ONLINE
>             mfisyspd8p1                                 ONLINE
>             mfisyspd7p1                                 ONLINE
>
> # zpool import -f xensr
> cannot import 'xensr': one or more devices is currently unavailable
>
> Could it be a bug with importing non-exported degraded pools or 
> unreported corruption?  I tried the FreeNAS IRC channel and got some 
> assistance, but no solution.  I cannot get logged into their forums. 
> The OpenZFS advises to use platform specific mailing lists.  I decided 
> to try this mailing list.
>
>
> Thanks,
> Arthur
>
> This e-mail and any attachments may contain CONFIDENTIAL information, 
> including PROTECTED HEALTH INFORMATION. If you are not the intended 
> recipient, any use or disclosure of this information is STRICTLY 
> PROHIBITED; you are requested to delete this e-mail and any 
> attachments, notify the sender immediately, and notify the Mediture 
> Privacy Officer at privacyofficer at mediture.com.
>
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"