SOLVED FreeNAS 9.10 Kernel Panics Upon Import.

[Janky Jay]

Hello All,

I was recently (today) wondering why my FreeNAS system wasn't responding so I headed to my server room only to find this on the monitor:

So, it appears my FreeNAS system rebooted for some reason and was unable to import my pool upon reboot. I tried rebooting again and again the system panic'd. So, I grabbed the latest version of 9.10, installed it to a USB and booted that up. I can see the pool, but again, if I attempt to import it, FreeNAS spits out thousands of lines of kernel panic (too fast to read or capture... I suppose I could make a video?) and then simply reboots.

A 'zpool import' shows (the "storage" pool is the culprit):

Code:

~# zpool import
   pool: storage
	 id: 4000399371077928498
  state: ONLINE
 status: The pool was last accessed by another system.
 action: The pool can be imported using its name or numeric identifier and
		the '-f' flag.
   see: http://illumos.org/msg/ZFS-8000-EY
 config:

		storage										 ONLINE
		  raidz2-0									  ONLINE
			gptid/0421878c-600a-11e5-8e85-0030485f14b4  ONLINE
			gptid/ea728b06-aa59-11e3-b1e2-bc5ff4acb030  ONLINE
			gptid/29d0e497-b1f4-11e3-bbc5-bc5ff4acb030  ONLINE
			gptid/c30caf31-1464-11e4-9160-bc5ff4acb030  ONLINE
			da9										 ONLINE
			gptid/3a8f47ac-f0de-11e2-975a-bc5ff4acb030  ONLINE
			gptid/3b8ec9db-f0de-11e2-975a-bc5ff4acb030  ONLINE
			gptid/3c8eec94-f0de-11e2-975a-bc5ff4acb030  ONLINE
			gptid/172f94c3-1a13-11e4-ae57-bc5ff4acb030  ONLINE
			da12										ONLINE
			gptid/8181e362-24da-11e3-9b63-bc5ff4acb030  ONLINE
			gptid/406ee583-f0de-11e2-975a-bc5ff4acb030  ONLINE

   pool: freenas-boot
	 id: 12100669110508998217
  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
		  mirror-0  ONLINE
			da0p2   ONLINE
			da1p2   ONLINE

And viewing the 'smartctl' output for all the disks suggests none of them are in a failed state (from what I can tell, anyhow). If anyone would like all that output, I'll be glad to supply it.

Has anyone seen this type of behavior before? Any ideas as to how I can fix this? I'm absolutely stumped and would be devastated to lose this data. I have had plans to build a backup server for this data but I don't have the hardware yet... :( Any and all help would/will be greatly appreciated.

-Janky Jay, III

 

[m0nkey_]

Janky Jay joined us in the chatroom, managed to get his pool mounted read-only so he can at least attempt to recover his data.

If anyone is wondering, this command did the trick:

zpool import -o readonly=on -R /mnt [tank]

 

[Janky Jay]

Janky Jay joined us in the chatroom, managed to get his pool mounted read-only so he can at least attempt to recover his data.

If anyone is wondering, this command did the trick:

zpool import -o readonly=on -R /mnt [tank]

I actually had to use:
zpool import -o readonly=on -f -R /mnt [tank] (Had to "-f" force it), but this certainly helped. I have read-only access to my pool and am able to back it up to another location. Thanks, m0nkey_!