hoping for some assistance with my unraid system after a unclean shut down. I now have a drive that unmountable and it says my parity is not valid. 

 

For some back story on exactly what happened. lost power to system and when it came back online i had to re-assign all of the drives but one came up as unmountable. at that time it started doing a parity check saying parity was not valid. I then took the array offline and unsure how to proceed. if I bring the array online I can open a few folders and see files so I know everything is not lost. Looking for some assistance recovering what I can.

 

Unraid v 6.1.9 

 

any assistance is greatly appreciated. 

 

thanks

 

Keith

 

I just created my account today so it looks like I will not be able to make any more posts after this. If someone is able to assist or ask questions I will update this original post. thanks

 

 

 

 

Edited October 10, 20187 yr by KTgsxr
new user

Please post up the Diagnostics file    Tools    >>>   Diagnostics      with your next post.  Plus, tell us which disks are the ones that you think there is an issue with by Disk number or the last four digits of the serial number.  

thank you for the response I have attached the requested file

and last 4 of the Serial # is 3444e. 

tower-diagnostics-20181010-1457.zip

4 hours ago, KTgsxr said:

For some back story on exactly what happened. lost power to system and when it came back online i had to re-assign all of the drives

This is an old bug on v6.1.9, you should have upgraded long ago.

 

Please post new diags after starting the array, with or without parity assigned, as long as you're sure which drive is parity, especially since parity and disk1 are showing a RAID id, not the actual disk model/serial, if earlier you assigned the wrong disk as parity and a parity sync started it may now be unrecoverable.

 

 

 

 

that is possible I might have assigned the wrong disk. I thought it would stop me if I did not recognize it as the correct one. The server has just been up and running has not chacked for updates as was not having any issues. 

2 minutes ago, KTgsxr said:

I thought it would stop me if I did not recognize it as the correct one.

No, when doing a new config (and this bug acts as a new config) all disks are considered new, Unraid has no idea which disk was which and lets you assigned them any way you want.

 

Do another new config and assign all disks as data disks, leave parity unassigned, start the array and post new diags.

here you go. thank you again for trying to help me out

tower-diagnostics-20181010-1530.zip

Maybe I wasn't very clear before, leave parity slot empty but assign all disks as data disks, including the one that was assigned as parity, one disk is still unassigned:

 

Oct 10 15:29:39 Tower emhttp: 35000c5003e135973 (sde) 1953514584

 

Assigned it as disk7, start the array and new diags

never mind it let me 

tower-diagnostics-20181010-1553.zip

Edited October 10, 20187 yr by KTgsxr

if i'm seeing this correctly now that have that disk mounted as disk 7 I can see files on it. so i'm guessing this was not my parity drive. the drive that is not able to be mounted is my parity drive. should I repair that unmountable drive and put it back as parity and allow it to rebuild? I will wait to hear from you but this is looking promising.

 

thank you

 

so it looks like I now just need to figure out how to change my disk 1 back to my Parity drive. Even tho its unmountable i can not start the array without disk 1 and cant not just move it up.

 

How can change my array back to a 6 disk setup and then move the 7th back to Parity?

 

I really do appreciate the help as it now looks like I have not lost any data which I was sure I was pretty sure I had. 

 

Disk7 still mounts, that's good news, just do another new config, this time assign disk1 as parity, you can check parity is already valid since it mostly is but then run a correcting parity check.

Thanks I did that late last night and  just got back it check and it has finished parity sync. everything appears good! My Docker tab was missing  and had to disable/renable that and thats working now. I think i'm fully working with no lost files. I'm going to go ahead and update to a newer version. thank you for all your help.

 

Keith