So I was on Unraid 7.0.1 with it running stable for months, waiting for a stable release, and finally decided to upgrade to 7.1.2 yesterday. Did the upgrade and rebooted, and the array didn't come back online. Saying that disk sdd was too small. I tried another reboot and nothing.

 

All my disks were happy, so I did a new config and added them back in, though now I have the message "unmountable" message as shown below:

 

 

I tried an xfs_repair on it though no luck:

 

 

I did start doing a offsite data backup a couple of months back, so I have a partial backup, though ideally want back the rough 2TB data on that disk.

 

Worth noting I have a full unraid backup from Monday if that helps.

 

Anything else I can try before pulling the disk and trying to do data recovery?

 

Thanks in advance!

 

Please post the diagnostics.

Sure. Attached!tower-diagnostics-20250515-0838.zip

There's something going on with disk1 capacity, post the output from:

 

fdisk -l /dev/sdd

and for comparison

fdisk -l /dev/sde

 

It is odd. Same disks as I remember. As requested:

 

There are issues with the partitions, post the output from:

 

gdisk /dev/sdd

 

Sure:

 

Also for sde:

Try repairing for disk1 only for now, since that's the one showing an issue, with the array stopped, and after that gdisk command, type w to try and correct the partition.

Okay, can you please confirm the repair sequence as it isn't obvious from the options available?

Did some Googling, so verified the error, and then wrote to it using gdisk:

 

This looks successful. When starting the array, the disk still gets the same error - "Unmountable - wrong or no file system"

Edited May 15, 20251 yr by Watcher56

Post new fdisk output for that disk and new diags.

Sure, as below.

tower-diagnostics-20250515-1252.zip

There's still an issue with the partition, it's smaller than it should be:

 

May 15 11:40:25 Tower kernel: mount: attempt to access beyond end of device

 

Rebuilding the disk from parity should resolve the problem, since Unraid would recreate the partition with the correct size, but you can also first try just to create the correct partition on top of that one, not sure it will work, but it won't make things worse, with the array stopped type:

 

sgdisk -o -a 8 -n 1:32K:0 /dev/sdd

 

Then retest

run as below, though still the same error when I start the array:

 

How best to build it from parity?

Edited May 15, 20251 yr by Watcher56

Now getting this:

 

Rebooted too to keep everything clean.
 

 

Best to do a New Config to setup the array?

Edited May 15, 20251 yr by Watcher56

Do a new config, sync parity, and when that is done, unassign disk1, to see if the emulated disk mounts, but if creating a new partition didn't, it may be the same.

New config created, array started and disk is back online!!!

 

Parity is now syncing

 

Thank you so much for your assistance here, I thought I had lost all of the data on that drive.

 

I'll be sure to let parity finish, and keep the full offsite backup running.

 

Thanks again for your support and getting to the bottom of this!

1 hour ago, Watcher56 said:

array started and disk is back online!!!

So disk1 mounted with the new partition? I understood it didn't help.

After running the sgdisk, on first starting the array I was still getting the same error "Unmountable - wrong or no file system".

 

However, after the array was stopped I was getting a different error, as I couldn't start the array as it was saying "wrong" device as shown in my screen above, as though something had changed.

 

I then ran the "New config", added the disks and it just worked.

 

The sgdisk command seemed to be key to correcting the disk, though it wasn't picked up by unraid straight away.

 

Hope that makes sense with my steps.

Ahh, OK, I forgot to mention that you would need to refresh the GUI after the sgdisk command so that it would detect the new partition size, that explains it, and glad to hear it worked.

That does make sense. Very glad at this end 

Edited May 15, 20251 yr by Watcher56