Ubuntu 12.04.1 LTS (precise) has still this problem, no visual
indication of fsck process.
With even small raid setup, fsck takes easily 10 min or more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/4
> * Filesystem check progress reporting, including cancellation. LP: 446596.
* Filesystem check progress reporting, including cancellation. LP: #446596.
Please write in the proper format for LP.
--
fsck does not show progress during boot
https://bugs.launchpad.net/bugs/446596
You received this
Closing manually, changelog typo.
mountall (0.2.5) karmic; urgency=low
* Filesystem check progress reporting, including cancellation. LP: 446596.
* When we're waiting for a mountpoint, if a few seconds of inactivity
passes, report what we're waiting for and allow Escape to drop you to
I can confirm that version 0.2.5 of mountall resolves the problem (I have
karmic, ext3 file system on an i686 machine): now appears this progress bar
[--]
with # to indicate the progress:
[##]
I had to modify the max-
I've uploaded a new version of mountall (0.2.5) to the ubuntu-boot PPA,
as usual I would appreciate a little testing before I upload it to the
archive proper.
Thanks
** Changed in: mountall (Ubuntu Karmic)
Status: In Progress => Fix Committed
--
fsck does not show progress during boot
ht
Even with only a 50G / partition, I was convinced that my laptop was
hanging and it was only on the third reboot when I tried booting up in
"recovery" mode that I figured out it was because it was fscking because
it'd reached the mount limit. And I've been using Linux primarily for
over a decade n
Just ran forced check of /dev/sda1 without usplash on the boot, not a
peep on the console from mountall or fsck. If an inexperienced end user
hits a forced check on a big drive, maybe a 1TB drive, they will surely
conclude the machine has hung up-and will again on subsequent boots.
This will be a
As of now, usplash will show the console when killed for a manual
fsck run, but is nonreponsive during a forced check. It will of course
time out on a long enough check.
There is also a console bug at this part of the boot process that may
complicate a fix. When I was playing with temporary m
In addition to showing fsck progress, Jaunty allows the user to cancel
the fsck. It would be nice if Karmic allowed the same.
--
fsck does not show progress during boot
https://bugs.launchpad.net/bugs/446596
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
After recent upgrades, the screen is no longer in the text mode but the
new splash screen still does not show fsck progress indicator (I know
that it must be fsck since some reboots were after a very unclean
shutdown).
--
fsck does not show progress during boot
https://bugs.launchpad.net/bugs/446
** Package changed: e2fsprogs (Ubuntu) => mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Importance: Undecided => High
** Changed in: mountall (Ubuntu)
Status: New => In Progress
** Changed in: mountall (Ubuntu)
Milestone: None => ubuntu-9.10
** Changed in: mountall (Ubuntu)
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33317529/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/33317530/XsessionErrors.txt
--
fsck does not show progress during boot
https://bugs.launchpad.net/bugs/446596
You receive
12 matches
Mail list logo
