zpool import after failed Auto Import volume not visible in GUI

[Marcel]

I tried to Auto Import Volume on FreeNAS 9.1.1, which failed (no user message, but no volume visible in the GUI as well), a retry gave a database locked error.
Importing the volumes in a shell with 'zpool import <volume>' did import the volumes, but resulted in 'cannot mount '/VOL001': failed to create mountpoint' (because I needed to set the altroot to /mnt probably). Also the volume is not visible in the GUI.
Is it possible to import from the command prompt, so the volume is mounted and FreeNAS (GUI) sees the volume as well (probably needs sqlite3 table updates) or is setting the altroot correctly enough for the volume to be seen by the GUI?
I understand I probably need to provide more information why the Auto Import failed (which is the real problem), but the coming 3 hours my volume is resilvering, so I can try more later and provide logs if needed.

 

[cyberjock]

If your volume is resilvering it is already imported.

Send me a PM with your skype info. I'll see if I can help you.

 

[Marcel]

Thanks for your offer, it was too late when I wrote the message and let the nas do its work.
It seems the problem is with only one volume (raidz2), other volumes did mount without problems with Auto Import. The other volumes I could also import with 'zpool import -R /mnt volume', but that single volume causes the import to hang. So this is probably the reason Auto Import fails.
I could not see any log changes when importing, so I can not see what zpool is doing or why it is hanging. In another shell zpool status did list the volume ONLINE without errors, but 'ls /mnt/VOL001' returns an empty directory, while 'zpool import -R /mnt VOL001' is still running. I have started the import again and will let it 'run' for a few hours.
Is there any command to check the volume or to get the zpool import give some more feedback?

 

[Marcel]

After running for several hours, without any disk activity, I don't think anything is happening, zpool just hangs (btw. I don't use any encryption/dedup on my volumes). The pool lists fine, but mount does not give any mountpoint for VOL001 (and zpool import is still running), so still an empty /mnt/VOL001 directory:

Code:

NAME                                    SIZE  ALLOC  FREE    CAP  DEDUP  HEALTH  ALTROOT
VOL001                                  21.8T  16.4T  5.31T    75%  1.00x  ONLINE  /mnt
  raidz2                                21.8T  16.4T  5.31T        -
    gptid/8f6ec308-a9e2-11e2-821b-0025903b9558      -      -      -        -
    gptid/3e93550f-ccf4-11e0-923d-0025903b9558      -      -      -        -
    gptid/3ec182be-ccf4-11e0-923d-0025903b9558      -      -      -        -
    gptid/80b29514-d8a0-11e0-aec6-0025903b9558      -      -      -        -
    gptid/3f33e86a-ccf4-11e0-923d-0025903b9558      -      -      -        -
    gptid/3f66b371-ccf4-11e0-923d-0025903b9558      -      -      -        -
    gptid/3f97dc43-ccf4-11e0-923d-0025903b9558      -      -      -        -
    gptid/c2a03385-a926-11e2-8540-0025903b9558      -      -      -        -

and zfs list is even showing the plugin jails:

Code:

NAME                                                        USED  AVAIL  REFER  MOUNTPOINT
VOL001                                                      12.3T  3.72T  12.2T  /mnt/VOL001
VOL001/jails                                                2.51G  3.72T  137M  /mnt/VOL001/jails
VOL001/jails/.warden-template-9.1-RELEASE-amd64-pluginjail  506M  3.72T  506M  /mnt/VOL001/jails/.warden-template-9.1-RELEASE-amd64-pluginjail
VOL001/jails/bacula_1                                        610M  3.72T  714M  /mnt/VOL001/jails/bacula_1
VOL001/jails/dlna_1                                          706M  3.72T  810M  /mnt/VOL001/jails/dlna_1
VOL001/jails/sickbeard_1                                    614M  3.72T  711M  /mnt/VOL001/jails/sickbeard_1

Also 'zpool history VOL001' gives a lot of old snapshot create/destroy info, so that part seems to be working, just not the mount part, I see no files.
Is there any device I could access or mount, so I can access my files?
I will try 'zpool import -R /mnt -F -n VOL001' first to see if that helps, else I will try with FreeNAS 8.3.2 later this evening and see if that makes a difference.

 

[Marcel]

import -F -n did not do anything either, so I tried something else I found:
'zpool import -o readonly=on -R /mnt VOL001' did work! Now I can get to my files.
Still no clue why a normal import is not working, but at least I can copy my files (to big for a backup,...I know...).
Perhaps there is a command that can analyse the volume on errors why the volume is not mounting read/write?

 

[warri]

I think there were some other users in the forum, who only could mount their pools as read-only. But I think all of those cases suffered from an unclean shutdown or insufficient hardware. What are your hardware specs? Did this happen after an upgrade from FreeNAs 8.x?

 

[Marcel]

No, for a couple of months I was already running on 9.1.1, since one drive fell out of another volume I had to reboot (nicely) my nas, but then it was hanging, probably on the mounting of this problematic volume. I am using a Supermicro X8DTH-IF-O board with an Areca ARC-1880i controller and plenty of ECC memory (no problems so far). The other volumes I could Auto Import from the GUI without any problems (including the one with the disk problem).
Perhaps I can import (non-readonly (and use -N), which would make the pool visible, but not mounted) and do a scrub to fix any internal zfs structure problems if there are any?