Second Disk Always Asks for Password when Logging in

Second Disk Always Asks for Password when Logging in. I have been trying advice from webpage after page.

My scenario is that I had Bazzite KDE installed. OS on SSD and game files on a HDD. I got fed up with being blocked by bazzite from fixing things; so I decided to wipe it and start fresh with Fedora KDE. This computer is just my experiment computer to learn and evaluate. Building a gaming PC and will be using Linux on there. So far it feels free and open compared to bazzite. Not going back. I did not do anything with the HDD. I checked the permissions for it and think it’s all fine. Steam is fine with it and I can use it just fine. But After setting known devices to be auto mounted I now have it asking for PW every-time I login. Not a deal breaker but would be nice if it were just available. As mentioned above I have tried half a dozen webpages of related advice given to others but either they don’t work for my setup or I am not understanding. Linux is new to me after moving away from MacOS. So could someone work through this with me so I can learn and fix issue.

Thanks

Maybe ‘own’ your disk with chown

Hi and welcome to :fedora: !

How did you set up the auto-mount? fstab or in KDE maybe?

1 Like

I used System settings Disks & Cameras and set Device Auto-Mount to All known devices mount on login and Attach. I checked that when it is mounted it’s in that list ant checked. that’s working. just ddisk still needs to be unlocked. I don’t recall it being encrypted unless Bazzite did it by default. I never had to autherise it in that version of Fedora.

I looked at a couple of chown solusions but i couldn’t get them to work. i suspect that was on my limited understanding. They didn’t elaborate on anything so tried some what seemed like logical alterations but didn’t understand. man lists confuse me also. not loked at the man for chown.

man is confusing.
try chown again, there are some good instructions online.
If you cant get it I’ll post a better reply when I’m in my PC tonight.

Please share the output of lsblk -f.

I’ll see what more I can figure out with ‘chown’…

FYI :
drwxrwxrwx 6 ekdor ekdor 4096 Mar 11 20:10 /run/media/ekdor/Storage

and:
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1 ext4 1.0 Storage d85ec932-f397-41ac-be7f-88f89c960c26 769.3G 11% /run/media/ekdor/Storage
sdb
├─sdb1 vfat FAT32 ECB7-A685 579.5M 3% /boot/efi
├─sdb2 ext4 1.0 f8b02d1b-a9ef-4ecb-a1be-63edfad55b49 1.3G 25% /boot
└─sdb3 btrfs fedora c614cced-0c1b-4ba2-8642-3766779ae43d 96.8G 12% /home
/
zram0 swap 1 zram0 864eb695-3197-4a62-b339-15c3b720ba32 [SWAP]

I looked at the doc for chown and it clarified something. I was seeing $user:$user on webpages but it looks like they should have written it as $user:$group ?? I had tried

‘sudo chown -R $ekdor:$ekdor /run/media/ekdor/Storage’

previously and again just now with no effect on my issue. I checked that the permissions info for the Storage is user=ekdor and group=ekdor. Running that it seems to pause for a bit as if it did something. It ends with a blank prompt and no info about what happened good or bad…

Try it without the $ signs. $user is a placeholder for your username and groupname.
So write:
sudo chown -R ekdor:ekdor /run/media/ekdor/Storage

3 Likes

ok I tried that. again it appears to do something, as in there was a wait and then a valid prompt. But on a reboot the password prompt popped up immediately after login.

I noticed that in permission properties, if i click group there is an option for wheel. should be selected instead of ekdor?

Also would I benefit from reformatting it with this install?

If I did what format would be best to use for storage?

Ext4 or Btrfs if you are using it solely on Linux.
However you should be able to get this fixed without a format.

For other reasons, I now don’t have much on it. So not too much hassle to do that. It’s currently ext4. yes only used locally on this system. It would be a good opportunity for me to get slightly familiar, Since this is just an assessment build and wont be the end of the world if I stuff it.

The issue sounds like this reported bug:

As an alternative to using auto-mount, you could instead configure the system to mount this drive on boot (i.e. it gets mounted as root before you log in, and your user account and password are not involved).

You could do this either by:

  1. manually editing /etc/fstab
  2. using the KDE Partition Manager app (right-click on the partition in question and choose “Edit Mount Point”

I’ll check this out after I reformatting. My thought it maybe my (former) Bazzite install formatted it as root access and not everyone. Noticing that it handles lots of things differently to Fedora Desktop (using/used KDE on both). For my experience it’s worth trying anyway.

If it had, root would be the group and chown should change that.

No harm formatting, we here don’t know how Bazzite works.

That’s determined by the permissions of the mountpoint: it’s not something that gets “formatted onto the drive” so to speak.