Your message dated Fri, 3 Aug 2018 16:30:54 +0200
with message-id <20180803143054.kbvxp2e5gyfvxxja@mbpah>
and subject line Re: No message when fsck is running at boot
has caused the Debian Bug report #903309,
regarding No message when fsck is running at boot
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.)
--
903309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903309
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: util-linux
Version: 2.29.2-1
On Debian Wheezy, when fsck was run at boot, it displayed a message and
progress bar with percentage done.
Today, on Debian Strech, I just got an intermitent cursor and a black
screen, no more no less, no other message was present, so I had to
"reisub" to restart the system thinking something went wrong. This time
I removed "quiet" from GRUB's menu and now fsck message and percentage
was displayed as usual.
This is the first time this happens so it could have been a puntual
glitch but I prefer to point this out and if needed, recap more
information about it (not sure what logs to check).
Gretings,
--
Camaleón
--- End Message ---
--- Begin Message ---
On Sun, Jul 08, 2018 at 07:25:34PM +0200, Camaleón wrote:
> Package: util-linux
> Version: 2.29.2-1
>
> On Debian Wheezy, when fsck was run at boot, it displayed a message and
> progress bar with percentage done.
>
> Today, on Debian Strech, I just got an intermitent cursor and a black
> screen, no more no less, no other message was present, so I had to
> "reisub" to restart the system thinking something went wrong. This time
> I removed "quiet" from GRUB's menu and now fsck message and percentage
> was displayed as usual.
>
> This is the first time this happens so it could have been a puntual
> glitch but I prefer to point this out and if needed, recap more
> information about it (not sure what logs to check).
This is not a problem with fsck itself, but whatever is launching it.
In todays age the bootup phase is heavily parallelled. If you want
to present anything meaningful to the user which isn't completely
scrambled you need some kind of message aggregator. You can use
plymouth for that as an example.
Regards,
Andreas Henriksson
--- End Message ---
