SOLVED Lost Volume after upgrade to 11.1, working now on 11.0 u4

[i4m]

ThinkServer TS440
4 CPUs x Intel(R) Xeon(R) CPU E3-1245 v3 @ 3.40GHz
ESXI 6.0 u3, 32GB ram, 4 x 2TB HDD attached to LSI LSI1068E raid card in raid-z1 pool called nas, 1 x 1TB HDD, 1 x 250GB SDD.

i upgraded from 11.0 u3 to 11.1 without issue. a few days later i was unable to access any shared drives and the gui was unresponsive. i reloaded my machine and at bootup it was stuck at importing pool, eventually i got a "slow spa_sync" message. I searched the net and found others, some time ago, with this same issue who left their systems and they restored themselves. I left my system in this state for over a week and the fault remained.

I created a fresh vm, installed 11.0 u4 and moved my raw disks from the broken vm to this new one, although in the gui the new 11.0 u4 vm can see the individual disks it won't see the pool to import as a volume. i then tried the same with 9.3 with the same results

i then moved the raw disks back to the original vm :
i managed to load "FreeNAS-9.3-STABLE-201509022158" and it shows the pool and allows me to import the volume and all my data appears intact.
i then managed to load 11.0 u1 and my pool loaded fine again all data present
i then managed to load 11.0 u3 and my pool loaded fine again all data present
i then managed to load 11.0 u4 and again my pool loaded fine all data present

I'm sticking with 11.0 u4 for the moment.

I started writing this post as a call for help, but have managed to get up and running through the course of gathering info for the post. Im shareing in case it helps someone else.

 

[Ericloewe]

Well, that title is misleading. The pool was never "lost", it just wouldn't import due to a bug in 11.1. It sounds like a trivial distinction, but it does make a difference.

 

[i4m]

Well, that title is misleading. The pool was never "lost", it just wouldn't import due to a bug in 11.1. It sounds like a trivial distinction, but it does make a difference.

yes it is trivial :).

when it happens, it is lost to you, all your data is unavailable. Once you've worked out how to get it back its not lost. Then you work out its a bug in the new OS. :)

When something is gone and you no longer have it its generally described as lost.

Back to the issue i was faced with......

i was unsuccessful importing the volume in a new vm and i'm not sure why, i'll need to understand why in case i have the need to import the volume in a new vm again.

Code:

FreeBSD 11.0-STABLE (FreeNAS.amd64) #0 r321665+25fe8ba8d06(freenas/11.0-stable): Mon Sep 25 06:24:11 UTC 2017


	FreeNAS (c) 2009-2015, The FreeNAS Development Team

	All rights reserved.

	FreeNAS is released under the modified BSD license.


	For more information, documentation, help or support, go here:

	http://freenas.org

Welcome to FreeNAS

[root@freenas] ~# zpool import

   pool: freenas-boot

	id: 16924077627963850640

  state: ONLINE

 status: Some supported features are not enabled on the pool.

 action: The pool can be imported using its name or numeric identifier, though

	some features will not be available without an explicit 'zpool upgrade'.

 config:


	freenas-boot  ONLINE

	  da0p2	 ONLINE


   pool: nas

	id: 3559927002665857005

  state: ONLINE

 action: The pool can be imported using its name or numeric identifier.

 config:


	nas											 ONLINE

	  raidz1-0									  ONLINE

		gptid/2e4ded5e-4737-11e3-a697-009c02abd7cd  ONLINE

		gptid/2ef6184c-4737-11e3-a697-009c02abd7cd  ONLINE

		gptid/d372c18b-4808-11e3-94b2-009c02abd7cd  ONLINE

		gptid/69dc2257-ad23-11e3-93a0-009c02abd7cd  ONLINE

	  gptid/587b7a88-9c12-11e5-8338-000c2902e55b	ONLINE

	cache

	  da6p1

	logs

	  gptid/47ed0870-9c14-11e5-8338-000c2902e55b	ONLINE

Code:

[root@freenas] ~# zpool status Storage -v

cannot open 'Storage': no such pool

cannot open '-v': name must begin with a letter

[root@freenas] ~# zpool status nas -v

cannot open '-v': name must begin with a letter

  pool: nas

 state: ONLINE

  scan: scrub repaired 0 in 228h41m with 0 errors on Tue Jan  9 04:42:04 2018

config:


	NAME											STATE	 READ WRITE CKSUM

	nas											 ONLINE	   0	 0	 0

	  raidz1-0									  ONLINE	   0	 0	 0

		gptid/2e4ded5e-4737-11e3-a697-009c02abd7cd  ONLINE	   0	 0	 0

		gptid/2ef6184c-4737-11e3-a697-009c02abd7cd  ONLINE	   0	 0	 0

		gptid/d372c18b-4808-11e3-94b2-009c02abd7cd  ONLINE	   0	 0	 0

		gptid/69dc2257-ad23-11e3-93a0-009c02abd7cd  ONLINE	   0	 0	 0

	  gptid/587b7a88-9c12-11e5-8338-000c2902e55b	ONLINE	   0	 0	 0

	logs

	  gptid/47ed0870-9c14-11e5-8338-000c2902e55b	ONLINE	   0	 0	 0

	cache

	  da6p1										 ONLINE	   0	 0	 0


errors: No known data errors

anyone able to offer an insight as to why i was unable to import the volume in a new instance even though the raw disks where online to the freenas OS?

Thanks

 

[Ericloewe]

I see a pool "nas" that is already imported. If it doesn't show up in the GUI, it's because you went around its back and imported it in the CLI.

 

[i4m]

thats interesting,
when i create a new disk in the vm, install freenas on it, change the bios disk order and boot it, i see the pool available for import.

but i don't when i do the same from a new vm instance.

 

[Ericloewe]

Export it from the CLI. Then you can import it from the GUI.

 

[i4m]

Thanks Eric,

can you advise on the procedure for CLI export?

 

[Ericloewe]

You managed to zpool import it just fine, so zpool export poolname

 

[i4m]

Thanks Eric,

the pool import however i did it was many years ago, prob 2013 when i was doing global support on a redhat based product and i was more familiar with required syntax for zfs on freebasd. i've been back on networks for a few years now and a lot of the commands needed for specific procedures are out of my head, hence the ask. But thanks.