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.
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.
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.