JonathanM

BTW, ideally you want to use as many of the modular power connections as possible to split the load evenly across as many wires as possible.

According to this link https://www.corsair.com/us/en/p/psu/cp-9020252-na/rm850x-shift-80-plus-gold-fully-modular-atx-power-supply-cp-9020252-na it comes with 2 PATA cables with 4 molex connectors each. It has 5 connectors on the PSU itself, each can take either SATA or PATA cables, so if you order 3 of these, https://www.corsair.com/us/en/p/pc-components-accessories/cp-8920315/premium-individually-sleeved-peripheral-power-molex-style-cable-4-connectors-type-5-gen-5-black you can have 20 4 pin molex connectors.

appdata backup plugin

You've been doing this tech thing with Unraid for a very long time, relatively speaking. Why not salvage your old hardware and build another Unraid box with used parts? A backup tower would only need to be powered up for the duration of the backup, so heat and power consumption aren't a huge factor. You could use a couple new faster drives in your production box, and move your current smaller drives to the backup unit. You seem to be focused on the ability to plug the bare drives into a windows box to read natively, but once you add hardware RAID into the mix you lost that already. If the hardware RAID enclosure dies, you would need to source a compatible unit to read the drives. If you run a second Unraid server, the drives are portable to virtually any hardware as you know. IIRC @Hoopster has something like this set up and running with automatic scripting to do the backups.

As long as parity is not currently installed and valid, yes. If the array has valid parity added disks will be cleared, which irretrievably erases them. Tools, new config, preserve all will allow you to add the disks without erasing them and build parity with all the disks.

I don't think you can use a vdi directly, I believe it must be converted to a raw image first. After you have a raw image, just define a new VM using the normal GUI and point the primary disk to your image.

Please attach your diagnostics zip file as mentioned in the pinned post.

Script that checks for the existence of a specifically named file. If that file does not exist, create it. If it does exist, rm -rf. Every time the script runs you need to delete the file.

Theoretically CLRF issues are dealt with automatically, IIRC all system calls to the flash config files are run through the fromdos function.

No, but you will have to contact support to have them manually update the key.

Nope, I'm just living with it. The mapping program I use, uNmINeD, gives a permission error for the GUI version, but I can live with that because the CLI version still works fine, and that's what I use on a schedule to generate a webpage for the people using my server. I'm not happy that the GUI version of the mapping program doesn't work, but it doesn't effect my daily workflow. There probably is a solution, but I haven't put in the legwork because it works enough for me as is.

You have the trial period you can use for 30 days, then you can do the starter subscription for $49. That will give you at least 1 year, probably longer, until you need to pay more for updates. If, at the end of all that, you decide you want lifetime updates, you can change to a lifetime for $209. Total outlay, $258, and only after living with Unraid for much more than a year before you have to make a choice. So, the "penalty" for not going to lifetime immediately is only $9 net. Try it out for free, and if it looks good and you want to continue, get the starter license. If at the end of all that, you want to change to lifetime, you aren't spending significantly more than if you fork it all out immediately.

You need to ask in the support thread for the specific container you are using, there are several different implementations. Click on the container icon in Unraid's GUI, and select the support item to get to the correct area.

I'll pile on a little. First post of this thread.

Keep in mind the slackware version is a moving target, you will likely need to recreate your steps with new versions of Unraid.

Or, if the cause is truly just one container, start roughly half of the containers, check, if the problem is found, start half of the those, if the problem isn't found, start half of the remainder. Depending on how many items you have to check, elimination by halves can be much quicker than 1 by 1.

No, at the moment Unraid only supports LUKS natively. File system level encryption has to be handled manually, which you seem to be doing without issue. You can certainly look through the feature requests area of the forum, and if it's not already requested, add a topic.

If both new and old hardware are using plain SATA controllers or HBA's in IT mode, the array disks will move without any intervention. VM's that have hardware passed through will need to be edited, as the hardware will change (duh). Docker containers are typically hardware agnostic, but once again, if there is any hardware passed directly to them... Set the array to NOT auto start. Confirm recent parity check had 0 errors. Move all drives, if the new hardware will boot legacy it should boot right up, if not you may need to rename the EFI- folder to EFI. Make sure you research any BIOS quirks needed for your specific AMD combo, there are many more gotcha's with AMD than there are with intel when it comes to linux and by extension Unraid. There is a whole thread on troubleshooting AMD issues.

cheap insurance, if you use it correctly

mc at the console?

Hopefully you have enough RAM to cache the entire video.

Diagnostics might hold some clues.

AFAIK an unclean shutdown detected startup doesn't honor auto starts on purpose, reasoning is probably so that a possible boot loop will not happen. Does everything work properly if the prior shutdown completed successfully?

What about the reader? Same?

Can you figure out a way to take the temperature inside the enclosure? I'd be afraid of cooking it.