Boot From NVME Fails Because systemd-fsck-service Start Fails on Timeout on Partition

English Install/Boot/Login
1

OK, so I installed an Adata NVME PCIe SSD, specifically XPG SX8200 Pro 512GB 3D NAND NVMe. I installed LEAP 15.1 on it with root and home and efi-boot and swap all on the drive with around 424GB left over which I intend to use for storing my VirtualBox virtual machines. I did not create that partition or fomat it until today. I’ve been booting and using the system for the past week or so.

Everything has been fine until I created the additional partition for the remaining portion of the drive which is intended for the virtual machines. I installed a logical partition inside the extended partition (which also holds my home partition) using Gparted from the Gparted live CD. The partition is formatted as ext4. The file system label is Data6.

lsblk shows:

lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0   3.7T  0 disk
└─sda1        8:1    0   3.7T  0 part /Data2
sdb           8:16   0   3.7T  0 disk
└─sdb1        8:17   0   3.7T  0 part /Data5
sdc           8:32   0   3.7T  0 disk
├─sdc4        8:36   0    10G  0 part /OldHome
├─sdc5        8:37   0   1.8T  0 part /Data1
└─sdc6        8:38   0   1.8T  0 part /Data4
sdd           8:48   0   1.8T  0 disk
└─sdd1        8:49   0   1.8T  0 part /Data3
sr0          11:0    1  1024M  0 rom  
nvme0n1     259:0    0   477G  0 disk
├─nvme0n1p1 259:1    0     1K  0 part
├─nvme0n1p2 259:2    0   500M  0 part /boot/efi
├─nvme0n1p3 259:3    0     4G  0 part [SWAP]
├─nvme0n1p4 259:4    0    35G  0 part /
├─nvme0n1p5 259:5    0    15G  0 part /home
└─nvme0n1p6 259:6    0 409.2G  0 part /Data6

I created a mount point for it under / called Data6. I edited the /etc/fstab to put the new partition in with the exact same options as all my hard drive partitions, i.e., as you see here:

rhack@linux-h2ol:~> cat /etc/fstab
UUID=9c8dce57-1c43-4436-86dd-06b70db462e2  swap       swap  defaults                     0  0
UUID=7df10d3e-99cf-4d67-8c19-b319d26e9d96  /          ext4  acl,user_xattr               0  1
UUID=c3c2b83e-5d88-4da0-8abb-d97d61ea3333  /home      ext4  data=ordered,acl,user_xattr  0  2
UUID=86f5a543-3e63-4401-ae20-ea8264188377  /Data1     ext4  user,exec,acl,user_xattr     0  2
UUID=b610d0cd-9066-44db-8629-4a2369d11aa5  /Data2     ext4  user,exec,acl,user_xattr     0  2
UUID=c36a110c-1a13-46e9-b275-4c5203dab88b  /Data3     ext4  user,exec,acl,user_xattr     0  2
UUID=85e6b16d-c00e-4f6d-a9c1-0c61de664e50  /Data4     ext4  user,exec,acl,user_xattr     0  2
UUID=bba2cf27-d77e-4ef8-9f02-01c29b7c140f  /Data5     ext4  user,exec,acl,user_xattr     0  2
UUID=7d11e52d-e270-4950-a7fe-9895bad7d49a  /Data6     ext4  user,exec,acl,user_xattr     0  2
UUID=ee67b744-61c6-4892-aad4-5146d9c9e33f  /OldHome   ext4  user,exec,acl,user_xattr     0  2
UUID=0F45-A46C                             /boot/efi  vfat  defaults                     0  0

When I boot, the system hangs for several minutes, then drops to emergency mode, and I have to log in as root and examine the journal which shows that the systemd.fsck.service start failed due to a timeout on that partition.

I’ve spent the last several hours researching the issue. I find that according to the documentation on the systemd fsck service, it is supposed to obey the file check flag in the /etc/fstab file. So I set that to 0 to skip the check to at least see if the system would boot if it skips the check. That had no effect. Systemd continues to run the fsck start and fails on that partition. The only way to get the system to complete the boot is to remove the partition from the /etc/fstab table. Examining the partition with Gparted shows nothing evidently wrong. Running a manual fsck on that partition when unmounted shows it as clean:

fsck /dev/nvme0n1p6
fsck from util-linux 2.33.1
e2fsck 1.43.8 (1-Jan-2018)
Data6: clean, 11/26820608 files, 1963437/107269632 blocks

I can manually mount and umount the partition on the file system directory with no problem as a normal user. I can then create a file on it with no problem. The problem appears to be strictly the systemd.fsck-service times on out when accessing that partition and that partition only.

I’m at my wit’s end. The primary two reasons for buying and installing an NVME SSD was to speed up boot and program loading - and to run virtual machines at better speed than on a hard drive. Of course, I can manually mount the partition as I indicated above but that’s going to be an irritation. What really gripes me is that the systemd fsck service is not adhering to the documentation where it says it is supposed to acknowledge the file check flag in /etc/fstab - and it absolutely does not. I’ve also read elsewhere that most of the workarounds for this sort of thing which are intended to stop the systemd fsck service from doing this sort don’t work either. In other words, there’s no apparent way to turn this nonsense off.

Thanks in advance for any help.

2

You should be able to use “noauto” as an option. Then the partition won’t be mounted at boot.

I think it won’t force an “fsck” if you mount “ro”, but I have not tried that recently.

That “fsck” is timing out is the real problem. I can’t guess what would cause that.

3

I would try the nofail mount option, mainly to have boot proceed “normally”, but also to see if data6 eventually automounts, and what dmesg has to say about it.

4

BTW if it is this one:

nvme0n1     259:0    0   477G  0 disk 
├─nvme0n1p1 259:1    0     1K  0 part
├─nvme0n1p2 259:2    0   500M  0 part /boot/efi
├─nvme0n1p3 259:3    0     4G  0 part [SWAP]
├─nvme0n1p4 259:4    0    35G  0 part /
├─nvme0n1p5 259:5    0    15G  0 part /home
└─nvme0n1p6 259:6    0 409.2G  0 part /Data6

I do not see the extended (and thus the logical) partition you are talking about.
It may be me, but I find

fdisk -l

more illuminating.

5

There isn’t an extended on a GPT disk.

It may be me, but I find

fdisk -l

more illuminating.
https://forums.opensuse.org/showthread.php/536947-fdisk-vs-gdisk-vs-parted-vs-sfdisk-vs-blkid-vs-lsblk-vs-dfsee-compared?p=2909806#post2909806 might be further enlightening. :smiley:

6

Of course not, but the OP more or less starts with saying so. I am a bit dumb, but most often, from the moment I do not understand anymore what somebody is describing, I mistrust any interpretation I may have about a problem and any communication about a case until I am convinced that we understand the background in the same way from both sides of the discussion.

7

Right, it’s not a GPT disk. It’s only 500GB so I made it a regular disk.

8

Here you go.

Disk /dev/nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: ADATA SX8200PNP                         
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xbc5e9159

Device         Boot     Start        End   Sectors   Size Id Type
/dev/nvme0n1p1      110592000 1000212479 889620480 424.2G  f W95 Ext'd (LBA)
/dev/nvme0n1p2           2048    1026047   1024000   500M ef EFI (FAT-12/16/32)
/dev/nvme0n1p3        1026048    9414655   8388608     4G 82 Linux swap / Solaris
/dev/nvme0n1p4        9414656   82814975  73400320    35G 83 Linux
/dev/nvme0n1p5      110596096  142053375  31457280    15G 83 Linux
/dev/nvme0n1p6      142055424 1000212479 858157056 409.2G 83 Linux

Partition table entries are not in disk order.

As you can see, the extended partition begins at 11059609 which corresponds to the start of my home partition, and ends at the end of the disk (minus 1MB or so unallocated) and encompasses the 409.2GB Data6 partition.

And you’re right, it’s best that we’re on the same page. I never use fdisk, I always use Gparted GUI which unfortunately doesn’t have a print option.

9

I will try that, but frankly I suspect that systemd will ignore that, too. I’ve heard that it ignores most of the workarounds for this sort of thing. But we’ll see.

