You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it would be nice to have an option to customize the name of the device mapping, e.g.
/dev/mapper/foobar
Use case: I have two external devices which are not always connected to OMV. But they are both identified as "/dev/sdb" which leads to problems with the shares.
The text was updated successfully, but these errors were encountered:
Then you need to setup unique labels to the filesystem over the luks device, and mount the filesystems with labels which is the default in omv when present. then it won't matter if the device mapper is sda-crypt, sdb-crypt etc.
As now LUKS2 supports labels we could use that to generate a sort of unique dm name. But there will be no option for the user to set the dm name explicitly.
Oh, thanks for the label hint. I totally missed that.
Well, the unique dm name might be nice to have, but my basic problem is actually solved with the labels
Hi,
it would be nice to have an option to customize the name of the device mapping, e.g.
/dev/mapper/foobar
Use case: I have two external devices which are not always connected to OMV. But they are both identified as "/dev/sdb" which leads to problems with the shares.
The text was updated successfully, but these errors were encountered: