JonathanM

I have advocated before to change things completely, where each share has 2 settings. Initial file placement, and mover enabled or not. If mover is enabled for a share, a new field for destination would appear. That would simplify explanations, and allow for pool to pool mover configuration.

No. There is no "installation" as Unraid runs in RAM, so it's loaded from the license USB stick into RAM on every boot. Here is the forum section on running Unraid as a VM. While not officially supported by Limetech, it has been done successfully on several hypervisors. Since Unraid boots from a USB, runs in RAM, and itself hosts VM's, running it as a VM can be rather complicated. https://forums.unraid.net/forum/46-virtualizing-unraid/

👍

I don't have any experience with it, but there is this.

Some older motherboards didn't boot properly if the EFI folder existed, I guess they got confused whether they were supposed to boot traditionally or UEFI. The compromise was made to properly configure the EFI folder but rename it if the checkbox to enable UEFI boot wasn't checked when the flash was created. Are you selecting the Allow UEFI checkbox in the customize section?

Look at the last daily health report you received from the server notification. It will have a list of your drives.

This would be an incredible amount of work to do well. I would love to see it, but the logistics to set this up are beyond me. You can certainly post a feature request, but I wouldn't expect anything to come of it, at least not for the foreseeable future. If we get server to server over WAN, that would be enough to allow like minded individuals who trust each other to set up backups in private, not mediated through Limetech. That is an achievable goal, so maybe request that first?

Attach diagnostics to your next post in this thread. While many are successful at using Unraid on a local desktop, that's not the primary use case, and there may be some hardware that just doesn't cooperate.

If you have another pc not in use, if you can get 2 ethernet ports in it you can use it as a quick way to keep your internet up if you need to reboot unraid. pfSense backup files are plain XML, it's easy to edit the ports to match the hardware so you can seamlessly move your pfSense install to pretty much any compatible hardware in minutes. Simply install pfSense on the device you want to use, take a basic backup to get the port names correct, then take your live backup and edit the port names to match the backup hardware and restore your live backup to the temporary box. All your firewall rules, VPN's, everything else should come back up. I have an old laptop with a second ethernet cardbus adapter that I can fire up in a minute or two if I need to take the server down for an extended period of time.

Little gain for a lot of work. If you want more network speed, 10Gbps adapters and infrastructure would be a better use of your resources. Others may have a different opinion, but that's what I personally did.

Yep. Hopefully there will be zero errors. If there is any other result it would be nice to know why. Your description of adding the drives and the order of events leaves me suspicious that something didn't go right. When was the last time you had a zero error parity check?

Please do a non-correcting parity check and see what results you get.

You can't format the drive while the array is stopped.

There is a basic misunderstanding here. At the bottom of the main GUI there should be a checkbox and dialog to initiate Unraid's formatting of any unformatted disks in the array. The piece that you quoted assumes you would check that box and allow Unraid to do its thing. If you format a drive BEFORE adding it to a parity protected array it will be erased anyway, so no need (or use) to format a drive before adding it. You must let Unraid do the formatting after you add it.

Those two things are currently mutually exclusive. You can change back and forth with a reboot though.

Nope, the server is functioning normally, it's just a display thing on mine.

I use plink with the /batch switch, it works for me.

Mounting it with the Unassigned Devices plugin should work.

Unraid doesn't aggregate drives like normal RAID in the parity array. Each data drive is individually formatted, and root folders on each drive are merged as user shares. The parity drive(s) must be the same size or larger than any single data drive.

Where did you see it was recommended? It was, many years ago for version 5 and earlier, but now it can cause issues.

The first link seems to be a RAID controller, which is not recommended for multiple reasons. You want a plain HBA which just passes along the disks to Unraid without interfering.

That doesn't parse, since krusader is a container as well.

https://dlcdnets.asus.com/pub/ASUS/mb/LGA1151/PRIME_B365-PLUS/E15233_PRIME_B365-PLUS_UM_WEB.pdf#p18 Strange to me that it won't start, it's been my experience that mismatched sizes result in single channel mode, not outright failure.

Which motherboard?