It would be an optimum solution if it would ignore the file system check during boot, then on first access it automagically mounts and lets the mount mechanism decide whether to run fsck or not. From what I’ve read, this requires other manipulations than just “nofail”, but I’d have to reread a bunch of systemd stuff to figure out how that works, if it does.

I’ll test the nofail and report back.

10

OK, I just tested the boot with nofail on the partition in question, as per the /etc/fstab here:

linux-h2ol:/home/rhack # cat /etc/fstab
UUID=9c8dce57-1c43-4436-86dd-06b70db462e2  swap       swap  defaults                     0  0
UUID=7df10d3e-99cf-4d67-8c19-b319d26e9d96  /          ext4  acl,user_xattr               0  1
UUID=c3c2b83e-5d88-4da0-8abb-d97d61ea3333  /home      ext4  data=ordered,acl,user_xattr  0  2
UUID=86f5a543-3e63-4401-ae20-ea8264188377  /Data1     ext4  user,exec,acl,user_xattr     0  2
UUID=b610d0cd-9066-44db-8629-4a2369d11aa5  /Data2     ext4  user,exec,acl,user_xattr     0  2
UUID=c36a110c-1a13-46e9-b275-4c5203dab88b  /Data3     ext4  user,exec,acl,user_xattr     0  2
UUID=85e6b16d-c00e-4f6d-a9c1-0c61de664e50  /Data4     ext4  user,exec,acl,user_xattr     0  2
UUID=bba2cf27-d77e-4ef8-9f02-01c29b7c140f  /Data5     ext4  user,exec,acl,user_xattr     0  2
UUID=7d11e52d-e270-4950-a7fe-9895bad7d49a  /Data6     ext4  nofail,user,exec,acl,user_xattr  0  2
UUID=ee67b744-61c6-4892-aad4-5146d9c9e33f  /OldHome   ext4  user,exec,acl,user_xattr     0  2
UUID=0F45-A46C                             /boot/efi  vfat  defaults                     0  0

The boot does proceed without hanging, and the partition is not mounted, as expected.

When I open Dolphin and click on the partition in Places and select “Mount”, it prompts me for the root password. Upon entering that, the partition is mounted, as shown here in lsblk:

linux-h2ol:/home/rhack # lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda           8:0    0   3.7T  0 disk 
└─sda1        8:1    0   3.7T  0 part /Data2
sdb           8:16   0   3.7T  0 disk 
└─sdb1        8:17   0   3.7T  0 part /Data5
sdc           8:32   0   3.7T  0 disk 
├─sdc4        8:36   0    10G  0 part /OldHome
├─sdc5        8:37   0   1.8T  0 part /Data1
└─sdc6        8:38   0   1.8T  0 part /Data4
sdd           8:48   0   1.8T  0 disk 
└─sdd1        8:49   0   1.8T  0 part /Data3
sr0          11:0    1  1024M  0 rom  
nvme0n1     259:0    0   477G  0 disk 
├─nvme0n1p1 259:1    0     1K  0 part 
├─nvme0n1p2 259:2    0   500M  0 part /boot/efi
├─nvme0n1p3 259:3    0     4G  0 part [SWAP]
├─nvme0n1p4 259:4    0    35G  0 part /
├─nvme0n1p5 259:5    0    15G  0 part /home
└─nvme0n1p6 259:6    0 409.2G  0 part /run/media/rhack/Data6

Note that it mounts it not on the directory /Data6 but rather under /run/media/rhack/Data6. I can access the files on it, no problem. It seems to basically treat this the same as if it were one of my external hard drives in one of my docking stations that I use for backups. However, the Recent Devices icon does not show it, like it does the external drives.

Mount shows it as mounted:

