Parity drive 01 is deactivated parity 02 seems to be okay, one Array Disk is now emulated :(

[ahab666]

Hello,

 

due to a general power outage, I found my server in that bad (or just annoying) situation.

What is the fastest way to restore the whole system - I am quite sure that there are no hardware problems with the HDD's a.s.o.

 

If you need any log files, please tell me how to generate and/or where to find them ....

 

Cheers - ahab

[itimpi]

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

[ahab666]

Off course - here is the diagnostic archive .....

tower-diagnostics-20230816-2026.zip

[JorgeB]

The usual way forward is just to rebuild the disabled disk and re-sync parity, you can do both at the same time.

[ahab666]

Hmm, THX 4 the quick answer - could you please describe it a bit more detailed - I am a complete *NIX noob

 

THX in advance

[JorgeB]

https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself

[ahab666]

@JorgeB

 

After reading the doc I am even more confused. 

I tried the unassign, reassign , re-sync (in maintenance mode) but I have got a buck load of read errors from my Parity 2 drive, something like 500 000 reads and with more than 20 Million errors. Also some of the emulated data seem to be destroyed = unreadable now.

 

Now I am SMART testing the 2 Parity and the "defective" Data drive in maintainence mode - short smart shows no errors, extended seems not to work at all, on the 2 Parity drives it the testing stops at 10%.

 

I am getting a little bit nervous now.

 

cheers

[JorgeB]

Post new diags.

[ahab666]

@JorgeB et al,

 

Extended SMART still running ATM at 50 % - still in maint mode 😞 I guess the diag module only makes sense if the array is started - does it ?

 

cheers  

[JorgeB]

You can post the current diags.

[ahab666]

@JorgeB et al,

 

here we go, sirs,  diagnostics - btw - both short and extended SMART Tests for both Parity disks are clean ....

 

BTW - during re-sync I am getting that drive is either full or something is flooding my syslog warning. the  memory usage for logging is constantly at 100 %

 

cheers

tower-diagnostics-20230819-1509.zip

Edited August 19, 2023 by ahab666
addendum

[JorgeB]

Unfortunately the logs are filled with these:

 

Aug 19 08:02:24 Tower rpc.mountd[9958]: refused mount request from 192.168.0.11 for /Shows (/Shows): unmatched host
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug 19 08:02:25 Tower rpc.mountd[9958]: refused mount request from 192.168.0.11 for /aomei (/aomei): unmatched host
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug 19 08:02:52 Tower rpc.mountd[9958]: refused mount request from 192.168.0.11 for /Audio (/Audio): unmatched host
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug 19 08:02:54 Tower rpc.mountd[9958]: refused mount request from 192.168.0.11 for /Data (/Data): unmatched host
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Aug 19 08:02:54 Tower rpc.mountd[9958]: refused mount request from 192.168.0.11 for /Isos (/Isos): unmatched host

 

Reboot and post new diags after array start.

[ahab666]

@JorgeB et al,

 

the 3 short and extended SMART tests are all error free, so far there are no errors on Parity 1, Parity 2 and/or the Data Drive in question.

here are 2 diag files the name explains what they are .... i could pack and send you the smart log files as well if you need them.

 

cheers

tower-diagnostics-20230820-1927 maint mode.zip tower-diagnostics-20230820-1937 norm. mode.zip

[ahab666]

rebuild is in progress 4.8 %  done atm - last attempt "stopped" at 4.6 - i am hopeful again ....

Edited August 20, 2023 by ahab666
update

[JorgeB]

Disks look good, and unlikely to have so many failed disks at the same time, shame the errors were not visible due to log spam, but rebuild and post new diags if it happens again, make sure the log spam is not continuing.

[ahab666]

okay - lets say the recovery of my data drive works out, and it changes back to a physical=not emulated state. How can I recover the first parity drive ?

Do I need to pre-clear it 1again and then rebuild parity ?

 

BTW 2 new diagnostic files one after the rebuild, one after a reboot and some maintenance (2 docker app updates)

 

 

cheers

tower-diagnostics-20230822-0900 after reboot.zip tower-diagnostics-20230822-0842 after rebuild.zip

Edited August 22, 2023 by ahab666
addendum

[JorgeB]

7 hours ago, ahab666 said:

How can I recover the first parity drive ?

Unassign parity, start array, stop array, re-assign parity, start array.

[ahab666]

I'd like to thank JorgeB for his patience - he helped me a ton !!!

At least I did not fall into dispair and precleared either my Data Drive nor the "failed" parity drive.

JorgeB you are the best thank you , thank you , thank you (x1000)