New SSD requires password to mount

[email protected]

I believe systemd after targets work tho I have never tried them
Try adding this to mount options

x-systemd.after=network-online.target

[email protected]

You may be right, but I worked around this using https://wiki.archlinux.org/title/NetworkManager#Network_services_with_NetworkManager_dispatcher

Essentially, I added the CIFS shares to my fstab with the _netdev option and created /etc/NetworkManager/dispatcher.d/30-nas-shares.sh containing:

WANTED_CON_UUID="UUID-OF-MY-WIFI-IN-NETWORK-MANAGER"

if [ "$CONNECTION_UUID" = "$WANTED_CON_UUID" ]; then
  case "$2" in
    "up"|"vpn-up")
      mount -a -t cifs
      ;;
  esac
fi

This waits for my WiFi to come up, ensures it's my home WiFi, and then mounts my shares.

There are probably other and better ways to do it, but it works.

[email protected]

Try adding the nofail and _netdev options in your fstab entry. I have this on a few computers that connect to nfs shares including my laptop that obviously can only connect when I'm at home or on VPN. Example:

server:/path /mnt/path nfs4 defaults,nofail,_netdev 0 0

? Offline

KDE has option to automount during login. I found that to be the best solution.

[email protected]

As you mentioned elsewhere it's encrypted.

Take a look at /etc/crypttab and creating and adding a key file that can unlock the drive.

Essentially your additional SSD will have both a password and a file containing a password that can unlock the drive. When you unlock your root filesystem (I'm guessing at boot) it will then have the key file that can unlock the SSD.

Something like cryptsetup luksAddKey /dev/pathtossd --new-keyfile /etc/newpassword

Systemd might make this easier to setup nowadays.

[email protected]

Be sure to restrict it to only be readable by root.

sudo chmod 400 /etc/newpassword

[email protected]

Will that add two minutes to my boot time though?

[email protected]

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.

[email protected]

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)

[email protected]

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.

agnos.is Forums

New SSD requires password to mount