linux-image-4.15.0-34-generic does not allow logging in via recovery mode.

Bug #1795259 reported by Randy Robinson on 2018-09-30
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-signed-hwe (Ubuntu)
Undecided
Unassigned

Bug Description

When using the GRub boot loader, I have 3 generic images to choose from. They range from .0-34 generic up to .0-36 generic. However, .0-34 is the only full OS, and does not allow logging in via recovery mode.

My other problem is when booting either .0-35 or .0-36 the alert is shown that /dev/mapper/ubuntu--vg-root does not exist and automatically boots busybox 1.27. I have yet to find the
answers online.

When running the command fsck /dev/mapper/ubuntu--vg-root, I am given the warning that running a file
systems check will cause problems. Since I am down to only one working image, this is something that
I would hate to compromise.

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers