[SOLVED] Duplicate error

[Bleys]

When booting up I get a duplicate error.
..sometimes, other times it just breezes through.


Anway I found my games drive twice in fstab:

/dev/sda1 /media/bleys/Games ext4 defaults 0 0
UUID=bbe6d531-3740-4a39-8bab-e829cc93ad97 /media/bleys/Games ext4 defaults,noatime 0 0

Can I just replace the /dev/sda1 line with the UUID line?


When pasting the whole fstab the spacing got messed up.
I can still do that if it is preferred.

[jlittle]

If the UUID is indeed that of /dev/sda1, delete the /dev/sda1 line. You can check by running sudo blkid, or ru The device enumeration by the firmware (aka BIOS, loosely), which is where the "a" for drive 1 comes from, can change at the whim of the firmware, usually if something is plugged in or out.

I dislike UUIDs, they are not easy for people to work with. Your "spacing got messed up" is a classic case. I much prefer using labels, but one has to make sure they are well defined. Here's my desktop's /etc/fstab:

#file system   mount       type   options                      dump pass
LABEL=main     /           btrfs  defaults,subvol=@r,noatime     0   1
LABEL=main     /home       btrfs  defaults,subvol=@h,noatime     0   2
PARTLABEL=swap none        swap   sw                             0   0
LABEL=EFI      /boot/efi   vfat   umask=000,noatime,noauto,user  0   1
#
# the new hard drive for miscellaneous stuff
LABEL=stuff    /mnt/stuff  btrfs  defaults,noatime,noauto,user   0   2

# mounts on the old Seagate, which is MBR
LABEL=pics     /mnt/pics   ext4   defaults,noatime,noauto,user   0   2
LABEL=vm       /mnt/vm     ext4   defaults,noatime,noauto,user   0   2 
LABEL=work     /mnt/work   btrfs  defaults,noatime,noauto,user   0   2
LABEL=qhome    /mnt/qhome  ext4   defaults,noatime,noauto,user   0   2

[jglen490]

If both lines are active, then "comment" one of them. By that, I mean place a # at the beginning of the line for one of the entries.

This is what mine looks like.

# /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/nvme0n1p2 during installation
UUID=353966f5-f485-4db8-baeb-b0500c42a263 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=547D-88B8 /boot/efi vfat umask=0077 0 1
# /home was on /dev/nvme0n1p3 during installation
UUID=f259144e-4345-478b-b840-7b5573801bb0 /home ext4 defaults 0 2
# swap was on /dev/nvme0n1p4 during installation
UUID=ca7c042b-1e20-466e-995e-185724576873 none swap sw 0 0

Note that the UUID line is actually active, and is generally preferred..

[Bleys]

Thank you both. For now I will stick with commenting it.
That quick fix fits in with the little amount of time I have this weekend.
But I've got to say, that label method looks very satisfying.

Also I'm glad to see errors=remount-ro that means I don't have to worry about it.

[GreyGeek]

While UUID's are more difficult to work with (if one does not use copy&paste) than /dev/sdxn, the basic problem with /dev/sdxn is that it can point to different drives at different times. For example, I had created a two disk raid device using /dev/sda and /dev/sdb. I took my CD-ROM drive out and replaced it with an HDCADDY that I had installed a 750 HD in. I expected it to boot up as /dev/sdc. I was stunned when it came up as /dev/sdb Sure enough, my raid was /dev/sda and /dev/sdc. From that time on I have always use UUID mounting.

[Bleys]

Have not seen any duplicate errors since commenting it out.
This topic can be closed. See you when the next problem pops up =)