Drive Name changed

[clifford64]

I have a 12 disk x 6 mirror pool that I have been slowly replacing drives in. I recently ran into an issue where my drive names seem to have changed.
Previously, I had it ordered so the name of the drive matched up with the slot the drive was in. Being that these are mirrors, I would like to keep them together for organization purposes. For example, da0=drive 1, da1=drive 2, da2=drive 3 and so on.

Now, the physical disk order hasn't changed, but the drive names have. da0-da2 are normal, but da11= Drive 3, da3= drive 5, da4= drive 6. Like the daX has shifted for some reason.

Now I know this has no impact on my pool because truenas uses the GPTID to map them to the vDevs, but it would be nice to get the correct order back. I have already tried a reboot, but that didn't do anything. I tried popping out the drive and then putting it back in, but that didn't seem to do anything either. Any ideas?

Potentially export/offline the pool and then pop the drives in one at a time so the order is recognized? Or just leave it alone. I have been using the daX number to match up the physical drive location in my documentation. Should I be using something else in my documentation like the GPTID instead and drop daX number?

zpool status

Code:

  pool: iSCSI-Pool
 state: ONLINE
  scan: resilvered 6.37M in 00:00:02 with 0 errors on Thu May  5 12:28:25 2022
config:

        NAME                                            STATE     READ WRITE CKSUM
        iSCSI-Pool                                      ONLINE       0     0     0
          mirror-0                                      ONLINE       0     0     0
            gptid/5ccaae80-c3ab-11ea-99a0-001e67ae35eb  ONLINE       0     0     0
            gptid/b0b6fe1a-9940-11eb-a106-001e67ae35eb  ONLINE       0     0     0
          mirror-1                                      ONLINE       0     0     0
            gptid/5cd67028-c3ab-11ea-99a0-001e67ae35eb  ONLINE       0     0     0
            gptid/a46c29de-9d5f-11ec-b18d-001e67ae35eb  ONLINE       0     0     0
          mirror-2                                      ONLINE       0     0     0
            gptid/5a6c40ff-c3ab-11ea-99a0-001e67ae35eb  ONLINE       0     0     0
            gptid/37818987-b84f-11eb-b40f-001e67ae35eb  ONLINE       0     0     0
          mirror-3                                      ONLINE       0     0     0
            gptid/5b660348-c3ab-11ea-99a0-001e67ae35eb  ONLINE       0     0     0
            gptid/e14b791a-adab-11eb-b40f-001e67ae35eb  ONLINE       0     0     0
          mirror-4                                      ONLINE       0     0     0
            gptid/c2f15a23-7022-11ec-bffa-001e67ae35eb  ONLINE       0     0     0
            gptid/658b8681-c3ab-11ea-99a0-001e67ae35eb  ONLINE       0     0     0
          mirror-5                                      ONLINE       0     0     0
            gptid/648a198d-c3ab-11ea-99a0-001e67ae35eb  ONLINE       0     0     0
            gptid/8e9e03ce-a45e-11eb-b40f-001e67ae35eb  ONLINE       0     0     0
        cache
          gptid/95deded5-89b4-11eb-a106-001e67ae35eb    ONLINE       0     0     0

errors: No known data errors

glabel status

Code:

                                      Name  Status  Components
gptid/245116d1-bef3-11e9-9870-001e67ae35eb     N/A  ada0p1
gptid/95deded5-89b4-11eb-a106-001e67ae35eb     N/A  ada1p1
gptid/5ccaae80-c3ab-11ea-99a0-001e67ae35eb     N/A  da0p2
gptid/b0b6fe1a-9940-11eb-a106-001e67ae35eb     N/A  da1p2
gptid/5cd67028-c3ab-11ea-99a0-001e67ae35eb     N/A  da2p2
gptid/37818987-b84f-11eb-b40f-001e67ae35eb     N/A  da3p2
gptid/5a6c40ff-c3ab-11ea-99a0-001e67ae35eb     N/A  da4p2
gptid/e14b791a-adab-11eb-b40f-001e67ae35eb     N/A  da5p2
gptid/5b660348-c3ab-11ea-99a0-001e67ae35eb     N/A  da6p2
gptid/c2f15a23-7022-11ec-bffa-001e67ae35eb     N/A  da7p2
gptid/658b8681-c3ab-11ea-99a0-001e67ae35eb     N/A  da8p2
gptid/648a198d-c3ab-11ea-99a0-001e67ae35eb     N/A  da9p2
gptid/a46c29de-9d5f-11ec-b18d-001e67ae35eb     N/A  da11p2
gptid/8e9e03ce-a45e-11eb-b40f-001e67ae35eb     N/A  da10p2
gptid/8e800362-a45e-11eb-b40f-001e67ae35eb     N/A  da10p1
gptid/5716c193-c3ab-11ea-99a0-001e67ae35eb     N/A  da0p1

 

[NugentS]

I use serial number. the /dev/dax is arbitary and can change on a reboot. The GPTID is too big to be useable
I have a visio diagram that I have model, serial number and pool written on (hmm, must update that as I have removed some disks - as with all documentation keeping it up to date is the problem).

 

[clifford64]

I use serial number. the /dev/dax is arbitary and can change on a reboot. The GPTID is too big to be useable
I have a visio diagram that I have model, serial number and pool written on (hmm, must update that as I have removed some disks - as with all documentation keeping it up to date is the problem).

So probably not worth trying to change the daX number to match?

 

[NugentS]

So probably not worth trying to change the daX number to match?

Nope

 

[sretalla]

If you move drives around or remove them and re-insert in a different order, the drive identifier (daX) can change.

If you wipe and re-partition a disk, the gptid will change.

So with both of those items being variable for a physical disk, stick with serial number.