Help restoring boot pool mirror with multiple partitions

[mattyv316]

After upgrading to Bluefin, I started to receive the DIF unsupported message for my 2 mirrored SSD drives.
"Disk(s): sdc, sdb are formatted with Data Integrity Feature (DIF) which is unsupported."
These 2 - 400GB SSD drives are mirrored with multiple partitions. a 20ishGB boot-pool and a second partition with about 370GB called ssd-storage.
I started by making /dev/sdb/ offline in the UI from the ssd-storage pool menu options (I did not see an offline option from the boot pool stats screen. Just a replace option).
Once /dev/sdb/ was offline, both boot-pool and ssd-storage were marked as degraded. I then formatted (which also removed the protection) /dev/sdb/. After the format, I rebooted the server. When it came back up, I went to the UI for ssd-storage and replaced the disk with the newly formatted SSD. The system reslivered the pool and thought all was good. After another reboot, I noticed boot-pool was still degraded.
I am unable to fix it since, it seems, replacing the disk for ssd-storage pool didn't replace the mirror with both partitions, it only replaced the ssd-storage partition of the drive.
Does anyone have any pointers on how I can get this corrected?

 

[jgreco]

Does anyone have any pointers on how I can get this corrected?

Not to put too fine a point on that, but, yeah, don't do try to do the system to do things that it is not designed to do. You can pull it apart and start over properly. TrueNAS doesn't support "partitions" and if you try to force it, of COURSE it has no idea how to reassemble your jigsaw puzzle. Do NOT expect the system to be able to do drive replacements through the GUI for your unsupported partitioned disks. We are not going to be able to tell you exactly how to fix this because it really depends on what was done to begin with. You will want to go back to whatever misguided resource led you on this misadventure, figure out how to duplicate the partitioning strategy, and then see if you can get ZFS to do a replacement on that partition. This is not a HUGE amount of work, but it is complex and abstract enough that the developers decided there was no way in hell they felt that the TrueNAS system could do this, certainly not reliably.

You are best off pulling it apart, using proper boot drives, ideally something like 120GB mirrored SSD's, then using a pair of SSD's for your ssd-storage pool.

 

[mattyv316]

Not to put too fine a point on that, but, yeah, don't do try to do the system to do things that it is not designed to do. You can pull it apart and start over properly. TrueNAS doesn't support "partitions" and if you try to force it, of COURSE it has no idea how to reassemble your jigsaw puzzle. Do NOT expect the system to be able to do drive replacements through the GUI for your unsupported partitioned disks. We are not going to be able to tell you exactly how to fix this because it really depends on what was done to begin with. You will want to go back to whatever misguided resource led you on this misadventure, figure out how to duplicate the partitioning strategy, and then see if you can get ZFS to do a replacement on that partition. This is not a HUGE amount of work, but it is complex and abstract enough that the developers decided there was no way in hell they felt that the TrueNAS system could do this, certainly not reliably.

You are best off pulling it apart, using proper boot drives, ideally something like 120GB mirrored SSD's, then using a pair of SSD's for your ssd-storage pool.

Honestly didn't know it was that frowned upon. I originally just followed a howto in these forums when I first setup my TrueNAS server. Since then, it has been a lot of learning. Point taken about separating the pools to their own drive(s), but right now, I am out of bays and need to get this corrected.

I was able to get the boot pool back to mirrored and was able to partition the drive's 4th partition. It is ready to attach to my ssd-storage pool, but I am stuck trying to put together a 'zpool attach' command. I need to find the partitions' uuid, but scale does not have gpart. I think this is the only step I am missing. Is there a way in scale to retrieve the partition uuid?

 

[Samuel Tai]

Is there a way in scale to retrieve the partition uuid?

Try blkid from shell. You should be able to read off the partition UUID for the partition in question.

 

[jgreco]

I originally just followed a howto in these forums when I first setup my TrueNAS server

I'm not aware of any such howto, and I'm pretty sure we would not allow such to exist without a big warning label to prevent these sorts of problems. Anyone have any idea where this might be?

 

[mattyv316]

Try blkid from shell. You should be able to read off the partition UUID for the partition in question.

Thanks, I will give this a shot

 

[mattyv316]

I'm not aware of any such howto, and I'm pretty sure we would not allow such to exist without a big warning label to prevent these sorts of problems. Anyone have any idea where this might be?

HOWTO: Using a pair of large SSDs with boot and data pools for SCALE

 

[jgreco]

Fixed. Thanks.