zpool import?

[PerryM]

In the process of trying to update to 9.10.2 and having similar problems to many others, I've managed to lose my configuration. I have created a new boot on a USB stick and this runs fine but it is not re-creating my volumes. If I go to shell, and type 'zfs list' I get the full volume info that I would hope for, but many of them have a mountpoint marked 'legacy'. The freenas-boot entry says 'none'.
I have undoubtably done everything wrong but any help in rescuing my situation would be much appreciated. I am rather ancient and will struggle with any shell requirements beyond simple copying!
I have a keyboard and monitor on the FreeNAS system, and also access to the Web GUI
System:
5x 3TB drives, 16GB memory, USB stick boot drive
Merry Xmas!

 

[PerryM]

I tried zpool import -f MitchNAS (MitchNAS = my zpool name) but it fails because the 'freenas=boot' : pool already exists

Would it help if I reinstalled the last version of 9.10.1 that I had before the update?
To be more specific with my mistakes - I updated my USB sticks with the 9.10.2 version on a different computer, it worked fine but the Web GUI strongly advised to 'Recover' and so I re-installed it on my NAS machine (from the ISO) using the first option, and that is when I lost the configuration.

 

[Ericloewe]

it worked fine but the Web GUI strongly advised to 'Recover'

What? What error message did you get, exactly?

 

[PerryM]

Hi Eric
I'm old and befuddled and my memory is pretty bad, but here goes:
After I had loaded 9.10.3 on my two USB sticks on the other computer, and successfully rebooted the FreeNAS machine - I looked at ensuring they were both recognised in the 'boot' page on the Web GUI. There was only one shown, so I clicked 'Attach' to add the second. It then said there was something wrong with the boot files on the first USB stick and switched to the second with a warning to recover ASAP. I managed to get the optical drive working in the FreeNAS m/c so then used the ISO disk to perform an 'Install/Update' (the first option) which it appeared to successfully do (I did it twice for the two drives). Upon reboot I had lost my configuration and all my volumes.
As described by several other users, this came about because the auto-update to 9.10.2 via the Web Gui left me with a system that had a loop in the boot routine and thus the need to reload my sticks.
I'm just off to my relations for Xmas lunch!
Feliz Natal

 

[Ericloewe]

The easy solution is to backup your config file (it should be already, but it never hurts to tell people to keep it backed up) and then reinstall from scratch. I'd probably try new boot devices, it typically isn't worth the effort to mess around with them until they work.

 

[PerryM]

Humour me Eric - I've got a completely blank configuration so why would I need to back it up? I have to confess that I haven't been backing up the files before and looking in the computer I normally use to access the web GUI I cannot see any likely candidates - just the one from the last boot.
If I cannot get back to where I was automatically - can I rebuild the volume info manually? If I load the previous volume structure by hand will it pick up the existing data in the zfs pool?
I am currently pretty much stupified by the fear of wiping out the volume data!
If you read my previous posts you will see that I already reinstalled from scratch.

 

[Ericloewe]

Humour me Eric - I've got a completely blank configuration so why would I need to back it up?

You wouldn't. It's just hard to keep all the details from all the threads neatly archived in my head. :p

If I cannot get back to where I was automatically - can I rebuild the volume info manually? If I load the previous volume structure by hand will it pick up the existing data in the zfs pool?

The data should be exactly as you left it, but that's really the bare minimum that any storage system is supposed to do (not sure why people occasionally feel that their data might be lost if they lose their configuration). You'll just have to reconfigure shares and maintenance tasks (scrubs, SMART, snapshots, replication, ...).

 

[PerryM]

So taking it one step at a time - how do I access the data via FreeNAS? The mount points are shown in zpool but it won't allow me to import them.

 

[joeschmuck]

What is the output (in code tags please) of "zpool list" and "zpool status".

 

[joeschmuck]

Here is an example of what I'm looking for:

Code:

[root@freenas] ~# zpool list
NAME           SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
farm          10.9T  6.65T  4.23T         -    17%    61%  1.00x  ONLINE  /mnt
freenas-boot  9.94G  2.78G  7.16G         -      -    27%  1.00x  ONLINE  -
[root@freenas] ~# zpool status
  pool: farm
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
        still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0 in 5h6m with 0 errors on Sun Dec 18 05:06:15 2016
