FWIW, I noticed that delete (DEL) did that on Mint recently.
To directly address the ‘what does this mean’ question -
Well, ok, first answering the timer thing. The first half tells you how much time has passed since the wait started, the 2nd half tells you the
max wait time.
What this (probably) means is that there is a line in your /etc/fstab that references a UUID that isn’t found on the machine.
For a list of UUIDs on the machine, type:
blkid
You should see something like:
oakgatecontrol diskimage # blkid
/dev/sdb1: UUID="9784dc82-83f9-4ed6-8d18-e4f2635b4909" TYPE="ext4"
/dev/sdc1: UUID="60A84E9BA84E7018" TYPE="ntfs"
/dev/sdc5: UUID="0f87cf0e-fb08-4371-8759-096c44ea8b05" TYPE="ext4"
/dev/sdc6: UUID="44ca480b-3824-4191-9005-7f5da9a0cc99" TYPE="swap"
/dev/sdc7: UUID="cb82d09d-10e3-420d-be67-cf80ec00d3ce" TYPE="ext4"
/dev/sda1: UUID="240bde04-44c7-46ba-b868-5006c7ac9c63" TYPE="ext2"
/dev/sdf1: UUID="083459d8-9414-49d6-a7c1-4379194e53d6" TYPE="ext2"
Now, to see what is in the fstab, do ‘egrep UUID /etc/fstab’
You should see something like:
oakgatecontrol diskimage # egrep UUID /etc/fstab
UUID=cb82d09d-10e3-420d-be67-cf80ec00d3ce / ext4 errors=remount-ro 0 1
UUID=44ca480b-3824-4191-9005-7f5da9a0cc99 none swap sw 0 0
UUID=9784dc82-83f9-4ed6-8d18-e4f2635b4909 /mnt/space ext4 errors=remount-ro 0 3
UUID=5c93bc13-a2d0-4da5-98b7-be43d3595924 /HOSTS_BAK ext4 errors=remount-ro 0 2
If you compare the UUID lines above with the UUIDs listed from blkid, you should find one in fstab that isn’t in blkid list.
Look at where it was supposed to be mounted, and maybe that will explain it to you. (e.g. if the UUID is a swap partition, then did you remove the swap? Re-‘mkswap’
it? Maybe you combined 2 partitions? Whatever, hopefully what the fstab thought that UUID is for should point you toward a fix).
Oh, one last thing:
dev-disk-by\x2uuid-377be6ee\x2dc467\x2d44fc\x2de7dad05366fd.device
is referencing UUID 377b6ee-c467-444fc-e7dad05366fd (you have to convert the \x2d into the ‘-‘ that is in the UUID itself), so look for that in your FSTAB.
Or, you can just do ‘grep -i 377b6ee-c467-444fc-e7dad05366fd /etc/* 2> /dev/null’ and see all references to that UUID in /etc (warning - this is the sledgehammer approach! If you look at fstab, that should be the place this UUID shows
up, but if not, use the sledgehammer. IF the sledgehammer doesn’t work, use the jackhammer: ‘find /etc -type f -print0 | xargs -0 grep -i 377b6ee-c467-444fc-e7dad05366fd’ (or maybe that last one is a nuke, don’t know for sure
J)
Rusty
From: PLUG-discuss [mailto:plug-discuss-bounces@lists.phxlinux.org]
On Behalf Of Bob Elzer
Sent: Wednesday, September 05, 2018 6:56 AM
To: Main PLUG discussion list
Subject: Re: What does this mean?
Not sure if this works for kubuntu, but when the system is booting you can hit the esc key and it should show the all the boot messages.
On Wed, Sep 5, 2018, 12:20 AM Jim <jim.nantz15@comcast.net> wrote:
Whenever I boot the computer into Kubuntu 18, it takes a couple of
minutes to boot. For a while the screen is blank. Finally I'm able to
see what it's doing as it boots, and I find this.
a start job is running for
dev-disk-by\x2uuid-377be6ee\x2dc467\x2d44fc\x2de7dad05366fd.device
Then in parenthesis there is a timer like this (1min 9s / 1min 30s) The
number before the slash counts up to 1min 30s then the system continues
booting like it should.
Any idea what this is or how to fix it?
thanks
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss