Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #64531 > unrolled thread
| Started by | Bjoern Schiessle <bjoern@schiessle.org> |
|---|---|
| First post | 2019-07-24 23:20 +0200 |
| Last post | 2019-07-28 03:00 +0200 |
| Articles | 7 — 6 participants |
Back to article view | Back to linux.debian.kernel
Bug#932935: System refuses to boot, logsave not found - requires manual a fsck Bjoern Schiessle <bjoern@schiessle.org> - 2019-07-24 23:20 +0200
Bug#932935: System refuses to boot, logsave not found - requires manual a fsck mg-devin@nym.hush.com - 2019-07-25 09:00 +0200
Bug#932935: System refuses to boot, logsave not found - requires manual a fsck Trevor Bekolay <tbekolay@gmail.com> - 2019-07-25 17:30 +0200
Bug#932935: Christopher Obbard <chris@64studio.com> - 2019-07-25 18:50 +0200
Bug#932935: Fixed mg-devin@nym.hush.com - 2019-07-25 21:00 +0200
Bug#932935: (No Subject) "Joshua W. Lawson" <joshuawlawson@pm.me> - 2019-07-27 18:50 +0200
Bug#932935: marked as done (System refuses to boot, logsave not found - requires manual a fsck) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2019-07-28 03:00 +0200
| From | Bjoern Schiessle <bjoern@schiessle.org> |
|---|---|
| Date | 2019-07-24 23:20 +0200 |
| Subject | Bug#932935: System refuses to boot, logsave not found - requires manual a fsck |
| Message-ID | <ynwQ1-7hl-1@gated-at.bofh.it> |
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.
[toc] | [next] | [standalone]
| From | mg-devin@nym.hush.com |
|---|---|
| Date | 2019-07-25 09:00 +0200 |
| Message-ID | <ynFTj-4t1-3@gated-at.bofh.it> |
| In reply to | #64531 |
[Multipart message — attachments visible in raw view] — view raw
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.
[toc] | [prev] | [next] | [standalone]
| From | Trevor Bekolay <tbekolay@gmail.com> |
|---|---|
| Date | 2019-07-25 17:30 +0200 |
| Message-ID | <ynNQR-15M-5@gated-at.bofh.it> |
| In reply to | #64531 |
[Multipart message — attachments visible in raw view] — view raw
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.
[toc] | [prev] | [next] | [standalone]
| From | Christopher Obbard <chris@64studio.com> |
|---|---|
| Date | 2019-07-25 18:50 +0200 |
| Subject | Bug#932935: |
| Message-ID | <ynP6i-1Lo-17@gated-at.bofh.it> |
| In reply to | #64531 |
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.
[toc] | [prev] | [next] | [standalone]
| From | mg-devin@nym.hush.com |
|---|---|
| Date | 2019-07-25 21:00 +0200 |
| Subject | Bug#932935: Fixed |
| Message-ID | <ynR85-2WQ-3@gated-at.bofh.it> |
| In reply to | #64531 |
[Multipart message — attachments visible in raw view] — view raw
Update to e2fsprogs fixed my problem now...
[toc] | [prev] | [next] | [standalone]
| From | "Joshua W. Lawson" <joshuawlawson@pm.me> |
|---|---|
| Date | 2019-07-27 18:50 +0200 |
| Subject | Bug#932935: (No Subject) |
| Message-ID | <yoy3n-5Fc-3@gated-at.bofh.it> |
| In reply to | #64531 |
[Multipart message — attachments visible in raw view] — view raw
How does one fix the error if they do not have an older kernel and are stuck with only BusyBox?
[toc] | [prev] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2019-07-28 03:00 +0200 |
| Subject | Bug#932935: marked as done (System refuses to boot, logsave not found - requires manual a fsck) |
| Message-ID | <yoFHB-1TM-33@gated-at.bofh.it> |
| In reply to | #64531 |
[Multipart message — attachments visible in raw view] — view raw
Your message dated Sun, 28 Jul 2019 00:50:51 +0000 with message-id <E1hrXOl-0009BE-NA@fasolo.debian.org> and subject line Bug#932854: fixed in initramfs-tools 0.134 has caused the Debian Bug report #932854, regarding System refuses to boot, logsave not found - requires manual a fsck to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 932854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932854 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web