Okay, sorry I was wrong again. The other issue just handles the
cryptswap-stuff which seems to be an issue for years in Ubuntu (and gets
closed most of the times).
However, I was finally able to boot my system and wanted to share for
others who might be run into this issue with systemd timeouts:
Ah, I'm sorry. I just realized this is rather this issue:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/953875
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I just found out that running "cryptdisks_start cryptswap1" allows me to
activate the swap with swapon.
So I guess the UUID references are fine and there is some systemd-crypto-issue
going on.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I'm having the same issue now. I upgraded from Ubuntu 16.04 to 16.10.
I was able to boot twice into a running system, but I had no luck the other
times besides from these two times.
However, this gives you the chance to, hopefully, solve this issue.
And as I'm landing in the recovery console
I have noticed this problem on 2 machines upgraded from Ubuntu 14.04 to Ubuntu
16.04, when trying to boot the upgraded system for the first time. The really
bad issue is that after timing out, the system is going to hang with messages
like:
[58Z?Z1.5?Z840] INFO task systemd:21547 blocked for
@pitti
I am unable to reproduce it with 3.19.0-20 nor 3.19.0-18.
So I installed back systemd-sysv and I will do the debug stuff
next time I have the issue.
I guess the issue was related to a strange state of swap or the disk
and after booting once with upstart something fixed it. fsck??
--
You
It could be related that ext4 was in a bad state and systemd was not able to
use it
then upstart executed fsck to fix it and now I can again use systemd.
# /var/log/syslog.4.gz
$ zgrep -h fsck /var/log/*.gz
Jun 8 08:43:06 mbp kernel: [1788385.038996] FAT-fs (sdb1): Volume was not
properly
Thanks for your report. I don't see anything immediately wrong with your
/etc/fstab, blkid looks fine and has matching UUIDs. So I'm afraid I
need a full log to see what happened.
In the grub boot menu under Advanced options, please select the one-
time boot with systemd (you don't need to change
Please attach /etc/fstab from your system, and show the output of 'swapon'
when booted with upstart.
@vorlon content of fstab see Bug Description
$ sudo swapon
NAME TYPE SIZE USED PRIO
/dev/sda6 partition 7.9G 11.5M -1
Ok, I will try to go back to systemd for science ;-)
$ sudo
The sdb1 one is most likely an USB stick (FAT, not ext4). Your ext4 root
partition is sda5 which is shown as clean now. Could still be that a
previous fsck cured it, of course -- this wouldn't appear in
/var/log/syslog as it happens very early at boot already while the root
partition is still
P.S. don't ask me to go back to systemd-sysv... I am fine with
upstart
upstart is not a supported option in Ubuntu 15.04 and later. Are you
willing to help the Ubuntu developers debug this issue? That will
probably require you booting systemd to confirm the fix.
Please attach /etc/fstab
Please note that my swap is NOT encrypted so it's not related to bug
1440098 or 953875
** Package changed: cryptsetup (Ubuntu) = systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
12 matches
Mail list logo
