Slow boot, long kernel load time, due to wrong resume deviceHow to diagnose/fix very slow boot on Ubuntu...

Explain the objections to these measures against human trafficking

En Passant For Beginners

Closed form for these polynomials?

QGIS: use geometry from different layer in symbology expression

Is it a fallacy if someone claims they need an explanation for every word of your argument to the point where they don't understand common terms?

Knowing when to use pictures over words

Could flying insects re-enter the Earth's atmosphere from space without burning up?

Can we use the stored gravitational potential energy of a building to produce power?

How can I deal with a significant flaw I found in my previous supervisor’s paper?

Manipulating a general length function

"On one hand" vs "on the one hand."

High pressure canisters of air as gun-less projectiles

What do you call a fact that doesn't match the settings?

Are there any monsters that consume a player character?

What is the time complexity of enqueue and dequeue of a queue implemented with a singly linked list?

Compound Interest... with Wizard Money

Program that converts a number to a letter of the alphabet

What is the etymology of the kanji 食?

Quenching swords in dragon blood; why?

Can pricing be copyrighted?

Is there a better way to make this?

integral inequality of length of curve

Do authors have to be politically correct in article-writing?

Getting a UK passport renewed when you have dual nationality and a different name in your second country?



Slow boot, long kernel load time, due to wrong resume device


How to diagnose/fix very slow boot on Ubuntu 18.04Slow boot time (Ubuntu 18.04) on SSDSlow startup 18.04 on an SSDVery slow boot on Ubuntu 18.0418.04 delayed boot - which device?Slow boot time (Xubuntu 18.04)Error on boot: “failed to connect to lvmetad” after 18.04 installTrying to add Windows 7 to grub2Unable to boot into Windows 10 after installing Ubuntukernel takes long load timeUbuntu 16.04 on Asus d541 N bad blockUbuntu 16.04 login loop withLong starting time, slow bootAre those /etc/fstab settings ok?Why remounting root file system takes a lot of time?Slow boot due to long loader timeboot very slowly after upgrade ubuntu 18.04













28















For some time, my boot process is taking too long (almost 1 min.).



systemd-analyse time 


shows that kernel is taking 35.765s



Looking at dmesg, it seems that the problem is with mounting file systems:



...
[ 2.186084] sdb: sdb1 sdb9
[ 2.186919] sd 2:0:0:0: [sdb] supports TCG Opal
[ 2.186922] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 2.499795] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.844320] clocksource: Switched to clocksource tsc
[ 35.670493] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 35.782128] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 35.803610] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
...


My /etc/fstab looks like this:



# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=3996-2381 /boot/efi vfat umask=0077 0 1
#/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0


How can I troubleshoot this ?



EDIT: looking closely at the boot messages (after removing the quiet option in grub), I spotted a suspicious line:



gave up waiting for suspend/resume device


I think my swap is encrypted, and I also think the UUID in /etc/initramfs/conf.d/resume does not correspond to any device.



Should I disable resume/suspend? and how to do that?










share|improve this question




















  • 5





    The problem is actually at ``` Begin: Running /scripts/local-premount ``` It is displayed during the boot (if you disable quiet). Due to some reason this premount script is taking a 30 seconds or so.

    – Sudhanshu
    Mar 11 '18 at 11:27













  • This question/answer is valuable because it helps solve a bug in Lubuntu Bionic, so please help reopen it :-)

    – sudodus
    Apr 20 '18 at 14:37


















28















For some time, my boot process is taking too long (almost 1 min.).



systemd-analyse time 


shows that kernel is taking 35.765s



Looking at dmesg, it seems that the problem is with mounting file systems:



...
[ 2.186084] sdb: sdb1 sdb9
[ 2.186919] sd 2:0:0:0: [sdb] supports TCG Opal
[ 2.186922] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 2.499795] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.844320] clocksource: Switched to clocksource tsc
[ 35.670493] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 35.782128] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 35.803610] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
...


