itimpi

Is there anything that all drives share that you might have disturbed? If using a HBA is it well seated in the motherboard?

Sounds as if you have been emulating that missing disk ever since without realising it 😒. It is a common misconception that unassigning a disk is all that is required not realising that doing so will make Unraid treat it as a failed disk and start emulating it. To stop this happening you need to follow the correct procedure to remove a disk from the array as documented 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.

The diagnostics definitely show disk1 to disk22 present. Are you sure that the message is not associated with disk23 disk24 which are not present.

If you have decent backups I would think that single parity is enough. I personally only tend to go for dual parity when the number or array disks gets to be something like 10-12 (but I have decent backups in place). However it is basically your decision to make. It is always worth remembering that backups are still important as although parity can protect against a disk failure it does not protect against other ways to lose data such as File System corruption (perhaps caused by bad hardware), user error, etc.

I have identified that this can happen with the latest plugin update (v2023.11.26) after you resume a manually started parity check. It should however be harmless other than spamming the log every few minutes (although I agree that can make it difficult to find a real problem) as no action is taken by the plugin at that point. I am now testing a fix for the next release of the plugin to stop the spamming from occurring.

CRC errors indicate connection errors. Since CRC error counts are stored internally to the drive they never reset to 0 so you can only stop them increasing. You can ask Unraid to only tell you about changes by clicking on the Orange icon for the drive on the Dashboard and selecting the Acknowledge option. In the vast majority of cases it is the power or SATA cabling to the drive causing the CRC errors to occur, although as was mentioned old LSI firmware seems to sometimes cause this to happen when it should not. A quick way to check the cabling is to swap it with another drive and see if the errors follow the drive or the cabling.

Have you tried initially creating it as a Public share to confirm if you have an authentication problem?

There is a discussion of Clear v Preclear here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.

Are you sure that Unraid has not disabled the device and is now emulating it? It might be worth posting your system's diagnostics zip file so we can check there for a problem.

The next steps would be to put an 'clean' install of Unraid onto another USB (no licence needed) to see if that loads indicating something in your configuration. You could try this for both the 6.12.4 and 6.12.5 releases.

Try removing the Mover Tuning plugin.

According to the diagnostics you are now running 6.12.5. You could try reverting to your previous release by copying the contents of the ‘Previous’ folder on the flash drive back to the top level, or by using the process described here in the online documentation to see if that solves the issue.

Have you tried connecting to http://192.168.50.217 which from the diagnostics looks like the IP address of your server? This would be because the array is not set to auto-start so until you get into the GUI to start it that is expected behavioyt.

Did you reboot the server after starting the Parity Sync? Just asking as it appears you have the Parity Check Tuning plugin installed and it has currently paused the Parity Sync (which it probably should not have) after restarting the sync as you have the restart option set. You could try disabling that option or even removing the plugin for the time being to see if that helps.

Try removing the Mover Tuning plugin.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread so we can get an idea of what might be going on.

The settings in your screenshot only set the server listening for messages. To get it to log the server it is running on you need to set one of the last two fields as mentioned in the documentation for setting up the syslog server.

Have you tried going to http;//192.168.1.11 which appears to be the address of your server. it appears the link is only trying to operate at 100Mbps instead of 1000Mbps. This can happen if the LAN cable in use does not have all pins connecting.

the plugin simply tells Unraid to resume the operation that was in progress when the array was shut down. It is up to Unraid to decide what type of operation that is. The plugin will also only attempt the restart if it thinks the shutdown was a tidy shutdown. Having said that I will see if there is anything I can spot.

Yes, SMR drives can slow down when writing but should read at normal speeds. When there was a considerable price advantage to using SMR drive then it made sense with Unraid as it is most frequently used with media data that stays static once written so the write penalty was bearable.

No. A parity sync overwrites everything on a drive so existing contents are irrelevant. As a point to note a preclear is never NEEDED. It is just often done as a confidence check on a drive. You might find this section of the online documentation that discusses this to be of interest.

CMR is fine - it is SMR that can be very slow once the drives internal buffer gets full.

Yes - it is going to take forever. I normally expect it to take ~2 hours per TB as a rule of thumb so MUCH quicker than you are currently getting. Before doing anything you might want to have a quick look at the syslog (via button at top right of GUI to see the continual reset on ata2 (which is the parity2 drive) as that shows you the symptom in the log when you have such an issue.

Can you swap the disk to another position? Unraid does not care where drives are connected as it identifies them by serial number.

What about the power to the drive? The noises could be an indication of insufficient power. Do you use power splitters to get enough connections - they can cause problems. You could try swapping the power cables with another drive to see if the problem stays with the drive or moves with the cable change.