New SSD requires password to mount
-
I installed an additional SSD on my pc. Everything works ok, except I need to unlock it with my root password on every session so that it mounts.
I've tried formatting it to change the 'owner', tried adding it to the user group, and I can't find any other solutions. Any ideas?
This happens irrelevant of DE (happens on KDE and hyprland). I'm running tumbleweed, though this looks like a config problem rather than a distro problem.
I have had the issue of having to enter a password to access an additional drive on my Manjaro PC.
I was pointed to this as a possible solution and it worked for me.
It may or may not work for you though.
-
I installed an additional SSD on my pc. Everything works ok, except I need to unlock it with my root password on every session so that it mounts.
I've tried formatting it to change the 'owner', tried adding it to the user group, and I can't find any other solutions. Any ideas?
This happens irrelevant of DE (happens on KDE and hyprland). I'm running tumbleweed, though this looks like a config problem rather than a distro problem.
I know a lot of people are recommending fstsb entries, but since you're using a DE, you can have the credential stored in the wallet / session manager for your DE. KDE and Gnome should both have an automount option using keys from there. Then you also can find a preference somewhere to unlock your wallet / session keys thing on login. Bing bang boom you should have it mount and unlock automatically without having to enter any extra stuff with the added benefit of not leaving the key around (though since it seems you have FDE anyway that's a minor issue depending on your threat model)
-
Will that add two minutes to my boot time though?
Nope it doesn't add anything for me. The _netdev option tells mount to wait until the network is connected before attempting to mount. And the nofail option tells it not to error or block the process that called it if the mount doesn't work or is delayed.
Now if the mount contains your etc or other critical config files, it could cause problems and maybe you want to wait, so don't want the nofail. And of course this kind of thing is somewhat OS specific depending on what boot system is used, so YMMV, but on Fedora, Rocky, and Ubuntu, it has worked for me for many years.
-
System shared this topic on