rhack@linux-h2ol:~> mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=8164552k,nr_inodes=2041138,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
/dev/nvme0n1p4 on / type ext4 (rw,relatime,data=ordered)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=25,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=22614)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
/dev/nvme0n1p2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/nvme0n1p5 on /home type ext4 (rw,relatime,data=ordered)
/dev/sda1 on /Data2 type ext4 (rw,nosuid,nodev,relatime,data=ordered,user)
/dev/sdd1 on /Data3 type ext4 (rw,nosuid,nodev,relatime,data=ordered,user)
/dev/sdc6 on /Data4 type ext4 (rw,nosuid,nodev,relatime,data=ordered,user)
/dev/sdb1 on /Data5 type ext4 (rw,nosuid,nodev,relatime,data=ordered,user)
/dev/sdc4 on /OldHome type ext4 (rw,nosuid,nodev,relatime,data=ordered,user)
/dev/sdc5 on /Data1 type ext4 (rw,nosuid,nodev,relatime,data=ordered,user)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1634500k,mode=700,uid=1000,gid=100)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/nvme0n1p6 on /run/media/rhack/Data6 type ext4 (rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)

And I can unmount it as root (didn’t try it as normal user) if I specify the device designation, but not the /Data6 (because it’s not mounted there, obviously.)

Not sure I’m liking this solution. It’s relatively easy to mount - just click on the partition and enter the root password. But I’ll have to remember to unmount it on any reboot if there has been file activity, like I do with my external drives. It would be better if the system would automatically mount it on my accessing the partition (and if necessary run a fsck) while the system buffer any data to the partition until the drive is ready. According to an Archlinux wiki entry, I quote:

Local partition

In case of a large partition, it may be more efficient to allow services that do not depend on it to start while it is checked by fsck. This can be achieved by adding the following options to the /etc/fstab entry of the partition:
noauto,x-systemd.automount
This will fsck and mount the partition only when it is first accessed, and the kernel will buffer all file access to it until it is ready. This method can be relevant if one has, for example, a significantly large /home partition.

The impression I get from reading that is the noauto prevents the item from being mounted at boot, and the x-systemd,automount creates a “mount unit” somewhere under /etc/systemd that controls how the partition is handled which allows for an automatic mount of the partition and a fsck as required, which is how I’d like to do it if no easier workaround can be found.

But the way I have it now, it’s not mounting at the desired location specified in the /etc/fstab. i.e., /Data6. Is there a way to make it do that - and unmount it with the rest of the regularly mounted hard drives on a reboot? I’ve been reading the systemd.automount and systemd.mount man pages but they are massively confusing.

If there isn’t an easy way to do that, I can probably just manually mount the partition as root when I need to use it on /Data6 and then remember to unmount it when rebooting. It’s going to be used for virtual machines exclusively so I’ll probably be able to remember to unmount it when I’m done with them. But it would be nice if the system could do that itself - preferably without having to read twenty or more separate man pages on systemd.

11

First you show /etc/fstab that contains UUID. Then you show fdisk output that contains no UUID. There is no evidence that UUID used in /etc/fstab actually matches UUID of your filesystem located on partition 6.

12

Showing both the full contents of /etc/fstab and the output of lsblk -f will help:

erlangen:~ # cat /etc/fstab
UUID=8b190950-c141-4351-9198-7a9592b4fb34  /                ext4      defaults             0  0
UUID=704621ef-9b45-4e96-ba7f-1becd3924f08  /home            ext4      defaults             0  0
UUID=f5177cae-4082-44ed-9471-b99030f06866  /home-HDD        ext4      defaults             0  0
UUID=083dd95e-4073-43b1-a213-ad3ed8dd9a33  /Tumbleweed-SSD  ext4      defaults             0  0
UUID=f4c5463f-f43d-420a-a0ea-4456cfbc54fa  /home-SSD        ext4      defaults             0  0
UUID=6DEC-64F9                             /boot/efi        vfat      defaults             0  0
#
/home-HDD/drives/SAMSUNG-SP2014N/p6.sqsh   /drives/SAMSUNG-SP2014N/p6  squashfs  noauto,loop          0  0
UUID=047d4d83-a9a7-482e-8d15-a1c855a637ea  /Fedora          ext4      noauto,data=ordered  0  0
UUID=f3c36796-d1b7-426d-9bef-6c61c39db0b1  /Xubuntu         ext4      noauto,data=ordered  0  0
UUID=3760cc8d-f468-4654-855b-afcd31071075  /Tumbleweed-HDD  ext4      noauto,acl,user_xattr,data=ordered  0  2


