Help. I messed up while doing a rebuild on one of my drives and cut power midway. 

Now the other good drive is saying it is unmountable. 

If I let the rebuild complete can I get the data back from the other disk that says its unmountable? 

I have 1x 8tb parity drive and 2x 4gb in array

 

New to unraid 

Attach Diagnostics to your NEXT post in this thread 

tower-diagnostics-20240226-2134.zip

Emulated disk2 is mounted and has plenty of data. Rebuild seemed to be going OK.

 

2 hours ago, samth3kiwi said:

If I let the rebuild complete can I get the data back from the other disk that says its unmountable?

Should be OK. At least, letting rebuild complete shouldn't make it any worse than it is. We can check filesystem on disk1 after.

 

2 hours ago, samth3kiwi said:

I have 1x 8tb parity drive and 2x 4gb in array

Just in case you have some misunderstanding. Parity that large will allow you to use 8TB data disks in the array. Parity doesn't have to be any larger than the largest single array data disk.

 

Parity is not a backup and doesn't contain any of your data. It is just an extra bit that allows a missing disk to be calculated from all the other disks.

 

I would expect 4TB rebuild to take 8-12 hours. How long does it say for rebuild to complete?

 

Any Errors in the Errors column in Main - Array Devices?

Hi thanks for the reply. I have let the data rebuild on the disk 2 . Stopped the array and started in maintenence mode and checked disk 1. It came back to mount and unmount.

I tried the repair and didn't like it . So I tried the repair with deleting logs and is now doing a rebuild. Does show my data so will let that finish and hopefully that will sort it.

 

Is there any way to get back my docker set up as before problem? Everything was gone. Or do I need to set up again?

 

Yea I know that I don't need to use larger disk for parity. More for future upgrades. Plan on putting larger disks in future

I don't understand why you are rebuilding disk1. It wasn't disabled. All you needed to do for that disk was check filesystem.

 

Attach diagnostics to your NEXT post in this thread.

Just some forum advice. Please post screenshots and not photos.

Hmm OK. After I did the disc check with -L it showed data on the disc. And tried start array and that's when the rebuild started. 

 

Might not of done it correctly or right process. Not really sure to be honest still learning. 

 

Hopefully it will be OK. No critical on the drive just bit of a pain to re download 

7 minutes ago, samth3kiwi said:

tried start array and that's when the rebuild started

You must have left some things out of your explanation. If the disk wasn't disabled/emulated, it would not be rebuilt when you started the array.

 

Did you perhaps unassign the disk?

Ahh yes I think I might of got confused with mount and unmount and unassigned and assigned. I guess they are different? 

I didn't really have a lot of time this morning and wanted to get it started before I went to work. 

It is still going now but my file structure is the same as before. So hoping it will be fixed even if I have done extra steps 

3 hours ago, samth3kiwi said:

confused with mount and unmount and unassigned and assigned

mount is when the OS gets the filesystem ready for access. Not at all related to installing or assigning a disk.

 

12 hours ago, samth3kiwi said:

Stopped the array and started in maintenence mode and checked disk 1. It came back to mount and unmount.

Probably what you got was xfs_repair telling you to mount the disk so it could try to play back the log, or else you would have to let it delete the log with -L so it could proceed. Unraid had already determined the disk was unmountable, but xfs_repair doesn't know about that so it just followed its "script".

 

25 minutes ago, trurl said:

Not at all related to installing or assigning a disk.

Well, obviously you can't mount a disk that isn't installed. You can mount an unassigned disk though.