I had something happen the other night with one of my 5x3 drive cages. Think one of the ports went bad, and I didnt notice my server was getting read errors on one drive and another drive was listed as missing seemed to be two main issues.

 

Regardless one thing led to another and I rebooted the server. Everytime running into various but different config issues. 

Eventually I took all the drives (5) out of the cage and powered each up separately and reconnected them. During this whole process Disk 9 keep coming back as either missing or unmountable. I think my partiy might have become corrupt during the problems.

Last night I rebuilt the Drive 9 without issue. Everything seemed fine. But then I put all the drive back into the tower and rebooted the system back up, once again, Disk 9 came back unmountable.

Do I need to run a "New Config" after the rebuild?

Or is the actual parity as is now, screwed up beyond repair and I have to instead find a way to get the data off the drive without rebuilding it.

I was about to rebuild again, then run "New config" and reboot, but after 2 days of that happening, my fear is yet again getting "Unmountable" upon restart of server and I am back to square one after wasting multiple days. 

Wanted to know if anyone could just point me in correct direction so the time to repair/fix the issue isn't wasted on trial and error.

matrix-diagnostics-20240517-0820.zip

Edited May 17, 20242 yr by Cornbreadman

DIsk9 needed a filesystem check, but it was formatted instead, so now it's mounting, but of course the data will be gone.

So once rebuild is done, what would be my best course of action? When I reboot something is causing the drive to be unmountable again. 

Should I run a filesystem check before rebooting, to make sure everything looks good?

Would a new config help anything? 

Once the rebuild is done reboot and post new diags if the disk is unmountable again.

Just finished. And before even restarting seeing that Disk 9 is empty now. So looks like that data is gone from the parity somehow.

Before reboot, as rebuild was finishing up.

 

After reboot, all drive assignments are different.

 

 

Haven't started the array. That is where everything went wrong last time, and the disk came back unmountable.

matrix-diagnostics-20240518-0526.zip

Edited May 18, 20242 yr by Cornbreadman

14 minutes ago, Cornbreadman said:

And before even restarting seeing that Disk 9 is empty now.

That's expected:

20 hours ago, JorgeB said:

but it was formatted instead, so now it's mounting, but of course the data will be gone.

 

15 minutes ago, Cornbreadman said:

all drive assignments are different.

Not sure what you mean, they look the same to me, post new diags after array start.

9 minutes ago, JorgeB said:

That's expected:

 

But shouldn't it have rebuilt from parity? 

edit: nevermind, just realized I formatted it while array was running, making it the new parity. Great.

 

Started array. EVerything green.

matrix-diagnostics-20240518-0537.zip

Edited May 18, 20242 yr by Cornbreadman

Back to issues.

 

 

Disk 4 is emulated 

Disk 9 has errors showing

 

 

matrix-diagnostics-20240518-2326.zip

It's not logged as a disk problem, looks more like a power/connection issue, replace both cables.

 

Also, any reason why your are running an old release candidate? Update to latest stable.