NAS 326 change disks

gyulav

In fdisk it has an error:

"GPT PMBR size mismatch (3907029167 != 3519069871) will be corrected by w(rite).
The backup GPT table is corrupt, but the primary appears OK, so that will be used.
GPT PMBR size mismatch (3907029167 != 3519069871) will be corrected by w(rite)."

Parted was fixed this error:
(parted) print list
Error: The backup GPT table is corrupt, but the primary appears OK, so that will
be used.
OK/Cancel? OK
Warning: Not all of the space available to /dev/sda appears to be used, you can
fix the GPT to use all of the space (an extra 3907008000 blocks) or continue
with the current setting?
Fix/Ignore? Fix

Now fdisk delete/re-create partition is OK. :)

Reboot NAS.

/proc/partition show new larger size.

resize2fs: … on-line resizing required
old_desc_blocks = 117, new_desc_blocks = 233
resize2fs: Permission denied to resize filesystem

I think: i must unmounting (hard) and stop device.

Mijzelf

Or partition delete with fdisk is not needed?

Yes it is. mdadm doesn't 'know' anything about the block device below it. So it cannot resize the containing partition.

And the filesystem is not Linux RAID, but Linux filesystem.

That doesn't actually matter. It's just a label in the partition table. The partition itself is just a bunch of sectors, and at least in an MBR partition table it's completely ignored by Linux. I think it's also ignored in a GPT table. In any case it can be easily changed.

It did not work.

That is strange. It ought to work. I wonder if the implementation of fdisk on the NAS can only deal with 32 bit sector addresses? Does /proc/partitions show a 4TB sda?

If yes, try parted.

parted /dev/sda

print

resizepart

gyulav

https://community.zyxel.com/en/discussion/comment/76864#Comment_76864

Thanks, and sorry. I did not fix/improve previous post understandably.

fdisk and grow is OK.

Only resize is problem.

"resize2fs: … on-line resizing required
old_desc_blocks = 117, new_desc_blocks = 233
resize2fs: Permission denied to resize filesystem"

I think: i must unmounting (hard task) and stop device. Then i must run e2fsck.

Mijzelf

You must unmount the filesystem (/dev/md2, I suppose), but not stop it. If you stop it, the md device is gone, and only /dev/sda3 is left. But that doesn't contain a filesystem.

Then run e2fsck on /dev/md2.

gyulav

@Mijzelf : Thanks.

It is work.