[SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

hughparker1 · 2016-07-08 11:03:17

DELL Vostro 1520
CPU: Intel Mobile Core 2 Duo T6670 @ 2.20GHz Penryn 45nm Technology
Graphics: Intel Mobile Intel 4 Series Express Chipset Family (Dell)
RAM: 4.00GB Dual-Channel DDR2 @ 398MHz (6-6-6-18)
Storage: 223GB Crucial_CT240M500SSD1 ATA Device (SSD)

I noticed my boot time for BunsenLabs is now 90 seconds while before it was only 10 seconds.

I always get boot message...

[  **] A start job is running for dev-disk-by\x2duuid

This always lasts for 90 seconds.

I ran command "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/sda9 during installation
UUID=82741faf-8d66-4542-929a-ff2f3a9f33c9 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda8 during installation
UUID=cdfd1708-0cee-4d0e-b3ec-4350a24986a2 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
hugh@DELL-VOSTRO-BUNSENLABS:/etc$

I notice that "fstab" states "/ was on /dev/sda9 during installation" which is correct because I noticed that partition numbers were changed during a recent Debian Stretch installation (I have a multi-boot setup) "/" is now on /dev/sda7

"fstab" also states "# swap was on /dev/sda8 during installation" again this was changed during Debian installation. "swap" is now on /dev/sda6

Is this change in partition numbers the reason for this boot delay?

Also "UUID=82741faf-8d66-4542-929a-ff2f3a9f33c9" is the correct UUID partition for BunsenLabs.

I had a look online for a solution but couldn't see anything that fits my situation. I'm still learning linux but can use terminal if I know correct syntax.

Is there any way I can fix this without re-installing BunsenLabs?

Last edited by hughparker1 (2016-07-08 14:39:59)

damo · 2016-07-08 11:10:10

This situation occurs if you have recently installed to another partition, so the UUID for swap has been changed. Get the new UUID for swap with

sudo blkid

Edit your fstab with the new value.

apacus11 · 2016-07-08 12:14:13

I use LABELS instead of UUID so new distros don't bork my fstab.
Just change the UUID=... for /dev/sda*

hughparker1 · 2016-07-08 12:52:42

damo wrote:

This situation occurs if you have recently installed to another partition, so the UUID for swap has been changed. Get the new UUID for swap with
sudo blkid
Edit your fstab with the new value.

thanks damo for reply. I ran command "sudo blkid" and I can see the swap partition sda6 is correct and also the UUID is shown....

/dev/sda6: UUID="9d78e76a-d938-4209-ab58-dea421fcc8cb" TYPE="swap" PARTUUID="80ce69fb-06"

... but this is the same value that is already in my fstab "9d78e76a-d938-4209-ab58-dea421fcc8cb" see fstab below...

hugh@DELL-VOSTRO-DEBIAN:/etc$ cat 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/sda11 during installation
UUID=aa528ef6-1be9-440f-9d6b-a8bc9468c26e /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda7 during installation
UUID=9d78e76a-d938-4209-ab58-dea421fcc8cb none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/sda3 /media/NTFS ntfs defaults,umask=007,gid=46 0 0
hugh@DELL-VOSTRO-DEBIAN:/etc$

Am I missing something, not sure what I should do now, or what part of fstab I should edit.

Last edited by hughparker1 (2016-07-08 13:00:27)

damo · 2016-07-08 13:03:31

Which installation is handling the boot process? Each fstab swap UUID should be the same.

The two fstabs you have posted are different. One has

# swap was on /dev/sda8 during installation
UUID=cdfd1708-0cee-4d0e-b3ec-4350a24986a

The other has

# swap was on /dev/sda7 during installation
UUID=9d78e76a-d938-4209-ab58-dea421fcc8cb

hughparker1 · 2016-07-08 13:55:22

damo wrote:

Which installation is handling the boot process? Each fstab swap UUID should be the same.

Linux Lite is in charge of boot process

damo wrote:

The two fstabs you have posted are different. One has

# swap was on /dev/sda8 during installation
UUID=cdfd1708-0cee-4d0e-b3ec-4350a24986a

The other has

# swap was on /dev/sda7 during installation
UUID=9d78e76a-d938-4209-ab58-dea421fcc8cb

You are right, sorry about that.

here is the correct output run from BunsenLabs...

hugh@DELL-VOSTRO-BUNSENLABS:~$ 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/sda9 during installation
UUID=82741faf-8d66-4542-929a-ff2f3a9f33c9 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sda8 during installation
UUID=cdfd1708-0cee-4d0e-b3ec-4350a24986a2 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
hugh@DELL-VOSTRO-BUNSENLABS:~$


hugh@DELL-VOSTRO-BUNSENLABS:~$ sudo blkid
[sudo] password for hugh: 
/dev/sda1: LABEL="System Reserved" UUID="52F2484EF248390D" TYPE="ntfs" PARTUUID="80ce69fb-01"
/dev/sda2: UUID="70DA4B9CDA4B5D8A" TYPE="ntfs" PARTUUID="80ce69fb-02"
/dev/sda3: LABEL="NTFS" UUID="18306502711B6C00" TYPE="ntfs" PARTUUID="80ce69fb-03"
/dev/sda5: LABEL="MINT" UUID="e2b6f5f1-97dc-458c-9263-69e8581cf8e2" TYPE="ext4" PARTUUID="80ce69fb-05"
/dev/sda6: UUID="9d78e76a-d938-4209-ab58-dea421fcc8cb" TYPE="swap" PARTUUID="80ce69fb-06"
/dev/sda7: LABEL="BUNSENLABS" UUID="82741faf-8d66-4542-929a-ff2f3a9f33c9" TYPE="ext4" PARTUUID="80ce69fb-07"
/dev/sda8: LABEL="LINUX-LITE" UUID="407668e2-31a5-4a4b-b9b6-4b798b0324b0" TYPE="ext4" PTTYPE="dos" PARTUUID="80ce69fb-08"
/dev/sda9: LABEL="XUBUNTU" UUID="3df43af2-8a74-411c-af98-0f4528729f89" TYPE="ext4" PARTUUID="80ce69fb-09"
/dev/sda10: LABEL="DEBIAN" UUID="aa528ef6-1be9-440f-9d6b-a8bc9468c26e" TYPE="ext4" PARTUUID="80ce69fb-0a"
/dev/sda11: LABEL="CHALETOS" UUID="d26dc2fd-3517-4136-a7ca-3afa12d50d5a" TYPE="ext4" PTTYPE="dos" PARTUUID="80ce69fb-0b"
hugh@DELL-VOSTRO-BUNSENLABS:~$

/dev/sda6 is now swap partition
should I just need to change swap UUID value in fstab to UUID="9d78e76a-d938-4209-ab58-dea421fcc8cb"

So changing from...

# swap was on /dev/sda8 during installation
UUID=cdfd1708-0cee-4d0e-b3ec-4350a24986a2 none            swap    sw              0       0

changing to ....

# swap was on /dev/sda8 during installation
UUID=9d78e76a-d938-4209-ab58-dea421fcc8cb none            swap    sw              0       0

I guess I will need to do this for the other two operating systems that are also slow to boot?

Thanks very much for your help and patience.

damo · 2016-07-08 14:00:25

damo wrote:

... Each fstab swap UUID should be the same...

hughparker1 · 2016-07-08 14:39:23

damo wrote:

damo wrote:
... Each fstab swap UUID should be the same...

that's it sorted now.

BunsenLabs now boots in 10 seconds

Xubuntu and Linux Mint 18 Mate now both boot in 15 seconds

Not bad for a 6 year old laptop fitted with SSD last year.

thanks for all your help and patience. I am learning a bit more every day with your advice and guidance.

damo · 2016-07-08 14:48:27

NP

Head_on_a_Stick · 2016-07-08 20:06:19

If the hard drive uses a GUID partition table rather than MBR-style then the swap lines in /etc/fstab can be deleted as systemd will mount the swap partition automatically.

#1 2016-07-08 11:03:17

[SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

#2 2016-07-08 11:10:10

Re: [SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

#3 2016-07-08 12:14:13

Re: [SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

#4 2016-07-08 12:52:42

Re: [SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

#5 2016-07-08 13:03:31

Re: [SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

#6 2016-07-08 13:55:22

Re: [SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

#7 2016-07-08 14:00:25

Re: [SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

#8 2016-07-08 14:39:23

Re: [SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

#9 2016-07-08 14:48:27

Re: [SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

#10 2016-07-08 20:06:19

Re: [SOLVED] [ **] A start job is running for dev-disk-by\x2duuid

Board footer