JonathanM

I think if you delete the partition it will reformat. If you can't figure it out, post in the Unassigned Devices support thread.

What path mappings do you have in the plex container? Docker containers can only access the files on the host that you give them paths to, and they see the files in the container path. So if you have a media share on unraid, it would be /mnt/user/media on the host side of the path mapping, and you could set the container side to be /media. Then in the plex container all the files in /mnt/user/media would show up under /media.

If you truly don't want any of that existing data, you can always just format it. The swap part of the conversion won't work with a cache drive anyway. If you want to play it safe and keep the data, disable VM and Docker services in setup, so the tabs no longer appear in the GUI, then set all shares that have data on the cache to cache:YES and run the mover. That should empty the cache to the array, then once there is no data left on the cache, format it, and set the shares you changed to cache:YES to cache:Prefer and run the mover again. Once that is done and the data is back, enable docker and VM services.

Well, the 1st 8 characters match, but the internal number has a bunch more digits. As long as they all report unique numbers I wouldn't worry too much.

Virtualizing Unraid has never been supported. It's not forbidden, but it's always been, "if it works, great, if not, it's up to you to figure out how to make it work" If you can figure out what needs to be changed to get it working again, and that change won't break things for people NOT virtualizing Unraid, then there is a high likelyhood that your fix will be included.

When shopping for server grade pieces, make sure you get a plain IT mode HBA instead of a RAID controller. Unraid doesn't play well with RAID. Some RAID controllers can be forced into submission, but you are much better off getting the correct controller to begin with instead of fighting with it. There is a thread with compatible controller models.

Right click on one of the drives, select Change Drive Letter and Paths... What path does it show to access it?

Most likely you will have to view the screen on the server at some point to troubleshoot, so I'd work towards that regardless. You should be able to connect the USB stick to your desktop computer, look in the previous folder, and copy everything out of that folder back into the root of the flash drive and get back running again.

The flash drive is mounted to /boot, array drives are mounted to /mnt/diskXX, pool drives are mounted to /mnt/poolname Since the flash is FAT32, files stored there can't have the full set of linux attributes, so if you store your files there you need to copy them elsewhere and apply the correct perms with your script.

That path exists only in RAM, and is recreated every boot. If you make changes there you will need to script the change to occur on every reboot.

I think some motherboard and BIOS combinations can make it work, however it's not a typical use case, so finding documentation may be difficult.

Assuming all the drives involved are perfectly healthy, just replace one at a time starting with parity and Unraid will rebuild your data to the new drives.

After a reboot, yes.

Why does xteve have 11GB of temp files?

Probably, but why throw away the progress you made? The command line you posted is specifically tailored to resuming a transfer. Just run the same command and it should pick up where it left off. After that rsync finishes, you can check the transfer by issuing rsync with the same source and destination, but substitute -narcv for the -avPX part. It will compare the source and destination, and list any differences. If it returns to the command line without listing any files, it means the source and destination are identical.

Same here.

Can you SSH into it from another pc? If so, type powerdown -r and see what happens.

Be sure you set up and verify that you get notifications so you have immediate feedback of any issues. Since Unraid works with the entire surface of all the drives, it's a good idea to do an extended smart test on all your drives before you trust them. The parity build and check will also help you gain confidence in the drives.

If you are using my preferred command line for rsync (one line for the initial copy, a second run through to verify) then you could to a file system check on the destination drive to be sure it's clean, then issue the same copy command again and it will pick up where it left off, then the rsync verify command will catch any inconsistencies. You didn't say what exact commands you were using, so it's tough to advise on best options.

Don't use disks in Unraid that are ready to fail. The way Unraid parity works it uses the entire capacity of ALL remaining drives to reconstruct the failed drive, so if a second drive dies you will lose all the data on both drives. The moment a drive fails, ALL rest of the data drives plus the parity drive are read to emulate the failed drive, and writes to the missing drive's slot update the parity drive. As an example, say you have replaced all your older disks except one, and it doesn't have much content, so you aren't worried about replacing it. Now, out of the blue without warning, one of your new disks, full of data, dies on you. Now, that old drive that was on its last legs is called into constant use to emulate the failed drive, and it must survive reading the entire capacity to rebuild the failed new drive. You hope it survives long enough to get through the rebuild process, but chances are, it's not going to. You must always be able to trust all your drives to perform perfectly, so when one of them inevitably fails the rest are in good shape. Any drive that shows signs of failure must be replaced ASAP.

https://forums.unraid.net/topic/43651-plug-in-unbalance/?do=findComment&comment=1098819

Rootfs has nothing to do with the flash drive space wise. The flash is mounted at /boot The command given was to check space at / which is the root. Problems sometimes occur when there are typos, like capitalization errors.

If you want. Did you read the support thread on the plugin?

Attach your diagnostics zip file to your next post in this thread.