Confirmed – mostly.
Running: Mint 18 Cinnamon 64-bit
Kernel: 4.4.0-78
Laptop: Lenovo Thinkpad Yoga 12
Backstory:
I have a dual boot with windows 10, which I evidently messed up because I would
get a (busybox) prompt every once in a while. Generally running a manual fsck
would fix that. Last night, had problems logging in (we're talking a couple
minutes to boot to login, then hours to actually get past the login screen. I
went ahead and tried to go into recovery mode tonight and fix it.
First glaring issue was that I kept getting a message that I had no
swap. Googled a bit found a solution to try was to reformat the swap
partition and reset /etc/fstab. I was able to do this with only
occasionally running into this "double screen" bug.
Great. Reboot. Same issue logging in.
When I went into recovery mode to try again, I am now getting this
option almost every time. In fact, my initial boot includes "[ OK ]
Started Monitoring of LVM2 mirrors, snapsots etc. using dmeventd or
progress polling." across the first entry. Because the first entry is
where it places the cursor, it appears there may be a timing issue.
Oooop. some crap just happened. Without touching it, it now started
giving me a weird output. It starts with "[ OK ] Stopped Run anacron
jobs." and has a whole misaligned lists of "[ OK ]" and a few
"[FAILED]." The failed are "Failed to start Set console font and
keymap" and "Failed to start Console System Startup Logging.
After all of this, I get "Welcome to emergency mode! After logging in,
type "journalctl -xb" to . . . ."
Gave root password as requested, and now we're to the second opening
screen. Lighter bluew, "root@LT-A ~#" is now on the first line, but
hasn't covered the "Resume normal boot" portion.
Does this help? Probably not, but I am getting extremely frustrated.
There are times when I boot and was able to work in recovery mode.
--
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/1636503
Title:
recovery mode gets borked after some time out
Status in systemd package in Ubuntu:
Confirmed
Bug description:
(Linux mint 18 / Xenial)
after booting in recovery mode from grub.
If you just wait 30-60seconds, a new stream of messages appear and something
gets messed up, you can't use recovery mode any more, you have to do a hard
reboot.
You don't need to do something in particular for this to happen,
simply some time out occurs.
---
more precisely, one of the messages say(copied manually):
"[FAILED] Failed to start Console System on Startup logging.
see 'systemctl status console-kit-log-system-start.service' for more details.
It seams, it tries to launch a second recovery mode on top of the
previous one after the error.
I confirm, this is happening on both my PC linux mint 18 64bits,
laptop linux mint 18 32bits and some one else from a forum on a
ThinkPad X201 with Mint 18 KDE 64-bit.
On my systems, both are fully up to date, 32 and 64 bit. Kernels don't
seam to change anything.
systemd version 229-4ubuntu11
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636503/+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
