itimpi

The tool seems to not work on some systems, not sure why. You should instead try the Manual Install method documented here in the online documentation.

Looks like you may have done something wrong with the New Config - did you hit the Apply button? You should have been able to switch the disk1 to the parity slot immediately after you ran New Config.

The diagnostics show what look like connection issues for /dev/sdg which I assume is disk5 and then it disappears. Aug 1 00:01:06 Tower kernel: ata6.00: configured for UDMA/133 (device error ignored) Aug 1 00:01:06 Tower kernel: sd 6:0:0:0: [sdg] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Aug 1 00:01:06 Tower kernel: sd 6:0:0:0: [sdg] tag#5 Sense Key : 0x5 [current] Aug 1 00:01:06 Tower kernel: sd 6:0:0:0: [sdg] tag#5 ASC=0x21 ASCQ=0x4 Aug 1 00:01:06 Tower kernel: sd 6:0:0:0: [sdg] tag#5 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 Aug 1 00:01:06 Tower kernel: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Aug 1 00:01:06 Tower kernel: Buffer I/O error on dev sdg, logical block 0, async page read Aug 1 00:01:06 Tower kernel: ata6: EH complete Aug 1 00:01:06 Tower emhttpd: error: ckmbr, 2291: Input/output error (5): read: /dev/sdg Aug 1 00:01:06 Tower emhttpd: ckmbr error: -1 Aug 1 00:01:06 Tower kernel: mdcmd (6): import 5 Aug 1 00:01:06 Tower kernel: md: import_slot: 5 empty I would suggest you carefully check that cabling to the drive (both power and SATA) is well seated and try again.

Correct - mover will not overwrite an existing file as this indicates something that is not normal and user intervention is required. You have to decide which copy to keep and delete the other. I suspect the one on primary storage takes precedence but I am not certain. This should never happen in normal operation. It takes the user doing something under the covers bypassing normal operation to create a duplicate.

Probably rebooting the server is enough, but a full power cycle would not hurt. You could also consider trying a different USB port (preferably USB2 if you have one).

Your flash drive is not showing up in the SMART information which makes me think it has dropped offline. That would explain the server name reverting to the default.

According to the diagnostics you formatted disk1 which is NOT part of the rebuild process. You would have got a dialog warning you that doing so would create an empty file system on the drive and update parity to reflect this. You are therefore rebuilding an empty file system on disk1. I suspect that docker.img file was on disk1 and your format lost it and thus a new empty one has been created which explains why your docker containers are gone.

Click on the pool on the Main tab and change it to use the Single profile.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

There is no simple answer to your statement. ZFS had advantages in some scenarios and disadvantages in others. You perhaps need to give some information about your expected usage, and also about the size of server you are thinking of setting up to get informed feedback.

That is normally recommended for performance reasons anyway.

That is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

Do you have Turbo Write enabled? If so this would explain your symptoms as a write to any drive requires all drives to be spinning.

It is worth noting that the CRC error count never resets to 0 - the aim is to stop it increasing.

Had the problem occurred when these diagnostics were captured?

If it replaces a drive then it will be rebuilt with that drives contents. Its current contents are irrelevant as the rebuild process overwrites every sector in the drive. If it is added as a new drive then any existing contents will first be cleared so again any existing content is irrelevant.

This will not be enough if there are still 13 drives assigned to the combination of array and pools, you have to get rid of one of the assignments. I would suggest that you use Tools->New Config to using the "keep array" option and start the array without a pool attached. You can always add it back later.

If you want the drive to be used as a drive within a VM, then you will need to remove the drive from the array. You CAN pass through drives that are NOT part of the array or a pool to a VM. If you want the VM to access the content that is on the array drives then you do this by accessing it via a network share just as you would if the VM was a physically separate PC running Windows.

The diagnostics show resets on the parity disk followed by write errors which is why it was disabled. Are you sure your PSU is up to handling the drives? The resets looked like they could be cabling errors (SATA or power) so. Heck that carefully. You could run an extended SMART test on the drive to test its health.

No. You cannot have a drive allocated to the array passed through to a VM. You would need to remove it from the VM definition complete;ly.

This process should work and make Unraid start rebuilding the parity. Can you please repeat the steps and at the end if it is still not fixed take new diagnostics so we can see what was happening at each stage.

Have you tried running Tools->New Permissions on that share to see if it fixes your problem? If it does then that means there were permission issues on the folders/files in the share so the question then becomes what you did to put the files there.

The XML provided would corrupt disk3 if you ran the VM. You cannot pass a physical disk that is part of the array through to a VM without corrupting it and invalidating parity.

The ‘shutdown’ command from the CLI does exactly what pressing the Shutdown button in the GUI does. The section on troubleshooting unclean shutdowns applies regardless of how the shutdown process is initiated.

Handling of unmountable drives is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.