Probably corrupted Zpool

[nickalleyne]

Hey everyone,

I have a question, and I think I know the answer, but I figure I should ask anyway.

A couple months ago, my main NAS server died, and due to time / $ constraints, I have been unable to purchase a new one. The plan was to do so in the new year.

As such, I attached the disks to my primary workstation, and began running it as a VM with VMware workstation, and passing through the 3 physical disks. I have been running it with 6GB of ram (latest version of 9.10), and it has been going well, with the exception of Windows rebooting from time to time for updates, which probably is not rebooting it as gracefully as it should.

Upon logging in a couple hours ago, I am getting the following error: freenas kdb enter panic

There is a lot of other stuff associated with it, which I can post if requested (unable to copy and paste, so will need to manually type if needed, just not sure what to enter).

I have tried upgrading to 11 U4 to see if I am able to import it, but no go, same error.

I am fully aware that I am running a very unsupported method, and so I understand if I lose my data (the important stuff I have an offsite backup, which I unfortunately noticed just 2 days ago was not backing up the last 3 months, but that is fine, nothing too important is gone).

Thanks in advance for any help and insight.

Edit: I have also tried upping the ram but no luck there either.

 

[Stux]

Take a screenshot of the error.

 

[nickalleyne]

Thanks, I didn't even think about that. Image is attached.

 

[nickalleyne]

The only thing I get before that (it scrolls past too fast to capture, and I am unable to change the console screen size to capture more for some reason, even though I have set it), is this message below.

 

[Stux]

I’m not sure, but this may just be a corrupt boot device.

Try reinstalling FreeNAS to a new USB and booting off that, then import your pool.

 

[nickalleyne]

I have tried that, well I tried installing a new version (11 U4), and I can boot into the OS, but once I do, and I try to import the pool, the entire OS just reboots (I get a similar error as posted above (actually pretty much exactly the same) before it reboots on its own). If I try to manually import via command line it forces me to use -f, as it says it was open before (sorry dont remember the exact error, as I am not in front of it currently, but that is the outcome).

 

[nickalleyne]

A couple other notes:
1) These are WD red drives (if that matters)
2) I turned scrubs off, as I had read it could cause problems with doing physical disk passthrough within a VM (I cannot find where I read that)
3) I think I know what may have caused to to fail, the fact that I have them mounted as physical disks, but did not set as "independent" for snapshots, so something may have paused the VM, and caused an issue there, as when it came back up I feel like it came out of a paused state (no idea why, that is just what I am remembering)

 

[Stux]

Well, you could try mounting with rollback. You might need to do some searching on that.

 

[nickalleyne]

So it seems there are a few new things:

1) I can access the data when I mount it as readonly, and it seems to mount fine
2) there are no ZFS snapshots (it was only potentially VMware I was thinking of anyway), confirmed when I have it mounted as readonly, I only see the jails snapshots

Bright side is I can access the data, it is just going to take me a while to get it off.