itimpi

Are all drives spun up? Temperatures are not displayed for drives that are currently spun down.

High Water does not try to keep files together - it is the Split Level setting that controls this. Switching to Most Free will not help as Split Level over-rides Allocation method.

Removing a parity dtive is covered here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI. You can now use the standard procedure for adding drives to the array as documented in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.

You are probably confusing the system by having both drives with the same ‘UNRAID’ label?

Because there if there is a problem on a drive there is no way to identify which one it might be. With modern drives the assumption is that they will return an error if they do not read a sector successfully, but it is possible that is not always the case. checksums is the only way to be certain (either built into the file system or via an add on are the only way to validate this.

When ‘correcting’ parity the assumption is that the data drives are good and parity needs to be updated to match. This is the same whether you have single or dual parity, in neither case is a problem drive identifiable as the cause of a parity error.

You also need to have the docker and VM services disabled to allow the files to be moved to the cache pool by mover as they keep files open (and mover cannot move open files).

I am confused - the cache drive is part of the share.

CRC error counts are nearly always caused by the cabling to the drive. Since they never reset you need to aim to stop them increasing at any appreciable rate,

If you do not think that you have a drive playing up then the only thing you can sensibly do is run a correcting parity check. If you have not rebooted then you can post your diagnostics covering the period in question to see if anyone can spot anything. If you want to know if you have 'bit rot' on array drives then you need to either be using BTRFS as the file system or use the File Integrity plugin to maintain checksums.

It would be nice if this was the case but apparently it is not always that easy

I would not expect it to run natively on Unraid. If there is a docker container for it then that should work.

Nothing has changed in this area for a long time. It could be coincidence and a Windows update happened around the same time and this is behind the issue?

First time I have heard of such a limitation. I would expect IDE mode to give performance issues

You could try opening up the syslog in a window before starting the array? at the moment the symptoms feel very like they must be hardware related in some way. Are you sure that the power supply is OK for the hardware. Building parity is a time when the system will be most demanding. Have you tried running memtest (one of the options on the boot menu) to check out the RAM? What speed are you clocking the RAM at? Make sure it is within the rating for your motherboard/CPU combination. Overclocking RAM is a not infrequent cause of crashes.

Did you manage to get the syslog server set up?

Have you tried via the server IP address? You may simply be having problems with name resolution. There should be nothing in the latest release that stops things working.

It is worth seeing if you can make a ssh connection.

This is expected if the drives have not previously been formatted by Unraid. This could take quite a long time to complete if you are simultaneously building parity. If not done at the same time it is normally quite quick. As the server is still operational you may find that if you close the browser and then connect s second time then you get something useful. If not then wait until parity is built.

Most people simply let the High Water share allocation method handle it as it will start balancing things out as the drives get fuller.

I could not see any attempt to assign the disks in the posted diagnostics Maybe taking some diagnostics after doing the assignments but before starting the array might give a clue. it might also be worth configuring the syslog server to see if that captures any additional information after attempting to start the array.

You should be able to upload it to the forum - not sure why it fails for you. I cannot download from the link you provided so cannot help.

No idea - I have always used the manual method as the USB Creator does not seem to recognise all USB drives. I must admit I thought it DID take the files from your backup.

It will be the syslog file in the logs folder.

because the mover application ignores shares that have the Only setting. It also ignores open files so you typically have to (temporarily) disable the Docker/VM services when trying to get everything on the cache. If it was the Extended test then typically around 2 hours per TB Yes