The_N4RF

I'm always so amazed when perfect strangers will help me in the internet ;). Thanks for the response, no I have no idea why Parity 2 would be getting all the errors. It's the only drive that hasn't been touched by my upgrades? With your suggestion I'll "unpause" the parity check. I believe the "write corrections" box is already enabled, so full steam ahead.

Hi Everyone, I thought I better ask my question specifically since my precious data hangs in the balance. I recently charged ahead to upgrade my 3x 2TB array with 4TB drives after one of the 2TB drives failed. Along the way I had to upgrade a 3TB parity as well. This whole process did not go smoothly, but eventually I thought it was back up to snuff. The initial parity check after the last attempt finished successfully (one of the "new" drives failed and had to be replaced again). However, during a parity check today I noticed the sync errors were skyrocketing in the hundreds of millions, with thousands being added every second. I haven't noticed any data access issues or other instability. Some of the new drives run hotter under load than the old 2TB drives (41-43c). I'm a habitual tinkerer, so I fear my unraid config is far from "vanilla". Unraid 6.12.6 onprem-diagnostics-20241202-1359.zip

Has anyone had this issue with autodiscripper? It just cycles through startup with this error. Standard ripping (via the GUI) is working fine. [autodiscripper] ERROR: Cannot access state directory. Verify UMASK value. I've already confirmed both the default and autodiscripper directories are 777. Thanks!

Yes, Windows automatically uppercases anything you put on the drive name. Good clarification.

Confirmed this also worked for my SanDisk FIT 16GB USB2 drive. Renaming to "unraid" through file explorer _while_ the tool is stuck at "syncing the filesystem" allowed the deployment to continue. Anecdotally this seems to relate to >8GB drives. All of my other drives worked fine, but this is the first >8GB drive I've deployed to.