Kilrah

Looks to be an issue in the Share Floor plugin, should report in the support thread for that.

User should be user, not capitalised.

To set up a mirrored boot pool you need 2 blank drives. So you have to move everything off the old pair to a temp location in order to put in the new and set it up as boot+data, then copy everything back.

Edit the VM, select cores/count again?

Unraid array is great for mixing different size drives, but it's designed for HDDs, SSDs will have no trim if you use that. You can use multiple pools by pairing matched sized drives but you're gonna lose a lot to protection. So you have to choose what matters most, optimal space usage but suboptimal performance and potentially faster wear by using them as array or losing a lot of capacity and dealing with separate volumes with them in pools.

Can always go read the files directly https://github.com/garybowers/bootimus/tree/main/docs/en

Neat! Just removed iVentoy a few days ago because the image had never been rebuilt... Might want to add vars for BOOTIMUS_PROXY_DHCP_ENABLED BOOTIMUS_WINDOWS_SMB_ENABLEDProbably defaulting to false. In the unraid context it'll probably be often useful/necessary to run it on br0 e.g. if Pi-Hole is used (Pihole needs to be on br0, Bootimus needs to be able to talk to it but it can't when on bridge). br0 is also needed for BOOTIMUS_WINDOWS_SMB_ENABLED since otherwise it'd conflict with unraid's own samba. Also usually not recommended to use --restart=always as that can create loops in case of bad config.

Some people have had to downgrade their plex containers lately as transcode broke for some platforms in recent updates.

The above, and also make sure to set min free space on each share correctly so that media shares consider the cache full before appdata/system/anything other that'd be critical for apps working.

VMs will use almost everything you give them for caching that's usually pointless, so you don't want to give more than necessary.

Correct.

Array disk order doesn't matter when only using the Parity 1 slot.

That should not need more than 2-4GB. Can install something like Beszel to log container memory usage for a day or 2 and look at what the usage is like.

You should have "Bind selected to VFIO at boot". If not, screenshot what you're looking at.

Should be able to untick and save/reboot. Is that controller used in any VM? If so it'd have to be unselected from there first

I mean to me what would be "really bad" is to only backup appdata once a month 😁 for me it's nightly

The button's kinda messed up in the corner since this plugin hasn't been maintained in a long time and didn't get updated for 7.3's layout changes.

You'd use monthly...

Disk5 keeps losing connection with the controller, check connections/replace SATA cable Apr 20 22:49:34 Tower kernel: ata6.00: status: { DRDY } Apr 20 22:49:34 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Apr 20 22:49:34 Tower kernel: ata6.00: cmd 60/00:e8:40:fd:00/03:00:00:00:00/40 tag 29 ncq dma 393216 in Apr 20 22:49:34 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Apr 20 22:49:34 Tower kernel: ata6.00: status: { DRDY } Apr 20 22:49:34 Tower kernel: ata6: hard resetting link Apr 20 22:49:39 Tower kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 20 22:49:40 Tower kernel: ata6.00: configured for UDMA/33 Apr 20 22:49:40 Tower kernel: ata6: EH complete Apr 20 22:49:40 Tower kernel: ata6.00: exception Emask 0x10 SAct 0x3ff0000 SErr 0x4090000 action 0xe frozen Apr 20 22:49:40 Tower kernel: ata6.00: irq_stat 0x00400040, connection status changed Apr 20 22:49:40 Tower kernel: ata6: SError: { PHYRdyChg 10B8B DevExch } Apr 20 22:49:40 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Apr 20 22:49:40 Tower kernel: ata6.00: cmd 60/00:80:40:21:01/01:00:00:00:00/40 tag 16 ncq dma 131072 in Apr 20 22:49:40 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) Apr 20 22:49:40 Tower kernel: ata6.00: status: { DRDY } Apr 20 22:49:40 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Apr 20 22:49:40 Tower kernel: ata6.00: cmd 60/00:88:40:22:01/04:00:00:00:00/40 tag 17 ncq dma 524288 in Apr 20 22:49:40 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)

Failing USB drives. Many of us have some that have been working fine for years, but not everyone is that lucky.

Unbind any bound system devices, make sure to disable autostart for the VMs if enabled. Reboot, rebind, and also select the proper device in the VM template again as it might have changed.

Sounds like you're passing through the wrong device, and that yeets the USB away from Unraid. If you did something like update the OS or BIOS inbetween that can change the PCI addresses so that what was your GPU is now the USB controller... Always should remove all binds before doing that then set them up again afterwards. Some 2070S have USB-C ports, you didn't plug your Unraid boot device to that, right?

Filled the form?

You can, but most of the things that are designed to be exposed already have their own tracking and are updated regularly. Some apps build new images nightly regardless. You'll quickly be spending your entire time tracking things if you go down that rabbit hole... I tend to check my Docker page once in a while and look at container creation dates, I'd only start worrying if something that is exposed is more than 3ish months old or so. If it's long unmaintained then I'll reevaluate whether I need it or not or should rebuild/maintain my own container, replace with an entirely different app,... Often it'll be something like the tag or repo changed, or development has moved to a fork, which can't necessarily get automated even if you build yourself.

https://crontab.guru/ says it's invalid too.