I'm trying to replace an 8TB drive with a 16TB drive. I started the rebuild like I have done in the past and it looks like it's working normally. But after about 4 hours, the web GUI became unreachable and I couldn't ping the server from the Windows PC. I restarted the server and was able to get back to the web GUI. It had a popup saying the parity check / rebuild finished in 4 hours, but obviously it didn't and starting the array again just started another rebuild. But that failed again after about 4 hours.

 

I can't put the original 8TB drive back in, because now it thinks the 16TB drive is the original one and says the 8TB is smaller than "the original".

 

What can I do here? And what could be causing the crash after 4 hours? The drive I'm adding is a WD Red Pro and I checked and erased it using Data Lifeguard Diagnostic for Windows before trying to add the first time.

 

Let me know if you need any more information from me. Thanks in advance for the help.

I did not have syslog mirroring to flash, so I just enabled that while my third attempt at a rebuild is running. If it crashes again, I'll post the syslog afterwards in here. Until then, I did pull a diagnostics file if anyone thinks it might be helpful.

tower-diagnostics-20231218-1843.zip

It failed again during the rebuild. I've attached the syslog. I don't really see anything so far, so I'd appreciate if anyone could take a look and see if they get any clues as to what's going on.

syslog

There's nothing relevant logged, suggesting a hardware issue, try with a different PSU if you have one.

My rebuild just finished successfully. While searching, I found this old thread: https://forums.unraid.net/topic/132371-unraid-crashes-during-data-rebuild/

 

So just to eliminate the possibility, I changed out the battery on my motherboard before trying another rebuild. Turns out it worked. Array is back up and 0 errors during the parity check. Thanks to anyone who looked through the logs to see if they could find anything.