Kilrah

qcow2 is the extension used for qcow2 images, so that is your image file, should be easy to see with the size.

You're giving that path to the app so that's within the container, your script is running on the host OS and doesn't have access to that. You'd have to add a path map to a folder, and configure both sides with their respective paths.

OK, SSDs in array isn't recommeded so wouldn't have expected that.

Parity is not computationally intensive, it's all 100% limited by drive speed (unless you have controller bottlenecks too). The 8TB drives are just both much faster than the 4TB ones and only half their way in on the actual platters while the 4TBs were at the inner end where they're slowest. It'll gradually slow down again now, but yeah you get a "jump" after the end of a disk.

Parity build will continue as normal writing the correct parity to the whole disk, i.e. zeros. Check does the same, it checks they are zeros. That is so that whenever you add a new drive that's larger and now uses that parity space it's already prepared for it.

boot-repair-disk is a good tool for that., make a VM for it, select it as iso, manually specify the vdisk and point to the one of your ubuntu VM. But growing can be done within the running system so you can just open gparted in that and grow your partition.

Usually that's a sign your vpn provider has rotated credentials and you need to grab new config files.

More details about the situation would help. Issues seem to be with disk0 and disk1, not parity. Detail the hardware setup.

The plugin should really parse the output of patch and output messages a normal user can understand based on the various possible results instead of just dumping the raw output.

That will be it.

Optical drives aren't supported AFAIK

The appdata folder is for the zim files, there's nothing else it needs to store persistently.

That's what serves the unraid web ui. Because this is a separate purpose-built container to make reverse proxying easy, yeah it also uses nginx but that's almost irrelevant. Almost every service you'll run will run its own separate copy of nginx or other web server.

Usually it's because they haven't been properly unmounted last time they were used, connect to a Windows machine, check disk, eject properly

Contents are balanced according to share settings as long as you copy to /mnt/user/[share] or /mnt/user0/[share] (no cache). Nope. Has to be the supported ones for array/pools i.e. xfs, btrfs or zfs.

Only if they're in the right format and with troubles, just use the unassigned devices plugin to mount them and any of the many ways to copy data.

That's not the error, what follows is. typically means the folder was empty The Docker image shouldn't be backed up. It being included from the system share doesn't match with your lists.

Try turning it off, if it doesn't stop you can open htop in terminal and find / try to kill it... but that may not work anyway.

You have Docker set to folder mode, not image. On ZFS drives that's known to be unreliable unless you set the backing FS to overlay, which isn't the case. https://docs.unraid.net/unraid-os/release-notes/7.0.0/#add-support-for-overlay2-storage-driver

LT's always been pretty keen about minimizing RAM use, probably a bit too much given current hardware, everything used to be in RAM but /usr and /lib were moved out in 6.12. But there are still people running it on 4-8GB systems where 1GB extra for the OS makes a significant difference... probably difficult to decide which group to favor by default.

Array started and everything available.

If you want only one copy it'll have to be in the appdata backup's folder. There is no option to have it only in another folder. An extra backup copy never hurts and neither do a few hundred megs, so why bother.

That's normal, at some point the GPU gets detached from unraid as it was bound to vfio so the display just freezes in its last state. Depends what hardware you have/if your CPU has a built-in GPU. If so BIOS needs to be set to keep the iGPU enabled and to have it as primary.

The user in the standard NC container is 33. You probably added the user=99:100 to get the correct permissions, that'll work, if you don't want that error remove it and chown the data/appdata to 33:33. I don't know anything about fpm, sorry.

Same as before, where the relevant shares are set to reside.