erlangen:~ # lsblk -f
NAME        FSTYPE LABEL          UUID                                 FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                   
├─sda1      ext4                  fad3604b-5a61-4653-8c14-518d850400ba                
├─sda2      ext4   Tumbleweed-HDD 3760cc8d-f468-4654-855b-afcd31071075                
└─sda4      ext4   Home-HDD       f5177cae-4082-44ed-9471-b99030f06866      2T    42% /home-HDD
sdb                                                                                   
├─sdb1      vfat                  4A24-B10D                                           
├─sdb2      ext4   Xubuntu        f3c36796-d1b7-426d-9bef-6c61c39db0b1                
├─sdb3      ext4   Tumbleweed-SSD 083dd95e-4073-43b1-a213-ad3ed8dd9a33   10.4G    60% /Tumbleweed-SSD
├─sdb4      ext4   Home-SSD       f4c5463f-f43d-420a-a0ea-4456cfbc54fa  114.3G    63% /home-SSD
└─sdb5      btrfs                 d2a744da-8a53-4321-aada-81f97e7f8d63                
nvme0n1                                                                               
├─nvme0n1p1 ext4   Fedora         047d4d83-a9a7-482e-8d15-a1c855a637ea                
├─nvme0n1p2 ext4   Tumbleweed     8b190950-c141-4351-9198-7a9592b4fb34    9.8G    64% /
├─nvme0n1p3 ext4   Home           704621ef-9b45-4e96-ba7f-1becd3924f08  178.1G    56% /home
└─nvme0n1p4 vfat                  6DEC-64F9                              87.3M    13% /boot/efi
erlangen:~ #
13 
rhack@linux-h2ol:~> cd /dev/disk/by-uuid
rhack@linux-h2ol:/dev/disk/by-uuid> ll
total 0
lrwxrwxrwx 1 root root 15 Jul 30 18:05 01e2fd8f-825b-4348-a731-737962f23ea3 -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 15 Jul 30 18:05 0F45-A46C -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Jul 30 18:05 7df10d3e-99cf-4d67-8c19-b319d26e9d96 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 10 Jul 30 18:05 85e6b16d-c00e-4f6d-a9c1-0c61de664e50 -> ../../sdc6
lrwxrwxrwx 1 root root 10 Jul 30 18:05 86f5a543-3e63-4401-ae20-ea8264188377 -> ../../sdc5
lrwxrwxrwx 1 root root 15 Jul 30 18:05 9c8dce57-1c43-4436-86dd-06b70db462e2 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 10 Jul 30 18:05 b610d0cd-9066-44db-8629-4a2369d11aa5 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jul 30 18:05 bba2cf27-d77e-4ef8-9f02-01c29b7c140f -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jul 30 18:05 c36a110c-1a13-46e9-b275-4c5203dab88b -> ../../sdd1
lrwxrwxrwx 1 root root 15 Jul 30 18:05 c3c2b83e-5d88-4da0-8abb-d97d61ea3333 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 10 Jul 30 18:05 ee67b744-61c6-4892-aad4-5146d9c9e33f -> ../../sdc4

And here’s the blkid report:

