diag attached.

I have had four drives fail in the last few weeks,  nothing changed physcially.

 

While recovering from dual HDD failure (have two parity - phew!) yet another has dropped and one also in error

I"m worried, what should I be looking at / for?

Any advise gratefully received..

 

server-diagnostics-20220406-1830.zip

Syslog isn't complete, but disks are dropping offline and reconnecting, this is usually a power/connection problem, see if the disks share something in common like a minSAS cable or a power splitter, if not the PSU would be the main suspect.

Thanks, will go check!.

Ok I checked and it's almost certainly power, all drives which barfed were on the same cable.  I was not able to replace all components but that which I could has been replaced and all reseated and run more neatly...

 

Unraid started up again but now one of the drives shows as unmountable, new diag attached.

As it shows unmountable and so not emulated, have I just lost data??

 

server-diagnostics-20220406-2034.zip

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

It is emulated, but the emulated disk is unmountable. Best approach is to repair the emulated filesystem, then rebuild to a different disk and keep the original as is just in case.

 

Looks like it is currently rebuilding parity2. You can let that complete, or stop it to do the repair.

Or it could be the physical disk is mountable, in which case you could New Config it back into the array and rebuild both parity. Any writes to the emulated disk since it became disabled would be lost, but since it doesn't mount probably no writes could be done.

 

Lets see what @JorgeB thinks.

Thank-you.

I paused the parity rebuild, and fixed the fs in maint mode.

 

Just restarted and partiy build is continuing on 2nd parity disk.

Failed drive still emulated (red cross) but does not show unmountable any more.

 

I have a spare drive so once parity2 is done I'll rebuild to that one..

1 minute ago, fysmd said:

fixed the fs

Did anything end up in lost+found share?

some but I've no way to knowing what they are/were

(or do I!?)

 

Repair often can't determine what folder a file belongs in, or even what the filename was. Linux "file" command might help determine what type of file they are. You can examine those files or any others on the emulated disk to see if you can figure out what they are or what is missing.

And the original disk, if mountable, might be another way to figure out what they are or what is missing and copy them from the original.

Thanks for your help.  My drives have remained stable and parity2 (just) completed building.

 

I need to work out how to get the probably-fine-but out of the darray drive back in there now but I'l going to leave it for another day - for us both to recover a bit

Bought some larger drives for parity(s) so they can go in once all back to normal..

 

KR

Ian.