PyCoder

I just read this on the news and just my 2 cents... I bought years ago the pro key, which I don't use anymore, so I don't really care but... I get it if you had a professional branch and a community like TrueNAS, but Unraid is mostly used by home users, so a annually subscription will probably only push people towards TrueNAS Scale, OMV. There is no real advantage anymore over TrueNAS Scale, especially with raidz@expansion and a professional branch with professional support doesn't exist sooooo....

Changed Priority to Annoyance

I changed the mountpoint to /mnt/deadpool and change all the settings from /deadpool to /mnt/deadpool. How do I downgrade to 6.9? I can only see a rollback to 6.10.2. Ty btw.

Yeah, I just saw it, see the edit. But it's nonsense when everything works outside /mnt (e.g. Docker) but VM isn't working anymore since 6.10. Ty. Anyway, I guess it's time to switch the system. Example: Working in Docker and anywhere else.

I can't download the virt-win ISO anymore because the path doesn't exist according to the UI and as shown in the console output the path exists and has the right permission. Check the screenshot (4. Storage path invalid). I had non of these issues before 6.10. EDIT: Ok, apparently since 6.10 the user is FORCED to use a folder in /mnt?! When I bind (mount -o bind) the folder /deadpool/VM to /mnt/user/VM its working. That's just nonsense.

Yeah reboot works but as soon as I stop and start VM manually I have the same issue and I can reboot again. So that's not a solution. It worked before 6.10.x Also all the paths are broken and offset and they worked before 6.10.x

Done

Same issue!

Yeah but there was also an issue with docker.img on ZFS with update 2.0 or 2.1 thats why I changed it to directory which worked now for weeks till 2 days ago. Hmmm, I'll switch back to docker.iso if that doesn't work I'll try zvol with ext4. lets try Edit: docker.iso on zfs blocked /dev/loop and docker in zfs directory f* ups contrainers. My solution with only ZFS: zfs create -V 30gb pool/docker mkfs.ext4 /dev/zvol/pool/docker echo "mount /dev/zvol/pool/docker /mnt/foobar" >> /boot/config/go Working like a charm

Hi Did you guys make a new update? Cause the last time im moved my docker form the btrfs image to a ZFS directory and now out of the blue i cant update or remove or start docker containers anymore?! I even deleted the directory (zfs destroy -r) and reinstalled all dockers.. after 1 day i had the exact same issue again. Has someone a solution?

Oh ty. Im running 6.9.2. But i'll switch to directory mode. Cheers Edit: i just figured that i clicked ont he wrong button when i wanted to replay 😂 sorry

Hi Is it possible that you guys introduced some nasty bugs with that update? My system is not reacting anymore and everytime when i force it to reboot loop2 starts to hang with 100% cpu usage and docker.img is on my ZFS pool. Started after i updated zfs for unraid to 2.0.0.

I mean I can put the drives to sleep by myself but why are they waking up? There is 0 read / write to the drives and on TrueNAS i dont have to export them to make them sleep. So it must be some unraid stuff that is going on? I made a script now that exports the drives and puts them to sleep.

Hi Is it possible to integrate dm-integrity for bit-rot detection? It would be an additional layer below the XFS and we would have bit-rot detection. See: https://www.kernel.org/doc/html/latest/admin-guide/device-mapper/dm-integrity.html I know btrfs has checksums but XFS is still the default and btrfs is "stable" but still not finished. Cheers!