Results 1 to 4 of 4

Thread: Lucid drive check on startup

  1. #1
    Join Date
    Mar 2008
    Location
    GreaterManchesterUK
    Beans
    201
    Distro
    Ubuntu 11.10 Oneiric Ocelot

    Lucid drive check on startup

    I'm glad the occasional automatic drive check is still available on Lucid ,
    but unless I am mistaken it seems to take much,much, longer, ages in fact , has anyone else experienced this ?

  2. #2
    Join Date
    Apr 2010
    Beans
    327

    Re: Lucid drive check on startup

    Had the same problem. I dual boot fedora 11 and Ubuntu with a 250 gig sata drive. The filesystem check took forever. Seems to slow down more as it progresses. When the percentage reached around 90 percent it started to progress very slow. I almost thought it had stalled out for some reason.

    Shouldnt take that long. Running fsck in a term window is much faster.

    coffee

  3. #3
    Join Date
    May 2010
    Location
    Geelong Australia
    Beans
    16
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Lucid drive check on startup

    Had the same problem. There seems to be a bug in mountall see https://bugs.launchpad.net/bugs/571707 . Installing new package from lucid proposed fixed the problem for me. Disk check time dropped from 30 minutes to 20 secs.
    Hope this helps

  4. #4
    Join Date
    Apr 2008
    Location
    Waukesha, WI
    Beans
    56
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Lucid drive check on startup

    Quote Originally Posted by Ron S View Post
    Had the same problem. There seems to be a bug in mountall see https://bugs.launchpad.net/bugs/571707 . Installing new package from lucid proposed fixed the problem for me. Disk check time dropped from 30 minutes to 20 secs.
    Hope this helps
    Tried this and it seemed to work ok up to 70% then became v-e-r-y slow. From the same thread, I found this, which echoed my symptoms exactly:

    OBSERVATIONS

    The fsck message "(...) non-contiguous (...)" Which I assume indicates the end of the fsck, is printed in the Virtual Terminal ("outside" plymouth) at around 70% + ~10-20 seconds.

    Disk activity is null from this point on (presumed end of fsck above).

    Bootchart crashes if trying to catch the whole boot at once with plymouth (at least for my 1h boot).

    This problem seems to occur in both plymouthd and mountall, semi-simultaneously:
    If you are in the plymouth screen, plymouthd is the cpu-gobbler, if you switch away from it using the arrow keys, mountall instead takes over the cpu-eating.


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •