sde only has on partition and all the others have 1 and 2. is this going to cause a problem? I added it though the gui.
Thanks
Rob Version: ElectricEel-24.10.2.1
Depending the version you were running when the drive was added, it could be an issue if no padding space was left to account for possible replacement by a marginally smaller drive.
Check partition boundaries.
@Winnielinnie, any thoughts as to what I should do? I always wondered why that space was there. Sounds like I may have gotten stuck in a odd spot. If they are adding that back, it must be for a reason.
You should be fine. It is just changes from when swap and swap partitions were dropped in Scale. The ‘buffer’ fix is for when you try to replace a hard drive and the new drive is slightly smaller even if they both claim the same size in Tb. There have been instances within the same manufacturer and model of size changes.
Yes, very much so. TrueNAS expects pools to consist of UUIDs, not /by-id/ devices. So don’t replace the UUID ones at all, and replace (e.g.) sdh2 with its matching device under /dev/disk/by-partuuid/.
Not really. The PARTTYPE column is simply a lookup for a generic name to match a partition type UUID. TrueNAS Core creates partitions with one UUID (516E7CBA-6ECF-11D6-8FF8-00022D09712B - “FreeBSD ZFS”), TrueNAS Scale creates partitions with another (6A898CC3-1DD2-11B2-99A6-080020736631 - “Solaris & Apple (Mac) ZFS”). There isn’t a unique UUID for Linux ZFS, otherwise TrueNAS Scale would probably use that.
Why did Truenas install them as //dev/sdx if Partition UUID is the best way? Also, you know what is not printed on the outside of the drive, UUID. Asking because I am dumb.
Serial Number is the only unique identifier of the drives for replacements. You should put labels with at least the last few characters of the SN so you can see them in case. Three or four characters. If you have 100 drives, you may need full serial numbers. It’s helpful when you need to pull dead drive …xyz and you can’t read the default label location.
UUIDs cannot be printed since they are created by software, but they are the sole identifier that is guaranteed to not change over the life of the drive in the pool.
Serial numbers are nice… but some controllers may lie about them.
That was my plan, to replace the displayed /dev/sdb2, sdc2… with commands like the following.
zpool replace new-tank 727d67bc-00f6-4a82-99ac-e9773239a744 /dev/disk/by-id/ata-SAMSUNG_MZ7LM1T9HMJP-00005_S2TVNX0KA17264-part1
and get:
invalid vdev specification
use '-f' to override the following errors:
/dev/disk/by-id/ata-SAMSUNG_MZ7LM1T9HMJP-00005_S2TVNX0KA17264-part1 is part of active pool 'new-tank'
is it safe to -f(force) I would like to get some consistent naming
I would just run the commands to correct what you see to the default ZFS behavior
sdh2 being replaced by the UUID for the associated partition. You have two doing the default and 5 to make your desired changes to.
I would have to look at the GUI but it, probably, only expects device name or UUID. It may break with other values.
I had this in my Notepad. It may be of help going forward
Here is the command to match device names and partuuids: