No Capacity Expansion After Disk Upgrade

TrueNAS General
, ,
1

Hello, I am contacting this forum because the capacity of my pool has not increased after changing my three 6TB disks to 8TB disks (RAIDZ-1)
Current size : 10.77 TiB
Expected size : 14,56 TiB
Current OS : TrueNAS Scale ElectricEel-24.10.0.2

I expected it to do it automatically as I have read. Especially since TrueNAS detects changes in hard drive size.

I have been using TrueNAS for a short time and am having trouble diagnosing the problem. I saw an old topic on the old Truenas forum which talks about a similar problem but I would like confirmation of the problem before embarking on fairly long disk change operations and risking. (I have a 4th 8TB disk not used if necessary for manipulations )

Could anyone help me to describe what is the problem ? I share the results of some commands:

  • sudo lsblk -f
NAME   FSTYPE            FSVER LABEL         UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                              
└─sda1 zfs_member        5000  DATA          13695333462XXXXXXXXX                                
sdb                                                                                              
├─sdb1                                                                                           
├─sdb2 vfat              FAT32 EFI           78E3-A95A                                           
└─sdb3 zfs_member        5000  boot-pool     7999731742920588349                                 
sdc                                                                                              
├─sdc1 linux_raid_member 1.2   truenas:swap0 03ccaf48-69f6-9f24-2fac-xxxxxxxxxxxx                
└─sdc2 zfs_member        5000  DATA          13695333462XXXXXXXXX                                
sdd                                                                                              
├─sdd1 linux_raid_member 1.2   truenas:swap1 08e06a96-fce7-9a6a-f298-xxxxxxxxxxxx                
└─sdd2 zfs_member        5000  DATA          13695333462XXXXXXXXX                                
sde
  • sudo parted -l
Model: ATA ST8000VN002-2ZM1 (scsi)
Disk /dev/sda: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  8002GB  8002GB  zfs          data


Model: ATA CT240BX500SSD1 (scsi)
Disk /dev/sdb: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      2097kB  3146kB  1049kB                     bios_grub, legacy_boot
 2      3146kB  540MB   537MB   fat32              boot, esp
 3      540MB   240GB   240GB   zfs


Model: ATA ST8000VX010-2ZR1 (scsi)
Disk /dev/sdc: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  2149MB  2147MB                     swap
 2      2150MB  6001GB  5999GB  zfs


Model: ATA ST8000VX004-2M11 (scsi)
Disk /dev/sdd: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      1049kB  2149MB  2147MB                     swap
 2      2150MB  6001GB  5999GB  zfs


Error: /dev/sde: unrecognised disk label
Model: ATA CT240BX500SSD1 (scsi)                                          
Disk /dev/sde: 240GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
  • sudo zpool status
  pool: DATA
 state: ONLINE
  scan: resilvered 4.21T in 09:49:48 with 0 errors on Sat Nov 30 21:37:58 2024
config:

        NAME                                      STATE     READ WRITE CKSUM
        DATA                                      ONLINE       0     0     0
          raidz1-0                                ONLINE       0     0     0
            30912e03-e40b-471b-af0e-xxxxxxxxxxxx  ONLINE       0     0     0
            315ac02f-195a-4d91-a00a-xxxxxxxxxxxx  ONLINE       0     0     0
            fefc624d-8ab2-428f-a606-xxxxxxxxxxxx  ONLINE       0     0     0

errors: No known data errors

  pool: boot-pool
 state: ONLINE
  scan: scrub repaired 0B in 00:00:30 with 0 errors on Mon Dec  2 03:45:31 2024
config:

        NAME        STATE     READ WRITE CKSUM
        boot-pool   ONLINE       0     0     0
          sdb3      ONLINE       0     0     0

errors: No known data errors
  • zpool get autoexpand DATA
NAME  PROPERTY    VALUE   SOURCE
DATA  autoexpand  on      local
2

Othe commands:

  • sudo zpool list
NAME        SIZE  ALLOC   FREE  CKPOINT  EXPANDSZ   FRAG    CAP  DEDUP    HEALTH  ALTROOT
DATA       16.4T  12.6T  3.73T        -         -     0%    77%  1.00x    ONLINE  /mnt
boot-pool   222G  13.3G   209G        -         -     0%     5%  1.00x    ONLINE  -
  • sudo zpool list -v DATA
DATA                                      16.4T  12.6T  3.73T        -         -     0%    77%  1.00x    ONLINE  /mnt
  raidz1-0                                16.4T  12.6T  3.73T        -         -     0%  77.2%      -    ONLINE
    30912e03-e40b-471b-af0e-xxxxxxxxxxxx  5.46T      -      -        -         -      -      -      -    ONLINE
    315ac02f-195a-4d91-a00a-xxxxxxxxxxxx  7.28T      -      -        -         -      -      -      -    ONLINE
    fefc624d-8ab2-428f-a606-xxxxxxxxxxxx  5.46T      -      -        -         -      -      -      -    ONLINE
3

While describing the problem, I thought of a solution :

With the UI :

  1. Replace sdc with my extra disk.
  2. Replace sdd with the old sdc.

Do it seem the best way to solve this ?

  • Why 2 disk of three got swap partition ?
  • Why the initial 2 disks replacement from 6To to 8To created this table instead of only one partition of 8TB but for the 3th disk, it look fine ?
4

This is a long-standing bug in SCALE that iX doesn’t seem interested in fixing. See:

1 Like
5

Thanx you @dan, in my case the solution was :

sudo parted /dev/sdc resizepart 2 100%
sudo parted /dev/sdd resizepart 2 100%

Last question:

  • Why the /dev/sda disk don’t get a swap partition. It is normal or it is a part of the bug that I need to fix ?
6

I’m not certain why this is the case, but it’s unlikely to be important–SCALE in the last couple of updates really doesn’t use swap in any event.