LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Bodhi
User Name
Password
Bodhi This forum is for the discussion of Bodhi Linux.

Notices


Reply
  Search this Thread
Old 04-10-2019, 04:57 AM   #1
zaivala
Member
 
Registered: Mar 2008
Location: Blaine TN USA
Distribution: ferenOS 2017.04, SolusOS, geckolinux
Posts: 175
Blog Entries: 12

Rep: Reputation: 30
Bootup 90-second delay


I am experiencing a boot slowdown in my bootup of Bodhi 5.0.0. I see the following message:

A start job is running for dev-disk-by/x2duuid-ib0bf28/x2e40e7/x2e9bad/x2e5cc3rr411e862.device (1s / 1min 30sec)

I counts down exactly 90 seconds before continuing.

Why is there a 90-second countdown for something I don't recognize?

I have tried to type the message correctly but may have typoed somewhere.
 
Old 04-10-2019, 07:10 AM   #2
RonCam
Member
 
Registered: Dec 2008
Posts: 111

Rep: Reputation: 47
Exclamation

Quote:
Originally Posted by zaivala View Post
... Why is there a 90-second countdown for something I don't recognize?
A search doesn't bring up the Bodhi-specific answer you most likely want, so I hope there will be more replies from our forum experts ... but while you are waiting for them to 'chime in' you may want to look here and see if any of what you will read fits your case. What you will read goes beyond the 'why' of your question and suggests a variety of fixes that have worked for others, for both Debian-related and non-Debian GNU-Linux operating systems.

Note, the fourth down from the top in the search results does mention a 'slow boot', and that one is Ubuntu-related. With DDG, your search results should be the same as what I just saw.
 
1 members found this post helpful.
Old 04-10-2019, 07:43 AM   #3
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 21,286

Rep: Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527
Quote:
Originally Posted by zaivala View Post
I am experiencing a boot slowdown in my bootup of Bodhi 5.0.0. I see the following message:

A start job is running for dev-disk-by/x2duuid-ib0bf28/x2e40e7/x2e9bad/x2e5cc3rr411e862.device (1s / 1min 30sec)

I counts down exactly 90 seconds before continuing. Why is there a 90-second countdown for something I don't recognize? I have tried to type the message correctly but may have typoed somewhere.
By any chance, have you formatted/used an encrypted USB/removable device?? If so, there may be an entry in /etc/crypttab, which is now waiting for that device to come online...which it won't, since its been removed. You can safely remove that offending line from that file...but if there are others, do NOT touch them, unless you know what you're doing.

You can also look in your /etc/fstab file for that line; if found, copy that file to another location, and then only remove that one line. And be sure to have a bootable media nearby, in case of problems.
 
1 members found this post helpful.
Old 04-10-2019, 08:19 AM   #4
sevendogsbsd
Member
 
Registered: Sep 2017
Distribution: FreeBSD
Posts: 768

Rep: Reputation: Disabled
This is systemd doing something with the disk referenced. You can look in the logs (journalctl) to see if they provide more detail. Some folks get messages like this on shutdown as well: 90 seconds seems to be the wait time used by systemd in general when something doesn't happen immediately.
 
1 members found this post helpful.
Old 04-10-2019, 09:40 AM   #5
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.0
Posts: 247

