How to enlarge zpool (after enlarging disk)

TrueNAS General
,
1

I am running a virtualized (in Proxmox) Truenas scale server (Dragonfish-24.04.2.5) and I am running out of disk space in this Truenas scale server.

So I took the following steps (Zpool called: Safe, old size: 1GB, new size 1.5Gb)

  • I shutdown the VM
  • Enlarged the disk in the Proxmox interface from 1 to 1,5GB
  • Started the Truenasscale VM in Proxmox
  • In a treunasscale shell performed:

zpool -v set autoexpand=on Safe

  • Also started a scrub from the UI (finished with no errors)

This did not make available the additional 0.5 GB. (in the Truenasscale UI the disk is shown as 1.5Gb)

How should I “unlock” this additional space? I hope to do this online, but if needed I can also boot into a liveCD. I would like to avoid copying all the data to a new disk…

Additional information:

root@truenasscale[~]# zpool list 
NAME        SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
Safe        997G   774G   223G        -      501G    41%    77%  1.00x    ONLINE  /mnt
boot-pool    19G  15.6G  3.43G        -         -    42%    81%  1.00x    ONLINE  -

root@truenasscale[~]# fdisk -l
Disk /dev/sda: 20 GiB, 21474836480 bytes, 41943040 sectors
Disk model: QEMU HARDDISK   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: EC9A3B2D-3C84-4E2C-9838-C8A9AF33A46E

Device       Start      End  Sectors  Size Type
/dev/sda1     4096     6143     2048    1M BIOS boot
/dev/sda2     6144  1054719  1048576  512M EFI System
/dev/sda3  1054720 41943006 40888287 19.5G Solaris /usr & Apple ZFS
GPT PMBR size mismatch (2097151999 != 3145727999) will be corrected by write.
The backup GPT table is not on the end of the device.


Disk /dev/sdb: 1.46 TiB, 1610612736000 bytes, 3145728000 sectors
Disk model: QEMU HARDDISK   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: DABFA12F-48A0-4D7D-B536-9EAAAA835F08

Device       Start        End    Sectors  Size Type
/dev/sdb1      128    4194304    4194177    2G Linux swap
/dev/sdb2  4194432 2097151966 2092957535  998G Solaris /usr & Apple ZFS


Disk /dev/mapper/sdb1: 2 GiB, 2147418624 bytes, 4194177 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

root@truenasscale[~]# mount | grep /mnt
boot-pool/ROOT/24.04.2.5/mnt on /mnt type zfs (rw,relatime,xattr,noacl,casesensitive)
Safe on /mnt/Safe type zfs (rw,noatime,xattr,posixacl,casesensitive)
Safe/Media on /mnt/Safe/Media type zfs (rw,noatime,xattr,posixacl,casesensitive)
Safe/FTP on /mnt/Safe/FTP type zfs (rw,noatime,xattr,posixacl,casesensitive)
Safe/Music on /mnt/Safe/Music type zfs (rw,noatime,xattr,posixacl,casesensitive)
Safe/Photos on /mnt/Safe/Photos type zfs (rw,noatime,xattr,posixacl,casesensitive)
root@truenasscale[~]#

image
image1762×631 115 KB

2

Use the “Expand Pool” button in the GUI.

3

What’s the point of running TrueNAS for a ridiculously small capacity, without redundancy, and in a setting which is known to eventually result in total data loss (virtual disk from hypervisor)?

5

Okay then, I know truenas scale is a bit of overkil for my use. I started looking at NAS server software, of those that I tested, TrueNAS scale kind of just stayed with me. What in your opinion would be better suited for my needs? (I know it is not a TrueNAS question, but I do hope you can provide a hint…

6

Pardon my ignorance, but where can I find such a butt

Thank you for that, even after your remark I had to use the AI search to find the button… “It is one of the buttons available at the top right of the Storage Dashboard screen”

7

Please give us details on how you are using your NAS and why you chose that setup. The better the details, the better the advice on other choices.

VIRTUAL