Squid

👍

prepending Yes You actually are running it directly (via the user script)

There is a plugin to allow you to use ZFS on unassigned disks To expand upon @trurl comment, For myself this is the biggest thing. When I started out researching what solution to use for my own storage, I was amazed and shocked that if the worst happened and I lost more drives than the redundancy could handle on a traditional RAID setup that I wouldn't just lose the data on the drives that failed, but I would lose absolutely every single file on the array with no chance of recovery. Sure, read speed is affected by that because of no striping, but for me in a worst case scenario I'd rather lose a fraction of my files than lose every single one. Maybe I'm just different, but I don't understand why anyone would gamble with losing everything than only losing some, especially since the size of many people's arrays prevent a complete 1:1 backup of it in the first place.

You have to either copy them say to /tmp and reference that (and change the permissions appropriately) or change the line to echo "/bin/bash /boot/config/plugins/user.scripts/scripts/StartVM/script" | at now Calling a script on the flash drive directly will run afoul of the security, because even though the plugin has never executed scripts directly from the flash, it has no control over what the script actually does.

Any apostrophes or the like in the username / password?

Yes. But they will probably get recreated if you don't disable docker and vm's in the settings. Not normally, but if you are on a Mac for instance, then finder will create hidden files pretty much everywhere you navigate to, and you have to enable show dot files in Global Share settings to remove them (or set finder to not create them in the first place, however you do that)

Latest version of FCP issues a warning about mirroring the flash

The plugin has never executed scripts directly from the flash drive

Applying mitigations is now a fact of life, but if slowdowns are your concern, you are able to completely disable any mitigations https://forums.unraid.net/topic/80563-plugin-disable-security-mitigations/

Upshot though is that under certain circumstances when that alert pops up (and it never should ever), it is possible (depending upon why it showed up) that the webGUI will not allow you to switch tabs away from Apps, and you're forced to reload the GUI in a new tab. Updating to change that behavior.

Mine are a Mac Catalina and a Mac Mojave with no passthrough on either. While I never run them both simultaneously, I did for this troubleshooting. They did work simultaneously an RC or 2 ago when I originally set them up.

https://forums.unraid.net/bug-reports/prereleases/680-rc6-starting-vm-causes-vms-to-disappear-from-dashboard-and-vm-tab-r726/?tab=comments#comment-7068

No conflict, as there's no passthrough on any of my VMs And, even if there was then it shouldn't disappear completely Nope Same as the pic in the OP. VM and dashboard sections are empty stating no VMs defined

Yup. Start with no VMs running. Start one VM from the dashboard. OK. Start another one and everything disappears.

Obviously CA issue. Make sure it's up to date.

BIOS's are OS agnostic But, in the OS drop down there is an option that says "BIOS" Then why bother. While I tend to update my BIOS every once in a while, no matter what you do it does entail a (very small) risk of bricking

BTW, nothing says you can't still use the array and transfer file(s) while a check is underway. It just slows stuff down.

Not permanently. I understood the question to be if you don't run the check will the ability to rebuild be compromised in the unlikely scenario of a rebuild being required. Until you run a parity check after an unclean shutdown, the answer is that you just don't know 100% if the parity is properly in sync with the drive. It is however always a big question / gamble as to whether or not it finds a sync error. If it doesn't, then the check was in vain, but at least you know. If it does, then it wasn't in vain, if a rebuild is necessary, then everything will work correctly. If you don't run the check and it would have found errors, then a rebuild will still work, but you run the risk that some file(s) may be corrupted.

This

If you can't run apt within your VM, then you're going to have to research that within the Ubuntu forums.

Just so you don't get the wrong idea, the "tainted" messages are completely normal and expected

It's a tough call. The safe answer is to do a parity check.

Does the drive still need to be formatted? If so, enable the mirror to flash in syslog server settings, and then format it and see what happens Those won't cause any problems. Guaranteed

You also at some point need to post the diagnostics. All me know is that ffdetect segfaulted. We have no clue what is running on the system, what is installed, what your configuration is etc etc etc.