I get the above every time I log in, with a pop-up asking for my password. It never used to happen on F30 but I created a new installation for F31 and it's been nagging me ever since. I also don't know why it talks about fedora_localhost-live as I've never installed Fedora from a live image. This install used LVM, against my better judgement, so that may have something to do with it.
This is under KDE, if it matters, and the pop-up just talks about "an application needing authentication", without saying which application.
Any thoughts?
poc
On Sat, 2020-02-01 at 16:20 -0700, Joe Zeff wrote:
On 02/01/2020 03:51 PM, Patrick O'Callaghan wrote:
Any thoughts?
Two. First, check to see if it's listed in /etc/fstab and second, find out if the "file" exists.
The file (/dev/fedora_localhost-live/home) does exist. /etc/fstab contains:
$ grep live /etc/fstab /dev/mapper/fedora_localhost--live-root / ext4 defaults 1 1 /dev/mapper/fedora_localhost--live-swap none swap defaults 0 0
That would imply I should add /dev/fedora_localhost-live/home to /etc/fstab, but it already contains:
$ grep home /etc/fstab UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 /home ext4 defaults 0 0
so I'm not clear on the logic of all this.
poc
On 2020-02-02 06:51, Patrick O'Callaghan wrote:
I get the above every time I log in, with a pop-up asking for my password. It never used to happen on F30 but I created a new installation for F31 and it's been nagging me ever since. I also don't know why it talks about fedora_localhost-live as I've never installed Fedora from a live image. This install used LVM, against my better judgement, so that may have something to do with it.
This is under KDE, if it matters, and the pop-up just talks about "an application needing authentication", without saying which application.
Any thoughts?
Thoughts, no. Questions, yes.
You said you didn't install from live. So, how did you install? You made /home on its own partition, yes? You said it used LVM against your better judgement. How did that happen? Are you saying you need to supply your user password twice to get to the KDE session?
On Sun, 2020-02-02 at 22:38 +0800, Ed Greshko wrote:
On 2020-02-02 06:51, Patrick O'Callaghan wrote:
I get the above every time I log in, with a pop-up asking for my password. It never used to happen on F30 but I created a new installation for F31 and it's been nagging me ever since. I also don't know why it talks about fedora_localhost-live as I've never installed Fedora from a live image. This install used LVM, against my better judgement, so that may have something to do with it.
This is under KDE, if it matters, and the pop-up just talks about "an application needing authentication", without saying which application.
Any thoughts?
Thoughts, no. Questions, yes.
You said you didn't install from live. So, how did you install?
From an install ISO, but not the Live distro.
You made /home on its own partition, yes?
Yes, as always.
You said it used LVM against your better judgement. How did that happen?
I normally disable it at installation, but this time I couldn't seem to find the right combination of options. The last time I did a full install is about 5 years ago and I've just been upgrading ever since. The new install was prompted by getting a new SSD and deciding to bite the bullet and use UEFI for boot instead of MBR.
Are you saying you need to supply your user password twice to get to the KDE session?
No, the login appears to work, but always shows this pop-up. Nevertheless, nothing seems to be disabled. In fact I often don't notice it because it's behind some other window. It's an annoyance rather than a showstopper.
poc
On 02/02/2020 07:14 AM, Patrick O'Callaghan wrote:
On Sat, 2020-02-01 at 16:20 -0700, Joe Zeff wrote:
On 02/01/2020 03:51 PM, Patrick O'Callaghan wrote:
Any thoughts?
Two. First, check to see if it's listed in /etc/fstab and second, find out if the "file" exists.
The file (/dev/fedora_localhost-live/home) does exist. /etc/fstab contains:
$ grep live /etc/fstab /dev/mapper/fedora_localhost--live-root / ext4 defaults 1 1 /dev/mapper/fedora_localhost--live-swap none swap defaults 0 0
That would imply I should add /dev/fedora_localhost-live/home to /etc/fstab, but it already contains:
$ grep home /etc/fstab UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 /home ext4 defaults 0 0
so I'm not clear on the logic of all this.
I don't know why it's trying to mount that partition at boot, but I do know a workaround. First, create a mountpoint, such as /mnt/foo. Then, add a line to /etc/fstab, mounting the partition there, but instead of using the default options, use noauto users. This will keep it from mounting at boot, but if you want to look at what's there, you can mount it as an ordinary user. HTH, HAND.
On 2020-02-03 02:27, Patrick O'Callaghan wrote:
No, the login appears to work, but always shows this pop-up. Nevertheless, nothing seems to be disabled. In fact I often don't notice it because it's behind some other window. It's an annoyance rather than a showstopper.
In your initial post you said. "the pop-up just talks about "an application needing authentication", without saying which application"
That doesn't sound like it has anything to do with mounting.
If instead of logging in to a KDE session you ssh in or login from a console session do you get a request to supply your pw a second time? Is /home mounted when you login in that way?
On Mon, 2020-02-03 at 03:41 +0800, Ed Greshko wrote:
On 2020-02-03 02:27, Patrick O'Callaghan wrote:
No, the login appears to work, but always shows this pop-up. Nevertheless, nothing seems to be disabled. In fact I often don't notice it because it's behind some other window. It's an annoyance rather than a showstopper.
In your initial post you said. "the pop-up just talks about "an application needing authentication", without saying which application"
That doesn't sound like it has anything to do with mounting.
I agree.
If instead of logging in to a KDE session you ssh in or login from a console session do you get a request to supply your pw a second time? Is /home mounted when you login in that way?
On a fresh boot, logging into a text console with root, /home is mounted.
On logging into my KDE session, the pop-up appears. A screenshot can be seen at:
https://drive.google.com/open?id=1NqOQLgkf1dqBFd3hp4hhP59-y66kwrf2
poc
On Sun, 2020-02-02 at 11:44 -0700, Joe Zeff wrote:
On 02/02/2020 07:14 AM, Patrick O'Callaghan wrote:
On Sat, 2020-02-01 at 16:20 -0700, Joe Zeff wrote:
On 02/01/2020 03:51 PM, Patrick O'Callaghan wrote:
Any thoughts?
Two. First, check to see if it's listed in /etc/fstab and second, find out if the "file" exists.
The file (/dev/fedora_localhost-live/home) does exist. /etc/fstab contains:
$ grep live /etc/fstab /dev/mapper/fedora_localhost--live-root / ext4 defaults 1 1 /dev/mapper/fedora_localhost--live-swap none swap defaults 0 0
That would imply I should add /dev/fedora_localhost-live/home to /etc/fstab, but it already contains:
$ grep home /etc/fstab UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 /home ext4 defaults 0 0
so I'm not clear on the logic of all this.
I don't know why it's trying to mount that partition at boot, but I do know a workaround. First, create a mountpoint, such as /mnt/foo. Then, add a line to /etc/fstab, mounting the partition there, but instead of using the default options, use noauto users. This will keep it from mounting at boot, but if you want to look at what's there, you can mount it as an ordinary user. HTH, HAND.
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
poc
On 02/02/2020 03:25 PM, Patrick O'Callaghan wrote:
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
Yes, I understand that, but I'm not clear if the partition you're asking about is the one mounted at /home.
On 2020-02-03 06:24, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 03:41 +0800, Ed Greshko wrote:
On 2020-02-03 02:27, Patrick O'Callaghan wrote:
No, the login appears to work, but always shows this pop-up. Nevertheless, nothing seems to be disabled. In fact I often don't notice it because it's behind some other window. It's an annoyance rather than a showstopper.
In your initial post you said. "the pop-up just talks about "an application needing authentication", without saying which application"
That doesn't sound like it has anything to do with mounting.
I agree.
If instead of logging in to a KDE session you ssh in or login from a console session do you get a request to supply your pw a second time? Is /home mounted when you login in that way?
On a fresh boot, logging into a text console with root, /home is mounted.
On logging into my KDE session, the pop-up appears. A screenshot can be seen at:
https://drive.google.com/open?id=1NqOQLgkf1dqBFd3hp4hhP59-y66kwrf2
Well, it seems related to udisks2.
What processes are running at pids 1942 and 944?
Shot in the dark....after reading a few, scattered google hits, what happens if you change
UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 to the actual partition definition?
On 2020-02-03 06:25, Patrick O'Callaghan wrote:
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
I don't know why it should be needed....but this may provide a workaround?
https://www.dynacont.net/documentation/linux/udisks2_polkit_Allow_unauthenti...
And I forgot how to read those entries, and may be totally wrong, but does
dconf list /org/
have freedesktop in the list?
On Sun, Feb 2, 2020, 3:42 PM Joe Zeff joe@zeff.us wrote:
On 02/02/2020 03:25 PM, Patrick O'Callaghan wrote:
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
Yes, I understand that, but I'm not clear if the partition you're asking about is the one mounted at /home.
This. Could you share the output of `mount` and `sudo lvdisplay`?
On Sun, 2020-02-02 at 16:16 -0700, T.C. Hollingsworth wrote:
On Sun, Feb 2, 2020, 3:42 PM Joe Zeff joe@zeff.us wrote:
On 02/02/2020 03:25 PM, Patrick O'Callaghan wrote:
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
Yes, I understand that, but I'm not clear if the partition you're asking about is the one mounted at /home.
This. Could you share the output of `mount` and `sudo lvdisplay`?
$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime,seclabel) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,seclabel,size=8009252k,nr_inodes=2002313,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,seclabel,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,seclabel,mode=755) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,seclabel,nsdelegate) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime,seclabel) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) /dev/mapper/fedora_localhost--live-root on / type ext4 (rw,relatime,seclabel) selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=17145) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime,seclabel) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,seclabel,pagesize=2M) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime,seclabel) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,seclabel) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) systemd-1 on /storage/Backups type autofs (rw,relatime,fd=54,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=23400) /dev/sda5 on /home type ext4 (rw,relatime,seclabel) /dev/sda2 on /boot type ext4 (rw,relatime,seclabel) /dev/sda1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=winnt,errors=remount-ro) /dev/sdc1 on /oldhome type btrfs (rw,relatime,seclabel,space_cache,subvolid=5,subvol=/) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=1612360k,mode=700) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,seclabel,size=1612360k,mode=700,uid=1000,gid=1000) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) /dev/fuse on /run/user/1000/doc type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
$ sudo lvdisplay --- Logical volume --- LV Path /dev/fedora_localhost-live/swap LV Name swap VG Name fedora_localhost-live LV UUID fTxmLI-LtUa-zBff-Ozyv-GiEY-XKhJ-nLTLFY LV Write Access read/write LV Creation host, time localhost-live, 2019-11-07 18:23:56 +0000 LV Status available # open 2 LV Size 7.72 GiB Current LE 1977 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0
--- Logical volume --- LV Path /dev/fedora_localhost-live/home LV Name home VG Name fedora_localhost-live LV UUID 20haaX-QwiB-aCN1-acvW-WAZT-JSbP-RoaiVF LV Write Access read/write LV Creation host, time localhost-live, 2019-11-07 18:23:57 +0000 LV Status available # open 0 LV Size <33.62 GiB Current LE 8606 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1
--- Logical volume --- LV Path /dev/fedora_localhost-live/root LV Name root VG Name fedora_localhost-live LV UUID 7i9QWE-pyJj-MbGC-pAP8-AQsK-Cb6H-1u5LOi LV Write Access read/write LV Creation host, time localhost-live, 2019-11-07 18:23:57 +0000 LV Status available # open 1 LV Size <68.86 GiB Current LE 17628 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:2
poc
On Mon, 2020-02-03 at 07:03 +0800, Ed Greshko wrote:
On 2020-02-03 06:24, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 03:41 +0800, Ed Greshko wrote:
On 2020-02-03 02:27, Patrick O'Callaghan wrote:
No, the login appears to work, but always shows this pop-up. Nevertheless, nothing seems to be disabled. In fact I often don't notice it because it's behind some other window. It's an annoyance rather than a showstopper.
In your initial post you said. "the pop-up just talks about "an application needing authentication", without saying which application"
That doesn't sound like it has anything to do with mounting.
I agree.
If instead of logging in to a KDE session you ssh in or login from a console session do you get a request to supply your pw a second time? Is /home mounted when you login in that way?
On a fresh boot, logging into a text console with root, /home is mounted.
On logging into my KDE session, the pop-up appears. A screenshot can be seen at:
https://drive.google.com/open?id=1NqOQLgkf1dqBFd3hp4hhP59-y66kwrf2
Well, it seems related to udisks2.
What processes are running at pids 1942 and 944?
$ sudo ls -l /proc/944/exe /proc/1942/exe lrwxrwxrwx. 1 poc poc 0 Feb 3 11:04 /proc/1942/exe -> /usr/bin/kded5 lrwxrwxrwx. 1 root root 0 Feb 3 11:04 /proc/944/exe -> /usr/libexec/udisks2/udisksd
Shot in the dark....after reading a few, scattered google hits, what happens if you change
UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 to the actual partition definition?
I'll try that in a while after I reboot.
poc
On Mon, 2020-02-03 at 07:12 +0800, Ed Greshko wrote:
I don't know why it should be needed....but this may provide a workaround?
https://www.dynacont.net/documentation/linux/udisks2_polkit_Allow_unauthenti...
Interesting, though I would have thought that /home would be mounted by root and not need special perms.
And I forgot how to read those entries, and may be totally wrong, but does
dconf list /org/
have freedesktop in the list?
No it doesn't:
$ dconf list /org/ blueberry/ cinnamon/ fedoraproject/ gnome/ gnucash/ gtk/ mate/ onboard/ virt-manager/ yorba/
poc
On 2020-02-03 19:06, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 07:03 +0800, Ed Greshko wrote:
On 2020-02-03 06:24, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 03:41 +0800, Ed Greshko wrote:
On 2020-02-03 02:27, Patrick O'Callaghan wrote:
No, the login appears to work, but always shows this pop-up. Nevertheless, nothing seems to be disabled. In fact I often don't notice it because it's behind some other window. It's an annoyance rather than a showstopper.
In your initial post you said. "the pop-up just talks about "an application needing authentication", without saying which application"
That doesn't sound like it has anything to do with mounting.
I agree.
If instead of logging in to a KDE session you ssh in or login from a console session do you get a request to supply your pw a second time? Is /home mounted when you login in that way?
On a fresh boot, logging into a text console with root, /home is mounted.
On logging into my KDE session, the pop-up appears. A screenshot can be seen at:
https://drive.google.com/open?id=1NqOQLgkf1dqBFd3hp4hhP59-y66kwrf2
Well, it seems related to udisks2.
What processes are running at pids 1942 and 944?
$ sudo ls -l /proc/944/exe /proc/1942/exe lrwxrwxrwx. 1 poc poc 0 Feb 3 11:04 /proc/1942/exe -> /usr/bin/kded5 lrwxrwxrwx. 1 root root 0 Feb 3 11:04 /proc/944/exe -> /usr/libexec/udisks2/udisksd
Shot in the dark....after reading a few, scattered google hits, what happens if you change
UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 to the actual partition definition?
I'll try that in a while after I reboot.
OK....
The odd thing I see in another answer is the output of mount. It has....
/dev/sda5 on /home type ext4 (rw,relatime,seclabel)
Which seems not to be related to LVM
On Sun, 2020-02-02 at 15:40 -0700, Joe Zeff wrote:
On 02/02/2020 03:25 PM, Patrick O'Callaghan wrote:
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
Yes, I understand that, but I'm not clear if the partition you're asking about is the one mounted at /home.
This is the complete device set:
$ lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 vfat 13EE-9841 579.2M 3% /boot/efi ├─sda2 ext4 39fbc534-68c2-421b-9bcd-96fd22320f37 675.2M 24% /boot ├─sda3 LVM2_member ecqU7k-cl5P-kOF6-VgjM-klvA-gS5h-nz4N5t │ ├─fedora_localhost--live-swap swap 6c16e7ba-a483-4832-ab9b-a32af7f46d62 [SWAP] │ ├─fedora_localhost--live-home ext4 929f2710-cb9e-44d4-bdd8-52f733a408e6 │ └─fedora_localhost--live-root ext4 d38245ca-2e6d-491f-991b-c93cb76ce1af 36G 41% / ├─sda4 LVM2_member mspawI-clTS-d00z-ToYG-EfYJ-NAaS-DUn3Vp └─sda5 ext4 home c1df25d9-4c89-43a5-886d-3bbbf8513b22 277.6G 79% /home sdb ├─sdb1 ntfs Recovery DEC47E01C47DDBE9 ├─sdb2 vfat 6881-A320 ├─sdb3 ├─sdb4 ntfs 2224823A248210C9 └─sdb5 ntfs 1C36E53036E50B98 sdc └─sdc1 btrfs home 6496d6da-6b7a-4cdd-9bb8-767c08d1c84e 294.4G 84% /oldhome sr0
poc
On Mon, 2020-02-03 at 19:11 +0800, Ed Greshko wrote:
On 2020-02-03 19:06, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 07:03 +0800, Ed Greshko wrote:
On 2020-02-03 06:24, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 03:41 +0800, Ed Greshko wrote:
On 2020-02-03 02:27, Patrick O'Callaghan wrote:
No, the login appears to work, but always shows this pop-up. Nevertheless, nothing seems to be disabled. In fact I often don't notice it because it's behind some other window. It's an annoyance rather than a showstopper.
In your initial post you said. "the pop-up just talks about "an application needing authentication", without saying which application"
That doesn't sound like it has anything to do with mounting.
I agree.
If instead of logging in to a KDE session you ssh in or login from a console session do you get a request to supply your pw a second time? Is /home mounted when you login in that way?
On a fresh boot, logging into a text console with root, /home is mounted.
On logging into my KDE session, the pop-up appears. A screenshot can be seen at:
https://drive.google.com/open?id=1NqOQLgkf1dqBFd3hp4hhP59-y66kwrf2
Well, it seems related to udisks2.
What processes are running at pids 1942 and 944?
$ sudo ls -l /proc/944/exe /proc/1942/exe lrwxrwxrwx. 1 poc poc 0 Feb 3 11:04 /proc/1942/exe -> /usr/bin/kded5 lrwxrwxrwx. 1 root root 0 Feb 3 11:04 /proc/944/exe -> /usr/libexec/udisks2/udisksd
Shot in the dark....after reading a few, scattered google hits, what happens if you change
UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 to the actual partition definition?
I'll try that in a while after I reboot.
OK....
The odd thing I see in another answer is the output of mount. It has....
/dev/sda5 on /home type ext4 (rw,relatime,seclabel)
Which seems not to be related to LVM
Indeed, curiouser and curiouser. There does appear to be an inconsistency somewhere.
poc
On 03.02.20 12:04, Patrick O'Callaghan wrote:
On Sun, 2020-02-02 at 16:16 -0700, T.C. Hollingsworth wrote:
On Sun, Feb 2, 2020, 3:42 PM Joe Zeff joe@zeff.us wrote:
On 02/02/2020 03:25 PM, Patrick O'Callaghan wrote:
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
Yes, I understand that, but I'm not clear if the partition you're asking about is the one mounted at /home.
This. Could you share the output of `mount` and `sudo lvdisplay`?
$ mount
...
/dev/mapper/fedora_localhost--live-root on / type ext4 (rw,relatime,seclabel)
..
$ sudo lvdisplay
..
--- Logical volume --- LV Path /dev/fedora_localhost-live/root LV Name root VG Name fedora_localhost-live
...
what's with the minus signs in both related to / (root)
the first has 2 minus signs, the second only 1.
On 03.02.20 12:15, Patrick O'Callaghan wrote:
On Sun, 2020-02-02 at 15:40 -0700, Joe Zeff wrote:
On 02/02/2020 03:25 PM, Patrick O'Callaghan wrote:
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
Yes, I understand that, but I'm not clear if the partition you're asking about is the one mounted at /home.
This is the complete device set:
$ lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 vfat 13EE-9841 579.2M 3% /boot/efi ├─sda2 ext4 39fbc534-68c2-421b-9bcd-96fd22320f37 675.2M 24% /boot ├─sda3 LVM2_member ecqU7k-cl5P-kOF6-VgjM-klvA-gS5h-nz4N5t │ ├─fedora_localhost--live-swap swap 6c16e7ba-a483-4832-ab9b-a32af7f46d62 [SWAP] │ ├─fedora_localhost--live-home ext4 929f2710-cb9e-44d4-bdd8-52f733a408e6 │ └─fedora_localhost--live-root ext4 d38245ca-2e6d-491f-991b-c93cb76ce1af 36G 41% /
the UUID doesn't match with the one your provided in the previous post:
--- Logical volume --- LV Path /dev/fedora_localhost-live/root LV Name root VG Name fedora_localhost-live LV UUID 7i9QWE-pyJj-MbGC-pAP8-AQsK-Cb6H-1u5LOi
On Mon, 2020-02-03 at 12:29 +0100, sixpack13 wrote:
On 03.02.20 12:15, Patrick O'Callaghan wrote:
On Sun, 2020-02-02 at 15:40 -0700, Joe Zeff wrote:
On 02/02/2020 03:25 PM, Patrick O'Callaghan wrote:
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
Yes, I understand that, but I'm not clear if the partition you're asking about is the one mounted at /home.
This is the complete device set:
$ lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 vfat 13EE-9841 579.2M 3% /boot/efi ├─sda2 ext4 39fbc534-68c2-421b-9bcd-96fd22320f37 675.2M 24% /boot ├─sda3 LVM2_member ecqU7k-cl5P-kOF6-VgjM-klvA-gS5h-nz4N5t │ ├─fedora_localhost--live-swap swap 6c16e7ba-a483-4832-ab9b-a32af7f46d62 [SWAP] │ ├─fedora_localhost--live-home ext4 929f2710-cb9e-44d4-bdd8-52f733a408e6 │ └─fedora_localhost--live-root ext4 d38245ca-2e6d-491f-991b-c93cb76ce1af 36G 41% /
the UUID doesn't match with the one your provided in the previous post:
--- Logical volume --- LV Path /dev/fedora_localhost-live/root LV Name root VG Name fedora_localhost-live LV UUID 7i9QWE-pyJj-MbGC-pAP8-AQsK-Cb6H-1u5LOi
Neither does the name (two dashes instead of one, as you noted in another reply) so I'm not sure what's going on here.
poc
On 2/3/20 5:01 AM, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 12:29 +0100, sixpack13 wrote:
On 03.02.20 12:15, Patrick O'Callaghan wrote:
On Sun, 2020-02-02 at 15:40 -0700, Joe Zeff wrote:
On 02/02/2020 03:25 PM, Patrick O'Callaghan wrote:
I'll bear it in mind, but given that this is /home, it should be mounted anyway (and in fact it is, see my reply to Ed).
Yes, I understand that, but I'm not clear if the partition you're asking about is the one mounted at /home.
This is the complete device set:
$ lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda ├─sda1 vfat 13EE-9841 579.2M 3% /boot/efi ├─sda2 ext4 39fbc534-68c2-421b-9bcd-96fd22320f37 675.2M 24% /boot ├─sda3 LVM2_member ecqU7k-cl5P-kOF6-VgjM-klvA-gS5h-nz4N5t │ ├─fedora_localhost--live-swap swap 6c16e7ba-a483-4832-ab9b-a32af7f46d62 [SWAP] │ ├─fedora_localhost--live-home ext4 929f2710-cb9e-44d4-bdd8-52f733a408e6 │ └─fedora_localhost--live-root ext4 d38245ca-2e6d-491f-991b-c93cb76ce1af 36G 41% /
the UUID doesn't match with the one your provided in the previous post:
--- Logical volume --- LV Path /dev/fedora_localhost-live/root LV Name root VG Name fedora_localhost-live LV UUID 7i9QWE-pyJj-MbGC-pAP8-AQsK-Cb6H-1u5LOi
Neither does the name (two dashes instead of one, as you noted in another reply) so I'm not sure what's going on here.
The "two dashes thing" is an artifact of the device mapper (/dev/mapper) which creates symlinks to the physicals. To include the path information in the link hyphens are replaced with two hyphens and slashes are replaced with a single hyphen.
To manually mount an LVM partition you may use the full mapper path with the "two dashes thing" or the more familiar /dev/fedora_localhost-live/home. They're equivalent.
On Mon, 2020-02-03 at 08:04 -0800, Mike Wright wrote:
Neither does the name (two dashes instead of one, as you noted in another reply) so I'm not sure what's going on here.
The "two dashes thing" is an artifact of the device mapper (/dev/mapper) which creates symlinks to the physicals. To include the path information in the link hyphens are replaced with two hyphens and slashes are replaced with a single hyphen.
To manually mount an LVM partition you may use the full mapper path with the "two dashes thing" or the more familiar /dev/fedora_localhost-live/home. They're equivalent.
OK, I never knew that, thanks
poc
On Mon, 2020-02-03 at 19:11 +0800, Ed Greshko wrote:
On 2020-02-03 19:06, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 07:03 +0800, Ed Greshko wrote:
On 2020-02-03 06:24, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 03:41 +0800, Ed Greshko wrote:
On 2020-02-03 02:27, Patrick O'Callaghan wrote:
No, the login appears to work, but always shows this pop-up. Nevertheless, nothing seems to be disabled. In fact I often don't notice it because it's behind some other window. It's an annoyance rather than a showstopper.
In your initial post you said. "the pop-up just talks about "an application needing authentication", without saying which application"
That doesn't sound like it has anything to do with mounting.
I agree.
If instead of logging in to a KDE session you ssh in or login from a console session do you get a request to supply your pw a second time? Is /home mounted when you login in that way?
On a fresh boot, logging into a text console with root, /home is mounted.
On logging into my KDE session, the pop-up appears. A screenshot can be seen at:
https://drive.google.com/open?id=1NqOQLgkf1dqBFd3hp4hhP59-y66kwrf2
Well, it seems related to udisks2.
What processes are running at pids 1942 and 944?
$ sudo ls -l /proc/944/exe /proc/1942/exe lrwxrwxrwx. 1 poc poc 0 Feb 3 11:04 /proc/1942/exe -> /usr/bin/kded5 lrwxrwxrwx. 1 root root 0 Feb 3 11:04 /proc/944/exe -> /usr/libexec/udisks2/udisksd
Shot in the dark....after reading a few, scattered google hits, what happens if you change
UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 to the actual partition definition?
I'll try that in a while after I reboot.
OK....
The odd thing I see in another answer is the output of mount. It has....
/dev/sda5 on /home type ext4 (rw,relatime,seclabel)
Which seems not to be related to LVM
Further to that:
$ ls -l /dev/disk/by-uuid/929f2710-cb9e-44d4-bdd8-52f733a408e6 lrwxrwxrwx. 1 root root 10 Feb 3 16:30 /dev/disk/by-uuid/929f2710-cb9e-44d4-bdd8-52f733a408e6 -> ../../dm-1 $ sudo dmsetup ls fedora_localhost--live-home (253:1) fedora_localhost--live-swap (253:0) fedora_localhost--live-root (253:2)
I also tried your suggestion of mounting the partition (dev/sda5) directly rather than via the UUID entry and it made no difference (on a fresh boot).
poc
I may be missing something here, but here's what I understand....
The system is mounting /dev/sda5 as /home, using the UUID of the file system on /dev/sda5, as specified in /etc/fstab.
*Something* is wanting something else that it somehow knows is located on LV fedora_localhost--live-home. What it wants or how it knows it is there is beyond me - sorry!
But my question would be - which is the *correct* file system for /home? The one on sda5, or the one on fedora_localhost--live-home?
On 2/3/20 8:52 AM, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 19:11 +0800, Ed Greshko wrote:
On 2020-02-03 19:06, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 07:03 +0800, Ed Greshko wrote:
On 2020-02-03 06:24, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 03:41 +0800, Ed Greshko wrote:
On 2020-02-03 02:27, Patrick O'Callaghan wrote: > No, the login appears to work, but always shows this pop-up. > Nevertheless, nothing seems to be disabled. In fact I often don't > notice it because it's behind some other window. It's an annoyance > rather than a showstopper. In your initial post you said. "the pop-up just talks about "an application needing authentication", without saying which application"
That doesn't sound like it has anything to do with mounting.
I agree.
If instead of logging in to a KDE session you ssh in or login from a console session do you get a request to supply your pw a second time? Is /home mounted when you login in that way?
On a fresh boot, logging into a text console with root, /home is mounted.
On logging into my KDE session, the pop-up appears. A screenshot can be seen at:
https://drive.google.com/open?id=1NqOQLgkf1dqBFd3hp4hhP59-y66kwrf2
Well, it seems related to udisks2.
What processes are running at pids 1942 and 944?
$ sudo ls -l /proc/944/exe /proc/1942/exe lrwxrwxrwx. 1 poc poc 0 Feb 3 11:04 /proc/1942/exe -> /usr/bin/kded5 lrwxrwxrwx. 1 root root 0 Feb 3 11:04 /proc/944/exe -> /usr/libexec/udisks2/udisksd
Shot in the dark....after reading a few, scattered google hits, what happens if you change
UUID=c1df25d9-4c89-43a5-886d-3bbbf8513b22 to the actual partition definition?
I'll try that in a while after I reboot.
OK....
The odd thing I see in another answer is the output of mount. It has....
/dev/sda5 on /home type ext4 (rw,relatime,seclabel)
Which seems not to be related to LVM
Further to that:
$ ls -l /dev/disk/by-uuid/929f2710-cb9e-44d4-bdd8-52f733a408e6 lrwxrwxrwx. 1 root root 10 Feb 3 16:30 /dev/disk/by-uuid/929f2710-cb9e-44d4-bdd8-52f733a408e6 -> ../../dm-1 $ sudo dmsetup ls fedora_localhost--live-home (253:1) fedora_localhost--live-swap (253:0) fedora_localhost--live-root (253:2)
I also tried your suggestion of mounting the partition (dev/sda5) directly rather than via the UUID entry and it made no difference (on a fresh boot).
Patrick,
Some quick notes about lvm. The essence of LVM is the volume group (VG). Volume groups contain logical volumes (LV). Volume groups are defined by specifying the raw devices, the physical volumes (PV), that provide the storage. In order to attach a PV to a VG the raw device /dev/sdX must be tagged as a PV. Until that is done (pvcreate) a raw device cannot be part of a VG. Once within a VG the raw device isn't really mountable because the filesystem on it is created at the LV level, not the raw device level.
Now as to sd5: try the command "pvs". It will show the tagged (defined) PVs AND it will show which, if any, VGs that they belong to.
If sda5 is NOT listed by "pvs" then your mount environment is mixed raw/LVM. Any way you look at it, you may mount both the raw device and the LV at the same point but only the most recent will be visible. I also have a hunch that mounting a raw device that is part of a VG is an invitation to disaster.
I hope that clarifies a bit where LVM fits into all this.
:m
On Mon, 2020-02-03 at 12:17 -0800, Mike Wright wrote:
Some quick notes about lvm. The essence of LVM is the volume group (VG). Volume groups contain logical volumes (LV). Volume groups are defined by specifying the raw devices, the physical volumes (PV), that provide the storage. In order to attach a PV to a VG the raw device /dev/sdX must be tagged as a PV. Until that is done (pvcreate) a raw device cannot be part of a VG. Once within a VG the raw device isn't really mountable because the filesystem on it is created at the LV level, not the raw device level.
Yes, I already understand that much in theory.
Now as to sd5: try the command "pvs". It will show the tagged (defined) PVs AND it will show which, if any, VGs that they belong to.
$ sudo pvs PV VG Fmt Attr PSize PFree /dev/sda3 fedora_localhost-live lvm2 a-- <128.00g <17.80g /dev/sda4 fedora_localhost-live lvm2 a-- <16.00g <16.00g $
If sda5 is NOT listed by "pvs" then your mount environment is mixed raw/LVM.
That appears to be the case.
Any way you look at it, you may mount both the raw device and the LV at the same point but only the most recent will be visible. I also have a hunch that mounting a raw device that is part of a VG is an invitation to disaster.
It wouldn't surprise me. How can I unravel this (short of a complete reinstallation)? I'm not enamoured of LVM and would be quite happy to revert to basic partitioning, but if that isn't feasible I'm willing to move forward to LVM-only if that's what it takes.
Thanks.
poc
On 2020-02-04 06:56, Patrick O'Callaghan wrote:
It wouldn't surprise me. How can I unravel this (short of a complete reinstallation)? I'm not enamoured of LVM and would be quite happy to revert to basic partitioning, but if that isn't feasible I'm willing to move forward to LVM-only if that's what it takes.
Well, first I would try to mount /dev/mapper/fedora_localhost--live-home someplace to see if there is any data to save.
If not, I'd use lvremove to get rid of it.
And then I'd use lvextend to distribute the freed space to root. That, or use pvresize to release the space from the pv.
Of course, I'd have to learn about those commands a bit more since it has been years since I've used them. :-) :-)
On 20-02-03 17:56:59, Patrick O'Callaghan wrote: ...
$ sudo pvs PV VG Fmt Attr PSize PFree /dev/sda3 fedora_localhost-live lvm2 a-- <128.00g <17.80g /dev/sda4 fedora_localhost-live lvm2 a-- <16.00g <16.00g $
...
It's very unusual to have two partitions on the same device provide Physical Volumes for a single Volume Group. It may be that none of the space on sda4 is in use, and it might be removed and the space used for something (like extending sda5).
Earlier you showed the output of `mount` and the output of `lvdisplay`. fedora_localhost-live/home does not appear to be in use, though swap and root are used. Whatever is asking for a password for home appears to be failing. Possibly any password would work as well. Mounting home might show that it is empty and simply a waste of 33 GB.
This all seems confused enough that starting over might be best.
On 2/3/20 2:56 PM, Patrick O'Callaghan wrote:
On Mon, 2020-02-03 at 12:17 -0800, Mike Wright wrote:
Some quick notes about lvm. The essence of LVM is the volume group (VG). Volume groups contain logical volumes (LV). Volume groups are defined by specifying the raw devices, the physical volumes (PV), that provide the storage. In order to attach a PV to a VG the raw device /dev/sdX must be tagged as a PV. Until that is done (pvcreate) a raw device cannot be part of a VG. Once within a VG the raw device isn't really mountable because the filesystem on it is created at the LV level, not the raw device level.
Yes, I already understand that much in theory.
Now as to sd5: try the command "pvs". It will show the tagged (defined) PVs AND it will show which, if any, VGs that they belong to.
$ sudo pvs PV VG Fmt Attr PSize PFree /dev/sda3 fedora_localhost-live lvm2 a-- <128.00g <17.80g /dev/sda4 fedora_localhost-live lvm2 a-- <16.00g <16.00g $
If sda5 is NOT listed by "pvs" then your mount environment is mixed raw/LVM.
That appears to be the case.
Any way you look at it, you may mount both the raw device and the LV at the same point but only the most recent will be visible. I also have a hunch that mounting a raw device that is part of a VG is an invitation to disaster.
It wouldn't surprise me. How can I unravel this (short of a complete reinstallation)? I'm not enamoured of LVM and would be quite happy to revert to basic partitioning, but if that isn't feasible I'm willing to move forward to LVM-only if that's what it takes.
I just went through the beginning of this thread. The issue was that attempting to mount /dev/fedora_localhost-live/home required a password.
Are you sure there's a problem?
Your mount output shows root, swap, home. / and swap are on LVs and /home is /dev/sda5. As far as the system is concerned /dev/fedora_localhost-live/home is just another partition that, as any other, requires root privilege to mount.
Unless I'm really missing something here...
:m
PD: Ten paciencia chapulín. LVM podría ser tu amigo.
On 2/3/20 4:52 PM, Tony Nelson wrote:
On 20-02-03 17:56:59, Patrick O'Callaghan wrote: ...
$ sudo pvs PV VG Fmt Attr PSize PFree /dev/sda3 fedora_localhost-live lvm2 a-- <128.00g <17.80g /dev/sda4 fedora_localhost-live lvm2 a-- <16.00g <16.00g $
...
It's very unusual to have two partitions on the same device provide Physical Volumes for a single Volume Group. It may be that none of the space on sda4 is in use, and it might be removed and the space used for something (like extending sda5).
Earlier you showed the output of `mount` and the output of `lvdisplay`. fedora_localhost-live/home does not appear to be in use, though swap and root are used. Whatever is asking for a password for home appears to be failing. Possibly any password would work as well. Mounting home might show that it is empty and simply a waste of 33 GB.
This all seems confused enough that starting over might be best.
Hi Tony,
Not unusual to me. I play a lot with VMs, containers, and data collections. I found the learning curve/overhead in time, etc with BTRFS and ZFS too demanding of my resources, whereas a basic understanding of LVM made my life soooo much easier. Drives are so large now that I often partition them into 50G chunks, tag them as PVs, and hand them out to my VGs as needed initially or to extend/expand. I don't know how scalable my approach is but it's worked well for me so far.
:m
On Tue, 2020-02-04 at 07:35 +0800, Ed Greshko wrote:
On 2020-02-04 06:56, Patrick O'Callaghan wrote:
It wouldn't surprise me. How can I unravel this (short of a complete reinstallation)? I'm not enamoured of LVM and would be quite happy to revert to basic partitioning, but if that isn't feasible I'm willing to move forward to LVM-only if that's what it takes.
Well, first I would try to mount /dev/mapper/fedora_localhost--live-home someplace to see if there is any data to save.
I did. There's nothing on it.
If not, I'd use lvremove to get rid of it.
Did that.
And then I'd use lvextend to distribute the freed space to root. That, or use pvresize to release the space from the pv.
Not sure if there is any actual space, but I'll look into it.
Of course, I'd have to learn about those commands a bit more since it has been years since I've used them. :-) :-)
Same here :-)
However, after removing the LVM and rebooting, I'm no longer getting the pop-up, so I'm crossing my fingers and declaring the issue solved.
Many thanks to all who made suggestions.
poc
On Mon, 2020-02-03 at 19:52 -0500, Tony Nelson wrote:
On 20-02-03 17:56:59, Patrick O'Callaghan wrote: ...
$ sudo pvs PV VG Fmt Attr PSize PFree /dev/sda3 fedora_localhost-live lvm2 a-- <128.00g <17.80g /dev/sda4 fedora_localhost-live lvm2 a-- <16.00g <16.00g $
...
It's very unusual to have two partitions on the same device provide Physical Volumes for a single Volume Group. It may be that none of the space on sda4 is in use, and it might be removed and the space used for something (like extending sda5).
Earlier you showed the output of `mount` and the output of `lvdisplay`. fedora_localhost-live/home does not appear to be in use, though swap and root are used. Whatever is asking for a password for home appears to be failing. Possibly any password would work as well. Mounting home might show that it is empty and simply a waste of 33 GB.
This all seems confused enough that starting over might be best.
Following Ed's suggestion, I removed the LVM and the pop-up no longer appears. Now I have to figure out how to recover the space.
Thanks.
poc
-
Ed Greshko -
Go Canes -
Joe Zeff -
Mike Wright -
Patrick O'Callaghan -
sixpack13 -
T.C. Hollingsworth -
Tony Nelson