I had to replace a failed drive that had the "dreaded" Red X.  OK, no problem. Followed the normal procedure to replace with a new drive of the same size.  That's where the fun started.

 

Formatted the drive, no problem....assigned it, no problem. Then I started having the array stuck on getting started. Did reboot to bring it back. disabled the new drive. Then brought it back, finally got array running and data rebuild started.

 

Data rebuild is running really, really slow. I've attached screenshot.  It's a 20 TB drive so I know it will take forever, but the data transfers are extremely slow and I'm not seeing any read/writes going on or errors.  

 

I looked at the diagnostics and I'm seeing the new drive marked invalid?  HUH??

 

Any ideas???

 

Thanks in advance

tower-diagnostics-20250502-1415.zip

Going to see if a different drive works

Nope! Different drive, changed cables. Ensured all cables seated fully. Same thing.  What is throwing me is I turned off all my dockers and cache was still writing. Even as the rebuild was slowly going down to 2.3mb/sec. Other thing throwing me is I ran a check and it said, like the first one, "invalid disk".....

 

Going to try something different. Going to assigned drive to a different slot and let it clear then format again. Then hope it works. If not, my "Hail Mary" might be to try new config and keep all the drives the same except the new one and see what happens.  I've honestly never had this happen before

tower-diagnostics-20250502-2001.zip

Edited May 3, 20251 yr by isrdude
additional info

Looks like a power/connection issue with that drive.

Hi Jorge....been awhile.  I changed up the SATAs, I'll need to recheck the power connection again.  I'm suspecting, now that you mentioned, the surge before the power outage that killed the disk, might have done in a power cable then.  Thanks. I'll check that too.

 

I'm wass planning on putting in the original disk since I keep getting the RED X invalid on that slot, to see if I could put it in again, fire it up, stop the array, remove the disk, reboot, power down, put in the disk that I'm preclearing now.  I figured I might as well use the time to test the new disk with a preclear before wasting more time.  Worst case, I rebuild as a new drive with lost data and pull over the data from my backup to rebuild.  Rather not go that route, but it's an option if the above don't work.  Hope I have some different power cables.....

Hi Jorge

What I ended up doing was letting the new disk preclear in a new assigned slot to ensure the power/data cabling all worked.  Then I had to remove the precleared drive but first I took it out of the drive history.  Then I removed it. restarted, went to new config. and did the ALL config.  After that, put all the drives back into the original assigned slots, including the drive that got knocked out,  Restarted the Array and did parity check/rebuild. 2 hours later, parity checked ok.  And all is good again.  I think I ran through every check and way to save data that exist!