Woke up to two failed drives. I have two paritys so at least looks like I can recover, but another drive started shooting up in error count and hasn't shown failed yet.

 

The two initial drives have the exact same error count. This all happened during a parity check. 

 

I've had to replace a data drive before, assuming same procedure with my current issue? 

 

Looking for the best way to go about this of course. Thank you. 

Please post the diagnostics.

azeroth-diagnostics-20221114-1210.zip

Looks more like a power/connection problem, also and since the syslog rotated cannot see the LSI firmware version, make sure it's the last one available: 20.00.07.00.

Okay if it's just a connection or power issue, best way to get these back to a working state in the array?

If the emulated disk is mounting and contents look correct you can rebuild on top, ideally after checking/replacing cables, you can also re-sync parity at the same time.

Thank you for the response. Could you clarify what you mean by build on top?

8 minutes ago, JorgeB said:

If the emulated disk is mounting and contents look correct you can rebuild on top, ideally after checking/replacing cables, you can also re-sync parity at the same time.

It's showing correctly. 

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

 

You can do both at the same time.

On 11/14/2022 at 1:35 PM, JorgeB said:

Looks more like a power/connection problem, also and since the syslog rotated cannot see the LSI firmware version, make sure it's the last one available: 20.00.07.00.

LSISAS2008: FWVersion(20.00.07.00)

Edited November 15, 20223 yr by slimshizn

On 11/14/2022 at 2:14 PM, JorgeB said:

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

 

You can do both at the same time.

So the data drive has become unmountable, so I'm running xfs_repair in maintenance mode. With a 12TB drive, I'm guessing it will take a while? waiting on a ton of `.....` for about 2 hours now.

Ran across https://forums.opensuse.org/showthread.php/537139-How-to-perform-xfs_repair-on-encrypted-partition. The disk is encrypted and shows unlocked in the gui. Not sure if that matters.

Post the output from the xfs_repair.

On 11/17/2022 at 3:09 AM, JorgeB said:

Post the output from the xfs_repair.

Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

I just started it. I'll let it run. With it being 12TB, should I be waiting days?

 

"Swap file start during array mount is disabled" is also showing up besides "Array Started" at the bottom right now. I'm guessing since I'm in maintenance mode. Haven't seen that before. Just a host of issues I need to work through to get back up and running. Going on a week now with my server down and out.

I also sent a support email out and linked this post trying to get more attention to the matter since I'm sitting at a week offline.

9 hours ago, slimshizn said:

Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

I just started it. I'll let it run. With it being 12TB, should I be waiting days?

 

Going on 9 hours so far, just making sure that this will have an output eventually and should let it continue to run, or I should stop it and find another way to fix the disk?

I tried removing it from the array, starting it, stopping it, re adding, and starting. The array shows "unmountable: volume not encrypted"

Here are some threads I've looked through

 

https://wiki.unraid.net/index.php/Check_Disk_Filesystems#xfs_repair

Essentially I've done what the wiki has told me to do, and now am stuck at

"attempting to find secondary superblock..."
"..................................................................................." on and on.

Started a new topic as this has moved to a different issue entirely.
https://forums.unraid.net/topic/131193-unmountable-volume-not-encrypted/