Univention Bugzilla – Bug 30575
Display line for fscheck to short
Last modified: 2014-06-12 09:19:51 CEST
When an fscheck runs into an error, it displays the corresponding message on top of the bootscreen. The display line however is to short for the full information. Neither the option fix nor the error description are shown. The only option fully visible is skip which can lead to additional Problems after the boot is completed. A customer has already reported a broken file system. It therefore would be good, if at least the Fix option is displayed.
Maybe we can simply disable Plymouth in that case
From https://wiki.ubuntu.com/Plymouth : Special FSCK messages The Ubuntu Plymouth theme supports a "special" message that allows mountall to display fsck progress messages ("fsck is 20% complete"). You can make use of this functionality by using a special message format: sudo plymouth --update=fsck:sda1:27 This will display a message like: Checking disk 1 of 1 (27% complete)
Fixed our plymouth script. Status message (running filesystem check) and "action" messages (press C to abort) are now handled/displayed separately.
For the QA please use a desktop image: 1. Force a fsck on next boot by running "touch /forcefsck" 2. Force an unclean fsck state with "debugfs -w -R "ssv state 2" $PARTITION http://serverfault.com/questions/285752/how-do-i-force-ext3-partition-to-the-error-state
(In reply to Moritz Muehlenhoff from comment #4) > For the QA please use a desktop image: > > 1. Force a fsck on next boot by running "touch /forcefsck" > > 2. Force an unclean fsck state with "debugfs -w -R "ssv state 2" $PARTITION > http://serverfault.com/questions/285752/how-do-i-force-ext3-partition-to-the- > error-state The additional information is currently shown as white text on light blue/white background, and hard to read. The background color should be changed -> REOPENED
(In reply to Lukas Walter from comment #5) > (In reply to Moritz Muehlenhoff from comment #4) > > For the QA please use a desktop image: > > > > 1. Force a fsck on next boot by running "touch /forcefsck" > > > > 2. Force an unclean fsck state with "debugfs -w -R "ssv state 2" $PARTITION > > http://serverfault.com/questions/285752/how-do-i-force-ext3-partition-to-the- > > error-state > > The additional information is currently shown as white text on light > blue/white background, and hard to read. > > The background color should be changed -> REOPENED fixed, changed color for "action" messages to black
(In reply to Felix Botner from comment #6) > > The background color should be changed -> REOPENED > > fixed, changed color for "action" messages to black Ok, the colour of the status message has been fixed.
UCC 2.0 has been released: http://docs.univention.de/release-notes-ucc-2.0.html If this error occurs again, please use "Clone This Bug".