Your message dated Wed, 12 Feb 2025 15:47:05 +0000 with message-id <[email protected]> and subject line Re: Bug#764786: initscripts: forced fsck on root filesystem doesn't give progress after installing sysvinit-core has caused the Debian Bug report #764786, regarding initscripts: forced fsck on root filesystem doesn't give progress after installing sysvinit-core 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 [email protected] immediately.) -- 764786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764786 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: initscripts Version: 2.88dsf-53.4 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After installing sysvinit-core and associated systemd stuff, I had a situation where the root filesystem had been mounted 34 times without checking and an fsck was forced. The fsck completed successfully but there was no progress indication unlike previously and I could not even tell if fsck was running or if the boot process had hung until it completed. * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? Progress reports on all fsck at boot-up. *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17.0+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages initscripts depends on: ii coreutils 8.23-2 ii debianutils 4.4 ii libc6 2.19-11 ii lsb-base 4.1+Debian13 ii mount 2.25.1-3 ii sysv-rc 2.88dsf-53.4 ii sysvinit-utils 2.88dsf-53.4 Versions of packages initscripts recommends: ii e2fsprogs 1.42.12-1 ii psmisc 22.21-2 initscripts suggests no packages. -- Configuration Files: /etc/default/rcS changed: VERBOSE=yes -- no debconf information
--- End Message ---
--- Begin Message ---On Tue, Mar 05, 2019 at 04:17:52AM +0000, Pierre Ynard wrote: > tags 764786 moreinfo > severity 764786 minor > thanks > > > After installing sysvinit-core and associated systemd stuff, I had a > > situation where the root filesystem had been mounted 34 times without > > checking and an fsck was forced. > > I'm confused by your setup. Which init was in use then, systemd or > sysvinit? What changed compared to before? Me too; sysvinit-core and systemd-sysv are no longer co-installable. Closing. Arthur, Feel free to reopen with more information if you think we are missing a current issue. Thanks Mark
--- End Message ---
