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

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
20
down vote

favorite
5












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



















  • 4




    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 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 at 14:37















up vote
20
down vote

favorite
5












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



















  • 4




    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 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 at 14:37













up vote
20
down vote

favorite
5









up vote
20
down vote

favorite
5






5





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 at 9:04

























asked Mar 11 at 8:42









alci

2,76043052




2,76043052







  • 4




    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 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 at 14:37













  • 4




    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 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 at 14:37








4




4




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 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 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 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 at 14:37











1 Answer
1






active

oldest

votes

















up vote
25
down vote



accepted










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 at 13:24







  • 1




    Brilliant! Thanks for the fix. It had me pulling my hair out!
    – Murray
    May 24 at 23:58










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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
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






























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
25
down vote



accepted










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 at 13:24







  • 1




    Brilliant! Thanks for the fix. It had me pulling my hair out!
    – Murray
    May 24 at 23:58














up vote
25
down vote



accepted










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 at 13:24







  • 1




    Brilliant! Thanks for the fix. It had me pulling my hair out!
    – Murray
    May 24 at 23:58












up vote
25
down vote



accepted







up vote
25
down vote



accepted






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 Apr 20 at 10:17









David Foerster

26.4k1362106




26.4k1362106










answered Mar 11 at 17:36









alci

2,76043052




2,76043052







  • 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 at 13:24







  • 1




    Brilliant! Thanks for the fix. It had me pulling my hair out!
    – Murray
    May 24 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 at 13:24







  • 1




    Brilliant! Thanks for the fix. It had me pulling my hair out!
    – Murray
    May 24 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 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 at 13:24





1




1




Brilliant! Thanks for the fix. It had me pulling my hair out!
– Murray
May 24 at 23:58




Brilliant! Thanks for the fix. It had me pulling my hair out!
– Murray
May 24 at 23:58

















 

draft saved


draft discarded















































 


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













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491