[Touch-packages] [Bug 1668535] Re: Ubuntu17.04-Failed to activate (encrypted) Swap Partition
** Changed in: systemd (Ubuntu Zesty) Status: Fix Committed => Fix Released -- 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/1668535 Title: Ubuntu17.04-Failed to activate (encrypted) Swap Partition Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Released Bug description: ---Problem Description--- Ubuntu17.04 installation with swap encryption ,Fails to activate Swap Partition. ---uname output--- Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---boot type--- VDVD installtion ---Steps to reproduce-- 1.Install creating a prep boot, swap and root partition. 2.Encrypt swap partition. 3.Installation completes, and after reboot can see the failed messages for activating swap partition. --Error-- While booting, [ OK ] Started AppArmor initialization. [FAILED] Failed to activate swap Swap Partition. See 'systemctl status dev-sda2.swap' for details. [FAILED] Failed to start Cryptography Setup for sda2_crypt. See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details. [DEPEND] Dependency failed for Encrypted Volumes. Starting Raise network interfaces... ---Logs--- root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service ? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 57 Docs: man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) Main PID: 2023 (code=exited, status=0/SUCCESS) Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service Job for systemd-cryptsetup@sda2_crypt.service failed because the control process exited with error code. See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl -xe" for details. root@tuleta4u-lp7:~# journalctl -xe -- The start-up result is done. Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session opened Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD ( cd / && run-parts --repo Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session closed Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up. Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt already Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has failed. -- -- The result is failed. Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda3 during installation UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 / xfs defaults 0 0 root@tuleta4u-lp7:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 235G 0 disk ??sda1 8:10 7M 0 part ??sda2 8:2028G 0 part ? ??sda2_crypt 253:0028G 0 crypt [SWAP] ??sda3 8:30 167.7G 0 part / ??sda4 8:4028G 0 part sdb 8:16 0 235G 0 disk sr0 11:01 631.3M 0 rom sr1 11:11 631.3M
[Touch-packages] [Bug 1668535] Re: Ubuntu17.04-Failed to activate (encrypted) Swap Partition
** Changed in: systemd (Ubuntu Zesty) Status: In Progress => Fix Committed -- 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/1668535 Title: Ubuntu17.04-Failed to activate (encrypted) Swap Partition Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Zesty: Fix Committed Bug description: ---Problem Description--- Ubuntu17.04 installation with swap encryption ,Fails to activate Swap Partition. ---uname output--- Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---boot type--- VDVD installtion ---Steps to reproduce-- 1.Install creating a prep boot, swap and root partition. 2.Encrypt swap partition. 3.Installation completes, and after reboot can see the failed messages for activating swap partition. --Error-- While booting, [ OK ] Started AppArmor initialization. [FAILED] Failed to activate swap Swap Partition. See 'systemctl status dev-sda2.swap' for details. [FAILED] Failed to start Cryptography Setup for sda2_crypt. See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details. [DEPEND] Dependency failed for Encrypted Volumes. Starting Raise network interfaces... ---Logs--- root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service ? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 57 Docs: man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) Main PID: 2023 (code=exited, status=0/SUCCESS) Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service Job for systemd-cryptsetup@sda2_crypt.service failed because the control process exited with error code. See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl -xe" for details. root@tuleta4u-lp7:~# journalctl -xe -- The start-up result is done. Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session opened Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD ( cd / && run-parts --repo Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session closed Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up. Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt already Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has failed. -- -- The result is failed. Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda3 during installation UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 / xfs defaults 0 0 root@tuleta4u-lp7:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 235G 0 disk ??sda1 8:10 7M 0 part ??sda2 8:2028G 0 part ? ??sda2_crypt 253:0028G 0 crypt [SWAP] ??sda3 8:30 167.7G 0 part / ??sda4 8:4028G 0 part sdb 8:16 0 235G 0 disk sr0 11:01 631.3M 0 rom sr1 11:11 631.3M
[Touch-packages] [Bug 1668535] Re: Ubuntu17.04-Failed to activate (encrypted) Swap Partition
This looks pretty similar to bug #1670336. Should one of these be marked as a duplicate? -- 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/1668535 Title: Ubuntu17.04-Failed to activate (encrypted) Swap Partition Status in systemd package in Ubuntu: In Progress Status in systemd source package in Zesty: In Progress Bug description: ---Problem Description--- Ubuntu17.04 installation with swap encryption ,Fails to activate Swap Partition. ---uname output--- Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---boot type--- VDVD installtion ---Steps to reproduce-- 1.Install creating a prep boot, swap and root partition. 2.Encrypt swap partition. 3.Installation completes, and after reboot can see the failed messages for activating swap partition. --Error-- While booting, [ OK ] Started AppArmor initialization. [FAILED] Failed to activate swap Swap Partition. See 'systemctl status dev-sda2.swap' for details. [FAILED] Failed to start Cryptography Setup for sda2_crypt. See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details. [DEPEND] Dependency failed for Encrypted Volumes. Starting Raise network interfaces... ---Logs--- root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service ? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 57 Docs: man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) Main PID: 2023 (code=exited, status=0/SUCCESS) Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service Job for systemd-cryptsetup@sda2_crypt.service failed because the control process exited with error code. See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl -xe" for details. root@tuleta4u-lp7:~# journalctl -xe -- The start-up result is done. Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session opened Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD ( cd / && run-parts --repo Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session closed Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up. Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt already Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has failed. -- -- The result is failed. Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda3 during installation UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 / xfs defaults 0 0 root@tuleta4u-lp7:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 235G 0 disk ??sda1 8:10 7M 0 part ??sda2 8:2028G 0 part ? ??sda2_crypt 253:0028G 0 crypt [SWAP] ??sda3 8:30 167.7G 0 part / ??sda4 8:4028G 0 part sdb 8:16 0 235G 0 disk sr0 11:01 631.3M 0 rom sr1 11:11
[Touch-packages] [Bug 1668535] Re: Ubuntu17.04-Failed to activate (encrypted) Swap Partition
the patch is already staged for the next upload of systemd at: https://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?h=stretch=f8a574b0b106f949c563e752f5925e0609f5faf6 -- 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/1668535 Title: Ubuntu17.04-Failed to activate (encrypted) Swap Partition Status in systemd package in Ubuntu: In Progress Status in systemd source package in Zesty: In Progress Bug description: ---Problem Description--- Ubuntu17.04 installation with swap encryption ,Fails to activate Swap Partition. ---uname output--- Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---boot type--- VDVD installtion ---Steps to reproduce-- 1.Install creating a prep boot, swap and root partition. 2.Encrypt swap partition. 3.Installation completes, and after reboot can see the failed messages for activating swap partition. --Error-- While booting, [ OK ] Started AppArmor initialization. [FAILED] Failed to activate swap Swap Partition. See 'systemctl status dev-sda2.swap' for details. [FAILED] Failed to start Cryptography Setup for sda2_crypt. See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details. [DEPEND] Dependency failed for Encrypted Volumes. Starting Raise network interfaces... ---Logs--- root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service ? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 57 Docs: man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) Main PID: 2023 (code=exited, status=0/SUCCESS) Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service Job for systemd-cryptsetup@sda2_crypt.service failed because the control process exited with error code. See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl -xe" for details. root@tuleta4u-lp7:~# journalctl -xe -- The start-up result is done. Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session opened Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD ( cd / && run-parts --repo Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session closed Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up. Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt already Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has failed. -- -- The result is failed. Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda3 during installation UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 / xfs defaults 0 0 root@tuleta4u-lp7:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 235G 0 disk ??sda1 8:10 7M 0 part ??sda2 8:2028G 0 part ? ??sda2_crypt 253:0028G 0 crypt [SWAP] ??sda3 8:30 167.7G 0 part / ??sda4 8:4028G 0 part sdb 8:16 0
[Touch-packages] [Bug 1668535] Re: Ubuntu17.04-Failed to activate (encrypted) Swap Partition
** Changed in: systemd (Ubuntu Zesty) Status: Confirmed => In Progress -- 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/1668535 Title: Ubuntu17.04-Failed to activate (encrypted) Swap Partition Status in systemd package in Ubuntu: In Progress Status in systemd source package in Zesty: In Progress Bug description: ---Problem Description--- Ubuntu17.04 installation with swap encryption ,Fails to activate Swap Partition. ---uname output--- Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---boot type--- VDVD installtion ---Steps to reproduce-- 1.Install creating a prep boot, swap and root partition. 2.Encrypt swap partition. 3.Installation completes, and after reboot can see the failed messages for activating swap partition. --Error-- While booting, [ OK ] Started AppArmor initialization. [FAILED] Failed to activate swap Swap Partition. See 'systemctl status dev-sda2.swap' for details. [FAILED] Failed to start Cryptography Setup for sda2_crypt. See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details. [DEPEND] Dependency failed for Encrypted Volumes. Starting Raise network interfaces... ---Logs--- root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service ? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 57 Docs: man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) Main PID: 2023 (code=exited, status=0/SUCCESS) Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service Job for systemd-cryptsetup@sda2_crypt.service failed because the control process exited with error code. See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl -xe" for details. root@tuleta4u-lp7:~# journalctl -xe -- The start-up result is done. Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session opened Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD ( cd / && run-parts --repo Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session closed Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up. Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt already Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has failed. -- -- The result is failed. Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda3 during installation UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 / xfs defaults 0 0 root@tuleta4u-lp7:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 235G 0 disk ??sda1 8:10 7M 0 part ??sda2 8:2028G 0 part ? ??sda2_crypt 253:0028G 0 crypt [SWAP] ??sda3 8:30 167.7G 0 part / ??sda4 8:4028G 0 part sdb 8:16 0 235G 0 disk sr0 11:01 631.3M 0 rom sr1 11:11 631.3M 0 rom
[Touch-packages] [Bug 1668535] Re: Ubuntu17.04-Failed to activate (encrypted) Swap Partition
** Also affects: systemd (Ubuntu Zesty) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Confirmed -- 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/1668535 Title: Ubuntu17.04-Failed to activate (encrypted) Swap Partition Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Zesty: Confirmed Bug description: ---Problem Description--- Ubuntu17.04 installation with swap encryption ,Fails to activate Swap Partition. ---uname output--- Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---boot type--- VDVD installtion ---Steps to reproduce-- 1.Install creating a prep boot, swap and root partition. 2.Encrypt swap partition. 3.Installation completes, and after reboot can see the failed messages for activating swap partition. --Error-- While booting, [ OK ] Started AppArmor initialization. [FAILED] Failed to activate swap Swap Partition. See 'systemctl status dev-sda2.swap' for details. [FAILED] Failed to start Cryptography Setup for sda2_crypt. See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details. [DEPEND] Dependency failed for Encrypted Volumes. Starting Raise network interfaces... ---Logs--- root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service ? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 57 Docs: man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) Main PID: 2023 (code=exited, status=0/SUCCESS) Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service Job for systemd-cryptsetup@sda2_crypt.service failed because the control process exited with error code. See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl -xe" for details. root@tuleta4u-lp7:~# journalctl -xe -- The start-up result is done. Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session opened Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD ( cd / && run-parts --repo Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session closed Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up. Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt already Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has failed. -- -- The result is failed. Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda3 during installation UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 / xfs defaults 0 0 root@tuleta4u-lp7:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 235G 0 disk ??sda1 8:10 7M 0 part ??sda2 8:2028G 0 part ? ??sda2_crypt 253:0028G 0 crypt [SWAP] ??sda3 8:30 167.7G 0 part / ??sda4 8:4028G 0 part sdb 8:16 0 235G 0 disk sr0 11:01 631.3M 0 rom
[Touch-packages] [Bug 1668535] Re: Ubuntu17.04-Failed to activate (encrypted) Swap Partition
** Changed in: debian-installer (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Dimitri John Ledkov (xnox) ** Package changed: debian-installer (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-17.03 -- 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/1668535 Title: Ubuntu17.04-Failed to activate (encrypted) Swap Partition Status in systemd package in Ubuntu: Confirmed Bug description: ---Problem Description--- Ubuntu17.04 installation with swap encryption ,Fails to activate Swap Partition. ---uname output--- Linux tuleta4u-lp7 4.9.0-11-generic #12-Ubuntu SMP Mon Dec 12 16:16:45 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux ---boot type--- VDVD installtion ---Steps to reproduce-- 1.Install creating a prep boot, swap and root partition. 2.Encrypt swap partition. 3.Installation completes, and after reboot can see the failed messages for activating swap partition. --Error-- While booting, [ OK ] Started AppArmor initialization. [FAILED] Failed to activate swap Swap Partition. See 'systemctl status dev-sda2.swap' for details. [FAILED] Failed to start Cryptography Setup for sda2_crypt. See 'systemctl status systemd-cryptsetup@sda2_crypt.service' for details. [DEPEND] Dependency failed for Encrypted Volumes. Starting Raise network interfaces... ---Logs--- root@tuleta4u-lp7:~# systemctl status systemd-cryptsetup@sda2_crypt.service ? systemd-cryptsetup@sda2_crypt.service - Cryptography Setup for sda2_crypt Loaded: loaded (/etc/crypttab; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2017-01-02 01:58:14 EST; 1min 57 Docs: man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) Main PID: 2023 (code=exited, status=0/SUCCESS) Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr Jan 02 01:58:14 tuleta4u-lp7 mkswap[2057]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 01:58:14 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# systemctl start systemd-cryptsetup@sda2_crypt.service Job for systemd-cryptsetup@sda2_crypt.service failed because the control process exited with error code. See "systemctl status systemd-cryptsetup@sda2_crypt.service" and "journalctl -xe" for details. root@tuleta4u-lp7:~# journalctl -xe -- The start-up result is done. Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session opened Jan 02 03:17:01 tuleta4u-lp7 CRON[3956]: (root) CMD ( cd / && run-parts --repo Jan 02 03:17:01 tuleta4u-lp7 CRON[3955]: pam_unix(cron:session): session closed Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Starting Cryptography Setup for sda2_cr -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has begun starting up. Jan 02 03:37:57 tuleta4u-lp7 systemd-cryptsetup[3960]: Volume sda2_crypt already Jan 02 03:37:57 tuleta4u-lp7 mkswap[3962]: mkswap: error: /dev/mapper/sda2_crypt Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: Failed to start Cryptography Setup for -- Subject: Unit systemd-cryptsetup@sda2_crypt.service has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-cryptsetup@sda2_crypt.service has failed. -- -- The result is failed. Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: Jan 02 03:37:57 tuleta4u-lp7 systemd[1]: systemd-cryptsetup@sda2_crypt.service: root@tuleta4u-lp7:~# cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda3 during installation UUID=44e6ba68-4cbb-4978-8d90-6077796b3715 / xfs defaults 0 0 root@tuleta4u-lp7:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 235G 0 disk ??sda1 8:10 7M 0 part ??sda2 8:2028G 0 part ? ??sda2_crypt 253:0
