JonathanM

The server won't get a DHCP address from the router if it's set to a static address, so it's real, and it's assigned, just not by the router.

Remove the empty folder and the calculation will go back to the single volume size. All root folders on all array drives and pools are part of the share, even if they are empty.

I believe you are correct, maintenance mode from step 2 until step 7 would be a good idea. In step 3 you need to assign it to the array so Unraid detects the step 6 removal and starts the emulation in step 7.
@trurl@JorgeB, anything I missed? I personally don't have any Unraid encrypted file systems in place so I may have missed something there. Possibly may need to set the file system to encrypted instead of auto on each of the data slots?
 
It wouldn't hurt to have a test drive or two, even old ones, to help validate the trial is working well before you commit to recovery and start attaching the real data disks. Starting completely over with new everything means memtest and at least some burn in hours before you should trust it. It would really suck to find out the new system mangles data while trying to recover a failed disk. I would really work over the trial system in step 1 to uncover any gremlins. After you are satisfied the new system is stable, you will need to set a "new config" to remove the test disks and prepare for step 2 and on.
 
Don't rush through any of this process. I fully expect you to pound on the trial for several days before moving on, preferably starting off with 24 hours of memtest, I'd download the latest free version from https://www.memtest86.com/ and run it.

Yes, I was saying you could avoid the license transfer by continuing to use the old USB stick. If you put the old license file on a new stick it will prompt you to transfer the license, blacklisting the old USB GUID. You can do that automated transfer once a year, if you do it sooner you have to contact support and tell them your situation. Why not continue to use the old stick? In my experience it's hard to find a good quality USB stick, I'd prefer to keep using a known good one than take a gamble on a new one until forced to by failure. If you keep a current backup it's a matter of minutes to do a transfer to a new stick.
 
I'm not sure what happens if you try to move an existing license to a stick that has been issued a valid trial. Presumably you could do that, but the automated system might not work, forcing you to contact support to get it moved.
@SpencerJ?

You can do the parity drives one at a time to maintain redundancy.

Possible, yes, but not likely. Relatively lots of programming and debugging for very little benefit. The existing method is proven to work in any case.

Click on the VM icon and select remove.

Is your monthly check correcting or non-correcting? If it's correcting, run a non-correcting check to be sure everything got back in sync. If it's non-correcting, run a correcting check followed by a non-correcting to make sure it's done. All this presupposes all your current drives are perfectly healthy.
 
If you don't know how to be sure of what I'm saying, attach diagnostics to your next post in this thread.

6.12 is still in RC phase, so you need to select the next branch instead of stable.

I use UrBackup for my local workstations, and a handful of remote machines as well. It handles windows and linux clients.

Use the webGUI

Unraid doesn't require it, but some motherboards halt before booting if no graphics chip is found. Some of those motherboards do have a setting to boot regardless, but you need to be able to get into the BIOS setup to make the change.
 
How do you know the motherboard is actually set to boot from the Unraid USB stick?

Random(ish) errors after adding a drive are typically caused by power issues, either poor connections or lack of capacity to service the extra load. Parity checks are a point of maximum power use, especially when first initiated and multiple drives are spun up.
 
A high resistance connection caused by a splitter can also be an issue, as it causes a voltage sag under load.

Corrupt filesystem?

Safari is known to be randomly problematic for some subset of folks.
 
Can you recreate the issues in a chrome based browser? Firefox almost works, but has a nasty habit of popping up a "resubmit information" dialog, which if you cancel, the browser works great, if you accept, it causes all sorts of issues.

Verify the disk type defined in the xml is correct, I seem to remember someone saying it reverted to raw instead of qcow or something like that.

This exactly.

Unraid assumes any multi-drive pool is redundant, since that's the default setting. It's a known issue.

Not recommended, be sure you keep good backups.
See the RAID section of this article, and many others.
https://itsfoss.com/btrfs/

Try setting the share to cache:yes, then run the mover. If you enable mover logging before you run it, you can see any error messages in the logs. If you can't figure it out from there, attach diagnostics to your next post and someone can take a look.

Looks perfect to me.
 
I'd add another step, after everything is complete do a non-correcting parity check, and be sure to keep an eye on the SMART status for all the drives through the whole procedure.

ddrescue appears to do the same thing as safecopy, and it's already available for Unraid in nerdtools.

Expedite replacement, don't bother with extensive testing of the new incoming drive, the rebuild process followed by a non-correcting parity check and long smart test will be a trial by fire for the new drive.
Might be a good idea to order another replacement to have on hand, I personally keep a tested drive same size as parity in a box as an on deck option.
Good reason to consider keeping a tested cold spare to limit time at risk.

Are you sure your phone didn't get connected to a guest network?

Try setting the primary vdisk bus to SATA instead of virtio.