Eol is very close; so its time to use a newer release
** Changed in: plymouth (Ubuntu)
Status: Triaged = Invalid
** Changed in: plymouth (Ubuntu Lucid)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm using 9x64 with all updates and I've posted question on mint forums
for last 6 month and have 0 replies. Auto fsck has never finished for me
on this install. Seems everyone is working on the newest disaster, ahh,
distribution. The problem with all linux distributions is that no-one
cares about
Steve Langasek (vorlon) wrote on 2011-10-25:
And there are a number of other plymouth bugs present that are higher-impact
than this one, so it is unlikely that this bug will receive further
attention for 10.04.
That's true for sure. With this in mind it is definitely a shame that Canonical
On Sun, Oct 30, 2011 at 06:49:14PM -, ingo wrote:
Steve Langasek (vorlon) wrote on 2011-10-25:
And there are a number of other plymouth bugs present that are higher-impact
than this one, so it is unlikely that this bug will receive further
attention for 10.04.
That's true for sure.
Please, are there any updates on this issue?
The bug is open since 2010-04-29!
I'm using Linux Mint Isadora 64bit and 32bit, both are having the same bugs.
Please update the Status to Won't fix!!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On 25/10/2011 21:31, queo wrote:
Please, are there any updates on this issue?
The bug is open since 2010-04-29!
I'm using Linux Mint Isadora 64bit and 32bit, both are having the same bugs.
Please update the Status to Won't fix!!!
But it's fixed in Ubuntu Oneiric.
--
Kind regards,
Loong
25.10.2011 18:38, Chow Loong Jin wrote:
But it's fixed in Ubuntu Oneiric.
And what does it change with regards to Linux Mint 9 Isadora users? Who cares if
this bug was fixed in some fresh-n-shiny Ubuntu and/or Mint release while it is
still not fixed in so-called Long Term Support version of
Dear Loong Jin,
thanks for your reply.
I always thought there is a support for 3 years for LTS releases (Ubuntu 10.04
is LTS).
Do I have the wrong information here?
Best regards,
Kurt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On 25/10/2011 22:59, queo wrote:
Dear Loong Jin,
thanks for your reply.
I always thought there is a support for 3 years for LTS releases (Ubuntu
10.04 is LTS).
Do I have the wrong information here?
Best regards,
Kurt
Sorry, let me correct myself. It's been fixed from lucid-updates
On Tue, Oct 25, 2011 at 05:42:18PM -, Chow Loong Jin wrote:
The status of the bug is correct -- it's fixed in mountall on Ubuntu, and
mountall in Lucid (via lucid-updates). If it's still broken in Linux Mint,
then
open a task there and set it to the appropriate status. There is no reason
Just installed ubuntu 10.04.3 64 bits, mountall is 2.15 and getting the same
problem. In this post looks like its solved, is it?
Tried workaround but is not working.
Any hint,
Thanks in advance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Please, are there any updates on this issue?
The mountall package 2.19 doesn'nt fix the problem.
Is anybody working on this to resolve this bug???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571707
Please, are there any updates on this issue?
The mountall package 2.19 doesn'nt fix the problem.
Is anybody working on this to resolve this bug???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571707
** Tags added: testcase
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571707
Title:
fsck progress stalls at boot, plymouthd/mountall eats CPU
To manage notifications about this bug go to:
this fix doesn't work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571707
Title:
fsck progress stalls at boot, plymouthd/mountall eats CPU
To manage notifications about this bug go to:
Oddly this was fixed in Ubuntu 10.4.2 and its sub-sequent releases. Mint
maintains that the bug lies upstream. Oh wth I'm using LMDE now
On Wed, Aug 24, 2011 at 3:34 PM, queo 571...@bugs.launchpad.net wrote:
this fix doesn't work
--
You received this bug notification because you are
Is there any help available regarding this bug please??
It is open since 2010-04-29 (!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571707
Title:
fsck progress stalls at boot, plymouthd/mountall
On 22.08.2011 17:31, queo wrote:
Is there any help available regarding this bug please??
It is open since 2010-04-29 (!)
Here: http://www.debian.org/devel/debian-installer/ - works reliably.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Excerpts from ingo's message of Mon Aug 22 16:07:50 UTC 2011:
On 22.08.2011 17:31, queo wrote:
Is there any help available regarding this bug please??
It is open since 2010-04-29 (!)
Here: http://www.debian.org/devel/debian-installer/ - works reliably.
Bug reports are for helping
the problem is not fixed yet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571707
Title:
fsck progress stalls at boot, plymouthd/mountall eats CPU
To manage notifications about this bug go to:
Dear Clement,
first of all I would like to thank you very much for the creation of this great
OS Linux Mint.
What I'm using:
HW: Lenovo Thinkpad T410
OS: Linux Mint Isadora 64bit with ext4 filesystem
I've updated the mountall package to version 2.19, but the problem still exists.
The fsck
** Changed in: linuxmint
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/571707
Title:
fsck progress stalls at boot, plymouthd/mountall eats CPU
--
mountall 2.19 added to Mint 9 repository as a level 4 upgrade.
@Justin: Let's keep an eye on it so we can eventually reduce the level
to 3 or even 2 in a week or so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I installed new mountall 2.19 and did sudo touch /forcefsck sudo reboot
but nothing has changed. It stucks and I can't see any % progression only
information ...presss C...
But when I press F1 I can see some info about ... plymouth main process
terminated with status ...
I wish I could sent a
Good day.
Clem please action the introduction of mountall 2.19 into the repos for
Linux Mint 9 LTS so this issue may be resolved.
Thanks
- Justin
** Changed in: linuxmint
Status: New = Confirmed
** Changed in: linuxmint
Importance: Undecided = High
** Changed in: linuxmint
When a disk check is performed, the progress stalls (I don't see any
progress bar or % but I can't hear a hard disk not working) and I press
F2 I see: plymouth main process terminated with status 1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
mountall 2.19 is available for Ubuntu 10.10. The description of the
bugfix between 2.15 and 2.19 appears to tackle this bug. The
dependencies of 2.19 are satisfied by Ubuntu 10.04. This bug hasn't gone
away with 2.15-3. So why has 2.19 not been provided to 10.04? This bug
is very annoying and
I activated level 4 and 5 updates in mitupdate and updated all packages
that are possibly related to this bug (mountall, upstart, plymouth) so
they are the same version as in Ubuntu 10.04 now. But the bug still
remains.
Does anybody know if Ubuntu 10.04 users still suffer from this bug?
--
fsck
Hello,
If people using a up-to-date 10.04 (or later) of stock Ubuntu are still
seeing symptoms described in this bug I would STRONGLY recommend they
file a new bug report. Mint users are similarly better off filing a bug
report in their distribution's bug tracker as it is difficult to tell
Well pardon me. I'm sorry for the wrong info. I just know what took place on
my system. So until you have walked in my shoes, you need to keep your
attitude and that I know all bull crap to yourself. So cancel my account,
who really cares. Its just a linux distro, life still goes on.
On Nov 14,
https://bugs.launchpad.net/linuxmint/+bug/675462
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Tuesday 16,November,2010 12:17 AM, Richard Postlewait wrote:
Well pardon me. I'm sorry for the wrong info. I just know what took place on
my system. So until you have walked in my shoes, you need to keep your
attitude and that I know all bull crap to yourself. So cancel my account,
who
@ Loong Jin
please accept my excuse regarding the statement that fixing the bug in
Lucid did take too long - 10 days ist really fast.
On the other hand - and that is probably why people including me get
upset so easily - the real root cause is something different and in no
way addressed to you
16.11.2010 00:25, ingo wrote:
The logical way to solve this issues/bugs would
be to purge plymouth and set up a good functional system.
Correct me if I'm wrong but it is perfectly possible to get rid of plymouth in
initramfs and following boot process by simply not installing plymouth themes
Enough. Your points are both understood. Quit spamming.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hello,
this Bug is nearly 7 month old and I can't understand, why it is not
fixed for LM 9.
Regards
Andreas
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It's fixed in Mint 10.
On Sun, Nov 14, 2010 at 8:45 AM, Andreas Jürgens
571...@bugs.launchpad.netwrote:
Hello,
this Bug is nearly 7 month old and I can't understand, why it is not
fixed for LM 9.
Regards
Andreas
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
Thanks for the answer and why not in Mint 9, because a lot of users will
work with Mint 9 till ending support in 2013?
I am one of it. ;)
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a
I can't answer that one; sorry. I just know it's fixed inMint 10, cause it
came up on my system the other day, took like maybe 3 to 5 minutes at the
most. Then it finished booting. I tried Ubuntu 10.10, before Mint 10 RC came
out. If I'm not mistaken Ubuntu still has the same problem.lol Mint's
On Monday 15,November,2010 01:38 AM, Richard Postlewait wrote:
I can't answer that one; sorry. I just know it's fixed inMint 10, cause it
came up on my system the other day, took like maybe 3 to 5 minutes at the
most. Then it finished booting. I tried Ubuntu 10.10, before Mint 10 RC came
out.
14.11.2010 19:59, Richard Postlewait wrote:
It's fixed in Mint 10.
Awesome! Then why the hell is this bug not fixed in latest LTS release? Regular
one-year support releases are just a toys for home linux users while corporate
one tend to use LTS releases for production use. And the fact that
On Monday 15,November,2010 04:42 AM, Alexey Loukianov wrote:
14.11.2010 19:59, Richard Postlewait wrote:
It's fixed in Mint 10.
Awesome! Then why the hell is this bug not fixed in latest LTS release?
Regular
one-year support releases are just a toys for home linux users while
corporate
Status in “mountall” source package in Lucid: Fix Released
But when - too late!
Such things happen when releases are time based instead of when it's
done. What is a LTS-release worth when takes months to become ready for
use.They are almost done approximately with second point release, so
15.11.2010 00:11, Chow Loong Jin wrote:
Status in “mountall” source package in Lucid: Fix Released
Again, Get The Facts™. I don't care what Mint LTS does, but Ubuntu LTS has it
fixed, so please don't confuse the two again.
Thanks for pointing out on this. So, what is the _real_ current
On Monday 15,November,2010 05:43 AM, ingo wrote:
Status in “mountall” source package in Lucid: Fix Released
But when - too late!
Such things happen when releases are time based instead of when it's
done. What is a LTS-release worth when takes months to become ready for
use.They are almost
On Monday 15,November,2010 08:54 AM, Alexey Loukianov wrote:
15.11.2010 00:11, Chow Loong Jin wrote:
Status in “mountall” source package in Lucid: Fix Released
Again, Get The Facts™. I don't care what Mint LTS does, but Ubuntu LTS has it
fixed, so please don't confuse the two again.
Sorry for my bad english and the following is translatet by google:
At certain intervals Mint 9 tries to examine me before the start of the
hard drives for errors. The process ever run for several hours, but he
has not come to an end. In the beginning, I can still read Mint
examined 1 of 2 hard
Here you can read the Thread in the community of linuxmintusers.de:
http://www.linuxmintusers.de/index.php?PHPSESSID=372fd229d183e69a2002e19784600d19topic=2532.msg18576#new
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug
15.11.2010 06:14, Chow Loong Jin wrote:
10 days is too long? Really?
If it was really fixed in that 10 days and all people reporting here blaming
Ubuntu are in reality just hadn't installed fresh updates or are using Mint
instead then it was fast enough to call it good level of support. If not
It is a shame that this bug is not yet solved for Mint 9
It's all very sad, after almost seven months.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just got a report from my clients using Linux Mint 9. Today three of
the workstations stalled at boot displaying plymouth animation screen
and doing nothing (this is roughly what the client complaint was).
Knowing about this bug I suggested them to press the C key on the
keyboard. Shortly after
Now, I have installed Linux Mint 10 Julia 64-bit
Linux 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:45:36 UTC 2010 x86_64
GNU/Linux
I checked with command
sudo touch /forcefsck sudo reboot
Unfortunately the problem still exist. I don't have progress bar showing in %.
The process was very
And, of course nothing logged under /var/log/fsck :-(
My logs are absolutely empty since install of Lucid:
cat /var/log/fsck/checkfs
(Nothing has been logged yet.)
cat /var/log/fsck/checkroot
(Nothing has been logged yet.)
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
and this is how it looks in Debian-Squeeze (after touch /forcefsck):
squeeze:/var/log/fsck# cat checkroot
Log of fsck -C -f -a -t ext3 /dev/sda1
Sat Nov 6 20:02:33 2010
fsck from util-linux-ng 2.17.2
/dev/sda1: 163080/498736 files (5.8% non-contiguous), 1624972/1994060 blocks
Sat Nov 6
This bug is not really fixed.
On mint 9 kde, when a fsck is asked by the system on boot, he progress
to 100% and plymouth works endless.
Press C or right arrow key does the boot continue.
When i hit esc on plymouth, i see this message : GLib-WARNING **:
getpwuid_r(): falied due to unknown user
I don't even have progress bar. I don't now how long I have to wait so I always
press C to stop this fsck process.
http://forums.linuxmint.com/viewtopic.php?f=29t=53170
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug
@axel: That issue is not probably related to this bug, and can even be
related to your graphic card driver or plymouth (you did not mention
whether you see the pink background with Ubuntu logo correctly or not).
Please open a new bug (if you can't find an bug for that already) for
your issue since
Have switched to Ubuntu 10.10. No issues at all. Thanks. I wasn't having the
problems your listing anyway.
On Oct 11, 2010 9:22 AM, papukaija 571...@bugs.launchpad.net wrote:
@axel: That issue is not probably related to this bug, and can even be
related to your graphic card driver or plymouth
I also have mountall 2.15.2 installed and I am receiving the error
described many times in this report:
- fsck does not run correctly at boot - stuck at 70% or so, no disk activity
- must hit C to cancel, then boot proceeds as expected
- file system is ext3, SATA
- running Mint 9 x64
- mountall
** Branch linked: lp:ubuntu/lucid-updates/mountall
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi,
i just came across this bug report after surfing the web for the problem i'm
experiencing. The symptom is that at boot time the disk check finishes 70%
within one or two minutes. From 70% to 74%, it takes about 5 minutes. From
75% to 100%, it takes a few hours with worst case so far
I'm getting the same issue on Server 10.04 LTS.
Installing mountall 2.15 appeared to fix the issue, but it has returned.
touch /forcefsck does not cause the issue - it only appears without
interference (seemingly). I also noticed it started occuring again when
the fsck on boot reports 'clean' as
On further investigation, it appears that no *actual* fsck is being
performed when I get this error.
When I use /forcefsck, it returns 0.1% non-contiguous after a short
delay, and boots normally.
When my boot stalls with a fsck message, no vterms, but sshd active, on
the connected display it
Yesterday, my Linux Mint cannot startup( without any information printed
in screen), the recovery mode doesn't work as well, the fsck printed the
check results then system stalled? I can restart but cannot proceed any
further...
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
@luojie-dune I updated yesterday (Ubuntu Lucid) and noticed that on re-
boot, the grub menu started showing up again, even though I had edited
the configoration files to hide it. Clearly a recent update meddled with
those files, without asking the user. I would imagine that is your issue
to. If
Hello,
on my production ubuntu server (HP380G6) 10.04 LTS i noticed this same issue.
console was hanging on an fsck .. and when logged i (ssh) a saw the
/sbin/plymouthd --mode=boot --attach-to-session
running.
ubuntu is completely uptodate (today) and having mountall 2.15
installed.
So with
** Description changed:
PROBLEM
When a disk check is performed, the progress stalls somewhere around 70%
and will then take a very long time finishing the remaining percent (10
minutes or more).
PATCH
- Patch for mountall has now been accepted into -proposed. See
-
** Changed in: plymouth (Ubuntu)
Status: Triaged = Invalid
** Changed in: plymouth (Ubuntu Lucid)
Status: Triaged = Invalid
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a
** Changed in: plymouth (Ubuntu)
Status: Invalid = Triaged
** Changed in: plymouth (Ubuntu Lucid)
Status: Invalid = Triaged
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a
Since the fix is still in -proposed and not released to normal updates,
I'm changing status to Fix Committed for Lucid.
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
Are you sure, arand? I recently upgraded to mountall 2.15 on a machine
without -proposed enabled. It does look as if packages.ubuntu.com is
still reporting mountall at version 2.14, but that would be a separate
issue.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
I just upgraded to mountall 2.15 from lucid-updates.
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member
Ah, yes, my bad. I was simply going by the janitor's message above.
Great to see this fix out the door.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is
nothing to sponsor left, unsubscribing ubuntu-sponsors
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package mountall - 2.15
---
mountall (2.15) lucid-proposed; urgency=low
[ Scott James Remnant ]
* Fix an obvious thinko error that meant that the Ignore fsck error key
for a hard failure was ignored.
* When cancelling filesystem checks, only cancel
I just have updated only mountall package from -proposed, and I can
confirm that for me disk check time is reduced from 20 minutes to less
than one minute.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification
Problem is a bit different over here. It gets stuck on 90% and takes
about half an hour to finsih after this. Adding nosplash to grub.cfg
somehow seems to resolve it. Maybe the bug should be moved to plymouth
section?
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
Uhm. Ignore the above. I now have read other comments and see that it's
the same.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
13thSlayer, have you checked if the patch fixes it for you?
And also.. any other general updates on this issue?
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Committed = Fix Released
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug
Upgrading to mountall - 2.15 in proposed fixed the problem for me. Disk check
now takes less than 30 secs. compared to about 30 minutes before. New package
has not caused any problems that I'm aware of.
Nice work thanks.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
Upgrading here solved the problem too. I see a slow down at 95% but it
finishes in a reasonable time. Good work.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which
Upgrading to 2.15 reduced the time from about 10 minutes (or more, even)
to about 1 minute or so.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
[notes #91 and #92]
Upgrading to mountall 2.15 resolved the problem on both machines.
Netbook scan about 10 seconds, desktop about one minute
(down from 10 minutes and one hour).
Using lucid-proposed can be *far* easier than the complex Wiki page suggests,
but it's been made
@ Sitsofe Wheeler, Steve Langasek etc: you are, of course, heroes all.
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I can verify that mountall 2.15 in lucid-proposed fixes this bug for my
x86_64 Thinkpad T61 laptop without introducing any new regressions. Good
work everyone!
Although the new mountall doesn't seem to fix Bug #577331, may I suggest
it be pushed to lucid-updates anyway as soon as verification is
On Mon, 2010-05-10 at 10:53 +, Michael Hampson wrote:
@ Sitsofe Wheeler, Steve Langasek etc: you are, of course, heroes all.
Can I add my praise?? I've done a bit of development and know how time
consuming and exasperating debugging can be. I've been following the
process and am sooo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10-05-10 06:29 AM, Bernat wrote:
I see a slow down at 95%
I'm pretty sure that's normal
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkvoHEkACgkQst0AR/DaKHveqgCcCXiiBUSI/BIxdhZFzUw7iMKI
Accepted mountall into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: mountall (Ubuntu Lucid)
** Description changed:
PROBLEM
When a disk check is performed, the progress stalls somewhere around 70%
and will then take a very long time finishing the remaining percent (10
minutes or more).
PATCH
+
+ Patch for mountall has now been accepted into -proposed. See
+
The fix works for me.
I upgraded mountall to v2.15, ran sudo touch /forcefsck and reboot:
Filesystem check took ~15sek for 400GB. Thank you!
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a
** Tags added: verification-done
** Tags removed: verification-needed
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I've tested with the proposed mountall, both with and without the plymouth
change in my ppa.
I've noticed no distinct difference in speed or otherwise between the two cases.
So from a /strictly/ /superficial/ point of view, the plymouth patch
does not seem to change anything when it comes to
This bug was fixed in the package mountall - 2.15
---
mountall (2.15) lucid-proposed; urgency=low
[ Scott James Remnant ]
* Fix an obvious thinko error that meant that the Ignore fsck error key
for a hard failure was ignored.
* When cancelling filesystem checks, only cancel
copied from lucid-proposed to maverick.
** Changed in: mountall (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: mountall (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: mountall (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
fsck progress
Deeply depressing, I just feel like a newbie reading all this stuff even
though I've been completely M$-free for almost two years, but I have the
same problem, I've been watching the boot screen for nearly an hour,
this really ought to be a top priority for an automatic update, it's
completely
Further to the immediately preceding post, as an experiment, I forced
fsck on my one-year-old Acer Aspire One Atom-based Netbook with fresh
10.04 install. It has *exactly* the same bug: the check slows to snail's
pace, and C doesn't cancel. You could hardly find two more diverse
machines with the
Michael,
On Sun, May 09, 2010 at 02:34:30PM -, Michael Hampson wrote:
Further to the immediately preceding post, as an experiment, I forced
fsck on my one-year-old Acer Aspire One Atom-based Netbook with fresh
10.04 install. It has *exactly* the same bug: the check slows to snail's
pace,
Sorry ... I'll check it and report back once it comes through on
automatic updates. I missed the note #86 because so many of these
90-something comments are in note form rather than sentences, with
abbreviations and technical terms that mean nothing to me: I find these
pages very difficult to
Hi Michael,
As one of the random people who has posted a quite a few of those
technical comments I must apologise. The aim wasn't to make other
people's lives harder...
It took the pretty much an entire day last week of non stop work for me
to get a handle on the problem (I'm not the world's
1 - 100 of 173 matches
Mail list logo
