Messed up big time, tried adding a 2nd Parity Drive.

[RobinG]

used the the webUI, it fixed the file system. put it back in the array and now it is doing a data-rebuild. should i let it do that or is it overwriting all the old data?

[RobinG]

yes, disk 3 had no contents so i am not concerned with that one.

[RobinG]

i saw the 3ish tb on the drive when i had it in unassigned devices , moved it to the array and now there is nothing...

[RobinG]

[trurl]

Sorry, I think there has been some miscommunication. I meant for you to check filesystem on emulated disk3, not on the unassigned disk.

 

Post new diagnostics

[trurl]

It looks like you must have told it to format both unmountable disks in the array. So if you rebuild disk1 now, the result will be the same as the emulated disk, which has been formatted.

[trurl]

3 minutes ago, trurl said:

Sorry, I think there has been some miscommunication. I meant for you to check filesystem on emulated disk3, not on the unassigned disk.

Sorry again, I meant emulated disk1. We don't care about disk3.

[RobinG]

got you, i stopped the rebuild right away and moved disk1 to unsassigned.

 

[RobinG]

skynet-diagnostics-20240128-1608.zip

[trurl]

These diagnostics don't match your screenshot. Did you New Config unmountable disk1 back into the array? Or what?

[trurl]

I think you must have posted old diagnostics

[RobinG]

I didn't new config, I stopped the array and moved the disk to unassigned, the xfs repair gui worked, i saw the 3tb on the drive then stopped the array and moved the disk back to the array, started the array and noticed it was rebuilding data.

[RobinG]

i think i did upload old diagnostics

skynet-diagnostics-20240129-2033.zip

[trurl]

The diagnostics you posted above are the same diagnostics you posted yesterday on page 1 on this thread.

[trurl]

How did disk1 and disk3 get formatted?

[RobinG]

well, i took disk1 out of the array and into unassigned. formated disk 3 cause it didnt have any data. never formated disk1. I am assuming when i moved it back to the array it started doing a data-rebuild of the "emulated" disk 1 which had no data...

[RobinG]

i should have copied the data over while it was unassigned, really bummed about that decision.

[trurl]

4 minutes ago, RobinG said:

well, i took disk1 out of the array and into unassigned. formated disk 3 cause it didnt have any data. never formated disk1. I am assuming when i moved it back to the array it started doing a data-rebuild of the "emulated" disk 1 which had no data...

It would have listed all of the unmountable disks and let you format them. One of the unmountable disks in the list was the missing/emulated disk1. So now the array is emulating a formatted disk1. So the only thing it can rebuild to disk1 now is an empty disk.

 

We will have to see if the physical disk can be mounted and if it still has files, or if the rebuild had already progressed enough to make it empty too.

 

Can you mount the original disk1 as an Unassigned Device?

[trurl]

I didn't think you were going to do a lot of stuff without waiting for advice.

[RobinG]

I should have waited for you, yes it is mounted. and has only 87gb on it now not 3ish tbs.

[trurl]

So it is empty now too. The 87GB is just overhead, no actual folders and files.

 

Do you have backups?

 

At this point, the usual advice is to see if some third party software can recover your data from the formatted disk. UFS Explorer is often mentioned.

[RobinG]

i don't have a backup. 

[trurl]

Oh yeah, I already asked that on page 1. Was any of it important and irreplaceable?

 

UFS Explorer

 

 

[RobinG]

all of it was. 

[trurl]

One of the great features of Unraid is that all of your other data disks are unaffected by this, since they are all independent filesystem that can be read all by themselves.

 

I will review this tomorrow and see if any other ideas come up.