Ubuntu
plymouth package

no fsck messages shown in details mode (no splash on cmdline)

Bug #540645 reported by Scott James Remnant (Canonical)
80
This bug affects 18 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Fix Released
High
Dimitri John Ledkov
Precise
Won't Fix
Undecided
Unassigned
Trusty
Fix Released
High
Dimitri John Ledkov

Bug Description

Binary package hint: plymouth

Tried booting in details mode (removed splash from cmdline) and didn't get any fsck messages, despite /forcefsck - need to investigate this as they should be visible

Related branches

lp:~xnox/ubuntu/trusty/plymouth/fsck-details
Upstart Reviewers: Pending requested
Ubuntu branches: Pending requested
Diff: 585 lines (+529/-0)
6 files modified
.pc/applied-patches (+1/-0)
.pc/details-update-status.patch/src/plugins/splash/details/plugin.c (+468/-0)
debian/changelog (+7/-0)
debian/patches/details-update-status.patch (+36/-0)
debian/patches/series (+1/-0)
src/plugins/splash/details/plugin.c (+16/-0)
lp:ubuntu/trusty-proposed/plymouth
Scott James Remnant (Canonical) (canonical-scott)
Changed in plymouth (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

This may be related to the details plugin never opening the terminal ;-)

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Maybe fixed, if that's the cause

Changed in plymouth (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Steve Langasek (vorlon) wrote :

The presumed fix was in the 0.8.1-1 upload - is it really fixed?

Revision history for this message
Noel J. Bergman (noeljb) wrote :

See also bug 549824. You won't get fsck messages if fsck isn't being executed.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Confirmed as still being an issue

Changed in plymouth (Ubuntu):
status: Fix Committed → In Progress
Revision history for this message
Malcolm Scott (malcscott) wrote :

Possibly related to bug 563916, for which I've just submitted a patch? (The details plugin doesn't support display_message at all.)

Revision history for this message
Mark - Syminet (mark-syminet) wrote :

Still no progress bar in Precise... possible xref bug 765735

Clint Byrum (clint-fewbar)
Changed in plymouth (Ubuntu):
importance: Medium → High
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

This affects server users pretty badly.. a long FSCK could be running for a while with no feedback to the technician waiting on it. Raising to High. The reason for this is that the details plugin does not implement on_boot_progress, which is used by mountall to send progress updates from fsck to plymouth.

Revision history for this message
auquicu (aebsbkrs) wrote :

Yes - after two hours still "Press C to cancel all checks in progress". Zero feedback.
There is no choice but to press C - no way to know whether the system is hung or doing something.

Revision history for this message
Mark - Syminet (mark-syminet) wrote :

Regarding this, I rebuilt a mountall package that fixed this bug and uploaded it to my PPA about two years ago.

I added the "--fsck-console" option to mountall, and then added the option to enable this at boot time by adding the line "FSCKCONSOLE=yes" to /etc/defaults/rcS. From the changelog:

   * Added "--fsck-console" parameter to use console progress bar. To
     enable, add "FSCKCONSOLE=yes" to /etc/defaults/rcS.

My PPA package is still sitting on Launchpad here: https://launchpad.net/~mark-syminet/+archive/syminet/+packages

If this seems a good approach, I'm willing to spend the time to take a look at this again but only if someone is willing to consider getting it into the distribution, since I only want to use distribution packages on servers for critical boot-things like this.

This really is a particularly nasty bug because servers can run for a long time without a power cut, etc. - but then that fateful day arrives and we are stuck without any idea if the remote machine is even hung, while bosses and customers are screaming about downtime demanding ETA's.

Dimitri John Ledkov (xnox)
Changed in plymouth (Ubuntu):
assignee: nobody → Dmitrijs Ledkovs (xnox)
Dimitri John Ledkov (xnox)
Changed in plymouth (Ubuntu Precise):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package plymouth - 0.8.8-0ubuntu11

---------------
plymouth (0.8.8-0ubuntu11) trusty; urgency=low

  * Implement update status (U) splash plugin function for details plugin,
    simply display those updates as text messages. (LP: #540645)
 -- Dmitrijs Ledkovs <email address hidden> Wed, 04 Dec 2013 12:36:46 +0000

Changed in plymouth (Ubuntu Trusty):
status: In Progress → Fix Released
Revision history for this message
Mark - Syminet (mark-syminet) wrote :

Fixed.

Revision history for this message
Steve Langasek (vorlon) wrote :

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release

Changed in plymouth (Ubuntu Precise):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.