It definitely is the initramfs. After successfully mounting the root
filesystem (sda10) the following messages are displayed:
-- /scripts/init-bottom/udev: line 25: nuke: not found
-- done.
-- init: line 303: run-init: not found
-- Target filesystem does not have requested /sbin/init.
-- init:
Closed as "user error" => "invalid"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860683
Title:
initramfs hang after today's updates
To manage notifications about this bug go to:
** Package changed: ubuntu => initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860683
Title:
initramfs hang after today's updates
To manage notifications about this bug go
Should I set the package to "initramfs" or "ext?fs" -- I do not know.
:D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860683
Title:
initramfs hang after today's updates
To manage notifications
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
** Description changed:
Xubuntu 18.04.3 updated yesterday (Jan 22, 2020).
- Today's updates cause initramfs to hang.
+ Today's (Jan 23, 2020) updates cause initramfs to hang.
Luckily I can restore my Jan 19, 2020 backup.
I assume the ext{2,3,4} updates to be the culprit.
Anyone else
After restoring my Jan 19, 2020 backup excluding e2fslibs, e2fsprogs and
libext2fs2 when updating gave no problems.
:D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860683
Title:
initramfs hang
