Messed up /etc/fstab???

[Modaljazz2018]

I am curious as to the accuracy of my /etc/fstab file. Suffering from a very slow boot. I thought maybe there could be a problem in this file. I don't understand most of this file....I see references to "sdb1 and sdb2". I remember when installing I put boot file in a small folder called "EFI".....

# /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/sdb2 during installation
UUID=1c36722b-fbf2-41d7-9b1f-8dfce00da9df / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sdb1 during installation
UUID=8DB2-3238 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0

[all41]

Suffering from a very slow boot

fstab errors can do this
please post the results of terminal inquiry:

Code: Select all

sudo blkid

[Modaljazz2018]

Here is result of issuing BLKID:

/dev/sda1: UUID="684F-B00B" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="50ebcb49-1aeb-416a-8d03-8ef96e2deb08"

/dev/sda3: LABEL="Windows" UUID="CE5AE4C75AE4AD81" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c143f964-ac70-4cc2-
badc-96c43fee35f0"

/dev/sda4: LABEL="Windows RE tools" UUID="7286A7B286A774EF" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="1b6169e6-41e5-452d-b07d-140a4212fd35"

/dev/sdb1: LABEL="DATA" UUID="AEBA5942BA59086B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="15897af4-669c-4ac7-864f-5cd4c69a85b0"

/dev/sdb2: LABEL="RECOVERY" UUID="8A0A5A840A5A6D67" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="7b44944a-3712-48b7-8650-65f5cbf293ab"

/dev/sdc1: UUID="8DB2-3238" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="9c785375-4e2e-48e6-bb6d-cf91a7cbdc77"

/dev/sdc2: UUID="1c36722b-fbf2-41d7-9b1f-8dfce00da9df" TYPE="ext4" PARTUUID="be65f8c3-8f5a-4f84-a0c6-c369cf9c1f04"

/dev/sdd1: UUID="c8ee27f1-5ab4-43a2-a087-1668446e2bd0" TYPE="ext2" PARTUUID="bc050d09-01"

/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="22aa0e16-d2d6-435a-9d9e-23b853fa21e0"

[trytip]

open disks and compare your UUID with your fstab . are they the same

[sgtor]

I am curious as to the accuracy of my /etc/fstab file. Suffering from a very slow boot. I thought maybe there could be a problem in this file. I don't understand most of this file....I see references to "sdb1 and sdb2". I remember when installing I put boot file in a small folder called "EFI".....

# /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/sdb2 during installation
UUID=1c36722b-fbf2-41d7-9b1f-8dfce00da9df / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sdb1 during installation
UUID=8DB2-3238 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0

Your settings are different in fstab. This is from your post of blkid.
/dev/sdc2: UUID="1c36722b-fbf2-41d7-9b1f-8dfce00da9df" TYPE="ext4" PARTUUID="be65f8c3-8f5a-4f84-a0c6-c369cf9c1f04"

/dev/sdc1: UUID="8DB2-3238" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="9c785375-4e2e-48e6-bb6d-cf91a7cbdc77"

I'm old school and I prefer to just use /dev/sdxx in my fstab file.

BTW you can also run this to see your boot details.

Code: Select all

systemd-analyze blame

[ricardogroetaers]

I am curious as to the accuracy of my /etc/fstab file. Suffering from a very slow boot. I thought maybe there could be a problem in this file. I don't understand most of this file....I see references to "sdb1 and sdb2". I remember when installing I put boot file in a small folder called "EFI".....

Your fstab is simple and correct. Comparing and commenting:

fstab:
# / was on /dev/sdb2 during installation
UUID=1c36722b-fbf2-41d7-9b1f-8dfce00da9df / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sdb1 during installation
UUID=8DB2-3238 /boot/efi vfat umask=0077 0 1

Output of the blkid command:
/dev/sdc2: UUID="1c36722b-fbf2-41d7-9b1f-8dfce00da9df" TYPE="ext4" ..........."
/dev/sdc1: UUID="8DB2-3238" TYPE="vfat" PARTLABEL="EFI System Partition" ......."

Notice how the device special file type "sdxn" changed after installation.
Was sdb2 and turned sdc2.
Was sdb1 and turned sdc1.

However the UUID of the file system is always the same.

The designation of a file system to be mounted by the special device file (sdxn) that represents should be avoided. This can lead to a different file system on the mount point that was established.
If we use the UUID, the file system is always mounted on the mount point that was established. No matter which port the device is or has been connected or if other devices are subsequently installed.

Note that in your fstab file systems root (/) and boot (/boot/efi) are checked for integrity when booting.
Note the number 1 in the last column in the fstab.
Depending on the size of the root partition and the amount of folders and files that may take a while.
For security reasons it is not recommended to disable this check.

Other reasons different from fstab must be considered. Resident programs loaded and initialized at startup, desktop composition and others.

[Modaljazz2018]

OK I issued "system-analyze -critical-chain" and found somethings in there that look like they are taking excessive time.....here is output:

The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @1min 9.927s
└─lightdm.service @1min 9.362s +564ms
└─systemd-user-sessions.service @1min 9.333s +27ms
└─network.target @1min 9.331s
└─wpa_supplicant.service @3.742s +1min 5.589s
└─dbus.service @3.483s
└─basic.target @3.350s
└─paths.target @3.350s
└─acpid.path @3.350s
└─sysinit.target @3.212s
└─apparmor.service @2.684s +527ms
└─local-fs.target @2.677s
└─run-user-1000-gvfs.mount @1min 16.141s
└─run-user-1000.mount @1min 12.146s
└─swap.target @2.495s
└─dev-disk-by\x2duuid-eaeb402c\x2d9b20\x2d4e19\x2da725\x2d918d63f5ea54.swap @2.470s +25ms
└─dev-disk-by\x2duuid-eaeb402c\x2d9b20\x2d4e19\x2da725\x2d918d63f5ea54.device @2.469s

I dont know what all this is but can some of these be disabled?