Hello, I’ve been having a bit of a problem with containers recently.
I didn’t start out with a container initially, but on some update one of my VMs got converter (?) to a container. Since things continued to work fine I didn’t question it.
One day I had to reboot the computer running TrueNAS, after the reboot however the container wouldn’t turn on anymore, saying the NIC was busy. I was on version 25.04.2.3 at the time, I thought I perform an update in the hope it would fix it. Updated to 25.04.2.6 but that didn’t help.
I thought to myself “Okay, I’ll just delete that container and recreate it, since the volume shouldn’t be affected by it, like with a VM, right?”, and I went ahead and deleted the container.
I was able to recreate a generic container with the same NIC, that booted and worked, however I can’t find a way to recreate a container that would access that very specific volume.
One thing I’ve noticed is that the dates are completely broken in the Volumes window, all showing “0001-01-01 00:53:28” with the size “unknown”. Could that be a culprit?
I tried digging around using sudo mc in the shell, went through my datasets but couldn’t find anything. Information about this online seems really inconsistent which isn’t helpful.
Could anyone help nudge me in the right direction to get this fixed somehow?
I think you’ve missundestood something.
If one of your vm’s got migrated to incus, it did not automatically become a lxc container. It was a vm managed by incus.
Incus was supposed to replace libvirt as vm management backend and also add lxc container.
If you converted your vm to incus, it’s still a vm, not an lxc.
Since then the change was reverted and vms are managed by libvirt again and lxc’s will be managed by libvirt starting with 26.04.
If you tried to add a vm zvol to an lxc this may be your issue.
That is roughly how I understood it, however when I try to recreate a vm it won’t let me pick the volume I actually want to reconfigure under the “Select Existing Zvol” option.
while over in the containers tab I get shown this list of volumes, of which I would want to choose homeassistant for the vm, but that one won’t show up in the vm setup configurator.
Name
Size
Created At
Used By
Win11_24H2_English_x64.iso
Unknown
0001-01-01 00:53:28
N/A
homeassistant
Unknown
0001-01-01 00:53:28
N/A
virtio-win-0.1.271.iso
Unknown
0001-01-01 00:53:28
N/A
I am not fully aware of what is going on in the background, but I have to admit I am rather confused about all this, moreso that I can’t find the supposed files for those volumes anywhere in the datasets. It’s weird and slightly worrying that I somehow did end up deleting something, but I really don’t know how that could’ve happened (unless deleting a container did actually delete the contents of the volume??)
That’s propably because you chose to migrate your existing zvol into the incus backend, instead of cloning it. You have to get that zvol back out of the incus subsystem and make it available to the libvirt backend again.
Edit:
The files are in a hidden dataset called .ix-virt
Or do I have to unmount/remount it to a path I want it to be at? I’m being a bit careful with the terminal here before I accidentally unmount something system critical.
This seems really confusing and stressful, especially after things were working before.
Hopefully someone familiar with TrueNAS containers can point you in the direction of what’s going wrong with the volumes.
I have tried a couple other things out, mostly just repeating what I had tried already since I’m really out of ideas. I could just redo the whole thing but that’s going to be such a huge hassle, while doable I’d also wish to avoid having to do that because of something that felt out of my control.
If there is no other option though, then I’ll have to stick with it and start from scratch.
