JonathanM

to mount a share you must use a valid user, not root
to connect to the console, you must use root, not one of the users
use that path as the rsync destination, assuming it mounted correctly and you see the contents of the unraid share at that local path.

What address and port are you trying in guac? I know a plain VNC client works fine for me using the server ip and the normal 5900, 5901, 5902, etc depending on what order the VM's were started. The VMS tab graphics column shows the port.

Here is a link to a post with some of the parts you need. I use it to start a VM after my gateway IP is pingable.
https://forums.unraid.net/topic/78454-boot-orderpriority-for-vms-and-dockers/?do=findComment&comment=727416
 
You could reuse some of the code to stop and start containers with the docker pause and unpause or stop and start.
 
It would need a major rewrite to accomplish exactly what you want cleanly, but I think all the parts are there.

The new config tool will allow assigning (and unassigning) whichever disks you want, any disk assigned to the parity slot(s) will be overwritten with a fresh parity build using only the assigned disks when the array is started.

I'm not familiar with the exact commands required, but I'm sure a Truenas pool doesn't import automatically YET. Something to do with the partition structure on Truenas using the second partition instead of the first. You should be able to import using the command line after each reboot, and importing automatically should be handled sometime in the nearish future.

Only if you had the syslog server already set up to mirror to the usb.

There should be a previous folder on the flash drive that contains the files that were replaced in the root. Either copy them back, or if you can't find a previous folder, download the 6.11.5 zip and get the root files from there. Don't overwrite anything in the config folder.

It will show an error count if there are any differences in what is read from the parity disk and what is calculated from the data drives. The messaging is currently the same whether those errors are simply noted, or corrected.
Correct. Parity is kept up to date in realtime as writes are done. As long as the drive internal caches have finished their writes before power is lost, there should be no sync errors.
 
If there are writes in progress, the data drives are higher priority, so it's entirely possible that a write can be successfully completed on the data drive but the parity write has yet to be fully committed, causing a sync error, a correcting parity check will complete that process. It's also possible for a power cut to corrupt a data drive if a write in progress gets cut off at just the wrong moment. In that case parity can't help, because it will have even older data. Most of the time the file system checks can at least get back to a readable state, at the expense of a corrupted file or several.

Unclear what you mean. The drives will remain accessible after you enter the passphrase until the server is shut down. When you start the server again the encrypted drives will be unavailable until the passphrase is entered.

Move the vdisk from the array to the pool using dynamix file manager or mc at the console or whatever your favorite file manager is, then change the VM XML to point to the new location.
 
Or, to make it even simpler, assign the pool as the primary location for the domains share, assuming the vdisk is in the domains share, and the array as the secondary location with the mover set to move from the array to the pool. This assumes your pool is big enough for all the content of the domains share.

Flipping the switch on the PSU kills power to the motherboard, then you need to press the normal power switch to drain the residual power in the capacitors in the PSU and on the motherboard. No need to leave it off for long, just so the motherboard has no more power to maintain the failed state, and has to reinitialize from a known state.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/#comment-511923
 

Port mapping only applies to bridge mode. When a container has a different IP address than the host, mapping is not used or needed, all ports are open and the listening port(s) are directly controlled by the application(s) in the container.

Definitely not.
While some hardware may work, it's not a universal thing. Hotswap has to be supported by the HBA and the drive cage, so it's safer to power down when unplugging and plugging drives.
 
The only quibble I have with your summary and the original is the last step, I'm not sure why it's there to be honest. Formatting would erase the pool, so don't do that unless you don't need the data on it.
@JorgeB, could you check that to see if I misread something?

That should be fine.

Was that after a restart without touching the interface with Firefox at all?

No.
 
That may change with future versions that don't require any disks in the parity array to start Unraid, but I'm just speculating on that.

The issue seems to be with Unraid still thinking the disk has a valid filesystem, if you stop the array and start it again so the disk shows unmountable, the write speed will increase dramatically. The only issue there is that the script won't work on an unmountable drive, so you must use the manual command line. If you mess up the command line, you can permanently erase a drive you didn't want to. If you are careful and match the md? correctly you will be ok.

Is the default format type still encrypted?

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.