JonathanM

Very plausible. The SATA slip fit connection is precise to fractions of a mm. Plastic and metal drive tray assemblies, not so much. I make it a habit to final tighten the screws in a drive tray allowing the drive to free hang against the partially tightened screws, holding the tray only. That way all the tolerances should stack up to put the drive to the absolute rear of the tray. SATA / SAS connectors are an electrical nightmare, they cause WAY more drive errors than actual disk failure.

Spill! Novel ways of causing intermittent issues are always interesting, especially non-intuitive stuff.

Nothing stopping you from purchasing another pro license if it makes you feel better. 🤣

Do the new config procedure with the keep all selected, then before starting the array remove the selection for parity1 and leave everything else intact, you can start the array with the checkbox selected saying parity is already valid and it will kick off a parity check.

Not even close. The drive assigned to slot parity1 is a simple parity sum, the drive assigned to slot parity2 is a complex calculation that includes slot number of the included data drives. Sure. As long as you leave the disks all in their assigned slots parity2 will remain valid, no need to have a drive in parity1.

A VERY vocal group complaining that the automatic updates were continually breaking their stuff, and basically saying Unraid should never be able to change the templates behind their back.

Tools, diagnostics, download the zip file, attach it as is to your NEXT post in this thread.

Reboot to clear out leftovers.

You could simply change the mappings to valid locations, no need to delete and reinstall.

There's your problem.

Best answer I can give is use the trial install and see how you like it. There are so many things Unraid can do that will be severely limited by that hardware, it's impossible for someone else to tell you whether the things it can do with those limitations are worth it.

Much safer for your data, as the removed drives will be a copy, and much less chance of user error causing data loss.

Possibly not, depending on the firmware of the drives in question. Personally I'd recommend just leaving it alone, keeping in mind that an occasional mass migration to empty specific drives in turn if you feel the need. Do you anticipate a high churn rate for the data with lots of changes and deletions?

Change the Download to: field in your first screenshot to /data/incomplete and the move to /data/Completed

Not possible for array or cache pool devices. The only way Unraid can use FAT32 besides the boot stick is with unassigned devices. Doesn't sound like it.

You keep copies elsewhere for backup, right?

Because it's still working. It copies, then deletes the source after the copy is successful.

It can't validate via the signature, it can only trust that the signature has been applied to a fully cleared disk. The signature is placed in a logical location on the disk such that any write access that would normally be applied to a fully blank disk will destroy the signature. If you were to take a precleared disk with signature intact and manually flip bits NOT in the signature area, Unraid would still trust it as precleared, and subsequent parity checks would find the altered area and either only alert or alert and alter the parity disk to match, depending on whether the check was correcting or not. If there was a disk failure before those bits were corrected in parity, then each altered bit would be incorrect on the emulated disk, causing anything from file system corruption to absolutely no noticeable effect if the bits were in unoccupied space on the emulated drive. Clear as mud? At some point between the finalization of the preclear process and adding the disk to the array, the signature was overwritten, causing Unraid to require a clearing cycle. When that occurred can be very tough to pin down, but any attempt to mount or read the precleared drive could possibly cause it.

That's not the point. It's not able to pass the drives through completely unmolested, it interferes with some functionality of the drives, unlike a true IT mode HBA. https://www.truenas.com/community/threads/lsi-3108-it-mode.46407/ This makes diagnosing and dealing with disk issues WAY more complicated than it needs to be.

You can turn off auto start for the downstream dependencies and script their startup manually. @Squid had a great container startup management tool with dependency checking that was plowed under when the OS introduced wait and ordering natively. Yes, I'm still bitter about that.🙂 So many of his superior implementations get tossed aside when the OS introduces a watered down version of the same functionality. Query the service in question from the command line. for example if you telnet to port 3306 if the mariadb is running it will spit out some version info and close the connection. If no response, it's not running.

Since there are a bazillion containers, each one has it's own support thread where you can research issues that others have had with it, and post if your issue hasn't already been addressed. You can find the support thread by clicking on the container in the GUI, and selecting the support option in the dropdown.

No. You need the BIOS from the physical card you are passing through.

Why not you?

Better for what? Different use cases have different needs, there is no single right answer for everyone.