TrueNas stecked in boot loop

[tJonathan]

Hello, I have a small TrueNas server virtualized on proxmox. TrueNas has at some point gefreezd, so I stopped the VM. But now TrueNas is stuck in a boot loop.
I think there is a problem with the pool, because when I unmount the HDDs TrueNas boots without any problems. I can also press Control C and the system boots, but in the Task tab I see that it tries to import the pool but gets stuck at 80. I also can't access the data, even though I see the pool listed decrypted in storage.

I also tried to roll in a backup, but it doesn't help either. Online I have also found nothing to the problem.

According to Proxmox, the VM always does nothing for a while, and then writes something to the hard drive.

Maybe someone can help me here, I would be very grateful!

Translated with www.DeepL.com/Translator (free version)

 

[tJonathan]

Here are some of the outputs i get from the Console.

 

[jgreco]

Welcome to the forums.

Sorry to hear you're having trouble. Please take a few moments to review the Forum Rules, conveniently linked at the top of every page in red, and pay particular attention to the section on how to formulate a useful problem report, especially including a detailed description of your virtual hardware, your hypervisor's physical hardware, HBA, and specific hard drives being used.

I also suggest reviewing the virtualization guides, and ask that you outline any deviations between your setup and known good setups.

"Absolutely must virtualize FreeNAS!" ... a guide to not completely losing your data.

[---- 2018/02/27: This is still as relevant as ever. As PCIe-Passthru has matured, fewer problems are reported. I've updated some specific things known to be problematic ----] [---- 2014/12/24: Note, there is another post discussing how to deploy a small FreeNAS VM instance for basic file...

www.truenas.com

 

[tJonathan]

Thanks for the tip. So the CPU is an 8 core kvm64 processor. As I said the whole thing is running on a proxmox system, with an Intel i5-11400 on a Z590 motherboard. The VM has 16GB RAM. I have three HDDs, all WD-RED Plus with 4TB in a RaidZ1 config, directly forwarded to the VM via sata.
The whole thing also ran two years absolutely stable until recently.

 

[tJonathan]

Code:

root@pTrueNAS[~]# zpool status
  pool: boot-pool
 state: ONLINE
status: Some supported and requested 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 repaired 0B in 00:00:21 with 0 errors on Tue Nov 15 03:45:21 2022
config:

        NAME        STATE     READ WRITE CKSUM
        boot-pool   ONLINE       0     0     0
          ada0p2    ONLINE       0     0     0

errors: No known data errors

  pool: data
 state: ONLINE
status: Some supported and requested 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 repaired 0B in 13:47:59 with 0 errors on Tue Nov 29 13:47:59 2022
config:
          raidz1-0                                      ONLINE       0     0 0
            gptid/29df45a3-0a98-11ed-999e-6d489391aa3c  ONLINE       0     0 0
            gptid/29eae0de-0a98-11ed-999e-6d489391aa3c  ONLINE       0     0 0
            gptid/29fbc57f-0a98-11ed-999e-6d489391aa3c  ONLINE       0     0 0

This output i get form running zpool status. Maybe it helps ....

 

[tJonathan]

So good news is that I can at least access the pool via the shell and read and write data.

 

[jgreco]

directly forwarded to the VM via sata.

What does this mean?

 

[tJonathan]

That the HDD ist direcly link to the VM, like in:

Passthrough Physical Disk to Virtual Machine (VM) - Proxmox VE

pve.proxmox.com

 

[jgreco]

That the HDD ist direcly link to the VM, like in:

Passthrough Physical Disk to Virtual Machine (VM) - Proxmox VE

pve.proxmox.com

That's probably not acceptable and it's certainly dangerous and ill-advised. I would imagine that this is being handled as some sort of virtual disk abstraction, which is basically going to have problems similar to RDM under ESXi. Pass through the entire PCIe controller using PCIe passthru as outlined in the virtualization guide I previously provided. Any opportunity that exists for I/O restructuring or reordering by the hypervisor platform presents significant risks for ZFS.