[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
I fetched the debug log using the debug console, however it's contents do not look suspicious to me... systemd seems to try to start the cryptsetup service, the only question probably is where the password prompt does end up... ** Attachment added: systemd jounal fetched using debug console. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4416839/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
Gunter, sorry about the none comment #2, that was obviously bogus, I mis- looked. Can you please follow /usr/share/doc/systemd/README.Debian to boot with a debug shell, then switch to it once it stalls, run journalctl -ab /root/journal.txt, reboot, and attach /root/journal.txt here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
@Anders: There is no syslog for a systemd boot. Can you please do the same exercise as in comment #9, attach the journal, and additioally /etc/crypttab and /etc/fstab? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
Requested syslog attached (for real). ** Attachment added: Syslog for two consecutive boots (systemd,upstart) https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412564/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
Requested syslog attached. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
When I boot using systemd, nothing is logged at all - maybe booting stalls even before rsyslogd is started? If I boot using upstart, the syslog is as follows - note the massive delay before activation of org.freedesktop.UDisks2 which causes the boot process to take quite long - Kubuntu 14.10 had a *much* faster boot process without such a delay. ** Attachment added: syslog while booting using upstart - there are no log entries if I try to boot using systemd https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412154/+files/upstart_syslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
I have a very similar issue. Upstart works but systemd does not. Lucs encrypted logical volume on a work computer. It has worked flawless with boot for many versions of Ubuntu (even before upstart I think). I can produce the syslog with two boots tomorrow. Also have taken a picture of the actual error message during boot with systemd, which is attached. Upstart presents the password prompt, systemd does not. ** Attachment added: Picture of output during boot with systemd https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+attachment/4412269/+files/20150609_175942.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
Some setup info as previous post: sda5_crypt UUID=acdea251-1e21-4612-afce-4101e364d6c6 none luks cryptswap1 /dev/dm-1 /dev/urandom swap,cipher=aes-cbc-essiv:sha256 mount -l with upstart sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=6130708k,nr_inodes=1532677,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1229448k,mode=755) /dev/mapper/lvm1-sysroot on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) none on /sys/fs/cgroup type tmpfs (rw,relatime,size=4k,mode=755) none on /sys/fs/fuse/connections type fusectl (rw,relatime) none on /sys/kernel/debug type debugfs (rw,relatime) none on /sys/kernel/security type securityfs (rw,relatime) tmpfs on /tmp type tmpfs (rw,noatime) none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) none on /run/shm type tmpfs (rw,nosuid,nodev,relatime) none on /run/user type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755) none on /sys/fs/pstore type pstore (rw,relatime) cgmfs on /run/cgmanager/fs type tmpfs (rw,relatime,size=100k,mode=755) /dev/mapper/lvm1-home on /home type ext4 (rw,relatime,data=ordered) /dev/sda1 on /boot type ext4 (rw,relatime,data=ordered) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime) tmpfs on /run/user/104 type tmpfs (rw,nosuid,nodev,relatime,size=1229448k,mode=700,uid=104,gid=111) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1229448k,mode=700,uid=1000,gid=1000) /home/user1/.Private on /home/user1 type ecryptfs (rw,nosuid,nodev,relatime,ecryptfs_fnek_sig=9609cabaf4e75b54,ecryptfs_sig=825adaf5c17ffed8,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta:
[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
crypt /dev/mapper/main-cryptstore none luks,noearly,discard This looks really curious -- the source device is none, so how is that finding out where the underlying encrypted device is? This should usually be something like UUID=12345, or /dev/sdb3 or whatever. Can you please boot with the systemd once, then again with upstart, and attach /var/log/syslog here? Thanks! ** Changed in: systemd (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453912] Re: systemd does not allow to boot with /home on dm-crypt
none is the key file: crypttab(5): The third field, key file, describes the file to use as a key for decrypting the data of the source device. Note that the entire key file will be used as the passphrase; the passphrase must not be followed by a newline character. However I'll try booting with the different init systems and attach the syslog results soon, hopefully this evening. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1453912 Title: systemd does not allow to boot with /home on dm-crypt Status in systemd package in Ubuntu: Incomplete Bug description: Since upgrading from version 14.10 to Kubuntu 15.04, my system does not boot normally any more. Maybe it's only a stupid oversight on my part, but not being a systemd pro, I'm currently at a loss of how to debug this any further. Hints and pointers to appropriate documentation are welcome! Kubuntu 15.04 quickly boots to a specific point where it seems to try to enable a dm-crypt partition which also carries /home, beside other data, and simply stalls. I'm not asked to enter my crytpdisk password and I also cannot enter it blindly without being asked. You can see the point where it stalls in the attached screenshot (photo of my screen). I can then press Ctrl+Alt+Del to cleanly restart the system but I could not find a way to get beyond this point with systemd. Using the alternative boot option with upstart works flawlessly. (Although booting with this boot option is really slow and it takes a while to reach the graphical login screen - it basically looks as if the system is waiting for some name resolving timeouts during boot, but that's a different issue, if've not debugged it further and maybe it's just gone once systemd works to boot my machine.) Further info about my setup: $ cat /etc/crypttab crypt /dev/mapper/main-cryptstore none luks,noearly,discard $ mount | egrep crypt /dev/mapper/crypt on /mnt/crypt type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /home type ext4 (rw,relatime,data=ordered) /dev/mapper/crypt on /var/lib/mysql type ext4 (rw,relatime,data=ordered) Here the first entry is the actual mount point while the other mount points are bind mounts: $ cat /etc/fstab | egrep crypt /dev/mapper/crypt /mnt/crypt ext4defaults0 2 /mnt/crypt/home /home nonebind0 0 /mnt/crypt/var_lib_mysql/var/lib/mysql nonebind0 0 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 11 20:28:18 2015 MachineType: Sony Corporation SVS13A3W9ES ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-16-generic root=/dev/mapper/main-root ro quiet init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service - /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-28 (13 days ago) dmi.bios.date: 03/13/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1021C8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1021C8:bd03/13/2013:svnSonyCorporation:pnSVS13A3W9ES:pvrC60BRBTW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVS13A3W9ES dmi.product.version: C60BRBTW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1453912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