config:

        NAME                                            STATE     READ WRITE CKSUM
        farm                                            ONLINE       0     0     0
          raidz2-0                                      ONLINE       0     0     0
            gptid/4b487003-0eb5-11e4-bd5d-6805ca0d397f  ONLINE       0     0     0
            gptid/4ba9997f-0eb5-11e4-bd5d-6805ca0d397f  ONLINE       0     0     0
            gptid/4c1547f5-0eb5-11e4-bd5d-6805ca0d397f  ONLINE       0     0     0
            gptid/4c7f3ea7-0eb5-11e4-bd5d-6805ca0d397f  ONLINE       0     0     0
            gptid/4ce23911-0eb5-11e4-bd5d-6805ca0d397f  ONLINE       0     0     0
            gptid/4d451b51-0eb5-11e4-bd5d-6805ca0d397f  ONLINE       0     0     0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: scrub repaired 0 in 0h0m with 0 errors on Sat Dec  3 03:45:08 2016
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          da0p2     ONLINE       0     0     0

errors: No known data errors
[root@freenas] ~#

 

[PerryM]

Like this?

Code:

[root@freenas ~]# zpool list																										
NAME		   SIZE  ALLOC   FREE  EXPANDSZ   FRAG	CAP  DEDUP  HEALTH  ALTROOT												
MitchNAS	  13.6T  6.06T  7.56T		 -	13%	44%  1.00x  ONLINE  -														
freenas-boot  7.31G   646M  6.68G		 -	  -	 8%  1.00x  ONLINE  -														
[root@freenas ~]# zpool status																									
  pool: MitchNAS																													
state: ONLINE																													
  scan: scrub repaired 0 in 5h8m with 0 errors on Sat Nov 12 21:08:43 2016														
config:																															
																																	
		NAME											STATE	 READ WRITE CKSUM												
		MitchNAS										ONLINE	   0	 0	 0												
		  raidz1-0									  ONLINE	   0	 0	 0												
			gptid/e95ded3b-6d3f-11e6-9c8a-bc5ff4805725  ONLINE	   0	 0	 0												
			gptid/ed7c0648-6d3f-11e6-9c8a-bc5ff4805725  ONLINE	   0	 0	 0												
			gptid/ee10d702-6d3f-11e6-9c8a-bc5ff4805725  ONLINE	   0	 0	 0												
			gptid/f2123c15-6d3f-11e6-9c8a-bc5ff4805725  ONLINE	   0	 0	 0												
			gptid/f63377e6-6d3f-11e6-9c8a-bc5ff4805725  ONLINE	   0	 0	 0												
																																	
errors: No known data errors																										
																																	
  pool: freenas-boot																												
state: ONLINE																													
  scan: none requested																											
config:																															
																																	
		NAME		STATE	 READ WRITE CKSUM																					
		freenas-boot  ONLINE	   0	 0	 0																					
		  da1p2	 ONLINE	   0	 0	 0																					
																																	
errors: No known data errors																										
[root@freenas ~]#

EDIT By JoeSchmuck to place in code tags

 

[joeschmuck]

You didn't put the data in code tags. I'll see if I can do that for you.

 

[joeschmuck]

So lets take this slowly and remember that I treat everyone like they know nothing so don't feel insulted if I ask you stupid questions. It just keeps us on a level playing field.

1) The data you provided, were you booted into FreeNAS 9.10.2 or a previous version? If a previous version, please specify.
2) When you are in the GUI and go to Storage -> Import Volume -> (try both No and Yes options for completeness) -> Do you see anything listed like "MitchNAS" ?
3) If you were running an older version of FreeNAS, can you import your pool back into this and does it work?
4) Do you have a copy of your original configuration file before you tried to upgrade?

I have to run for now, please post your results.

 

[PerryM]

Joe - I'm an engineer of about 50 years experience - I've always said there is no such thing as a stupid question! I really appreciate you taking this approach - I get very weary of the too common opposite!
I will get one beef off my chest - I cut and pasted the data from the Web GUI shell window. It pasted fine (retained format) into the Windows Notebook, and also into my Email client, but if I paste it into this forum's reply window then you see what I get.
Anyways - to your questions:
1) The shell data comes from FreeNAS 9.10.2.
2) The only volume I am offered in 9.10.2 is freenas-boot [zfs, id=14762726328409160336] - if I accept this it says it is not available.
3) The last time I saw my volumes in FreeNAS was when I was in 9.10.1 (probably the last stable ver). As I previously asked - would it help if I rebooted back into the older version? I would have to reload it onto my USB stick from an ISO
4) No I don't have a copy of the configuration file

