elecgnosis

Thanks again, and I just might. Should I run the correcting parity check in maintenance mode? Does it matter at this point?

Okay, done omni-diagnostics-20250528-1024.zip

I started in maintenance mode, do you mean for me to start the array normally?

Okay, thanks for your help. omni-diagnostics-20250528-0731.zip

omni-diagnostics-20250527-1643.zip

Tried to replace 12TB drive 15 with precleared 20TB drive. Data-rebuild began okay. Hours later, drive 11 starts throwing read errors and eventually gets auto-removed from the array, contents emulated. I paused the data-rebuild. I went to the now-unassigned drive 11 (disk sdaa under unassigned devices) and ran its extended Smart report. Took over a day, but cleared with no error. I pulled diagnostics at this time. (attached omni-diagnostics-20250526-1437) I read that in cases like this, it (might) be power and connectors. I stopped the array. I opened the case and checked drive SAS and power connectors. I hot-swapped an unassigned hot spare with the original 12TB drive that was going to be replaced. In the array config in Main, I replaced the precleared 20TB drive with the original 12TB in slot 15. I took a screenshot to confirm drive assignments. In Tools, I set a new config, preserving all assignments. I confirmed drive positions with the screenshot. I marked parity as valid. I started the array in maintenance mode. I pulled another set of diagnostics. (attached omni-diagnostics-20250526-1521) What should I do next to make sure that drive 11 is good? Should I run a parity-sync without writing corrections? omni-diagnostics-20250526-1437.zip omni-diagnostics-20250526-1521.zip

I started the array with a new config and almost immediately got errors on a different drive than I was having trouble with before. I'm going to go through the same Smart/Scrub checks, but I'm not expecting any surprises. Previously, I was running off of a voltage-regulating UPS. I didn't keep it during the move, so I wonder if that's the secret sauce here. I'm using an 850W power supply that has been rock-solid otherwise. I have a new UPS coming, but not for a couple weeks. If I still have trouble on the other side of that, I'll look into replacing the power supply. Marking this as solved for now.

Thanks. Do you have any guidance for the UI not responding? I can force a shutdown if I have to, I'm just trying to avoid it.

Forgot the files, here they are. omni-diagnostics-20231110-1910.zip

After moving recently, I started a new parity check to see whether my disks were still okay. Later, I checked in on it and it seemed to have ran for about six hours, then quit with read errors on disk 1 and connectivity problems with five other drives. There were also UDMA errors on a hot spare that didn't even have any data on it, besides a preclear record. I shut down the server without downloading diagnostics (sorry). I checked how secure data and power cables were, moved some drives around in the server's slots, then powered back on. Next I unassigned the drive with read errors and mounted it in unassigned devices. I ran a BTRFS scrub. It returned an exit code of 0, meaning no errors. Then I ran an extended SMART scan on it and all of the other drives that had connectivity problems. Hopefully those show up in the diagnostics I've included here. Today, I tried reassigning my hot spare to the array in the position that the read error disk had. I accepted that the replacement drive would be rebuilt over and started the array. The operation didn't run for very long before the replacement drive came up with read errors, putting it in an unmountable state. I tried to stop the array, but none of the server buttons in Main are responding. I tried stopping the read-check as well, but nothing is responding there. I can click around the interface to do other things, just not this. I was able to pull both diagnostics and the system log. I also noticed that the system log had an error for /var/log being 97% full. I don't know if that's why the UI is acting like it is. The last time I was dealing with something like this, I remember finding something on the forum saying that stopping loop2 could get it to work again, but I haven't tried that yet. The BTRFS scrub leads me to believe that the original drive with the read error is okay. Should I just do a new config? I'll take any other steps you folks think I should try, otherwise.

I ended up doing a new configuration, sacrificing parity. I then spent the last week doing BTRFS scrubs on all of the original array drives, even the first one that had reported errors. All finished without errors. I'm rebuilding parity now.

I found these steps to try, and after mounting the drive, it appears that the data is still there. However, there's 9TB of data to back up. I don't have 9TB of free space available on any individual drive in the array, though I guess I could still back it up if I distribute the directories across multiple drives. Or I could swap the drive and let parity rebuild the data for me. Unless any of you think there's another route to fixed here that doesn't involve waiting ten days to write 18TB of data, that's the option I'm going to go with. I will hold on to the troubled drive in case something happens during the parity rebuild.

I was away from home for a week and when I got back, I noticed I had an error in Unraid. Something was wrong with a two-year-old drive. I shut down the server, checked the cables, and also moved the drive to another slot. The next startup, it appeared that the drive that I swapped its slot with also had a problem, so I shut down again and shuffled more drives around. This last startup, the one that I posted diagnostics from, still showed the first problem drive as "Unmountable: Unsupported or no file system" but at least it was the only one that seemed to be bad. I'm not sure how to proceed. I could just replace it with a hot spare, but I've seen some posts here where people in similar situations were able to repair or restore the file system and even add the drive back to the array. Diagnostics posted, please advise. my-diagnostics-20230715-1652.zip

That got it. Cables secured, moved drive 11 to another physical position, started back up. Data-rebuild running now. Good enough to call it solved for now, thank you.

I've cancelled the data-rebuild in the UI, but it doesn't seem to do anything. Should I just use the shutdown button? Latest diagnostics attached. omni-diagnostics-20230511-1102.zip