Hi all,

 

Just a question before I risk any further data loss.

 

I have a disk that Unraid is detecting as "Unmountable: Unsupported partition layout"

Now I have the option to format the drive. But if I do that do I that, will I be able to attempt a parity rebuild? or will Unraid recognize the disk serial number and then influence parity?

 

I hope someone can answer.

 

Kind regards

Alphahelix

2 minutes ago, Alphahelix said:

But if I do that do I that, will I be able to attempt a parity rebuild?

No, all data will be lost.

 

Please post your diagnostics.

xeon-diagnostics-20180911-1737.zip

As requested. Sorry I should have thought of that in the original post. 

How did this happened? i.e. was it working and it got like this after a reboot, out of the blue or after doing something to the array.

I had some issues with deleting some very old files. so I thought a restart might cure that. And after the reboot I got this. The files still cant be deleted. but that is for another thread.

It's strange happening after a reboot, but the only way to fix it is to rebuild that disk, to the same or to a new one, a new one would be safer if you have a spare, current disk looks mostly fine but there's an UNC error, though it's from some time ago.

 

In any case, stop the array, unassign disk8, start the array, emulated disk8 should now mount correctly and all data be accessible (assuming parity is in sync), after this either reassign old disk8 or a new disk and start the array to rebuild.

 

 

 

 

Thanks Johnnie,

 

Just to recap:

1: bring the array offline

2: remove disk8 from array

3: start array again

4: do what ever I need to do

5: stop array

6: assign a disk at minimum 6TB (size of disk8)

7: start array

 

Os it correctly understood that I can only format disk8 outside the array?

Yes, and if after step 3 the emulated disk doesn't mount don't start the rebuild, post new diags

Also, and mostly out of curiosity please post the output of:

 

sfdisk -l /dev/sdk

 

If you rebooted since the diags check disk8 is still sdk.

xeon-diagnostics-20180911-1821.zip

 

root@XEON:~# sfdisk -l /dev/sdk
Disk /dev/sdk: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

It looks like I can delete the files I spoke of before. so I think you got to the root cause of my problems. So I just have to format the drive (thinking of a preclear might be good) and the save up for a new replacement drive.

Disk /dev/sdk: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

This is very weird, there's no partition.

 

Emulated disk is not mounting, no filesystem superblock, are you sure disk8 was formatted and mounted before? It looks to me like it was never formatted, i.e. never had any data.

 

 

 

 

Im quite sure. But I have already made up my mind. I will order a new Ironwolf 8TB disk when I have saved up. I do not want to risk one disk to compromise the array. (I remember from my biology classes that wolf are pack animals, so I think its best to continue with Ironwolf disks... I know bad joke... But at least I have humor!)

 

But Johnnie, thank you for your assistance, it is much appreciated. 

1 minute ago, Alphahelix said:

Im quite sure.

I very much doubt it, pretty sure that disk was never formatted, and in any case the rebuilt disk you'll remain unmountable.

You where right! it is now done with parity rebuild. And it is unmountable once again.

Will the problem go away if I replace the 6TB disk with a new disk? or will Unraid simply write bad data from parity once again? If so... how do I salvage the data, as the data seems fine in emulated mode.

25 minutes ago, Alphahelix said:

You where right! it is now done with parity rebuild. And it is unmountable once again. 

That's the only possible outcome.

 

26 minutes ago, Alphahelix said:

Will the problem go away if I replace the 6TB disk with a new disk?

No.

 

Like I said the only thing that makes sense it that disk8 was never formatted, if it was you have two very serious and not directly related problems with your server:

 

-something deleted the partition from disk8, never seen this happen before

-your parity is invalid, since the emulated disk doesn't contain a valid filesystem.

42 minutes ago, Alphahelix said:

the data seems fine in emulated mode.

This doesn't make any sense in the context of everything else that has been said. If indeed you can see the emulated data for that disk, then you absolutely must NOT format.

 

But I thought it had already been established that the emulated disk was unmountable.

28 minutes ago, trurl said:

This doesn't make any sense in the context of everything else that has been said.

I'm guessing he's referring to the array data, emulated disk is unmountable, without a valid filesystem, like the disk was cleared (or precleared) then added to the array but never formatted, only other option that makes sense would be if the clear disk script was used on that disk.

I KNOW it was running fine friday/saturday. From sunday to tuesday (at my OP) the error presented itself. I honestly does not remember how I prepared the drive. But I do know it had a partition on it, now it seems the partition on Disk8 is gone even from parity. But question is if there is anything I can do from here or just accept the loss and format the drive and thus removing data and problems.

I don't see any way you can recover the data, since the only options I can think of for a disk being like that are:

 

-it was never formatted and didn't had any data

-it was cleared while still in the array

 

You can try to use a file recovery utility, like UFS explorer, but if I'm right it won't find anything.

I am still 100% sure it have had data or at least did not show up as unmountable. Wether or not the process of format/preclear was performed sufficiently enough, here I can honestly not remember how I did it. But data has been on the disk. Question is, if I format the drive now when it is unmountable (also in parity) then I guess whatever data it did hold is already gone now. or am I mistaken?

19 minutes ago, Alphahelix said:

Question is, if I format the drive now when it is unmountable (also in parity) then I guess whatever data it did hold is already gone now. or am I mistaken?

Yes, formatting would delete any data there.