[PLUG] Mount order on boot

John Jason Jordan johnxj at gmx.com
Thu Nov 28 01:04:43 UTC 2019


On Wed, 27 Nov 2019 18:54:38 -0500
tomas.kuchta.lists at gmail.com dijo:

>Check your disk and partition labels by:
>sudo lsblk -o name,mountpoint,label,size,uuid
>
>Maybe the labels are not unique or are missing.
>
>In general - file systems are mounted in the same order as per fstab.
>If you have duplicate/missing labels on disk partitions - which could
>happen during your dd/rsync install method - then things might get
>"entertaining".

The lsblk command listed only the four partitions, including their
Labels and UUIDs. All the Labels and UUIDs are unique. After all, there
are only four: Boot, Home, Data and Movies. Even I would find it hard
to screw that up:

NAME MOUNTPOINT		LABEL	SIZE   UUID
sda:
sda1  /media/jjj/Data 	Data	1TB    <UUID#>
sdb:
sdb1  /media/jjj/Movies 	Movies	11TB  <UUID#>
sdc:
sdc1  /				Boot		80G   <UUID#>
sdc2  /home			Home	400G <UUID#>

A bit of further duckduckgoing led me to the conclusion that the boot
order is now controlled by systemd, not the order as they are listed in
fstab. Figuring out systemd may be beyond me, but I'm working on it.

I still have the relatively benign grub error on boot: 'Error no symbol
table, press any key to continue.' If I do nothing it boots anyway, but
I also still have jbd2 periodically munching my /home partition. I did
sudo update-grub, which exited without errors, but when I rebooted I
still had the grub error. Right after the dist-upgrade from 16.04 to
18.04 the computer would not boot because /home had been
previously assumed to be /dev/sdb2, but Movies had become /dev/sdb so it
couldn't find a /home partition. I think the current grub error and the
disk-munching are connected to that initial boot problem, but sorting
it out is probably going to take me awhile. Figuring out what is going
on with boot order is probably part of understanding how to fix these
issues.

And yeah, when I try to move this system to a new drive in the new
computer that is still on its way, I expect issues. Video is one,
because both computers have NVIDIA video, but different chips and
resolutions - the old computer is 1980x1020 and the new one is capable
of 3840x2160. And boot issues are another. The Data and Movies
partitions are external, but / and /home may be interesting to move.
And then there is UEFI on the new computer.

My goal is to get 18.04 in perfect condition before the move. I had a
lot of deferred housekeeping on the old 16.04, e.g., launch menus had
become a mess, among other matters. (Creating and maintaining custom
launch menus is not trivial.) I've got the menus fixed (and backed up),
so next I want to attack the grub problem.



More information about the PLUG mailing list