Page 1 of 1

boot delay 90 secs dev-disk-by

Posted: 07 Aug 2019 11:04
by sxphild
This just started to happen..

I am running SolydX 201701 on a Dell 1525.

Boot time increased significantly. I examined boot.log
and found this line:

"A start job is running for dev-disk-by/[ long number] "
It ran for exactly 1min: 30 secs.

Online search found it had something to do with my swap partition.
Pulled up GParted, deleted the swap partition, and recreated it.
[didn't solve it]

So I commented out the line in fstab which contained the swap partition.
That worked....but now I have no swap partition.

Is there a better solution? The laptop has 4G RAM, so I haven't run into
any issues.

Thanks,

sxphild

Re: boot delay 90 secs dev-disk-by

Posted: 07 Aug 2019 11:34
by Arjen Balfoort
How big was the swap file?
Do you use swap for hibernation?

When you have the swap file configured, did you run:

Code: Select all

systemd-analyze critical-chain
Also check /var/log/boot.log
Right after the line "A start job is running for..."

Does the swap UUID in fstab matchth the output of

Code: Select all

sudo blkid

Re: boot delay 90 secs dev-disk-by

Posted: 07 Aug 2019 13:39
by kurotsugi
when you recreate the swap partition, you also change the uuid. find the new uuid using schoelje's instruction above then replace the uuid in fstab :3

Re: boot delay 90 secs dev-disk-by

Posted: 07 Aug 2019 16:34
by sxphild
To Arjen,

Size of Swap = 4G ( same as RAM size).

Since I have commented out the swap entry in boot.log, I
don't get a useful answer to running sysctrl, etc. and boot.log..

Later today I'll put it back and report to you.

But, from my recollection, the UUID was the same
even after reassiginng the swap partition. It also matched the
entry in boot.log...of course, it's a long number, so I could be wrong..

But we'll see..
Thank you both,

Phil

Re: boot delay 90 secs dev-disk-by

Posted: 07 Aug 2019 16:43
by sxphild
I just looked in three places for the UUID of the swap..

from fstab ( line I commented out ]
UUID=fab17f5c-432c-4d11-be06-ef3a24252c56 swap swap sw 0 0

from GParted:
UUID=01cdc06d-7095-4c23-b486-128630c1f8f2

from running "blkid":
UUID="01cdc06d-7095-4c23-b486-128630c1f8f2" TYPE="swap" PARTUUID="a57f48e4-01"

2 of them match...I am deleting the line in fstab, and rebooting..

Re: boot delay 90 secs dev-disk-by

Posted: 07 Aug 2019 16:58
by sxphild
OK.

Rebooting was fast ( as it was in the past).

ran blkid, and got the UUID of the swap.
copied as pasted it into fstab.
Rebooted - same fast boot.

Still not certain i have a mounted swap...

BTW, I don't ever use it for hibernation,
In fact no app I have run has probably ever come close to
using it...but again I have no wasy to gauge this except by
checking Task Manager once in awhile,,,

But all seems well now..

Phil

Re: boot delay 90 secs dev-disk-by

Posted: 07 Aug 2019 17:17
by SilverBear
Something similar has happened to me many times. I usually have between three and six distros installed on the same SSD, sharing the same swap (on a different HHD). And every time I install a new distro, that installer usually reformats the swap partition with a different UUID.

So what I usually do is to edit each OS's /etc/fstab so that the swap line reads:

Code: Select all

/dev/sdb8	swap	swap	sw	0	0
... instead of whatever UUID the installer renamed it.

Remember that the /etc/fstab can mount a partition by UUID, or by /dev/sd*, or by label, like so:

Code: Select all

LABEL=DATA_01          /mnt/DATA_01        ext4      auto,users,exec,relatime     1 2
Sometimes UUIDs are not the best option.

Re: boot delay 90 secs dev-disk-by

Posted: 07 Aug 2019 19:42
by sxphild
Silverbear,

Interesting. I just installed solydx 9 on a spare partition. But my fstab shows only the currently booted O/S i.e. solydx 8, not the other two( the remaining one is puppy linux).
The only other entry is the swap.

Can I just add the other partitions? E.g. dev/sda2 dev/sda3..

Re: boot delay 90 secs dev-disk-by

Posted: 09 Aug 2019 00:17
by ilu
fstab should only hold partitions used by the OS you are currently booting into (and data partitions of course, if you have any). Partitions belonging to another OS should not be mounted in fstab. What silverbear said only applies to the swap partition.

Or maybe I misunderstood your question?

Re: boot delay 90 secs dev-disk-by

Posted: 09 Aug 2019 01:15
by sxphild
Ilu,

You are right. My fstab shows only solydx and the swap partition. Thx for the clarification.

I have a lot yet to learn about Linux..luckily I like to learn, and these issues provide a way to do that!

Re: boot delay 90 secs dev-disk-by

Posted: 09 Aug 2019 02:05
by kurotsugi
you can safely mount a shared partition between two OS. I think it's a common practice on multi boot system. though, on linux, keep on mind to mount the shared partition somewhere safe, preferably under /media. else, you can manually mount the shared partition based on demand

Re: boot delay 90 secs dev-disk-by

Posted: 09 Aug 2019 06:38
by ilu
kurotsugi: This thread is about system partitions not about data partitions. Of course you can mount any partition you want anywhere you want. But somebody who is just starting with Linux should not do that - with system partitions! - because it's too easy to mess things up. The only shared system partition should be swap.

sxphild: the terminal command free should tell you whether swap is working. Or sudo swapon --show.

Re: boot delay 90 secs dev-disk-by

Posted: 09 Aug 2019 09:22
by kurotsugi
no worries. OP didn't mention anywhere specifically about system partition. he simply asked whether if it possible to mount other partitions. you even aksed whether if you understand him correctly. no harms is done

Re: boot delay 90 secs dev-disk-by

Posted: 09 Aug 2019 11:02
by sxphild
The idea to sub /dev/sda1 ( my swap partition) for the UUID
hit home this morning. I booted up the new
install of solydX 201902, and again got the 90 sec delay-
It as looking for the UUID the O/S had set when it installed, but
couldn't find it.

So, I edited both fstab files ( old version and new version's)
to read /dev/sda1...works a lot better that way.

Thanks to all who contributed..

Phil