My /etc/fstab looks like this:



# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=3996-2381 /boot/efi vfat umask=0077 0 1
#/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0


How can I troubleshoot this ?



EDIT: looking closely at the boot messages (after removing the quiet option in grub), I spotted a suspicious line:



gave up waiting for suspend/resume device


I think my swap is encrypted, and I also think the UUID in /etc/initramfs/conf.d/resume does not correspond to any device.



Should I disable resume/suspend? and how to do that?










share|improve this question




















  • 5





    The problem is actually at ``` Begin: Running /scripts/local-premount ``` It is displayed during the boot (if you disable quiet). Due to some reason this premount script is taking a 30 seconds or so.

    – Sudhanshu
    Mar 11 '18 at 11:27













  • This question/answer is valuable because it helps solve a bug in Lubuntu Bionic, so please help reopen it :-)

    – sudodus
    Apr 20 '18 at 14:37
















28












28








28


11






For some time, my boot process is taking too long (almost 1 min.).



systemd-analyse time 


shows that kernel is taking 35.765s



Looking at dmesg, it seems that the problem is with mounting file systems:



...
[ 2.186084] sdb: sdb1 sdb9
[ 2.186919] sd 2:0:0:0: [sdb] supports TCG Opal
[ 2.186922] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 2.499795] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.844320] clocksource: Switched to clocksource tsc
[ 35.670493] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 35.782128] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 35.803610] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
...


My /etc/fstab looks like this:



# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=3996-2381 /boot/efi vfat umask=0077 0 1
#/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0


How can I troubleshoot this ?



EDIT: looking closely at the boot messages (after removing the quiet option in grub), I spotted a suspicious line:



gave up waiting for suspend/resume device


I think my swap is encrypted, and I also think the UUID in /etc/initramfs/conf.d/resume does not correspond to any device.



Should I disable resume/suspend? and how to do that?










share|improve this question
















For some time, my boot process is taking too long (almost 1 min.).



systemd-analyse time 


shows that kernel is taking 35.765s



Looking at dmesg, it seems that the problem is with mounting file systems:



...
[ 2.186084] sdb: sdb1 sdb9
[ 2.186919] sd 2:0:0:0: [sdb] supports TCG Opal
[ 2.186922] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 2.499795] ata5: SATA link down (SStatus 0 SControl 300)
[ 2.844320] clocksource: Switched to clocksource tsc
[ 35.670493] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[ 35.782128] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 35.803610] systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
...


My /etc/fstab looks like this:



# <file system> <mount point>   <type>  <options>       <dump>  <pass>
/dev/mapper/ubuntu--vg-root / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=3996-2381 /boot/efi vfat umask=0077 0 1
#/dev/mapper/ubuntu--vg-swap_1 none swap sw 0 0
/dev/mapper/cryptswap1 none swap sw 0 0


How can I troubleshoot this ?



EDIT: looking closely at the boot messages (after removing the quiet option in grub), I spotted a suspicious line:



gave up waiting for suspend/resume device


I think my swap is encrypted, and I also think the UUID in /etc/initramfs/conf.d/resume does not correspond to any device.



Should I disable resume/suspend? and how to do that?







boot kernel






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 13 '18 at 9:04







alci

















asked Mar 11 '18 at 8:42









alcialci

3,04043255




3,04043255








  • 5





    The problem is actually at ``` Begin: Running /scripts/local-premount ``` It is displayed during the boot (if you disable quiet). Due to some reason this premount script is taking a 30 seconds or so.

    – Sudhanshu
    Mar 11 '18 at 11:27













  • This question/answer is valuable because it helps solve a bug in Lubuntu Bionic, so please help reopen it :-)

    – sudodus
    Apr 20 '18 at 14:37
















  • 5





    The problem is actually at ``` Begin: Running /scripts/local-premount ``` It is displayed during the boot (if you disable quiet). Due to some reason this premount script is taking a 30 seconds or so.

    – Sudhanshu
    Mar 11 '18 at 11:27













  • This question/answer is valuable because it helps solve a bug in Lubuntu Bionic, so please help reopen it :-)

    – sudodus
    Apr 20 '18 at 14:37










