FreeNAS Reboot Loop

rohanrob

Cadet
Joined
Dec 28, 2022
Messages
3
I am having an issue with my FreeNAS rebooting, I have never had an issue with it and am new to FreeNAS, any help would be appreciated. I can provide any more information if something is missing. The last command I ran was to recover my FreeNAS 500G drive

zpool import -F

I have this also, but the 500G is what I need, I have no problem rebuilding if I can recover the following:

1672253483541.png


1672253004556.png


1672253070020.png


1672253035876.png
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,996
Well you only gave your VM 2GB RAM, you are only short 6GB for the absolute minimum requirement. Increase your RAM and see if that helps.

The other problem I see is you are using virtual hard drives. That is just looking for problems. Don't do it unless you are just testing TrueNAS out. I would never trust my data to a vmdk file and I've been virtualizing TrueNAS for about a decade now.
 

rohanrob

Cadet
Joined
Dec 28, 2022
Messages
3
@joeschmuck Ok I appreciate the reply, I was testing it out, and then it worked so well I left it running. If that doesn't work, can I mount the disk and get the data back or recreate a new FreeNAS with recommended RAM and mount that vmdk?
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,996
I would first edit your VM config file to increase the RAM size and then try it, I'm hopeful it works. If that fails then geez, I'm not an ESXi expert so I don't want to give you bad advice. I don't mind causing problems for myself, but not others.
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,996
Let's say increasing the RAM doesn't work. I would next try to reinstall TrueNAS to the VM boot drive. If that fails to resolve the problem then I would delete the VM, leaving the vmdk files in tact and create a new VM and use existing vmdk for the data drive only, create a new boot drive vmdk file. Then install TrueNAS to the boot drive and cross your fingers.

I guess another way to access the data would be to create a VM of FreeBSD or some other OS that also supports ZFS, then mount the drive and access the data. The issue you have is the data is in a vmdk and it's in ZFS format within the vmdk. Makes things complicated.

Again, this is what I'd do. I have no idea if any of this after the first paragraph is smart to do.

Best of luck to you and I hope you didn't have anything important on that setup.
 
Top