Hello All,

I have been in the process of swapping the drives in my 8 drive ZFS2 array named Bigblue. The reason was two fold. The first being another 4TB drive had started to show errors, the second being I had already previously swapped two of the 4 TB drives for 16TB. I have purchased 6 more 16TB drives and have swapped all but one using zpool offline bigblue GUID > followed by zpool replace bigblue GUID sd#. Earlier I asked on discord why the drives weren't showing in the interface and were listed as dev, and was told the way I had swapped them was wrong. So I stopped the array and when selecting the correct drives for replacing in the UI, I see a wrong label. What is the correct process to remedy this? Remove the array (not delete) and then re-add? Let me know if I need to attach any logs.

9 hours ago, cadamwil said:

and have swapped all but one using zpool offline bigblue GUID > followed by zpool replace bigblue GUID sd#.

You should have used the GUI for that, post the output from zpool import

Here you go...

root@Beast:~# zpool import
pool: prossd
id: 10603483798625687601
state: ONLINE
status: Some supported features are not enabled on the pool.
(Note that they may be intentionally disabled if the
'compatibility' property is set.)
action: The pool can be imported using its name or numeric identifier, though
some features will not be available without an explicit 'zpool upgrade'.
config:
prossd ONLINE
mirror-0 ONLINE
sdb ONLINE
sdc ONLINE

pool: bigblue
id: 5709855171605561477
state: ONLINE
status: Some supported features are not enabled on the pool.
(Note that they may be intentionally disabled if the
'compatibility' property is set.)
action: The pool can be imported using its name or numeric identifier, though
some features will not be available without an explicit 'zpool upgrade'.
config:
bigblue ONLINE
raidz2-0 ONLINE
ata-ST16000NM001G-2KK103_ZL2558AN ONLINE
sdn ONLINE
sde ONLINE
sdf ONLINE
sdg ONLINE
sdd ONLINE
sdm ONLINE
sdi ONLINE
root@Beast:~#

Edited July 29, 2025Jul 29 by cadamwil

Zpool import/status is using the whole device, a result of doing them using the CLI, but should be OK since zfs typically still creates the partitions.

on main click on the first device for that pool and then "remove pool"

back on main, create a new pool with the same name and the correct number of slots

assign the pool devices, leave the filesystem set to auto

start the array to import the pool

If it fails to import post the diags after array start.

1 hour ago, JorgeB said:

Zpool import/status is using the whole device, a result of doing them using the CLI, but should be OK since zfs typically still creates the partitions.

on main click on the first device for that pool and then "remove pool"

back on main, create a new pool with the same name and the correct number of slots

assign the pool devices, leave the filesystem set to auto

start the array to import the pool

If it fails to import post the diags after array start.

That worked, what's the correct way to replace the last drive and autoexpand the array when the resilvering is done?

Edited July 29, 2025Jul 29 by cadamwil
correct punctuation

Are the instructions below the correct procedure when using ZFS?

Storage Management | Unraid Docs

Storage Management | Unraid Docs

To assign devices to

To perform the upgrade proceed as follows:

    Run a parity check if you have not done so recently and make sure that zero errors are reported. Attempting an upgrade if parity is not valid will result in the file system on the upgraded disk being corrupt.
    Stop the array.
    Unassign the disk you want to upgrade.
    Start the array to commit this change and make Unraid 'forget' the current assignment.
        Unraid will now tell you that the missing disk is being emulated. It does this using the combination of the remaining data drives and a parity drive to dynamically reconstruct the contents of the emulated drive. From a user perspective the system will act as if the drive was still present albeit with a reduced level of protection against another drive failing.
        If you started the array in Maintenance mode then this will ensure no new files can be written to the drive during the upgrade process
        If you started the drive in Normal mode then you will be able to read and write to the Emulated drive as if it was still physically present
    Stop the array.
        At this point the array is in the same state as it would be if the drive you have stopped using had failed instead of being unassigned as part of the upgrade process.
    Assign the (larger) replacement drive to the slot previously used for the drive you are upgrading.
    Start the array to begin rebuilding the contents of the emulated drive on to the upgraded drive.
        Since the replacement drive is larger than the one it is replacing when the contents of the emulated drive have been put onto the replacement drive Unraid will automatically expand the file system on the drive so the full capacity of the drive becomes available for storing data.

That's for the array only, you can use this:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/#findComment-480419