I was at work today but I am now off until next Tuesday (which is my 72nd birthday!)
cheers

 

[joeschmuck]

72nd Birthday, congratulations! I'm only 55 so I have a few years to catch up to you. And I can relate to the engineer mindset, we are a very technical breed.

Question time:
1) When you installed 9.10.2, was this an "upgrade" or was it a "clean install"?

If this was an upgrade then I'd create a configuration backup with the hopes that it may have some relevant data remaining but I'm not very hopeful. If this was a clean install then don't bother making a configuration backup.

Action time:
1) With the system powered off, disconnect your hard drives at either the SATA or power connectors. We don't want the drives being seen yet. I only do this as a precaution.

2) Perform a clean install, not upgrade, to the USB flash drive, ver 9.10.1-U4 (or whatever verion last worked). I would only use a single flash drive, not a mirror of two. I can explain why later but mirrored flash drives is something I don't agree with. Some extra things I like to do is if the USB Flash drive was previously used and could be considered suspect, I like to wipe the USB flash drive using my favorite tool (SDFormatter V4.0) and ensure the device is the proper size when done. There are many other tools that can also do the work like MiniTool Partition Wizard. Thsi step is not always needed but when troubleshooting FreeNAS with a USB Flash boot drive, well what can I say.

3) Boot up to FreeNAS 9.10.1 and all should be good. If it works then shutdown, plug in your drives and power back on.

4) Now cross your fingers and see if you can import your volume.

If you are able to restore your pool and data then I'd recommend you backup all your important data to DVD media or similar. I would then reconfigure your system settings and once all that is done, create a backup of your configuration file. Lastly I'd wait to see what is going on with 9.10.2. If another update comes out (I suspect it will), then wait 1 month to see what the fallout is.

If you are good using 9.10.1-xx then I'd just stick with it. Also one last bit of advice... When you do upgrade, if you get an alert stating to update/upgrade your pool, just disable the alarm and ignore it. Once you upgrade the pool features set then you cannot go backwards to an earlier version. The feature sets have never been important to the general home users in many years.

I hope this helps and feel free to ask any questions of me. I'm not the most knowledgeable person here but if I can't answer it, someone will jump in and offer up their two cents.

 

[PerryM]

Joe - brilliant - I did just as you said and this time it allowed me to import my pool. It all appears intact - I just need to reconfigure the system as it was.
During the installation (9.10.1U4), there was a long delay whilst it was apparently generating random numbers - it had long runs of full stops and occasional plus signs on the screen. What was that all about?

Do you know anything about v10? What would you advise when it comes out of beta?

Thanks very much for your advice - it is a brilliant early birthday present!
I promise this time to take regular configuration saves.

 

[joeschmuck]

During the installation (9.10.1U4), there was a long delay whilst it was apparently generating random numbers - it had long runs of full stops and occasional plus signs on the screen. What was that all about?

I honestly don't recall what all that is about but it's normal. I want to say it's generating an encryption key but I forget.

Do you know anything about v10? What would you advise when it comes out of beta?

I advice that if you want to play with it in a VM then play, but do not commit it to your main FreeNAS system. I'd give it at least 2 months unless you really want to be a tester. I have two FreeNAS systems, the second one is for playing so once FreeNAS 10 comes out, I'll wait a week and then probably upgrade that second system. If all works fine then I'll upgrade my main system.

As I said earlier, if you do upgrade, just don't upgrade your pool and you will be able to go back to the previous version.

I'm glad you were able to get your pool back. I have no idea why it refused to import into 9.10.2, that doesn't make sense to me. Once you have everything reconfigured and the configuration file saved, you could grab a different USB Flash drive and try a clean install on it of 9.10.2. Once it's booted up, then restore your configuration file. It "should" work, but if 9.10.1-U4 is working for you then I'd just hold out until 9.10 (+ 2 months) comes out. Keep your data safe.

Also for your situation, I'd turn off the automatic updates in the GUI. No need to be tempted by a daily email.