linux-h2ol:/dev/disk/by-uuid # blkid
/dev/nvme0n1p2: SEC_TYPE="msdos" UUID="0F45-A46C" TYPE="vfat" PARTUUID="bc5e9159-02"
/dev/nvme0n1p3: UUID="9c8dce57-1c43-4436-86dd-06b70db462e2" TYPE="swap" PARTUUID="bc5e9159-03"
/dev/nvme0n1p4: LABEL="Root" UUID="7df10d3e-99cf-4d67-8c19-b319d26e9d96" TYPE="ext4" PARTUUID="bc5e9159-04"
/dev/nvme0n1p5: LABEL="Home" UUID="c3c2b83e-5d88-4da0-8abb-d97d61ea3333" TYPE="ext4" PARTUUID="bc5e9159-05"
/dev/nvme0n1p6: LABEL="Data6" UUID="01e2fd8f-825b-4348-a731-737962f23ea3" TYPE="ext4" PARTUUID="bc5e9159-06"
/dev/sda1: LABEL="Data2" UUID="b610d0cd-9066-44db-8629-4a2369d11aa5" TYPE="ext4" PARTLABEL="Data2" PARTUUID="fd1629a8-05a3-4741-81f1-7b9f82af20bd"
/dev/sdb1: UUID="bba2cf27-d77e-4ef8-9f02-01c29b7c140f" TYPE="ext4" PARTLABEL="Data5" PARTUUID="a16a95a1-1bf1-4404-a09f-dd8f12497016"
/dev/sdc4: LABEL="OldHome" UUID="ee67b744-61c6-4892-aad4-5146d9c9e33f" TYPE="ext4" PARTLABEL="primary" PARTUUID="cc8e4bcf-f073-4b35-a390-b6b244a281fa"
/dev/sdc5: LABEL="Data1" UUID="86f5a543-3e63-4401-ae20-ea8264188377" TYPE="ext4" PARTLABEL="primary" PARTUUID="b884300d-57ce-466f-95c9-2e3a29766464"
/dev/sdc6: LABEL="Data4" UUID="85e6b16d-c00e-4f6d-a9c1-0c61de664e50" TYPE="ext4" PARTLABEL="primary" PARTUUID="94854c98-1515-454d-a0e2-72f74c4fa2d6"
/dev/sdd1: LABEL="Data3" UUID="c36a110c-1a13-46e9-b275-4c5203dab88b" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="dee898d4-d278-4833-afba-f87bba83623b"
/dev/nvme0n1: PTUUID="bc5e9159" PTTYPE="dos

And here’s the /etc/fstab UUID I’m using:

linux-h2ol:/dev/disk/by-uuid # cat /etc/fstab
UUID=9c8dce57-1c43-4436-86dd-06b70db462e2  swap       swap  defaults                     0  0
UUID=7df10d3e-99cf-4d67-8c19-b319d26e9d96  /          ext4  acl,user_xattr               0  1
UUID=c3c2b83e-5d88-4da0-8abb-d97d61ea3333  /home      ext4  data=ordered,acl,user_xattr  0  2
UUID=86f5a543-3e63-4401-ae20-ea8264188377  /Data1     ext4  user,exec,acl,user_xattr     0  2
UUID=b610d0cd-9066-44db-8629-4a2369d11aa5  /Data2     ext4  user,exec,acl,user_xattr     0  2
UUID=c36a110c-1a13-46e9-b275-4c5203dab88b  /Data3     ext4  user,exec,acl,user_xattr     0  2
UUID=85e6b16d-c00e-4f6d-a9c1-0c61de664e50  /Data4     ext4  user,exec,acl,user_xattr     0  2
UUID=bba2cf27-d77e-4ef8-9f02-01c29b7c140f  /Data5     ext4  user,exec,acl,user_xattr     0  2
UUID=7d11e52d-e270-4950-a7fe-9895bad7d49a  /Data6     ext4  nofail,user,exec,acl,user_xattr  0  2
UUID=ee67b744-61c6-4892-aad4-5146d9c9e33f  /OldHome   ext4  user,exec,acl,user_xattr     0  2
UUID=0F45-A46C                             /boot/efi  vfat  defaults                     0  0

You’re right. It doesn’t match. I could have sworn I got the partition UUID from GParted when I created the partition. Now I don’t know where I got it from. WTF? The UUID I’m using isn’t in either location. So where the hell did it come from? I have no idea. The only thing I can think of is that one or more of the external drives was mounted at the time and I accidentally clicked on that in Gparted GUI when looking for the UUID. That’s unlikely since I always turn them off in the morning on awakening. So I’m totally confused now. I appear to have hallucinated a UUID! LOL

I will change it to the UUID listed as “01e2fd8f-825b-4348-a731-737962f23ea3” - which is the UUID assigned to that partition according to the above.

This is undoubtedly the reason for the problem.

Thanks for this. I will remove the “nofail” and test this immediately and report back.

14

That was it.

Again, I have zero clue as to where I got that UUID I was using in /etc/fstab. It must exist somewhere but it clearly has nothing to do with the existing partitions on that NVME.

Thanks for catching that.