All was fine and suddenly, this afternoon, my server showed a dead drive. As this is a drive I had issues with previously in another box, but seemed to be okay now, I figured it was the drive.

Stopped array, powered down, popped in replacement, everything went well. Asked me to format, no problem there, Mounted drive, started array, all seemed fine and suddenly I was getting rebuild times of around 2.6 mbs and dropped down to 130 kbs or so. Said it would take 765 days to rebuild my 20TB drive. Yikes. Stopped all and decided to pop in a new cable. This drive is CONNECTED to MOBO SATA CONTROLLER PORT.

Turned everything back on and now it takes forever to get the array to start if it will start at all. Just get the wavy orange lines. I decided to power off via the PSU. Rechecked the cables and connections. All good. Restarted, got everything up, started a preclear that looked good so I stopped it to see what would happen. Back to the array starting just as in the screen capture. I can't get diagnostics to download while it's doing this but I've attached the diagnostics I ran right before I had the array starting freeze. I've a BAAAAAAD feeling my mobo sata controller is going bad on a channel. Looking for input from the crowd.

Thanks

tower-diagnostics-20250611-2032.ziptower-diagnostics-20250611-2032.zip

tower-diagnostics-20250611-2032.zip

Did a hard reboot to get back in to download diagnostics. I've attached. After downloading diagnostics, I tried to start array again. Guess What??? Same issue, just stuck in a startup mode.

tower-diagnostics-20250611-2203.zip

See if you can get the syslog after attempting to start the array:

cp /var/log/syslog /boot/syslog.txt

Jorge

I tried to reboot in order to do ask you asked. Just booted straight to BIOS. Wireless nor wired keyboard would work. Tried to reset CMOS, same thing. I think not only the MOBO sata controller, but MOBO itself has died. I was going to try and roll back from 7.1.3 to 7.0.1 but can't even get that far now that I can't get out of BIOS. Going to try a new MOBO when it arrives and see what happens. If the array won't start, I'll try what you suggest again. Maybe even the rollback. I've never had a controller or mobo go bad but from what I can gather, this has all the symptoms.

Thanks

Just downgraded, back to where when I click start for the array, it just thinks about it and never comes online just like in my first instance. I'm starting to wonder if my PSU is going bad and it's a power issue.

Edited June 21, 20251 yr by isrdude
more info

Hi Jorge

I replaced the MOBO with a new one that I tested. Everything is fine on the MOBO. Booted up, started the data rebuild and same thing happened that started this. Started rebuild at around 16.3 mbs and dropped to KBs. Attaching the syslog and diagnostics.

I am going to rollback the OS as this all started after I undated the OS.

Thanks

tower-diagnostics-20250620-2100.zip tower-syslog-20250621-0059.zip

Replace cables for disk5, both power and SATA, and try again, then post new diags.

OK. Be the 4th cable on 5....still showing bad, dang. Going to get new PSU today. Will let you know.

Thanks again

OK, changed the cable (still don't think that was the issue) and put in new PSU....upped power from 750W to 850W. Mounted and now the drive is rebuilding. Been monitoring for 20 minutes now and it's showing a speed estimate of 195.2 mbs!!!

Lesson learned, PSU going down the tubes can mimic a MOBO controller going back. Swap out the PSU first! Oh well, I have a spare MOBO now. That's something.

Thanks Jorge