Encrypted Drive mounted based on name jumping off pool

Ralms

Dabbler
Joined
Jan 28, 2019
Messages
29
Hi everyone,

I was hopping you could help me regarding a really annoying issue I've been having every since one of my drives jumped off my pool when by accident didn't it have plugged in and turned the server on.

So the setup is simple, Raid Z1 with 5 x 3TB drives.

As the pool is encrypted, I understand I have to use geli to attach the drive back.
But then when I tell the pool to go online with that drive again, it seems to be doing a hard connection with the drive name.
Which can change when I change the drives on the NAS.

2 days ago, I disconnected another drive that is not being used, resulting on a name change for this drive and the pool getting degraded after a reboot.

As you can see, doing "Zpool status"
1591627892982.png


The last drive for some reason is attached to "da6p2.eli" instead of the gptid as the other ones.

Could you provide me some guidance on how to fix this?

Thank you.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,700
offline it, then wipe the disk, create the swap and zfs partitions and use glabel status to get the gptid, then replace the old name with the gptid.

Be aware that you're without fault tolerance during the associated resilver operation. (and it seems you're already doing one, so I wouldn't necessarily mess with it until that's over)

But also, who really cares what the name is if it's working?
 
Last edited:

Ralms

Dabbler
Joined
Jan 28, 2019
Messages
29
offline it, then wipe the disk, create the swap and zfs partitions and use glabel status to get the gptid, then replace the old name with the gptid.

Be aware that you're without fault tolerance during the associated resilver operation. (and it seems you're already doing one, so I wouldn't necessarily mess with it until that's over)

But also, who really cares what the name is if it's working?

The issue with the name is not just visual or OCD, if I remove or add a drive on the server, that is not even part of this pool, sometimes the name can change of this drive (currently da6p2, but was da7p2 before).
1591642012296.png


The drive that I removed, since it's not being used right now, had an inferior number name to this one, so when I rebooted the server it started with the pool degraded as the drive was missing because had changed it's name.

So my logic is if I online the drive based on the Glabel instead of the name, it should prevent this from happening again.
I've had to manually mount and online this drive 3 times already this is why, every time I change something I already know.

Could you give more details on the last part "replace old name with the gptid" ?

Thank you for the help.
 
Top