Rep: Reputation: 47
similarly to journalctl dmesg can show system log entries. i mention that because my journalctl list goes on over 1000 lines. with dmesg you can add a level option (maybe journalctl as well. i'm just not as familiar with it) to see a bit less info that may prove to be helpful with
Code:
dmesg --level=err
(usually a shorter list for me) or
Code:
dmesg --level=warn
 
Old 04-10-2019, 09:46 AM   #6
sevendogsbsd
Member
 
Registered: Sep 2017
Distribution: FreeBSD
Posts: 768

Rep: Reputation: Disabled
You can get journalctl to show entries in reverse order (newest at top) but I can't remember how: "b" switch maybe.
 
1 members found this post helpful.
Old 04-10-2019, 09:54 AM   #7
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.0
Posts: 247

Rep: Reputation: 47
also a good idea. looks like -r --reverse shows newest entries (from the man page), -f --follow shows most recent entries and

Quote:
-n, --lines=
Show the most recent journal events and limit the number of events
shown. If --follow is used, this option is implied. The argument is
a positive integer or "all" to disable line limiting. The default
value is 10 if no argument is given.

Last edited by cordx; 04-10-2019 at 09:55 AM. Reason: clarity
 
Old 04-10-2019, 06:17 PM   #8
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 17,691

Rep: Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796
Generally this is because you have an entry in fstab with this UUID that is no longer valis - swap is usually the best bet, especially if you have re-installed. Also look at your boot options - notably the "resume=...".
 
1 members found this post helpful.
Old 04-11-2019, 12:50 AM   #9
zaivala
Member
 
Registered: Mar 2008
Location: Blaine TN USA
Distribution: ferenOS 2017.04, SolusOS, geckolinux
Posts: 175

Original Poster
Blog Entries: 12

Rep: Reputation: 30
Quote:
Originally Posted by TB0ne View Post
By any chance, have you formatted/used an encrypted USB/removable device?? If so, there may be an entry in /etc/crypttab, which is now waiting for that device to come online...which it won't, since its been removed. You can safely remove that offending line from that file...but if there are others, do NOT touch them, unless you know what you're doing.

You can also look in your /etc/fstab file for that line; if found, copy that file to another location, and then only remove that one line. And be sure to have a bootable media nearby, in case of problems.
Nope. Don't even know how to do that.
 
Old 04-11-2019, 12:55 AM   #10
zaivala
Member
 
Registered: Mar 2008
Location: Blaine TN USA
Distribution: ferenOS 2017.04, SolusOS, geckolinux
Posts: 175

Original Poster
Blog Entries: 12

Rep: Reputation: 30
Quote:
Originally Posted by RonCam View Post
A search doesn't bring up the Bodhi-specific answer you most likely want, so I hope there will be more replies from our forum experts ... but while you are waiting for them to 'chime in' you may want to look here and see if any of what you will read fits your case. What you will read goes beyond the 'why' of your question and suggests a variety of fixes that have worked for others, for both Debian-related and non-Debian GNU-Linux operating systems.

Note, the fourth down from the top in the search results does mention a 'slow boot', and that one is Ubuntu-related. With DDG, your search results should be the same as what I just saw.
The most promising comment I saw was that systemd can't find the /data location; the is to remove /data from fstab ... and I'm too stupid to know how to do that.
 
Old 04-11-2019, 01:17 AM   #11
zaivala
Member
 
Registered: Mar 2008
Location: Blaine TN USA
Distribution: ferenOS 2017.04, SolusOS, geckolinux
Posts: 175

Original Poster
Blog Entries: 12

Rep: Reputation: 30
A couple of those articles said to use Ctrl-C to stop the process on a one-time basis. I'm here to say it doesn't work.
 
Old 04-11-2019, 01:39 AM   #12
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 17,691

Rep: Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796Reputation: 2796
Fire up a terminal, run these and post the output - all of it.
Code:
journalctl -b 0 | grep -i uuid
cat /etc/fstab
 
2 members found this post helpful.
Old 04-11-2019, 04:55 AM   #13
RonCam
Member
 
Registered: Dec 2008
Posts: 111

Rep: Reputation: 47
Quote:
Originally Posted by zaivala View Post
The most promising comment I saw was that systemd can't find the /data location; the is to remove /data from fstab ... and I'm too stupid to know how to do that.
No, you are not stupid!! I can guarantee, no one on this forum was born knowing how to edit fstab. Look at this!

First step, backup fstab to something like fstab.old. After the renaming, the operating system will ignore it, but you can always reactivate it by bringing back the original name.

With the fstab file open in a text editor, instead of deleting lines straight-away, do this:
# The following line was inactivated on (date)
# The line you want to delete is here.

Then save.
Any line beginning with #[space] becomes a comment line, and so is ignored with the OS reads the file. After some time has passed and all is well, you can always come back to 'tidy up' the entries by really deleting them.
 
2 members found this post helpful.
Old 04-11-2019, 07:10 AM   #14
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 21,286

Rep: Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527Reputation: 5527
Quote:
Originally Posted by zaivala View Post
Quote:
Originally Posted by TB0ne
By any chance, have you formatted/used an encrypted USB/removable device?? If so, there may be an entry in /etc/crypttab, which is now waiting for that device to come online...which it won't, since its been removed. You can safely remove that offending line from that file...but if there are others, do NOT touch them, unless you know what you're doing.

You can also look in your /etc/fstab file for that line; if found, copy that file to another location, and then only remove that one line. And be sure to have a bootable media nearby, in case of problems.
Nope. Don't even know how to do that.
So instead of asking how, you don't even consider it? Those are just two, plain-text files...nothing special. You can just type:
Code:
cat /etc/crypttab  
or
cat /etc/fstab
...and there they are. Look for a matching line in either...if you find one, type in "sudo vi /etc/<whatever file has the line". Arrow down to that line. Press ":dd" to remove it. Press ":wq" to save and exit. Done.

Before changing either, copy those file somewhere else. Use the cp command to do that: "sudo cp /etc/fstab /etc/old-fstab" is a good example.

Last edited by TB0ne; 04-11-2019 at 07:11 AM.
 
1 members found this post helpful.
Old 04-17-2019, 04:56 AM   #15
zaivala
Member
 
Registered: Mar 2008
Location: Blaine TN USA
Distribution: ferenOS 2017.04, SolusOS, geckolinux
Posts: 175

Original Poster
Blog Entries: 12

Rep: Reputation: 30
[email protected]:~$ journalctl -b 0 | grep -i uuid
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start timed out.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: Dependency failed for /dev/disk/by-uuid/1b0b9f28-4745-40e7-9bad-5cc3ff41e862.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap/start failed with result 'dependency'.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start failed with result 'timeout'.
Apr 17 05:32:48 zaivala-ThinkPad-T430 systemd[1]: Listening on UUID daemon activation socket.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start timed out.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: Dependency failed for /dev/disk/by-uuid/1b0b9f28-4745-40e7-9bad-5cc3ff41e862.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap/start failed with result 'dependency'.
Apr 17 05:34:18 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start failed with result 'timeout'.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start timed out.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: Dependency failed for /dev/disk/by-uuid/1b0b9f28-4745-40e7-9bad-5cc3ff41e862.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap/start failed with result 'dependency'.
Apr 17 05:38:22 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start failed with result 'timeout'.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start timed out.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: Dependency failed for /dev/disk/by-uuid/1b0b9f28-4745-40e7-9bad-5cc3ff41e862.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.swap/start failed with result 'dependency'.
Apr 17 05:48:56 zaivala-ThinkPad-T430 systemd[1]: dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device: Job dev-disk-by\x2duuid-1b0b9f28\x2d4745\x2d40e7\x2d9bad\x2d5cc3ff41e862.device/start failed with result 'timeout'.
[email protected]:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda4 during installation
UUID=f243d2a0-bbfc-4917-a06d-04fc714a5d3d / ext4 errors=remount-ro 0 1
# swap was on /dev/sda1 during installation
UUID=1b0b9f28-4745-40e7-9bad-5cc3ff41e862 none swap sw 0 0
[email protected]:~$
 
  


Reply

Tags
bodhi, boot


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Bootup delay at /etc/rc.d/rc.udev dive Slackware 3 11-16-2007 01:25 PM
how to shorten the delay of hard disk initialization in bootup linux_hy Fedora 1 04-24-2007 11:56 PM
gnome fails to load on login after bootup - unless bootup first in win xp doubletruncation Fedora 6 12-07-2005 08:32 AM
fsck delay reported bootup time? rmang Linux - General 2 10-30-2005 05:29 PM
How to convert a bootup floppy to a bootup CD ? wlaw Linux - Newbie 2 07-15-2004 03:28 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Bodhi

All times are GMT -5. The time now is 05:34 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration