Ureadahead slows down boot process on Ubuntu 12.04












7















I'm using Ubuntu 12.04 64bit installed on a WD Velociraptor (10.000 rpm) hard disk. I'm not using Wubi, it's a clear install.



I think that "adding swap" procedure on boot takes too long. At first I thought that it has something to do with the swap mounting, but as you can see, I've spotted the problem in the "ureadahead" deamon.



You can see below dmesg partial output:




[ 5.347709] Console: switching to colour frame buffer device 210x65
[ 5.351756] fb0: VESA VGA frame buffer device
[ 5.613411] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 21.421858] Adding 1227772k swap on /dev/sda5. Priority:-1 extents:1 across:1227772k
[ 21.425834] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 21.425841] ADDRCONF(NETDEV_UP): eth1: link is not ready



Complete dmesg output



Taking into account my hard drive's speed, this delay is not normal.



After upgrading to the latest kernel (3.2.0.36 from 3.2.0.35) or after removing "/var/lib/ureadahead/pack" file, the problem is temporary solved, just for one boot.
After the second boot the problem returns.



This is the dmesg output when everything works perfect:



[    5.120096] Console: switching to colour frame buffer device 210x65
[ 5.124150] fb0: VESA VGA frame buffer device
[ 5.285586] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 6.953086] Adding 1227772k swap on /dev/sda5. Priority:-1 extents:1 across:1227772k
[ 7.516909] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.516916] ADDRCONF(NETDEV_UP): eth1: link is not ready


Complete dmesg output



As suggested in the comments I've tried to disable the swap mounting and the delay was moved to the next process, so it seems that it has nothing to do with swap mounting:
dmesg output:



[ 5.862973] EXT4-fs (sda3): recovery complete 
[ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready


@gertvdijk noticed that in the latest dmesg output my system recovered from something, but this just happened just when I've comment out the swap from "/etc/fstab".



I've spoted the problem

Ureadahead slows down the boot process. This is weird since the opposite should happen!

Below I'm posting bootchart images and dmesg output of three different boots:




  1. Without ureadahead (disabled following this guide) there is no
    delay:
    dmesg output (ureadahead disabled)
    bootchart output (ureadahead disabled)

  2. With ureadahead enabled first boot (pack file is build for the first time) no delay:
    dmesg output (ureadahead enabled)
    bootchart output (ureadahead disabled)


  3. With ureadahead enabled second boot (ureadahead full working) delay is back:
    dmesg output (ureadahead enabled second boot)
    bootchart output (ureadahead disabled second boot)



NOTE

My question seems to be a duplicate of this Very slow boot due to mounting filesytem which concerns Ubuntu 11.04 and has no solution yet! If any admin reading this, I don't know if I have to delete my question as a duplicate since the problem doesn't seems to be the swap mounting... if so, delete it, or please, inform me to do so!










share|improve this question

























  • Have you tried disabling swap for the time being to exclude all other causes? Just comment (prepend with #) the line for swap in /etc/fstab and reboot.

    – gertvdijk
    Jan 18 '13 at 1:07











  • Thank you for your interest!<br/>I've just tried it.. I no more have this issue but again booting takes more time than normal delaying on the next line "ADDRCONF(NETDEV_UP): eth0: link is not ready"! dmesg output: [ 5.862973] EXT4-fs (sda3): recovery complete [ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready

    – naskoos
    Jan 18 '13 at 9:16













  • Then it's not loading of swap being the cause. I see recovery complete in your logs, indicating that you haven't shut down your system properly. I feel there's a lot more going on... like... are you using Wubi for example?

    – gertvdijk
    Jan 18 '13 at 9:23













  • If you look above the output of the dmesg in the first update of my question, 17.589428 is not normal time for ADDRCONF! Sorry for the mess in my comments but how can I add a line break when writing a comment?

    – naskoos
    Jan 18 '13 at 9:26











  • No I'm not using Wubi! It's a clear install!

    – naskoos
    Jan 18 '13 at 9:27
















7















I'm using Ubuntu 12.04 64bit installed on a WD Velociraptor (10.000 rpm) hard disk. I'm not using Wubi, it's a clear install.



I think that "adding swap" procedure on boot takes too long. At first I thought that it has something to do with the swap mounting, but as you can see, I've spotted the problem in the "ureadahead" deamon.



You can see below dmesg partial output:




[ 5.347709] Console: switching to colour frame buffer device 210x65
[ 5.351756] fb0: VESA VGA frame buffer device
[ 5.613411] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 21.421858] Adding 1227772k swap on /dev/sda5. Priority:-1 extents:1 across:1227772k
[ 21.425834] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 21.425841] ADDRCONF(NETDEV_UP): eth1: link is not ready



Complete dmesg output



Taking into account my hard drive's speed, this delay is not normal.



After upgrading to the latest kernel (3.2.0.36 from 3.2.0.35) or after removing "/var/lib/ureadahead/pack" file, the problem is temporary solved, just for one boot.
After the second boot the problem returns.



This is the dmesg output when everything works perfect:



[    5.120096] Console: switching to colour frame buffer device 210x65
[ 5.124150] fb0: VESA VGA frame buffer device
[ 5.285586] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 6.953086] Adding 1227772k swap on /dev/sda5. Priority:-1 extents:1 across:1227772k
[ 7.516909] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.516916] ADDRCONF(NETDEV_UP): eth1: link is not ready


Complete dmesg output



As suggested in the comments I've tried to disable the swap mounting and the delay was moved to the next process, so it seems that it has nothing to do with swap mounting:
dmesg output:



[ 5.862973] EXT4-fs (sda3): recovery complete 
[ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready


@gertvdijk noticed that in the latest dmesg output my system recovered from something, but this just happened just when I've comment out the swap from "/etc/fstab".



I've spoted the problem

Ureadahead slows down the boot process. This is weird since the opposite should happen!

Below I'm posting bootchart images and dmesg output of three different boots:




  1. Without ureadahead (disabled following this guide) there is no
    delay:
    dmesg output (ureadahead disabled)
    bootchart output (ureadahead disabled)

  2. With ureadahead enabled first boot (pack file is build for the first time) no delay:
    dmesg output (ureadahead enabled)
    bootchart output (ureadahead disabled)


  3. With ureadahead enabled second boot (ureadahead full working) delay is back:
    dmesg output (ureadahead enabled second boot)
    bootchart output (ureadahead disabled second boot)



NOTE

My question seems to be a duplicate of this Very slow boot due to mounting filesytem which concerns Ubuntu 11.04 and has no solution yet! If any admin reading this, I don't know if I have to delete my question as a duplicate since the problem doesn't seems to be the swap mounting... if so, delete it, or please, inform me to do so!










share|improve this question

























  • Have you tried disabling swap for the time being to exclude all other causes? Just comment (prepend with #) the line for swap in /etc/fstab and reboot.

    – gertvdijk
    Jan 18 '13 at 1:07











  • Thank you for your interest!<br/>I've just tried it.. I no more have this issue but again booting takes more time than normal delaying on the next line "ADDRCONF(NETDEV_UP): eth0: link is not ready"! dmesg output: [ 5.862973] EXT4-fs (sda3): recovery complete [ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready

    – naskoos
    Jan 18 '13 at 9:16













  • Then it's not loading of swap being the cause. I see recovery complete in your logs, indicating that you haven't shut down your system properly. I feel there's a lot more going on... like... are you using Wubi for example?

    – gertvdijk
    Jan 18 '13 at 9:23













  • If you look above the output of the dmesg in the first update of my question, 17.589428 is not normal time for ADDRCONF! Sorry for the mess in my comments but how can I add a line break when writing a comment?

    – naskoos
    Jan 18 '13 at 9:26











  • No I'm not using Wubi! It's a clear install!

    – naskoos
    Jan 18 '13 at 9:27














7












7








7


1






I'm using Ubuntu 12.04 64bit installed on a WD Velociraptor (10.000 rpm) hard disk. I'm not using Wubi, it's a clear install.



I think that "adding swap" procedure on boot takes too long. At first I thought that it has something to do with the swap mounting, but as you can see, I've spotted the problem in the "ureadahead" deamon.



You can see below dmesg partial output:




[ 5.347709] Console: switching to colour frame buffer device 210x65
[ 5.351756] fb0: VESA VGA frame buffer device
[ 5.613411] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 21.421858] Adding 1227772k swap on /dev/sda5. Priority:-1 extents:1 across:1227772k
[ 21.425834] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 21.425841] ADDRCONF(NETDEV_UP): eth1: link is not ready



Complete dmesg output



Taking into account my hard drive's speed, this delay is not normal.



After upgrading to the latest kernel (3.2.0.36 from 3.2.0.35) or after removing "/var/lib/ureadahead/pack" file, the problem is temporary solved, just for one boot.
After the second boot the problem returns.



This is the dmesg output when everything works perfect:



[    5.120096] Console: switching to colour frame buffer device 210x65
[ 5.124150] fb0: VESA VGA frame buffer device
[ 5.285586] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 6.953086] Adding 1227772k swap on /dev/sda5. Priority:-1 extents:1 across:1227772k
[ 7.516909] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.516916] ADDRCONF(NETDEV_UP): eth1: link is not ready


Complete dmesg output



As suggested in the comments I've tried to disable the swap mounting and the delay was moved to the next process, so it seems that it has nothing to do with swap mounting:
dmesg output:



[ 5.862973] EXT4-fs (sda3): recovery complete 
[ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready


@gertvdijk noticed that in the latest dmesg output my system recovered from something, but this just happened just when I've comment out the swap from "/etc/fstab".



I've spoted the problem

Ureadahead slows down the boot process. This is weird since the opposite should happen!

Below I'm posting bootchart images and dmesg output of three different boots:




  1. Without ureadahead (disabled following this guide) there is no
    delay:
    dmesg output (ureadahead disabled)
    bootchart output (ureadahead disabled)

  2. With ureadahead enabled first boot (pack file is build for the first time) no delay:
    dmesg output (ureadahead enabled)
    bootchart output (ureadahead disabled)


  3. With ureadahead enabled second boot (ureadahead full working) delay is back:
    dmesg output (ureadahead enabled second boot)
    bootchart output (ureadahead disabled second boot)



NOTE

My question seems to be a duplicate of this Very slow boot due to mounting filesytem which concerns Ubuntu 11.04 and has no solution yet! If any admin reading this, I don't know if I have to delete my question as a duplicate since the problem doesn't seems to be the swap mounting... if so, delete it, or please, inform me to do so!










share|improve this question
















I'm using Ubuntu 12.04 64bit installed on a WD Velociraptor (10.000 rpm) hard disk. I'm not using Wubi, it's a clear install.



I think that "adding swap" procedure on boot takes too long. At first I thought that it has something to do with the swap mounting, but as you can see, I've spotted the problem in the "ureadahead" deamon.



You can see below dmesg partial output:




[ 5.347709] Console: switching to colour frame buffer device 210x65
[ 5.351756] fb0: VESA VGA frame buffer device
[ 5.613411] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 21.421858] Adding 1227772k swap on /dev/sda5. Priority:-1 extents:1 across:1227772k
[ 21.425834] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 21.425841] ADDRCONF(NETDEV_UP): eth1: link is not ready



Complete dmesg output



Taking into account my hard drive's speed, this delay is not normal.



After upgrading to the latest kernel (3.2.0.36 from 3.2.0.35) or after removing "/var/lib/ureadahead/pack" file, the problem is temporary solved, just for one boot.
After the second boot the problem returns.



This is the dmesg output when everything works perfect:



[    5.120096] Console: switching to colour frame buffer device 210x65
[ 5.124150] fb0: VESA VGA frame buffer device
[ 5.285586] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 6.953086] Adding 1227772k swap on /dev/sda5. Priority:-1 extents:1 across:1227772k
[ 7.516909] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.516916] ADDRCONF(NETDEV_UP): eth1: link is not ready


Complete dmesg output



As suggested in the comments I've tried to disable the swap mounting and the delay was moved to the next process, so it seems that it has nothing to do with swap mounting:
dmesg output:



[ 5.862973] EXT4-fs (sda3): recovery complete 
[ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready


@gertvdijk noticed that in the latest dmesg output my system recovered from something, but this just happened just when I've comment out the swap from "/etc/fstab".



I've spoted the problem

Ureadahead slows down the boot process. This is weird since the opposite should happen!

Below I'm posting bootchart images and dmesg output of three different boots:




  1. Without ureadahead (disabled following this guide) there is no
    delay:
    dmesg output (ureadahead disabled)
    bootchart output (ureadahead disabled)

  2. With ureadahead enabled first boot (pack file is build for the first time) no delay:
    dmesg output (ureadahead enabled)
    bootchart output (ureadahead disabled)


  3. With ureadahead enabled second boot (ureadahead full working) delay is back:
    dmesg output (ureadahead enabled second boot)
    bootchart output (ureadahead disabled second boot)



NOTE

My question seems to be a duplicate of this Very slow boot due to mounting filesytem which concerns Ubuntu 11.04 and has no solution yet! If any admin reading this, I don't know if I have to delete my question as a duplicate since the problem doesn't seems to be the swap mounting... if so, delete it, or please, inform me to do so!







ureadahead






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 13 '17 at 12:23









Community

1




1










asked Jan 17 '13 at 23:39









naskoosnaskoos

329412




329412













  • Have you tried disabling swap for the time being to exclude all other causes? Just comment (prepend with #) the line for swap in /etc/fstab and reboot.

    – gertvdijk
    Jan 18 '13 at 1:07











  • Thank you for your interest!<br/>I've just tried it.. I no more have this issue but again booting takes more time than normal delaying on the next line "ADDRCONF(NETDEV_UP): eth0: link is not ready"! dmesg output: [ 5.862973] EXT4-fs (sda3): recovery complete [ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready

    – naskoos
    Jan 18 '13 at 9:16













  • Then it's not loading of swap being the cause. I see recovery complete in your logs, indicating that you haven't shut down your system properly. I feel there's a lot more going on... like... are you using Wubi for example?

    – gertvdijk
    Jan 18 '13 at 9:23













  • If you look above the output of the dmesg in the first update of my question, 17.589428 is not normal time for ADDRCONF! Sorry for the mess in my comments but how can I add a line break when writing a comment?

    – naskoos
    Jan 18 '13 at 9:26











  • No I'm not using Wubi! It's a clear install!

    – naskoos
    Jan 18 '13 at 9:27



















  • Have you tried disabling swap for the time being to exclude all other causes? Just comment (prepend with #) the line for swap in /etc/fstab and reboot.

    – gertvdijk
    Jan 18 '13 at 1:07











  • Thank you for your interest!<br/>I've just tried it.. I no more have this issue but again booting takes more time than normal delaying on the next line "ADDRCONF(NETDEV_UP): eth0: link is not ready"! dmesg output: [ 5.862973] EXT4-fs (sda3): recovery complete [ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready

    – naskoos
    Jan 18 '13 at 9:16













  • Then it's not loading of swap being the cause. I see recovery complete in your logs, indicating that you haven't shut down your system properly. I feel there's a lot more going on... like... are you using Wubi for example?

    – gertvdijk
    Jan 18 '13 at 9:23













  • If you look above the output of the dmesg in the first update of my question, 17.589428 is not normal time for ADDRCONF! Sorry for the mess in my comments but how can I add a line break when writing a comment?

    – naskoos
    Jan 18 '13 at 9:26











  • No I'm not using Wubi! It's a clear install!

    – naskoos
    Jan 18 '13 at 9:27

















Have you tried disabling swap for the time being to exclude all other causes? Just comment (prepend with #) the line for swap in /etc/fstab and reboot.

– gertvdijk
Jan 18 '13 at 1:07





Have you tried disabling swap for the time being to exclude all other causes? Just comment (prepend with #) the line for swap in /etc/fstab and reboot.

– gertvdijk
Jan 18 '13 at 1:07













Thank you for your interest!<br/>I've just tried it.. I no more have this issue but again booting takes more time than normal delaying on the next line "ADDRCONF(NETDEV_UP): eth0: link is not ready"! dmesg output: [ 5.862973] EXT4-fs (sda3): recovery complete [ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready

– naskoos
Jan 18 '13 at 9:16







Thank you for your interest!<br/>I've just tried it.. I no more have this issue but again booting takes more time than normal delaying on the next line "ADDRCONF(NETDEV_UP): eth0: link is not ready"! dmesg output: [ 5.862973] EXT4-fs (sda3): recovery complete [ 5.887252] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 17.589428] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 17.589435] ADDRCONF(NETDEV_UP): eth1: link is not ready

– naskoos
Jan 18 '13 at 9:16















Then it's not loading of swap being the cause. I see recovery complete in your logs, indicating that you haven't shut down your system properly. I feel there's a lot more going on... like... are you using Wubi for example?

– gertvdijk
Jan 18 '13 at 9:23







Then it's not loading of swap being the cause. I see recovery complete in your logs, indicating that you haven't shut down your system properly. I feel there's a lot more going on... like... are you using Wubi for example?

– gertvdijk
Jan 18 '13 at 9:23















If you look above the output of the dmesg in the first update of my question, 17.589428 is not normal time for ADDRCONF! Sorry for the mess in my comments but how can I add a line break when writing a comment?

– naskoos
Jan 18 '13 at 9:26





If you look above the output of the dmesg in the first update of my question, 17.589428 is not normal time for ADDRCONF! Sorry for the mess in my comments but how can I add a line break when writing a comment?

– naskoos
Jan 18 '13 at 9:26













No I'm not using Wubi! It's a clear install!

– naskoos
Jan 18 '13 at 9:27





No I'm not using Wubi! It's a clear install!

– naskoos
Jan 18 '13 at 9:27










2 Answers
2






active

oldest

votes


















0














Try e4rat, it's faster and reliable



ppa https://launchpad.net/~trinitronx/+archive/minimal-no-ureadahead



how to use http://www.howtogeek.com/69753/how-to-cut-your-linux-pcs-boot-time-in-half-with-e4rat/






share|improve this answer































    -1














    Do a clean install of Ubuntu 13.10, it is the latest updated Ubuntu version. Your problems might be fixed under that version, updates always fix problems.






    share|improve this answer
























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f244450%2fureadahead-slows-down-boot-process-on-ubuntu-12-04%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      Try e4rat, it's faster and reliable



      ppa https://launchpad.net/~trinitronx/+archive/minimal-no-ureadahead



      how to use http://www.howtogeek.com/69753/how-to-cut-your-linux-pcs-boot-time-in-half-with-e4rat/






      share|improve this answer




























        0














        Try e4rat, it's faster and reliable



        ppa https://launchpad.net/~trinitronx/+archive/minimal-no-ureadahead



        how to use http://www.howtogeek.com/69753/how-to-cut-your-linux-pcs-boot-time-in-half-with-e4rat/






        share|improve this answer


























          0












          0








          0







          Try e4rat, it's faster and reliable



          ppa https://launchpad.net/~trinitronx/+archive/minimal-no-ureadahead



          how to use http://www.howtogeek.com/69753/how-to-cut-your-linux-pcs-boot-time-in-half-with-e4rat/






          share|improve this answer













          Try e4rat, it's faster and reliable



          ppa https://launchpad.net/~trinitronx/+archive/minimal-no-ureadahead



          how to use http://www.howtogeek.com/69753/how-to-cut-your-linux-pcs-boot-time-in-half-with-e4rat/







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 27 '14 at 14:38









          kennkenn

          2,84353065




          2,84353065

























              -1














              Do a clean install of Ubuntu 13.10, it is the latest updated Ubuntu version. Your problems might be fixed under that version, updates always fix problems.






              share|improve this answer




























                -1














                Do a clean install of Ubuntu 13.10, it is the latest updated Ubuntu version. Your problems might be fixed under that version, updates always fix problems.






                share|improve this answer


























                  -1












                  -1








                  -1







                  Do a clean install of Ubuntu 13.10, it is the latest updated Ubuntu version. Your problems might be fixed under that version, updates always fix problems.






                  share|improve this answer













                  Do a clean install of Ubuntu 13.10, it is the latest updated Ubuntu version. Your problems might be fixed under that version, updates always fix problems.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 8 '14 at 13:13









                  BraskBrask

                  1,4021018




                  1,4021018






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f244450%2fureadahead-slows-down-boot-process-on-ubuntu-12-04%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Questions related to Moebius Transform of Characteristic Function of the Primes

                      List of scandals in India

                      Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?