Pool size didn´t increase after HDD upgrade

I have a small NAS for Documents sharing running Dragonfish-24.04.2.2 on a Supermicro X9 with Intel(R) Xeon(R) CPU E3-1230 V2 @ 3.30GHz and 16G RAM.
Initially built a 3x4TB Raidz1. Today off lined one by one and replaced them all, but the available space still unchanged.

image

Any ideas appreciated.

The output of lsblk in the shell will show if this is, again, the SCALE bug with partitions.

1 Like

I’m more a core kind of guy. Trying Scale to see if worth the move …

sda        8:0    0   7.3T  0 disk  
└─sda1     8:1    0   3.6T  0 part  
sdb        8:16   0   7.3T  0 disk  
└─sdb1     8:17   0   3.6T  0 part  
sdc        8:32   0   7.3T  0 disk  
└─sdc1     8:33   0   3.6T  0 part  
sdd        8:48   0 111.8G  0 disk  
├─sdd1     8:49   0     1M  0 part  
├─sdd2     8:50   0   512M  0 part  
├─sdd3     8:51   0  95.3G  0 part  
└─sdd4     8:52   0    16G  0 part  
  └─sdd4 253:0    0    16G  0 crypt 
sr0       11:0    1  1024M  0 rom  

Interesting … so kill the pool and recreate? Can gparted be used to increase the partition? Starting rsync by the way :innocent:

Ouch. It partitioned 3.6 TiB out of your 7.3 TiB (“8 TB”) drives.

Scale kept the original partitions, as the original disks were 4TB. After finish my rsync, I’ll run gparted to increase the partitions and see if I can shot my foot or fix the problem. Any ways, IX should look into this, as I never had any issues with doing it with Core.

Yes, they should. They’ve had multiple bugs filed and said it’s fixed. I don’t know why they can’t get this right all of a sudden. Please file another.

Once you have, the command to fix the partition sizing would be, IIRC, parted /dev/sda 1 100%.

3 Likes

Will open another one.

Will try after my rsync finishes. So glad I upgraded all to sfp+ @ home …

@winnielinnie and @dan Thanks for your replies!

You can do it online; it won’t interrupt other tasks.

I know, just being myself and wanted to safeguard the data :slight_smile:

To do that with parted 3+:

  1. select the disk by running parted /dev/sdX, where X is your disk.
    i.e:
parted /dev/sda

You should see:

GNU Parted 3.5
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.´'
  1. List the partition
(parted) print  

The output in my case:

Disk /dev/sda: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
 1      2097kB  4001GB  4001GB  zfs

My drive is a 8TB, so its using half of that.

  1. List the free space:
(parted) print free                                                       
Model: ATA WDC WD80EFPX-68C (scsi)
Disk /dev/sda: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
        17.4kB  2097kB  2080kB  Free Space
 1      2097kB  4001GB  4001GB  zfs
        4001GB  8002GB  4001GB  Free Space

In this case shows 4TB free after the ZFS partition.

  1. To expand it:
(parted) resizepart 1 8002GB   

Note that no output will be provided by parted, so I confirmed with:

(parted) print free                                              
Model: ATA WDC WD80EFPX-68C (scsi)
Disk /dev/sda: 8002GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name  Flags
        17.4kB  2097kB  2080kB  Free Space
 1      2097kB  8002GB  8002GB  zfs

  1. Repeat for all impacted drive

Disclaims:
(1) Save your data first
(2) Use at your own risk

1 Like

File the bug.

Not sure how this can possibly still be an issue, but apparently it is.

1 Like

I did file.

2 Likes