[opensuse-factory] Heads up: problems with crypttab and LVM/mount by label
Hi all, I had two hours of fun getting my machine to boot again after todays update to FACTORY. * I mount my extra data partitions by label and they are on LVM * I have an old fashioned cryptohome (/etc/crypttab) Right now: * mount by label of LVM seems broken https://bugzilla.novell.com/789020 * cryptohome does not get mounted https://bugzilla.novell.com/789019 Also, I had to uninstall plymouth from "init=/bin/bash" and then mkinitrd, since it did not ask me for the passphrase and did not allow anything else to ask for the passphrasse, but I don't have enough information on that issue to file a bugreport and don't want to reboot my box now that it finally has booted and logged me in again ;-) The workaround for the mount by label problem was to replace "LABEL=/space /space ..." with "/dev/mapper/main-space /space" in /etc/fstab, the workaround for the cryptohome problem is to switch to VT1, log in and do a "mount /home", then switch back to X and log in via gdm. Good luck :-) seife -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Stefan Seyfried <stefan.seyfried@googlemail.com> [2012-11-09 16:22]:
Hi all,
I had two hours of fun getting my machine to boot again after todays update to FACTORY. * I mount my extra data partitions by label and they are on LVM * I have an old fashioned cryptohome (/etc/crypttab)
Right now: * mount by label of LVM seems broken https://bugzilla.novell.com/789020 * cryptohome does not get mounted https://bugzilla.novell.com/789019
Also, I had to uninstall plymouth from "init=/bin/bash" and then mkinitrd, since it did not ask me for the passphrase and did not allow anything else to ask for the passphrasse, but I don't have enough information on that issue to file a bugreport and don't want to reboot my box now that it finally has booted and logged me in again ;-)
The workaround for the mount by label problem was to replace "LABEL=/space /space ..." with "/dev/mapper/main-space /space" in /etc/fstab, the workaround for the cryptohome problem is to switch to VT1, log in and do a "mount /home", then switch back to X and log in via gdm.
Good luck :-)
Installation of M1 using LVM (without encryption) is also broken, it hangs at the partitioning step during installation. I haven't noticed anything on the console and not investigated further so far. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 09.11.2012 16:22, schrieb Stefan Seyfried:
Hi all,
I had two hours of fun getting my machine to boot again after todays update to FACTORY. * I mount my extra data partitions by label and they are on LVM * I have an old fashioned cryptohome (/etc/crypttab)
Right now: * mount by label of LVM seems broken https://bugzilla.novell.com/789020 * cryptohome does not get mounted https://bugzilla.novell.com/789019
Actually those bugs are duplicates. This was both caused by a mis-ported patch for lvm2 (the "dmsetup export" feature), which I fixed in Base:System, it's waiting for inclusion in Factory as sr#140943.
Also, I had to uninstall plymouth from "init=/bin/bash" and then mkinitrd, since it did not ask me for the passphrase and did not allow anything else to ask for the passphrasse, but I don't have enough information on that issue to file a bugreport and don't want to reboot my box now that it finally has booted and logged me in again ;-)
Zypper up brought back plymouth and I had to remove it again (and boot without "quiet" to get asked for a passphrase). Still no Idea how to debug it :-( -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-12 13:41, Stefan Seyfried wrote:
Zypper up brought back plymouth and I had to remove it again (and boot without "quiet" to get asked for a passphrase). Still no Idea how to debug it :-(
How about booting in systemv mode? It solved my problems? (12.1 and 12.2) - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlChTP4ACgkQja8UbcUWM1xcPgD/WcVlEiO9Mz7PpxEngKh6vIIU 9N4gFa3dZ0nYAxO1Vo0A/j7N6ft7l9eMUcd0VdAO8rgs3k5NUxcLWkMVB8qLG+/y =gsk6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2012-11-12 at 20:24 +0100, Carlos E. R. wrote:
On 2012-11-12 13:41, Stefan Seyfried wrote:
Zypper up brought back plymouth and I had to remove it again (and boot without "quiet" to get asked for a passphrase). Still no Idea how to debug it :-(
How about booting in systemv mode? It solved my problems? (12.1 and 12.2)
Considering that this is the -factory mailing list and the goal of factory is to stabilize 12.3 release, and factory has as declared goal to "only support systemd", any kind of advice of not using it is, at this time in Factory, not very productive (unless really meant as a short term workaround, which is not what you are suggesting). What we need is people pulling together in the same direction, towards a rock solid release 12.3... not having a stray community pulling in 15 different directions: we won't reach any of those target points ever otherwise. Best regards, Dominique PS: Sorry: I don't have a real solution for the OP... Stefan: I *AM* right in assuming that there is a bug reported about the issue, to make sure it gets on the right radars, right? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-12 20:33, Dimstar / Dominique Leuenberger wrote:
On Mon, 2012-11-12 at 20:24 +0100, Carlos E. R. wrote:
How about booting in systemv mode? It solved my problems? (12.1 and 12.2)
Considering that this is the -factory mailing list and the goal of factory is to stabilize 12.3 release, and factory has as declared goal to "only support systemd", any kind of advice of not using it is, at this time in Factory, not very productive (unless really meant as a short term workaround, which is not what you are suggesting).
What we need is people pulling together in the same direction, towards a rock solid release 12.3... not having a stray community pulling in 15 different directions: we won't reach any of those target points ever otherwise.
I know that any usage of systemv is temporary, or as a check. If it works there, then it clearly is a systemd issue or provoked by it. Me, I'm considering writing my own scripts to handle my encrypted filesystem needs (and bypass systemd). - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlChV+IACgkQja8UbcUWM1xBbwD+I1vjeZyRStjo47eaG2koLj+R mFVI7bZLesmOSqoC74kA/0ShBmKY8srHPZ7po5v2+CZ6rFzKCCH/5vIxjxNK0zYu =rJpL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 12.11.2012 21:11, schrieb Carlos E. R.:
I know that any usage of systemv is temporary, or as a check. If it works there, then it clearly is a systemd issue or provoked by it.
Well, plymouth is not supported by non-systemd boot AFAIK. As it apparently is a plymouth problem (removing plymouth and plymouth-scripts and then booting in verbose mode lets me enter the credentials on the console), I don't think I can verify anything with booting with traditional init.
Me, I'm considering writing my own scripts to handle my encrypted filesystem needs (and bypass systemd).
Well, I could of course do this. But as I'm running Factory not jut for fun but also to make sure that the next openSUSE release gets as good as possible, this would not be very productive. Best regards, Stefan -- Stefan Seyfried Linux Consultant & Developer -- GPG Key: 0x731B665B B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-12 22:44, Stefan Seyfried wrote:
Me, I'm considering writing my own scripts to handle my encrypted filesystem needs (and bypass systemd). Well, I could of course do this. But as I'm running Factory not jut for fun but also to make sure that the next openSUSE release gets as good as possible, this would not be very productive.
Yes, but I have been told in clear terms (ie, bugzilla) that the old crypto scripts are not going to be supported anymore. I may have no alternative. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlChisUACgkQja8UbcUWM1wbkQD/ZaV4geGIBybEJk8EU0YYrEGo 8QC2zaNi0IjOPuapVIYBAJwU+6Lr8u0ckNH58R2nfwOPTWCeipKPwHAljULq8njM =yoBt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 2012-11-13 00:48, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-11-12 22:44, Stefan Seyfried wrote:
Me, I'm considering writing my own scripts to handle my encrypted filesystem needs (and bypass systemd). Well, I could of course do this. But as I'm running Factory not jut for fun but also to make sure that the next openSUSE release gets as good as possible, this would not be very productive.
Yes, but I have been told in clear terms (ie, bugzilla) that the old crypto scripts are not going to be supported anymore. I may have no alternative.
What about moving to /etc/crypttab? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 13 novembre 2012 à 14:33 +0100, Jan Engelhardt a écrit :
On Tuesday 2012-11-13 00:48, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-11-12 22:44, Stefan Seyfried wrote:
Me, I'm considering writing my own scripts to handle my encrypted filesystem needs (and bypass systemd). Well, I could of course do this. But as I'm running Factory not jut for fun but also to make sure that the next openSUSE release gets as good as possible, this would not be very productive.
Yes, but I have been told in clear terms (ie, bugzilla) that the old crypto scripts are not going to be supported anymore. I may have no alternative.
What about moving to /etc/crypttab?
I gave solutions in the bug report on how to handle crypto volumes which are not auto-mounted, with systemctl. see https://bugzilla.novell.com/show_bug.cgi?id=775342 -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Tue, 13 Nov 2012 15:02:59 +0100 Frederic Crozat <fcrozat@suse.com> пишет:
Le mardi 13 novembre 2012 à 14:33 +0100, Jan Engelhardt a écrit :
On Tuesday 2012-11-13 00:48, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2012-11-12 22:44, Stefan Seyfried wrote:
Me, I'm considering writing my own scripts to handle my encrypted filesystem needs (and bypass systemd). Well, I could of course do this. But as I'm running Factory not jut for fun but also to make sure that the next openSUSE release gets as good as possible, this would not be very productive.
Yes, but I have been told in clear terms (ie, bugzilla) that the old crypto scripts are not going to be supported anymore. I may have no alternative.
What about moving to /etc/crypttab?
I gave solutions in the bug report on how to handle crypto volumes which are not auto-mounted, with systemctl. see https://bugzilla.novell.com/show_bug.cgi?id=775342
It lists multiple problems; skipping over fstab/crypttab interaction, there is at least one major usability issue. The following is under 12.2 (sorry still do not have time and guts :) to switch to factory), so factory could be different now. <quote>However, I get a WALL that the system wants the password - But I don't know where to enter that password.</quote> Expecting every user to (know how to) issue "pkexec systemd-tty-ask-password-agent" is naive. For GNOME there is systemd-gnome-ask-password-agent, but it is neither installed by default, nor is it started in GNOME session. I tried to run it manually and got: === terminal 1 ==== bor@opensuse:~> sudo systemd-ask-password --no-tty 'test password request' root's password: Broadcast message from root@opensuse.site (Tue, 13 Nov 2012 19:19:18 +0400): Password entry required for 'test password request' (PID 12246). Please enter password with the systemd-tty-ask-password-agent tool! Timed out bor@opensuse:~> ==== ==== terminal 2 ==== bor@opensuse:~> Broadcast message from root@opensuse.site (Tue, 13 Nov 2012 19:19:18 +0400): Password entry required for 'test password request' (PID 12246). Please enter password with the systemd-tty-ask-password-agent tool! systemd-gnome-ask-password-agent Refusing to render service to dead parents. ==== agent appeared in notification area, I tried multiple times to click it, by sheer luck got password request which resulted in above error. I do not know whether it lacks proper permissions or simply needs fixing for GNOME3. Should I file bug report? And is there password agent for KDE? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 13 novembre 2012 à 19:33 +0400, Andrey Borzenkov a écrit :
agent appeared in notification area, I tried multiple times to click it, by sheer luck got password request which resulted in above error. I do not know whether it lacks proper permissions or simply needs fixing for GNOME3. Should I file bug report?
Yes, please.
And is there password agent for KDE?
I'm not aware of such a beast.. I guess the GNOME one should work I think. -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
В Tue, 13 Nov 2012 17:32:42 +0100 Frederic Crozat <fcrozat@suse.com> пишет:
Le mardi 13 novembre 2012 à 19:33 +0400, Andrey Borzenkov a écrit :
agent appeared in notification area, I tried multiple times to click it, by sheer luck got password request which resulted in above error. I do not know whether it lacks proper permissions or simply needs fixing for GNOME3. Should I file bug report?
Yes, please.
https://bugzilla.novell.com/show_bug.cgi?id=789655 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-13 15:02, Frederic Crozat wrote:
I gave solutions in the bug report on how to handle crypto volumes which are not auto-mounted, with systemctl. see https://bugzilla.novell.com/show_bug.cgi?id=775342
Ah, comment 11. I did not notice it, sorry, and now I will not have access to that machine for a month more. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlCilNwACgkQja8UbcUWM1yyagD+PEn6tEuwUKnV0/23USdzZj8H iplgBB0xgY0+BhcH2DoA/iLzNCSvlz7fzr6HXPjX755GZwWKmJXKGAPMKkzomyzt =qiP0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2012-11-13 14:33, Jan Engelhardt wrote:
On Tuesday 2012-11-13 00:48, Carlos E. R. wrote:
What about moving to /etc/crypttab?
That is what I use, or attempted to. - -- Cheers / Saludos, Carlos E. R. (from 11.4 x86_64 "Celadon" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iF4EAREIAAYFAlCik70ACgkQja8UbcUWM1xt/wEAnBUtSppbfQ3Xn2CCzqmt7fvW QsoqrfZNaB+I5NogpfgA/0gZvev50P5aw66BO5GJfQvv29zmRjaobm+VjymRBNje =Xx3n -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 12.11.2012 20:33, schrieb Dimstar / Dominique Leuenberger:
PS: Sorry: I don't have a real solution for the OP... Stefan: I *AM* right in assuming that there is a bug reported about the issue, to make sure it gets on the right radars, right?
Actually I don't think I have enough information to support a bugreport (and I hate bugs that need me to reboot my machine to check for fixes :-), additionally, factory was a bit of a mess when I updated, so I'm still hoping it fixes itself after next update. But if it doesnt, I'll need to get my act together and will file a proper report. (Often, as the LVM issue has shown, finding all facts will actually let me fix the bug by myself :-) Best regards, Stefan -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 12/11/12 18:41, Stefan Seyfried wrote:
Actually I don't think I have enough information to support a bugreport
does booting with plymouth.debug and then reading /var/log/plymouth* provides any clue whatsoever ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 12.11.2012 22:41, schrieb Stefan Seyfried:
Am 12.11.2012 20:33, schrieb Dimstar / Dominique Leuenberger:
PS: Sorry: I don't have a real solution for the OP... Stefan: I *AM* right in assuming that there is a bug reported about the issue, to make sure it gets on the right radars, right?
Actually I don't think I have enough information to support a bugreport (and I hate bugs that need me to reboot my machine to check for fixes :-), additionally, factory was a bit of a mess when I updated, so I'm still hoping it fixes itself after next update. But if it doesnt, I'll need to get my act together and will file a proper report.
https://bugzilla.novell.com/789554
(Often, as the LVM issue has shown, finding all facts will actually let me fix the bug by myself :-)
SR#141258 -- not a complete fix but a good start, probably :-) Best regards, Stefan -- Stefan Seyfried Linux Consultant & Developer -- GPG Key: 0x731B665B B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Andrey Borzenkov -
Carlos E. R. -
Cristian Rodríguez -
Dimstar / Dominique Leuenberger -
Frederic Crozat -
Guido Berhoerster -
Jan Engelhardt -
Stefan Seyfried