Hi.

I've been updating my harddrives on my Unraid-server (moved Boot from an zfs-array of two SSD's to a single nvme-ssd). I have been messing around with the appdata location. Dockers work (after re-creating the Docker setup) but now I want to install VM's. I've removed the old libvrt iso-image and downloaded a new one, but the service won't start. Included are the diagnostiscs.

Before I re-install the whole server (a feasible option since it isn't in production yet) I'd like to understand what is wrong.

citadelle-diagnostics-20261008-0715.zip

The diagnostics show why the VM service won't start. Each time you enable it, Unraid tries to create the libvirt folder and fails:

mkdir: cannot create directory '/mnt/user/system': No space left on device

The system share no longer exists on any device, and Unraid can't create it with its current settings. It's set to Primary storage: cache and Secondary storage: Array, but your server has no array disks, only pools. Its Minimum free space is also set to about 94 GB, which is very high for a 128 GB pool.

To fix it:

1. Go to Settings → VM Manager and make sure the service is disabled.

2. Go to Shares → system. Set Primary storage to the pool you want (cache is a good choice for the libvirt image), set Secondary storage to None, and lower Minimum free space to something sensible, like a few GB. Click Apply.

3. Back in VM Manager, correct the libvirt storage location. It currently says /mnt/user/system/libvrt/libvirt.img (missing an "i"); /mnt/user/system/libvirt/libvirt.img is the default. Then enable the service.

While you're at it, some other share settings don't match where the data is:

- domains is set to cache only, but its folder is on raptor. New vdisks would go to the 128 GB SSD pool. Choose which pool you want for vdisks and set the share to it.

- appdata is set to cache with raptor as secondary, but all the data is on raptor.

- In Docker settings, the default appdata path is /mnt/cache/. You may want /mnt/user/appdata/ instead.

No reinstall is needed. If the service still fails after these changes, post new diagnostics.

Thanks a lot Jorge! Have a beer on me! :-)

All this will remind me I have to document the changes I make... For an old hand like me that should be obvious, but hey... I'm human. 😁

Anyway, everything now seems to work. Now for some fine-tuning.