SOLVED Zpools online, kernel panics when I try to zpool import

[Mehul V]

I was able to get the pool imported following the post HERE by @jpaetzel
It seems after setting the follow flags, I was able to stop kernel panic and actually try to recover the pool

Code:

set vfs.zfs.recover=1
set vfs.zfs.debug=1
boot -s

Then when I tried zpool import media, I got an error saying Recovery is possible, but I will lose 4 secs of my data (attached screenshot)

Then I tried zpool import -F media but it said pool was last used by a different system and that I should use -f if I want to force mount it.
So then I tried zpool import -Ff media. A bunch of things happened on screen and then I was able to see the pool when I ran zpool status.

So far, everything looks ok so I will try to recover the data and see what happens. I hope this helps others in the future. I will go over the FreeNAS 11 manual in more detail and try to make sure I am using best practices to reduce any more problems down the road.

 

[Jailer]

Make sure you run a scrub as indicated in that warning message.

 

[Mehul V]

Make sure you run a scrub as indicated in that warning message.

I already started FTPing files over. Is it safe to run scrub while server is already under heavy IOPS load?

 

[Jailer]

Should be safe but I'd wait until a scrub is complete so you're not copying corrupt data and saving it.

 

[Mehul V]

Should be safe but I'd wait until a scrub is complete so you're not copying corrupt data and saving it.

Is it really going to take 17 days for scrub to finish? :(

Code:

root@freenas:~ # zpool status
  pool: freenas-boot
 state: ONLINE
  scan: none requested
config:

		NAME		STATE	 READ WRITE CKSUM
		freenas-boot  ONLINE	   0	 0	 0
		  mirror-0  ONLINE	   0	 0	 0
			ada0p2  ONLINE	   0	 0	 0
			ada1p2  ONLINE	   0	 0	 0

errors: No known data errors

  pool: media
 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 in progress since Sat May 12 17:31:10 2018
		3.39T scanned at 2.96G/s, 27.8G issued at 24.3M/s, 34.4T total
		0 repaired, 0.08% done, 17 days 03:09:53 to go
config:

		NAME											STATE	 READ WRITE CKSUM
		media										   ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/3818dd94-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0
			gptid/38c52673-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0
			gptid/39b5e96b-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0
			gptid/3ab33b53-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0
			gptid/3bc7d6bf-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0
			gptid/3cbb075c-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0
			gptid/3da9375a-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0
			gptid/3ec0a49c-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0
			gptid/3fb2c842-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0
			gptid/40b3650d-231b-11e7-a716-008cfa183b7c  ONLINE	   0	 0	 0

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

 

[danb35]

Is it really going to take 17 days for scrub to finish? :(

Shouldn't--it should speed up as it proceeds.

 

[Ericloewe]

I was able to get the pool imported following the post HERE by @jpaetzel
It seems after setting the follow flags, I was able to stop kernel panic and actually try to recover the pool

Code:

set vfs.zfs.recover=1
set vfs.zfs.debug=1
boot -s

Then when I tried zpool import media, I got an error saying Recovery is possible, but I will lose 4 secs of my data (attached screenshot)

Then I tried zpool import -F media but it said pool was last used by a different system and that I should use -f if I want to force mount it.
So then I tried zpool import -Ff media. A bunch of things happened on screen and then I was able to see the pool when I ran zpool status.

So far, everything looks ok so I will try to recover the data and see what happens. I hope this helps others in the future. I will go over the FreeNAS 11 manual in more detail and try to make sure I am using best practices to reduce any more problems down the road.

If you need those flags, I'd say the pool is toast. Cancel the scrub, get your data off (and don't try to zfs send it and rebuild the pool.

 

[Ericloewe]

Of course, assuming that it won't import normally after this. If it does, then scrub it and work from there.

 

[Mehul V]

Of course, assuming that it won't import normally after this. If it does, then scrub it and work from there.

Thank you for the heads up. I'm too afraid to reboot it. I am currently coping pictures and important documents over. After that, all that is left is Music, Movies and TV shows. I will let it scrub but I don't really plan on keeping this pool alive. Once I have all my data via FTP/SSH, I am going to destroy the pool and re-build it from scratch

 

[Mehul V]

To be clear, you haven’t given ZFS full access to the drives. .

Now that I have some time to research, how do I know if ZFS has full access to the drives?

 

[Jailer]

One way is to check SMART status on a drive.