One of my HDD went out. I purchased a new HDD and it started to rebuild. I have now had the rebuild process cancel and stop the array for no reason that I can find. I thought it could be the HDD, because they were recertified drives, but I returned the 2 I had and bought brand new ones, it still does it.

 

Please help. I'm still kind of new to this.

tower-diagnostics-20250311-0954.zip

Disk4 rebuild seemed to be going OK in those, but it had just started when you took them.

Mar 11 09:54:02 TOWER kernel: md: recovery thread: recon D4 ...

Can't tell what might have happened before boot since those logs are gone unless you had syslog server setup to save them somewhere.

 

During rebuild, there should be lots in the READS columns of all other disks, lots in the WRITES column of disk4, zeros in the ERRORS column for all disks.

 

If it begins to have problems get new diagnostics and post them.

I was hoping the file would have everything since it didn't reboot the server, just stopped the array.

 

Since this is ongoing, I'll look into syslog saving.

 

I'll update if it happens again. Thanks!

rebooted here:

Mar 11 05:02:26 TOWER kernel: Linux version 6.1.118-Unraid (root@Develop-612) (gcc (GCC) 12.2.0, GNU ld version 2.40-slack151) #1 SMP PREEMPT_DYNAMIC Thu Nov 21 15:54:38 PST 2024

but array not started until here:

Mar 11 09:53:46 TOWER emhttpd: Mounting disks...

 

It rebooted itself at 5 in the morning?  What on earth. I don't think there is anything that would schedule a reboot, is there?

Looking at the syslog-previous in the diagnostics an explicit reboot was issued just after 05:00.   Looks like that is scheduled to run (probably in User Scripts).

Crap! You are right. I was trying to get it to reboot automatically several months ago and didn't think it worked and then got distracted. So it's been running this whole time. It wasn't the HDD's, it was that stupid script.

 

Thanks! I greatly appreciate the help.