Bug#932935: (No Subject)
How does one fix the error if they do not have an older kernel and are stuck with only BusyBox?
Bug#932935: Fixed
Update to e2fsprogs fixed my problem now...
Bug#932935:
Also broken for me on Debian Sid amd64 with kernel version linux-image-4.19.0-5-amd64. Same error message. Selecting version 4.19.0-4 in the grub menu makes the error go away. This is a critical error and will no doubt break many systems so belongs to have an appropriate severity.
Bug#932935: System refuses to boot, logsave not found - requires manual a fsck
Also happening for me on Debian sid, but I unfortunately don't have a prior kernel version to fall back on. fsck reports that the device is clean, no issues.
Bug#932935: System refuses to boot, logsave not found - requires manual a fsck
On Wed, 24 Jul 2019 23:09:46 +0200 Bjoern Schiessle wrote: > Package: linux-image-4.19.0-5-amd64 > Version: 4.19.37-6 > > I run Debian sid, with the latest Kernel. If I try to boot the system I > end up in BusyBox with following message: > > " > Resuming from hibernation > > /init: line 398: logsave: not found > The root filesystem /dev/mapper/potato-vg-root requires a manual fsck > " > > I tried to execute a manual fsck in the BusyBox console, fsck doesn't > report any errors but if I reboot the system I end up again in BusyBox > with the same message. > > If I switch to Linux 4.19.0-4-amd64 the system boots just fine. > > > > +1 for me. Going back to 4.19.0-2 (my last system) works for me. In my case the error is at /init: line 393: logsave: not found. When I do a manual fsck on the stated device there is no error.
Bug#932935: System refuses to boot, logsave not found - requires manual a fsck
Package: linux-image-4.19.0-5-amd64 Version: 4.19.37-6 I run Debian sid, with the latest Kernel. If I try to boot the system I end up in BusyBox with following message: " Resuming from hibernation /init: line 398: logsave: not found The root filesystem /dev/mapper/potato-vg-root requires a manual fsck " I tried to execute a manual fsck in the BusyBox console, fsck doesn't report any errors but if I reboot the system I end up again in BusyBox with the same message. If I switch to Linux 4.19.0-4-amd64 the system boots just fine.