This is a problem that I solved for myself and wanted to share with others just in case they experienced the same issue. I have a f4-423 and originally had 2x 12TB drives in TRAID. I was adding 2x more drives to the TRAID which completed successfully adding 1 drive at a time. I then went to expand the volume. There wasn't immediate feedback that the volume did or did not expand. Eventually the pool was reported as full but the volume remained the same size. After investigation within the terminal over SSH I determined that the logical volume had expanded but the partition did not. `resize2fs` is the tooling available on the device to expand the ext4 partition however this is what I experienced:
Code: Select all
# resize2fs /dev/mapper/vg1-lv1
resize2fs 1.43.7 (16-Oct-2017)
Resizing the filesystem on /dev/mapper/vg1-lv1 to 8781344768 (4k) blocks.
resize2fs: symbol lookup error: resize2fs: undefined symbol: ext2fs_dup_handle
This led me to
another post on this forum to which the solution was not shared other than contacting support. I did contact support and their advice was to disable the SSD cache which did not help.
I took it upon myself to try something different which was to statically compile the e2fsprogs tools which includes `resize2fs` like so (I did this using Ubuntu within Windows WSL2):
Code: Select all
wget https://cfhcable.dl.sourceforge.net/project/e2fsprogs/e2fsprogs/v1.47.1/e2fsprogs-1.47.1.tar.gz
tar xfz e2fsprogs-1.47.1.tar.gz
cd e2fsprogs-1.47.1
export CFLAGS=-static
export LDFLAGS=-static
./configure
make
scp ./resize/resize2fs <TNAS-USER>@<TNAS-IP-ADDRESS>:/opt/resize2fs
Use these new statically compiled binaries to run `resize2fs` as `/opt/resize2fs` and it works without the undefined symbol error.
