I had an unmountable file system on one of my array drives after swapping out a failing thumb drive. I did every command I could find to try and save it, but no matter what it was always unmountable/no file system on disk.

Now Ive removed the drive, and readded it to the array, the issue Im having I THINK is my overall drive space used before the drive failure was at 58%. During the drive rebuild its at 31%, while also being emulated by the parity. Im around 12hrs into rebuild and my replaced drive is still showing no data on the drive, nor has my overall storage in use increased.

During a rebuild does the array space in use increase, or will I see everything just magically reappear upon completion of the rebuild.

Here are my logs as well, hope Im making sense with what Im trying to convey.

tower-diagnostics-20201222-1056.zip

No valid filesystem is being detected on disk3, also rebuilding an unmountable disk will result in the same.

The disk is mountable now, but it seems to have started rebuilding before it was formatted, Im guessing I screwed that away? Would a cancel and rebuild it again fix it?

17 minutes ago, feyded1020 said:

The disk is mountable now

Yes, missed that since it's at the end of the df list, disk was formatted, so it's mountable, but formatting deletes all the data in a disk, and updates parity accordingly:

 

So no matter what, everything on that drive was toast anyways? As I could not rebuild or repair it through terminal?

The only possibility now is using a file recovery util, like UFS explorer.