During parity rebuilding of replacement drive, another drive had read errors [SOLVED]

[elecgnosis]

I had an old, smaller drive I wanted to replace with a newer, larger drive. I precleared the new drive, shut down the entire server, removed the drive I wanted to replace, and set the new drive in its place. I also pulled one other drive out to check its serial number and re-seated it.

Next I powered up the server, set the new drive to replace the old in the array, and started the rebuild.

I checked the server this morning and it appears that another older drive (not the one I re-seated) has a rack of read errors. Checking some notes I had, it seems that mysterious read errors have hit this drive before, but amounted to nothing as re-seating it resolved those issues at that time.

My problem now is, I want to re-seat or even re-position that drive in the server, but I don't know how to do that without ruining the data rebuild currently in process. Do I need to stop the rebuild, shut down the server, re-seat/reposition/check cables or do whatever physical maintenance this seems to call for, then resume the rebuild, presuming that the "problem" drive is just having physical issues?

Edited May 11, 2023 by elecgnosis
Solved

[JorgeB]

Please post the diagnostics.

[elecgnosis]

Here it is:

omni-diagnostics-20230511-0714.zip

[JorgeB]

Disk11 dropped offline and reconnected again, disk is usually a power/connection issues, and SMART looks good, cancel the rebuild check/replace cables, and try again.

[elecgnosis]

Thank you, I'll get to it. If I don't run into any other trouble, I'll mark as [SOLVED].

[elecgnosis]

I've cancelled the data-rebuild in the UI, but it doesn't seem to do anything. Should I just use the shutdown button?

Latest diagnostics attached.

omni-diagnostics-20230511-1102.zip

[JorgeB]

Type 'reboot' in the console, after a couple of minutes it will try to force a shutdown, better than pressing the button, but if that also doesn't work do it.

[elecgnosis]

That got it. Cables secured, moved drive 11 to another physical position, started back up. Data-rebuild running now.

Good enough to call it solved for now, thank you.