Seanmc980

The disk replacement went smooth. It was rebuilt in about 12 hours. I assumed, after the rebuild, that it would run a parity check, considering the freeze during the initial pre clear and the freeze during the following parity check.. the array shows started and it's states that parity is valid. It shows that the last parity check was today at 8:01am. This is confusing because the parity checks alone have typically taken my system over 24 hours.. I'm attaching my latest diagnostics. Should I just run a parity check, or am I good?? Thanks!btch-diagnostics-20260107-1203.zip

Thanks Trurl! Giving it a go now.

Ok, I clicked on the failing disk (2) and removed it. Started the array (had to check the box) and ran the diagnostics btch-diagnostics-20260106-1649.zip

My concern is that the server crashed during the pre clear of the new drive, then crashed during the parity check.. I didn't want to get my server into a position where I was trying to do too much at once and make matters worse. I did shut the server down, reseated all connections, removed several unassigned drives that were there just to move files around. I'd like to just swap the failing 2TB with the new 12TB, but wanted to be sure this was the right approach.. I didn't want to start the array yet, because the parity check had previously failed. I'm just looking for the best advise to move forward.

Ohh sorry! btch-diagnostics-20260106-1445.zip

btch-smart-20260106-1102.zip

I have an UNRAID setup with (1) 12TB parity, (2) 12TB disks and (1) 2TB disk. The system has been on battery backup and running for almost 500 days. I needed more storage, so I ordered another 12TB drive. I used the pre clear plugin and after almost 2 full days, it was at 98%. When I went to check on it later that night, the UNRAID GUI was acting weird, nothing was loading, I couldn't stop the array, I wasn't able to SSH into the server (it's remote). I left it overnight and found it the same in the morning. I had someone physically power it down. I started the array and noticed the the 2TB drive was showing an unhealthy SMART icon. I was already planning on moving this drive out once I got the new 12TB drive up. The parity check was around 8% when I went to bed, when I woke up, I wasn't able to remote in. The UNRAID was unresponsive. I got the server back up and left it stopped. I ran a short smart test on the 2TB and threw the logs into chatGTP. ChatGPT said that based off of the logs, the drive is failing, has been for awhile and would explain the freezing during the pre clear and parity check.. it suggested to remove the 2TB drive, assign the new 12TB in it's place, then rebuild the 2TB to the 12TB, then after that, run the parity check. I've had ChatGPT burn me before, so I'm checking in on the experts. Is this good advise? I wasn't able to find any previous logs because I guess these are stored in RAM? I can setup a syslog server if anyone highly recommends me to? I know these freezes are typically hardware related.. I'm just looking for the best advise. Thanks

The other drives (without errors) are all being powered off the built in harness Sata power, so this does point towards bad connection/bad power.

This drive was powered by an expansion sata power connector.. one of those old style HDD to Sata power adapters.. the one power cable was split three times to power 2 fans, then the sata adapter.. it was powering 4 drives, including the one with errors.. I wasn't aware that this was a terrible idea, until now. The power supply is an older modular ATX style, but I lost all the expansion cables in a move.. new power supply ordered, server shut down until I get it swapped and properly powered.. I'll report back when I get it retested. Thanks for your time.

How can you tell? I can replace the power cable and swap sata. I'll report back.

I tried the steps you suggested, but the drive came back with errors. It's paused at 10% of the rebuild/sync. I've attached the diagnosis zip..what should I do know? btch-diagnostics-20230911-0632.zip

I did reboot, like mentioned. Hopefully something in these logs will be helpful. Thank you btch-diagnostics-20230910-2024.zip

Hello, I went to shut down my server and noticed that one of my drives in the array had a red X next to it. It listed 64 errors in the column. I tried to restart hoping that a reboot would just fix the issue (knowing that it probably wouldn't) but the drive is still red. When I first noticed this, the drive was missing it's temperature reading. The system hung and never rebooted. I issued a shutdown, and eventually it did shut down, but it indicated that it wasn't a clean shut down. I started the array in maintenance mode and started a parity check.. I feel like this is probably a 20 hour waste of time, so i'm reaching out to support for help with getting this back up and running. After the reboot, the log files seemed to have cleared. The drive is still showing under the array but the drive's letters have changed.. it went from SDK to SDG and the drive is shown below in under historical device.. This array is made up of 4 12TB drives, with 1 parity, 1 2TB drives and 3 unassigned drives. I want to make sure I perform the right steps, this is my main server for all my media and back ups.. I really do not want to screw this up, please someone walk me through the process.. I found a couple of forum posts, but they linked to outdated and removed posts.