Advertising

Welcome to SparkyLinux forums
Zapraszamy również na polsko-języczne Forum https://forum.linuxiarze.pl

Errors on boot...

Started by tenfoot, August 28, 2017, 03:30:56 AM

Previous topic - Next topic

tenfoot

Using Sparky v5.0 on a dektop computer with a SDC drive. Until recently, the computer has always booted quickly - less than 15 seconds.

I normally power on the computer every morning and then leave it to boot, while I do other things.

This morning, however, I watched the computer boot and was astonished to see the following appear during boot up

[1.864903] nouveau 0000:01:00:0: bios: 008 1 14492028 14492028
[1.864968] nouveau 0000:01:00:0: bios: 008 1 00f11900 00f11900
[1.865029] nouveau 0000:01:00:0: bios: 008 1 00f11900 00f11900
[1.865086] nouveau 0000:01:00:0: bios: 008 1 00f11900 00f11900
[2.868223] usb 3-2: string descriptor 0 read error: -22
[3.279738] sd 6:0:0:0: [sdc] No Caching mode page found
[3.279819] sd 6:0:0:0: [scd] Assuming drive cache: write through
Gave up waiting for suspend/resume device
Sparky_Linux_V5.: clean, 277428/7290880 files, 126521290/29153280 blocks
[ flashing red light] A start job is running for dev=disk-by\x2uuid-b8afe7cf\x2d9dc5\x2d4dea\x2d89bb\x2d5e1a791a44b/.device (41s / 1min 302)


I assume, rightly or wrongly, that the references after dev-disk refers to uuids.  If so, the fstab file in  /etc.fstab may be relevant

# /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>
UUID=b8afe7cf-9dc5-4dea-89bb-5e1a1791a44b swap           swap    defaults,noatime,discard 0 0
UUID=b50f6274-69a9-4f49-8cdc-32e1ac2ffffd /              ext4    defaults,noatime,discard 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
# Data was on /dev/sdb1 during installation
UUID="70783429-bd9d-467f-ad32-682fd3768c93" media/zed/Data ext4 defaults 0 2
# USB-HDD was on /dev/sdc1 during installation
UUID="6092D5E95F8A15E5" TYPE="ntfs" PARTUUID="0018ad04-01" ntfs


I have tried the command blkid in the terminal with the following result:

zed@zed-pc:~$ blkid
bash: blkid: command not found
zed@zed-pc:~$


I then did some research on the internet and found an alternative option lsblk --fs.  This returned

zed@zed-pc:~$ lsblk --fs
NAME   FSTYPE LABEL            UUID                                 MOUNTPOINT
sda                                                                 
├─sda1 ext4   Linux Mint       96851c6a-3f84-4deb-a97f-2211663a18b6
├─sda2 swap                    8b69da22-b8a5-4b2c-971e-cd1d9cf3f85b
└─sda3 ext4   Sparky Linux v5. b50f6274-69a9-4f49-8cdc-32e1ac2ffffd /
sdb                                                                 
└─sdb1 ext4   Data             70783429-bd9d-467f-ad32-682fd3768c93 /media/zed/Data
sdc                                                                 
└─sdc1 ntfs   USB-HDD          6092D5E95F8A15E5                     /media/zed/USB_HDD
sr0                                                                 
sr1                                                                 
zed@zed-pc:~$


which indicates that the uuids in fstab are correct.

Now for some questions:

(a) has this error occurred as a result of an update/upgrade?

(b) Have I inadvertently done something wrong which causes this error?

(c) If the answer to (b) is "Yes" would someone kindly explain what I did that may have led to the error.

and most improtantly

(d) What can I do to solve the problem and get back to a rapid boot time, please.

Dogs laugh, but they laugh with their tails.

pavroo

Edit the /etc/fstab file as root and change the swap UUID from:
UUID=b8afe7cf-9dc5-4dea-89bb-5e1a1791a44b
to gotten via blkid (as root) or lsblk:
8b69da22-b8a5-4b2c-971e-cd1d9cf3f85b

Then check the file (edit as root in needed):
/etc/initramfs-tools/conf.d/resume
RESUME=UUID=
and make sure the resume uuid is the same as swap's blkid or lsblk say.

Then:
sudo update-initramfs -u -t -k all
sudo update-grub
Nothing is easy as it looks. Danielle Steel
Join #sparkylinux.org at [url="//irc.libera.chat"]irc.libera.chat[/url]

tenfoot

Thank you for your very prompt response.

Quote from: pavroo on August 28, 2017, 01:02:47 PM
Edit the /etc/fstab file as root and change the swap UUID from:
UUID=b8afe7cf-9dc5-4dea-89bb-5e1a1791a44b
to gotten via blkid (as root) or lsblk:
8b69da22-b8a5-4b2c-971e-cd1d9cf3f85b

I don't know how I failed to see that the uuid for swap was different.  Thank you for pointing out the need to change it. I have now done that.

QuoteThen check the file (edit as root in needed):
/etc/initramfs-tools/conf.d/resume
RESUME=UUID=
and make sure the resume uuid is the same as swap's blkid or lsblk say.

The directory /etc/initramfs-tools/conf.d/ is empty.

QuoteThen:
sudo update-initramfs -u -t -k all
sudo update-grub


I would appreciate further guidance, please.

Boot time is now down to 45 seconds!
Dogs laugh, but they laugh with their tails.

Slyvester

#3
Hi everyone,

What is really surprising for me is the configuration of your file : /etc/fstab and more specificalyy the line regarding your "swap" :
UUID=b8afe7cf-9dc5-4dea-89bb-5e1a1791a44b swap           swap    defaults,noatime,discard 0 0

This is what I got : "sudo leafpad //etc/fstab" (new installation of Sparkylinux 5.0 LXQT) :

# /dev/sda1
UUID=43b4d14e-132f-48d0-90f9-31ab93d95ef2 / ext4 relatime,noatime,errors=remount-ro 0 1
# /dev/sda2
UUID=6e45eb1f-aafc-417a-8f77-3c5101b689aa none swap sw 0 0

I'm not too sure that this line is correct, Tenfoot. I could be mistaking, who knows ?. What do you think about it, Pavroo ?



Slyvester

paxmark1

Slyvester
A swap example from Debian stable, lvm
/dev/mapper/raunes--vg-swap_1 none            swap    sw              0       0


"blkid"  needs to be run as root or via sudo. 

Side note - a quick way to see what is slowing down a boot is via "systemd-analyze blame" no need for sudo or root to use systemd-analyze.  Nice little thing, more at man systemd-analyze
Search forum for "More info easier via inxi"    If requested -  no inxi, no help for you by  me.

View the most recent posts on the forum