Kilrah

You should read, and ask in the support thread for the container you're planning to use. Unraid doesn't have anything to do about it, it's what the container supports that matters.

That is the kind of disrespectful behavior that has gotten many projects to just close their reporting system. Everything has CVEs all the time and most of them are irrelevant to a particular context, it's completely pointless to just list them all. If you wanted to be actually useful then instead of flooding the report system with the output of a tool they can run themselves you would assess how each of them apply to Unraid's usecase and only report those that are actually relevant and important, there might be one or 2 at most. Just dumping all without assessment only creates noise and unnecessary effort that would be better spent on what actually matters.

The upgrade wizard/workflow changed and you're so far back that your current version doesn't know about that, so it showed you the last of the old workflow it knows of.

Probably similar to NTFS, linux can read and write but if e.g. it's disconnected unexpectedly without properly unmounting the "dirty, needs filesystem check" flag gets set and that check needs to be done on an actual Windows machine. So try connecting the drive to your mac and do a filesystem check/repair there.

Maybe read the huge red text in the thread's first post

Yes.

Depends on your setup, but that's typically the reason you'd be using it for...

Had the same issue, you can do a docker container rm 55e202a76 ac3d0872d 67005eb58 ed2b8d87b a5997ca85 1614f6f71 fc47760df 4d58b3096 89e0a6c12 f2a43dfcf 7625586fc e1b73a6a4 f5740dce3 af43ac462 4e29b8bb0 0f0f588e2 caaa01b20 85d86490f be7eb8b2b 6656e56a8 a50313426 1de8a9af6 55a83fe73 80bfdd8f2 9f2accb82 ed47915f0 b180f0059 86d7b24d4 c861931f0 (the whole list of containers that have the RWLayer error) then reinstall those from apps->previous apps. Will be a lot faster than recreating the whole docker image.

Word on the street is NUT will be built-in, so no need for a plugin anymore.

Must not be running this container then. As mentioned a couple of posts earlier everything supported has the fixed versions.

Is it new for you to have stacks on br0? It's been that way for ages for me, br0 is created fresh each boot so has a new id, need to make your own macvlan/ipvlan network to avoid that

When you open the apps page, if it's been more than an hour since last time you did a background check for updates starts, that may take minutes, once it's finished the action centre either appears if there are updates i.e. there's something to action or doesn't if there isn't.

All supported versions (32-35) are updated.

Since TPM licensing is unavailable for VM installs that's indeed an interesting question...

That optical drives are slow, or at least by default tuned to be slow/silent/more error correction rather than fast and noisy. Believe there are some things you can tweak in makemkv but mostly it's a drive firmware thing, AFAIK you need libredrive-compatible drives to tweak for speed.

It seems something e.g kernel is now able to extract the real identifiers from usb drives instead of the enclosure identification, which is actually great and worth having to do manual changes. dlandon is also not involved with the standard UD plugins this thread refers to anymore.

Click settings, assign the same script, set to automount.

tiredofit has moved all their containers to a new nfrastack organization. Need to update the repo. https://github.com/nfrastack/container-freescout

All containers updated? Seems to be homeassistant_inabox_v3 causing the issue, which was supposedly fixed some time ago. https://forums.unraid.net/topic/200692-homeassistant-in-a-box-v3-vm-failures/#comment-1637640

See the post above yours for where to report issues.

UD has lost the assigned script and automount settings for my backup drive. Someone posted another problem with UD in the UD thread. EDIT: Ah, seems something causes udev to now gives the drive's real identifier instead of the enclosure's, so that's why reassigning was necessary. Some people on Discord have had the same problem with usb drives in array/pools which is more annoying.

UD has lost the assigned script and automount settings for my backup drive.

Just got an update yesterday. What and where? Many plugins have some individual components that are needed in older versions but not newer ones so you'll see that message for the unneeded ones.

What RAID type have you selected for it? By default it'd be RAID1 so half the capacity for redundancy.

Do we really need a slopped plugin to run docker image prune -f -a? Hopefully does not.