SO, not having 2 parity discs appears to have bitten me in the arse.

 

My parity disc is showing a red x and one of my data disc in not mountable [image attached].

 

The data disc is under warranty with free data recovery so its a maybe for getting the data back but in the meantime because the party appears to have failed I can't rebuild either.

 

What are my options for getting the server back up and running without the data [hoping that I will get it back from the data recovery service]?

 

If I rebuild the array, do all my apps still know where everything is? Or am I going to need to effectively start with a fresh UnRaid install  and reinstall everything from scratch? I now have enough replacements to run 2 parity but need a path to get back to operational [preferably] without starting from scratch.

 

Diags attached.

 

Thanks

greatwhite-diagnostics-20220922-1309.zip

Disabled and unmountable are two different things, were is the old disk9? It's not in the diags posted.

3 hours ago, JorgeB said:

Disabled and unmountable are two different things

And parity won't fix unmountable.

 

3 hours ago, JorgeB said:

were is the old disk9

Without valid parity you must have that disk to repair its filesystem and make it mountable again.

3 hours ago, JorgeB said:

Disabled and unmountable are two different things, were is the old disk9? It's not in the diags posted.

The old disc 9 is in a box ready to ship off to Seagate to have data recovery attempted on it.

 

23 minutes ago, trurl said:

And parity won't fix unmountable.

 

Without valid parity you must have that disk to repair its filesystem and make it mountable again.

I can pull it out of the box and plug it back in but then how do I attempt the repair?

2 minutes ago, ddm73 said:

pull it out of the box and plug it back in

Do that then start the array and post new diagnostics

Before that, go to Disk Settings and disable Autostart.

 

Your diagnostics indicate you had already added parity2 and also removed disk9, which doesn't agree with your screenshot.

 

But you hadn't yet started the array to begin parity build on the 2 parity disks. Is that still correct?

 

Do you think parity1 was valid before it became disabled?

 

24 minutes ago, trurl said:

Do that then start the array and post new diagnostics

Old disc reinstalled and new Diags attached.

greatwhite-diagnostics-20220922-2246.zip

17 minutes ago, trurl said:

Before that, go to Disk Settings and disable Autostart.

 

Sorry, Didn't see this before I reinstalled and restarted.

14 minutes ago, trurl said:

Your diagnostics indicate you had already added parity2 and also removed disk9, which doesn't agree with your screenshot.

 

But you hadn't yet started the array to begin parity build on the 2 parity disks. Is that still correct?

 

Do you think parity1 was valid before it became disabled?

 

The screen shot was prior to adding the 2nd parity but I didn't start the array with the new parity disc. So the array is back to how it was when it failed. I don't have any reason to suspect that the parity wasn't valid before it became disabled.

OK, the only reason I didn't want the array to start automatically is because I thought it might try to build both parity.

 

The standard thing to do now would be to try to repair filesystem on disk9, but I wonder if it would be useful to get parity back into the array so we could emulate disk9.

 

Just thinking out loud here, see if @JorgeB has any thoughts.

 

 

 

 

I guess check filesystem on disk9 wouldn't change anything as long as you do it with -n.

 

Check filesystem on disk9 (with -n). Be sure to capture the output so you can post it.

3 minutes ago, trurl said:

I guess check filesystem on disk9 wouldn't change anything as long as you do it with -n.

 

Check filesystem on disk9 (with -n). Be sure to capture the output so you can post it.

Sorry, I should have pointed out that you have a bit of a noob here. I can muddle my way through most things but Linux command line isn't one of them. Unless the check filesystem [with -n] isn't on the command line in which case I clearly even more lost than I thought. [I hope the comical self deprecation is coming through in my comments!!]

7 minutes ago, trurl said:

I guess check filesystem on disk9 wouldn't change anything as long as you do it with -n.

 

Check filesystem on disk9 (with -n). Be sure to capture the output so you can post it.

Is this what you mean?

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

Check filesystem in my post and your post and in any other post it appears in on the forum is a link explaining how to check filesystem. You want to do it from the webUI. It is possible to do it from the command line but webUI will do it correctly and you might get the command wrong.

2 minutes ago, trurl said:

Check filesystem in my post and your post and in any other post it appears in on the forum is a link explaining how to check filesystem. You want to do it from the webUI. It is possible to do it from the command line but webUI will do it correctly and you might get the command wrong.

Got it. Didn't think to click what was clearly a link!! 

By the way, SMART for disk9 looks fine except for 3 CRC errors and these are connection problems not disk problems. The disk firmware records these when it receives inconsistent data (checksum). (It can't know about any connection problem where it doesn't receive any data.)

 

51 minutes ago, ddm73 said:

ship off to Seagate to have data recovery attempted

Is this data so important you were willing to pay for data recovery?

15 minutes ago, trurl said:

I guess check filesystem on disk9 wouldn't change anything as long as you do it with -n.

 

Check filesystem on disk9 (with -n). Be sure to capture the output so you can post it.

Here you go.

 

20220922 - file system check - Disc9 - GreatWhite.txt

And regardless of the outcome, A huge thanks for the help and responsiveness!!

Run xfs_repair again without -n, and if it asks for -L use it.

14 minutes ago, JorgeB said:

Run xfs_repair again without -n, and if it asks for -L use it.

Do I restart the array in normal mode now?

20220922 - file system check -L - Disc9 - GreatWhite.txt

Yep.

6 minutes ago, JorgeB said:

Yep.

You guys are awesome!!!

Now I wonder what the go is with the parity disc?? should I just replace it with the new one I have there?

Parity disk looks healthy, re-sync it and if there are issues post new diags before rebooting.

Check if you have a new 'lost+found' user share and see what is there that repair couldn't figure out.

4 minutes ago, ddm73 said:

the parity disc?

SMART for parity looked good in earlier diagnostics. You can rebuild on top.

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