On starting up (or rebooting, obviously) this machine it always presents me with a box with the heading
Authentication is required to mount WDC WD20EARX-00PASB0 (/dev/sda1)
(screenshot attached).
I'm running the latest versions of everything (F33 workstation, KDE 5.20.5) presented to me but this has been happening for a long time, I don't even remember how many Fedora versions (I started at F15 I think).
It appears after the KDE login (I autostart KDE), but doesn't happen at all if I simply log out of my KDE session and then log back in.
Normally I give it my password (not the supervisor password, though my account is in the sudo-ers group) and carry on. To send this message I have purposely *not* given it the password and haven't closed the window, so it's still there but everything seems to function normally, so it's even not true, the disk must be mounted (it's the only hard drive mounted) so the authentication is *not* required. Just closing the window seems to be fine, too.
Any idea what's being upset here?
TIA
On Tue, 2021-03-30 at 11:00 +0100, Mark @ GMail wrote:
On starting up (or rebooting, obviously) this machine it always presents me with a box with the heading
Authentication is required to mount WDC WD20EARX-00PASB0 (/dev/sda1)
(screenshot attached).
I'm running the latest versions of everything (F33 workstation, KDE 5.20.5) presented to me but this has been happening for a long time, I don't even remember how many Fedora versions (I started at F15 I think).
It appears after the KDE login (I autostart KDE), but doesn't happen at all if I simply log out of my KDE session and then log back in.
Normally I give it my password (not the supervisor password, though my account is in the sudo-ers group) and carry on. To send this message I have purposely *not* given it the password and haven't closed the window, so it's still there but everything seems to function normally, so it's even not true, the disk must be mounted (it's the only hard drive mounted) so the authentication is *not* required. Just closing the window seems to be fine, too.
I've also been seeing this occasionally for many versions of Fedora/KDE, but less frequently now than in the past. I've no idea what causes it sometimes and not other times as my boot and login procedures are always the same. Some kind of race perhaps?
poc
On 3/30/21 7:00 AM, Mark @ GMail wrote:
On starting up (or rebooting, obviously) this machine it always presents me with a box with the heading
Authentication is required to mount WDC WD20EARX-00PASB0 (/dev/sda1)
(screenshot attached).
I'm running the latest versions of everything (F33 workstation, KDE 5.20.5) presented to me but this has been happening for a long time, I don't even remember how many Fedora versions (I started at F15 I think).
It appears after the KDE login (I autostart KDE), but doesn't happen at all if I simply log out of my KDE session and then log back in.
Normally I give it my password (not the supervisor password, though my account is in the sudo-ers group) and carry on. To send this message I have purposely *not* given it the password and haven't closed the window, so it's still there but everything seems to function normally, so it's even not true, the disk must be mounted (it's the only hard drive mounted) so the authentication is *not* required. Just closing the window seems to be fine, too.
Any idea what's being upset here?
I take it /dev/sda1 is / ?
Is there any difference in the output of mount from cli depending on if you provide your password to mount or not?
TIA
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
I take it /dev/sda1 is / ?
Is there any difference in the output of mount from cli depending on if you provide your password to mount or not?
sda1 is *everything* not just the root directory.
I don't have an answer to your question. This occurs during automatic startup and by the time it kicks in it's through the UI and the cli isn't showing. If I'm rebooting I generally switch it to show me the cli whilst it's going along but it's gone by the time this dialog shows itself.
I'm worried, due to lack of knowledge, about trying to unmount and then mount this, only, drive. Is it possible to do? I know how to stop the system automatically starting KDE and going to a login prompt instead, if that's required.
Mark
On 3/30/21 10:50 AM, Mark @ GMail wrote:
I take it /dev/sda1 is / ?
Is there any difference in the output of mount from cli depending on if you provide your password to mount or not?
sda1 is *everything* not just the root directory.
I don't have an answer to your question. This occurs during automatic startup and by the time it kicks in it's through the UI and the cli isn't showing. If I'm rebooting I generally switch it to show me the cli whilst it's going along but it's gone by the time this dialog shows itself.
I'm worried, due to lack of knowledge, about trying to unmount and then mount this, only, drive. Is it possible to do? I know how to stop the system automatically starting KDE and going to a login prompt instead, if that's required.
I meant the / filesystem .
No need to umount anything. When you reboot provide the password to the mount pop-up and then go to Konsole and run "sudo df -h". Reboot again and do the same thing without entering the password . Is the output of "sudo df -h" any different?
Mark
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
I meant the / filesystem .
No need to umount anything. When you reboot provide the password to the mount pop-up and then go to Konsole and run "sudo df -h". Reboot again and do the same thing without entering the password . Is the output of "sudo df -h" any different?
Oh, ok, yes, I can do that 8-) I'm definitely short on system knowledge, sorry.
Yes, in fact there is a difference, and a relevant one.
*With* the password an extra mount does show up, it says
/dev/sda1 477M 155M 293M 35% /run/media/mark/Boot
Guessing about this, presumably it *has* been mounted and used. If so, why is it complaining that a password is needed and *not* including it in the mount list if it doesn't get it?
Mark
On 3/30/21 11:23 AM, Mark @ GMail wrote:
I meant the / filesystem .
No need to umount anything. When you reboot provide the password to the mount pop-up and then go to Konsole and run "sudo df -h". Reboot again and do the same thing without entering the password . Is the output of "sudo df -h" any different?
Oh, ok, yes, I can do that 8-) I'm definitely short on system knowledge, sorry.
Yes, in fact there is a difference, and a relevant one.
*With* the password an extra mount does show up, it says
/dev/sda1 477M 155M 293M 35% /run/media/mark/Boot
Guessing about this, presumably it *has* been mounted and used. If so, why is it complaining that a password is needed and *not* including it in the mount list if it doesn't get it?
Seems like /dev/sda1 is /boot based on the mount point and the size? There is probably another /dev/sda1 entry in "sudo df -h" ?
Bottom line is you don't need to mount on KDE startup. You just need to find what is wanting to mount it though. Does Dolphin start up automatically when you login perhaps? Another place to look is in /etc/fstab .
Mark
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Seems like /dev/sda1 is /boot based on the mount point and the size? There is probably another /dev/sda1 entry in "sudo df -h" ?
Nope, it's the only one. The full output, err, slightly wrapped, is
devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 1.6G 1.6M 1.6G 1% /run /dev/mapper/ofedora-root 50G 23G 24G 50% / tempfs 8.0G 20K 8.0G 1% /tmp /dev/loop0 99M 99M 0 100% /var/lib/snapd/snap/core/10823 /dev/loop1 176M 176M 0 100% /var/lib/snapd/snap/postman/132 /dev/mapper/ofedora-alt 50G 53M 47G 1% /alt /dev/mapper/ofedora-home 1.7T 489G 1.2T 30% /home tmpfs 783M 208K 783M 1% /run/user/1000 /dev/sda1 477M 155M 293M 35% /run/media/mark/Boot
I may have fiddled with this at some point, I'm not sure.
Bottom line is you don't need to mount on KDE startup. You just need to find what is wanting to mount it though. Does Dolphin start up automatically when you login perhaps? Another place to look is in /etc/fstab .
I'm *trying* not to load Dolphin, nor any of the Gnome desktop, though I seem doomed to fail in that endeavour since it is there (how do I stop that!?) I use Krusader. It shows me mount manager which also shows that filesystem, but it looks like a report rather than a controller (?)
Nope, nothing about that in fstab. All it's got is (having removed some spaces)
/dev/mapper/ofedora-root / ext4 defaults 1 1 /dev/mapper/ofedora-alt /alt ext4 defaults 1 2 /dev/mapper/ofedora-home /home ext4 defaults 1 2 /dev/mapper/ofedora-swap swap swap defaults 0 0
tempfs /tmp tmpfs size=8G 0 0
I'm pretty sure I *have* fiddled with this at some time, but it says it was created by Anaconda on the 15th of March 2017...
So if it's Dolphin, what should I look at to stop this. And if it isn't, the same question applies :-)
Mark
On Tue, 2021-03-30 at 16:14 +0100, Mark @ GMail wrote:
Seems like /dev/sda1 is /boot based on the mount point and the size? There is probably another /dev/sda1 entry in "sudo df -h" ?
Nope, it's the only one. The full output, err, slightly wrapped, is
devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 1.6G 1.6M 1.6G 1% /run /dev/mapper/ofedora-root 50G 23G 24G 50% / tempfs 8.0G 20K 8.0G 1% /tmp /dev/loop0 99M 99M 0 100% /var/lib/snapd/snap/core/10823 /dev/loop1 176M 176M 0 100% /var/lib/snapd/snap/postman/132 /dev/mapper/ofedora-alt 50G 53M 47G 1% /alt /dev/mapper/ofedora-home 1.7T 489G 1.2T 30% /home tmpfs 783M 208K 783M 1% /run/user/1000 /dev/sda1 477M 155M 293M 35% /run/media/mark/Boot
I see you're using LVM (/dev/mapper), so I'm guessing your F33 was not a fresh install but an upgrade. F33 installs on BTRFS by default, and come to think of since I switched to BTRFS I'm fairly sure I haven't seen this problem. That might be a red herring of course.
I may have fiddled with this at some point, I'm not sure.
Bottom line is you don't need to mount on KDE startup. You just need to find what is wanting to mount it though. Does Dolphin start up automatically when you login perhaps? Another place to look is in /etc/fstab .
I'm *trying* not to load Dolphin, nor any of the Gnome desktop,
Dolphin is part of KDE, not Gnome. The Gnome equivalent is Nautilus.
Do you have the "Restore Manually Saved Session" option set (under Desktop Session in KDE Settings)? If you save a session with Dolphin running, it will restart when you log in.
Alternatively, check Autostart (under Workspace in Settings).
poc
I see you're using LVM (/dev/mapper), so I'm guessing your F33 was not a fresh install but an upgrade. F33 installs on BTRFS by default, and come to think of since I switched to BTRFS I'm fairly sure I haven't seen this problem. That might be a red herring of course.
Yes, upgrades for a long time now. I've only just found a way to do a clean install and then restore all my applications. I've not yet found the courage to try it :-) Perhaps F34
Dolphin is part of KDE, not Gnome. The Gnome equivalent is Nautilus.
Do you have the "Restore Manually Saved Session" option set (under Desktop Session in KDE Settings)? If you save a session with Dolphin running, it will restart when you log in.
Alternatively, check Autostart (under Workspace in Settings).
Errr, oh really? Thanks. I might've known that :-/ I've tried to remove it a few times, with some success. It's not in autostart, and I have "Restore previous session" set for login. I seem to remember that was the problem. Of course anything that loads Dolphin then causes it to persist into my next session. I don't remember what it was that likes to load it. But will/could it then mount this volume (?).
I s'pose the better option is to go to BTRFS. I read the blurb about it when they announced it would become the default and it seemed riskier than not changing something that's been working, but I expect I should do that.
Many thanks Mark
On Tue, 2021-03-30 at 17:42 +0100, Mark @ GMail wrote:
I see you're using LVM (/dev/mapper), so I'm guessing your F33 was not a fresh install but an upgrade. F33 installs on BTRFS by default, and come to think of since I switched to BTRFS I'm fairly sure I haven't seen this problem. That might be a red herring of course.
Yes, upgrades for a long time now. I've only just found a way to do a clean install and then restore all my applications. I've not yet found the courage to try it :-) Perhaps F34
It's not that difficult if you have a proper backup. I did it for F33 after using upgrades for many years, and am happy with the result.
Dolphin is part of KDE, not Gnome. The Gnome equivalent is Nautilus.
Do you have the "Restore Manually Saved Session" option set (under Desktop Session in KDE Settings)? If you save a session with Dolphin running, it will restart when you log in.
Alternatively, check Autostart (under Workspace in Settings).
Errr, oh really? Thanks. I might've known that :-/ I've tried to remove it a few times, with some success. It's not in autostart, and I have "Restore previous session" set for login. I seem to remember that was the problem. Of course anything that loads Dolphin then causes it to persist into my next session. I don't remember what it was that likes to load it. But will/could it then mount this volume (?).
I assume Dolphin will start up in whatever directory it happened to be in when the session was saved. That's how it works for me at any rate.
poc
It's not that difficult if you have a proper backup. I did it for F33 after using upgrades for many years, and am happy with the result.
Really? I'm not (just) talking about application data, which will all be in my home directory, but actually installing non-core apps. I've got a shedload of them installed and don't want to spend hours re- installing. Is that within the "not difficult"? If so, how does that work?
I assume Dolphin will start up in whatever directory it happened to be in when the session was saved. That's how it works for me at any rate.
It doesn't appear on the desktop at all, but sometimes there's a process there 8-(
Mark
On Wed, 2021-03-31 at 13:53 +0100, Mark @ GMail wrote:
It's not that difficult if you have a proper backup. I did it for F33 after using upgrades for many years, and am happy with the result.
Really? I'm not (just) talking about application data, which will all be in my home directory, but actually installing non-core apps. I've got a shedload of them installed and don't want to spend hours re- installing. Is that within the "not difficult"? If so, how does that work?
To a first approximation (and relying on my memory):
Make a list of installed apps: rpm -qa > LIST Copy LIST to a safe place. Install (or re-install) Fedora using BTRFS. Restore user data from backups. Also of course /etc/yum.d/* plus /usr/local and /opt if you use them. Install the apps: dnf install $(cat LIST) [may require several iterations if there are dependency errors]
I did this because I actually wanted a clean install and was starting from F32. As you already have F33 it may not be strictly necessary as you can convert ext4 to BTRFS in-place. See btrfs-convert(1).
poc
Thanks for that Patrick. It's about time I did a clean install, there are various niggly problems that it might fix so I'll tyr to do that when F34 arrives. Is BTRFS such a good thing it's worth converting before then?
Mark
PS By coincidence I found my conversation about Dolphin last time, and it was you helping me then too, so double thank you.
On Thu, 2021-04-01 at 10:14 +0100, Mark @ GMail wrote:
Thanks for that Patrick. It's about time I did a clean install, there are various niggly problems that it might fix so I'll tyr to do that when F34 arrives. Is BTRFS such a good thing it's worth converting before then?
[Note that on mailing lists it´s conventional to quote the relevant part of the message you are replying to]
That´s up to you, but if you´re going to do a clean install, there may be no point in converting to BTRFS first. Just back up everything and install F34 with the defaults when it arrives. Shouldn´t be too long now. That will get you BTRFS out of the box, though the installer might ask you, I forget.
Is it a Good Thing(tm)? IMHO it is now that Fedora is supporting it officially, but this being Linux you´ll get all sorts of opinions. I particularly like being able to define subvolumes with different properties, configure some types of RAID without having to learn about MD (though that ship has sailed in my case :-) and have BTRFS checksum my data transparently. Compression might also be attractive for some people though I don´t currently use it.
PS By coincidence I found my conversation about Dolphin last time, and it was you helping me then too, so double thank you.
Glad to be of help.
poc
That´s up to you, but if you´re going to do a clean install, there may be no point in converting to BTRFS first. Just back up everything and install F34 with the defaults when it arrives. Shouldn´t be too long now. That will get you BTRFS out of the box, though the installer might ask you, I forget.
The Fedora 34 default is BTRFS indeed, no questions asked :D
On Thu, 2021-04-01 at 13:13 +0200, Lukas Ruzicka wrote:
That´s up to you, but if you´re going to do a clean install, there may be no point in converting to BTRFS first. Just back up everything and install F34 with the defaults when it arrives. Shouldn´t be too long now. That will get you BTRFS out of the box, though the installer might ask you, I forget.
The Fedora 34 default is BTRFS indeed, no questions asked :D
OK
poc
-
Lukas Ruzicka -
Mark ＠ GMail -
Patrick Boutilier -
Patrick O'Callaghan