5




5





The problem is actually at ``` Begin: Running /scripts/local-premount ``` It is displayed during the boot (if you disable quiet). Due to some reason this premount script is taking a 30 seconds or so.

– Sudhanshu
Mar 11 '18 at 11:27







The problem is actually at ``` Begin: Running /scripts/local-premount ``` It is displayed during the boot (if you disable quiet). Due to some reason this premount script is taking a 30 seconds or so.

– Sudhanshu
Mar 11 '18 at 11:27















This question/answer is valuable because it helps solve a bug in Lubuntu Bionic, so please help reopen it :-)

– sudodus
Apr 20 '18 at 14:37







This question/answer is valuable because it helps solve a bug in Lubuntu Bionic, so please help reopen it :-)

– sudodus
Apr 20 '18 at 14:37












3 Answers
3






active

oldest

votes


















41














Ok, I found the solution, thanks to Sudhanshu's comment.



The problem was due to my swap being encrypted. So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device.



To disable this (as resuming from swap is not possible with an encrypted swap, and I don't use hibernation anyway), I modified this file: /etc/initramfs-tools/conf.d/resume.



In this file, a line with



RESUME=none


(instead of the UUID that was here) will disable waiting for a resume device.



Run



sudo update-initramfs -u


to apply the changes.



System now boots normally.






share|improve this answer





















  • 1





    I think you are affected by Bug #1763611, Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs. And you have shown how to squash the bug :-)

    – sudodus
    Apr 20 '18 at 13:24








  • 2





    Brilliant! Thanks for the fix. It had me pulling my hair out!

    – Murray
    May 24 '18 at 23:58



















1














None of those solutions above or elsewhere worked out for me but I have found a solution which reduces my boot time to 40 seconds from 2 minutes and 10 seconds.



I used to create and remove swap partitions and somehow these logs stayed in etc/fstab file. So my system was trying to mount those previously created swap partitions which no longer exists. So please let me explain what I did step by step.




  1. I ran this command sudo blkid | grep swap to find out my swap partitions. There was two but one does not actually exist (it does not refer to any of my partitions).


  2. So I went to edit /etc/fstab file by typing sudo gedit /etc/fstab


  3. Then I realized there are so many swap files which I had deleted but somehow resumed existing in this file. So I referred to step 1 and deleted partitions which no longer exist.



Please see two before & after /etc/fstab file screenshots. After this cleanout everything's working as normal.



This is unedited /etc/fstab file unedited /etc/fstab



and here after wiping out non-existing swap partitions clean /etc/fstab






share|improve this answer

































    0














    I also saw this in Linux Mint (based on Ubuntu), and spent some time working out what was going wrong.



    This happens if your system is installed on LVM and is using an LVM volume as the swap disk.



    There is a long-standing, recurring bug where the resume file incorrectly has a UUID (which is invalid for LVM) instead of the device path that it should have.
    See https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230



    You can fix it by editing the /etc/initramfs-tools/conf.d/resume file and replacing the UUID with the device path of the swap drive.
    The following command snippet will do this for you, using the first swap drive found and reported by blkid:



    sudo bash -c 'mv /etc/initramfs-tools/conf.d/resume /tmp/resume.bak; echo RESUME=$(blkid | grep swap | head -n 1 | cut -d : -f 1) > /etc/initramfs-tools/conf.d/resume'




    share








    New contributor




    Nameless Voice is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.




















      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%2f1013830%2fslow-boot-long-kernel-load-time-due-to-wrong-resume-device%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      41














      Ok, I found the solution, thanks to Sudhanshu's comment.



      The problem was due to my swap being encrypted. So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device.



      To disable this (as resuming from swap is not possible with an encrypted swap, and I don't use hibernation anyway), I modified this file: /etc/initramfs-tools/conf.d/resume.



      In this file, a line with



      RESUME=none


      (instead of the UUID that was here) will disable waiting for a resume device.



      Run



      sudo update-initramfs -u


      to apply the changes.



      System now boots normally.






      share|improve this answer





















      • 1





        I think you are affected by Bug #1763611, Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs. And you have shown how to squash the bug :-)

        – sudodus
        Apr 20 '18 at 13:24








      • 2





        Brilliant! Thanks for the fix. It had me pulling my hair out!

        – Murray
        May 24 '18 at 23:58
















      41














      Ok, I found the solution, thanks to Sudhanshu's comment.



      The problem was due to my swap being encrypted. So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device.



      To disable this (as resuming from swap is not possible with an encrypted swap, and I don't use hibernation anyway), I modified this file: /etc/initramfs-tools/conf.d/resume.



      In this file, a line with



      RESUME=none


      (instead of the UUID that was here) will disable waiting for a resume device.



      Run



      sudo update-initramfs -u


      to apply the changes.



      System now boots normally.






      share|improve this answer





















      • 1





        I think you are affected by Bug #1763611, Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs. And you have shown how to squash the bug :-)

        – sudodus
        Apr 20 '18 at 13:24








      • 2





        Brilliant! Thanks for the fix. It had me pulling my hair out!

        – Murray
        May 24 '18 at 23:58














      41












      41








      41







      Ok, I found the solution, thanks to Sudhanshu's comment.



      The problem was due to my swap being encrypted. So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device.



      To disable this (as resuming from swap is not possible with an encrypted swap, and I don't use hibernation anyway), I modified this file: /etc/initramfs-tools/conf.d/resume.



      In this file, a line with



      RESUME=none


      (instead of the UUID that was here) will disable waiting for a resume device.



      Run



      sudo update-initramfs -u


      to apply the changes.



      System now boots normally.






      share|improve this answer















      Ok, I found the solution, thanks to Sudhanshu's comment.



      The problem was due to my swap being encrypted. So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device.



      To disable this (as resuming from swap is not possible with an encrypted swap, and I don't use hibernation anyway), I modified this file: /etc/initramfs-tools/conf.d/resume.



      In this file, a line with



      RESUME=none


      (instead of the UUID that was here) will disable waiting for a resume device.



      Run



      sudo update-initramfs -u


      to apply the changes.



      System now boots normally.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Nov 23 '18 at 17:22









      abu_bua

      3,45081227




      3,45081227










      answered Mar 11 '18 at 17:36









      alcialci

      3,04043255




      3,04043255








      • 1





        I think you are affected by Bug #1763611, Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs. And you have shown how to squash the bug :-)

        – sudodus
        Apr 20 '18 at 13:24








      • 2





        Brilliant! Thanks for the fix. It had me pulling my hair out!

        – Murray
        May 24 '18 at 23:58














      • 1





        I think you are affected by Bug #1763611, Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs. And you have shown how to squash the bug :-)

        – sudodus
        Apr 20 '18 at 13:24








      • 2





        Brilliant! Thanks for the fix. It had me pulling my hair out!

        – Murray
        May 24 '18 at 23:58








      1




      1





      I think you are affected by Bug #1763611, Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs. And you have shown how to squash the bug :-)

      – sudodus
      Apr 20 '18 at 13:24







      I think you are affected by Bug #1763611, Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs. And you have shown how to squash the bug :-)

      – sudodus
      Apr 20 '18 at 13:24






      2




      2





      Brilliant! Thanks for the fix. It had me pulling my hair out!

      – Murray
      May 24 '18 at 23:58





      Brilliant! Thanks for the fix. It had me pulling my hair out!

      – Murray
      May 24 '18 at 23:58













      1














      None of those solutions above or elsewhere worked out for me but I have found a solution which reduces my boot time to 40 seconds from 2 minutes and 10 seconds.



      I used to create and remove swap partitions and somehow these logs stayed in etc/fstab file. So my system was trying to mount those previously created swap partitions which no longer exists. So please let me explain what I did step by step.




      1. I ran this command sudo blkid | grep swap to find out my swap partitions. There was two but one does not actually exist (it does not refer to any of my partitions).


      2. So I went to edit /etc/fstab file by typing sudo gedit /etc/fstab


      3. Then I realized there are so many swap files which I had deleted but somehow resumed existing in this file. So I referred to step 1 and deleted partitions which no longer exist.



      Please see two before & after /etc/fstab file screenshots. After this cleanout everything's working as normal.



      This is unedited /etc/fstab file unedited /etc/fstab



      and here after wiping out non-existing swap partitions clean /etc/fstab






      share|improve this answer






























        1














        None of those solutions above or elsewhere worked out for me but I have found a solution which reduces my boot time to 40 seconds from 2 minutes and 10 seconds.



        I used to create and remove swap partitions and somehow these logs stayed in etc/fstab file. So my system was trying to mount those previously created swap partitions which no longer exists. So please let me explain what I did step by step.




        1. I ran this command sudo blkid | grep swap to find out my swap partitions. There was two but one does not actually exist (it does not refer to any of my partitions).


        2. So I went to edit /etc/fstab file by typing sudo gedit /etc/fstab


        3. Then I realized there are so many swap files which I had deleted but somehow resumed existing in this file. So I referred to step 1 and deleted partitions which no longer exist.



        Please see two before & after /etc/fstab file screenshots. After this cleanout everything's working as normal.



        This is unedited /etc/fstab file unedited /etc/fstab



        and here after wiping out non-existing swap partitions clean /etc/fstab






        share|improve this answer




























          1












          1








          1







          None of those solutions above or elsewhere worked out for me but I have found a solution which reduces my boot time to 40 seconds from 2 minutes and 10 seconds.



          I used to create and remove swap partitions and somehow these logs stayed in etc/fstab file. So my system was trying to mount those previously created swap partitions which no longer exists. So please let me explain what I did step by step.




          1. I ran this command sudo blkid | grep swap to find out my swap partitions. There was two but one does not actually exist (it does not refer to any of my partitions).


          2. So I went to edit /etc/fstab file by typing sudo gedit /etc/fstab


          3. Then I realized there are so many swap files which I had deleted but somehow resumed existing in this file. So I referred to step 1 and deleted partitions which no longer exist.



          Please see two before & after /etc/fstab file screenshots. After this cleanout everything's working as normal.



          This is unedited /etc/fstab file unedited /etc/fstab



          and here after wiping out non-existing swap partitions clean /etc/fstab






          share|improve this answer















          None of those solutions above or elsewhere worked out for me but I have found a solution which reduces my boot time to 40 seconds from 2 minutes and 10 seconds.



          I used to create and remove swap partitions and somehow these logs stayed in etc/fstab file. So my system was trying to mount those previously created swap partitions which no longer exists. So please let me explain what I did step by step.




          1. I ran this command sudo blkid | grep swap to find out my swap partitions. There was two but one does not actually exist (it does not refer to any of my partitions).


          2. So I went to edit /etc/fstab file by typing sudo gedit /etc/fstab


          3. Then I realized there are so many swap files which I had deleted but somehow resumed existing in this file. So I referred to step 1 and deleted partitions which no longer exist.



          Please see two before & after /etc/fstab file screenshots. After this cleanout everything's working as normal.



          This is unedited /etc/fstab file unedited /etc/fstab



          and here after wiping out non-existing swap partitions clean /etc/fstab







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Feb 16 at 8:27









          mature

          2,1172730




          2,1172730










          answered Dec 8 '18 at 22:49









          denideni

          111




          111























              0














              I also saw this in Linux Mint (based on Ubuntu), and spent some time working out what was going wrong.



              This happens if your system is installed on LVM and is using an LVM volume as the swap disk.



              There is a long-standing, recurring bug where the resume file incorrectly has a UUID (which is invalid for LVM) instead of the device path that it should have.
              See https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230



              You can fix it by editing the /etc/initramfs-tools/conf.d/resume file and replacing the UUID with the device path of the swap drive.
              The following command snippet will do this for you, using the first swap drive found and reported by blkid:



              sudo bash -c 'mv /etc/initramfs-tools/conf.d/resume /tmp/resume.bak; echo RESUME=$(blkid | grep swap | head -n 1 | cut -d : -f 1) > /etc/initramfs-tools/conf.d/resume'




              share








              New contributor




              Nameless Voice is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.

























                0














                I also saw this in Linux Mint (based on Ubuntu), and spent some time working out what was going wrong.



                This happens if your system is installed on LVM and is using an LVM volume as the swap disk.



                There is a long-standing, recurring bug where the resume file incorrectly has a UUID (which is invalid for LVM) instead of the device path that it should have.
                See https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230



                You can fix it by editing the /etc/initramfs-tools/conf.d/resume file and replacing the UUID with the device path of the swap drive.
                The following command snippet will do this for you, using the first swap drive found and reported by blkid:



                sudo bash -c 'mv /etc/initramfs-tools/conf.d/resume /tmp/resume.bak; echo RESUME=$(blkid | grep swap | head -n 1 | cut -d : -f 1) > /etc/initramfs-tools/conf.d/resume'




                share








                New contributor




                Nameless Voice is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.























                  0












                  0








                  0







                  I also saw this in Linux Mint (based on Ubuntu), and spent some time working out what was going wrong.



                  This happens if your system is installed on LVM and is using an LVM volume as the swap disk.



                  There is a long-standing, recurring bug where the resume file incorrectly has a UUID (which is invalid for LVM) instead of the device path that it should have.
                  See https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230



                  You can fix it by editing the /etc/initramfs-tools/conf.d/resume file and replacing the UUID with the device path of the swap drive.
                  The following command snippet will do this for you, using the first swap drive found and reported by blkid:



                  sudo bash -c 'mv /etc/initramfs-tools/conf.d/resume /tmp/resume.bak; echo RESUME=$(blkid | grep swap | head -n 1 | cut -d : -f 1) > /etc/initramfs-tools/conf.d/resume'




                  share








                  New contributor




                  Nameless Voice is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  I also saw this in Linux Mint (based on Ubuntu), and spent some time working out what was going wrong.



                  This happens if your system is installed on LVM and is using an LVM volume as the swap disk.



                  There is a long-standing, recurring bug where the resume file incorrectly has a UUID (which is invalid for LVM) instead of the device path that it should have.
                  See https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230



                  You can fix it by editing the /etc/initramfs-tools/conf.d/resume file and replacing the UUID with the device path of the swap drive.
                  The following command snippet will do this for you, using the first swap drive found and reported by blkid:



                  sudo bash -c 'mv /etc/initramfs-tools/conf.d/resume /tmp/resume.bak; echo RESUME=$(blkid | grep swap | head -n 1 | cut -d : -f 1) > /etc/initramfs-tools/conf.d/resume'





                  share








                  New contributor




                  Nameless Voice is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.








                  share


                  share






                  New contributor




                  Nameless Voice is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 40 secs ago









                  Nameless VoiceNameless Voice

                  101




                  101




                  New contributor




                  Nameless Voice is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Nameless Voice is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Nameless Voice is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      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%2f1013830%2fslow-boot-long-kernel-load-time-due-to-wrong-resume-device%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

                      Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

                      Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

                      Simple Scan not detecting my scanner (Brother DCP-7055W)Brother MFC-L2700DW printer can print, can't...