[PLUG] Mount command creates new folders

[John Jason Jordan]

I have a second drive in my computer that the computer knows
as /dev/sda1. (/Home and / are on /dev/sdb.) There is a folder 'Data'
in /media/jjj/, which is where I want to mount /dev/sda1. But when I
use the command 'sudo mount /dev/sda1 /media/jjj/Data' the mount
command creates a new folder /media/jjj/Data1 and mounts /dev/sda1 in
it.

Why?

[Rich Shepard]

I have a second drive in my computer that the computer knows as /dev/sda1.
(/Home and / are on /dev/sdb.) There is a folder 'Data' in /media/jjj/,
which is where I want to mount /dev/sda1. But when I use the command 'sudo
mount /dev/sda1 /media/jjj/Data' the mount command creates a new folder
/media/jjj/Data1 and mounts /dev/sda1 in it.
Why?

John,

Tell us what mount points are defined and what partitions are on each. The
command 'mount' displays available mount points.

To learn what's on each one you can use either 'less /etc/fstab' or
'lsblk'.

I assume that /, /boot, and /swap are all on /dev/sda/. Is this correct?

Rich

[John Jason Jordan]

On Wed, 17 Oct 2018 10:46:48 -0700 (PDT)

Post by Rich Shepard
Tell us what mount points are defined and what partitions are on each.
The command 'mount' displays available mount points.
To learn what's on each one you can use either 'less /etc/fstab'
or'lsblk'.
I assume that /, /boot, and /swap are all on /dev/sda/. Is this
correct?

There are two physical drives inside the computer:

/dev/sdb which contains partitions for / and /home, sdb1 and
sdb2
/dev/sda which is just one partition, sda1

Normally you would expect /home and / to be on sda, but they were
installed on sdb because sdb is mSATA and the original sda was a
regular disk (and slower), and I wanted / and /home on the mSATA. I
tried to figure out how to reverse them so the mSATA would be sda, but
eventually I gave up and installed Xubuntu on sdb.

$mount (results below, edited)
/dev/sdb1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
/dev/sdb2 on /home type ext4 (rw,relatime,stripe=32745,data=ordered)
192.168.1.115:/volume1/Synology on /media/jjj/Synology type nfs
(rw,nosuid,nodev,noexec,relatime,vers=3,rsize=131072,wsize=131072,
namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=
192.168.1.115,mountvers=3,mountport=892,mountproto=udp,local_lock=
none,addr=192.168.1.115,user)
/dev/sdc1 on /media/jjj/Movies type ext4
(rw,relatime,stripe=8191,data=ordered)
/dev/sdc1 on /export/users/Movies type ext4
(rw,relatime,stripe=8191,data=ordered)
/dev/sdd1 on /media/jjj/128GB type ext4
(rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
/dev/sdd1 on /export/users/128GB type ext4
(rw,nosuid,nodev,relatime,data=ordered)
/dev/sda1 on /media/jjj/Data1 type ext4
(rw,nosuid,nodev,relatime,data=ordered,uhelper=udisks2)
/dev/sda1 on /export/users/Data1 type ext4
(rw,nosuid,nodev,relatime,data=ordered)

/dev/sdc1 is my Mediasonic enclosure (the source of recent angst, but
working fine now), connected by USB. Its label is 'Movies.' /dev/sdd1 is
a 128GB USB flash drive. Its label is '128GB.'

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 953.9G 0 disk
└─sda1 8:1 0 953.9G 0 part /export/users/Data1
sdb 8:16 0 447.1G 0 disk
├─sdb1 8:17 0 78.1G 0 part /
└─sdb2 8:18 0 369G 0 part /home
sdc 8:32 0 10.9T 0 disk
└─sdc1 8:33 0 10.9T 0 part /export/users/Movies
sdd 8:48 1 119.2G 0 disk
└─sdd1 8:49 1 119.2G 0 part /export/users/128GB
sr0 11:0 1 33.9G 0 rom <a Blu-ray drive>
sr1 11:1 1 4.1G 0 rom <a DVD drive, by USB)
loop0 7:0 0 87M 1 loop /snap/core/5145
loop1 7:1 0 87.9M 1 loop /snap/core/5328
loop2 7:2 0 87.9M 1 loop /snap/core/5548

Here is fstab (also edited to remove instructional comments):
UUID=27c11f6b-b443-417e-9853-12c99789d8d9 / ext4
errors=remount-ro 0 1
# /home was on /dev/sdb2 during installation
UUID=9a201393-e364-4d11-b372-877cded3b9cc /home ext4
defaults 0 2
/media/jjj/Synology nfs auto,user 0 0 192.168.1.115:/volume1/Synology
/media/jjj/Synology nfs auto,user 0 0
#so clients can see nfs share
/media/jjj /export/users none bind 0 0
#/dev/disk/by-label/256GB-1 /media/jjj/256GB-1 auto
nosuid,nodev,nofail,noauto,x-gvfs-show,x-gvfs-n$
<Something created this line, but not me. Just today I commented
it out because I didn't want '256GB' showing up in the GUI file
manager when it wasn't even plugged in. The device is a USB
flash drive.>

Any ideas how to get 'mount' to mount sda1 on /media/jjj/Data where I
tell it to instead of creating a new Data1 folder and mounting it there?

[Rich Shepard]

Post by John Jason Jordan
$mount (results below, edited)

John,

I meant to ask what mount moints you have on /mnt.

Post by John Jason Jordan
/dev/sdc1 is my Mediasonic enclosure (the source of recent angst, but
working fine now), connected by USB.
sdc 8:32 0 10.9T 0 disk
└─sdc1 8:33 0 10.9T 0 part /export/users/Movies
UUID=27c11f6b-b443-417e-9853-12c99789d8d9 / ext4
errors=remount-ro 0 1
# /home was on /dev/sdb2 during installation
UUID=9a201393-e364-4d11-b372-877cded3b9cc /home ext4
defaults 0 2
/media/jjj/Synology nfs auto,user 0 0 192.168.1.115:/volume1/Synology
/media/jjj/Synology nfs auto,user 0 0
#so clients can see nfs share
/media/jjj /export/users none bind 0 0
#/dev/disk/by-label/256GB-1 /media/jjj/256GB-1 auto
nosuid,nodev,nofail,noauto,x-gvfs-show,x-gvfs-n$
<Something created this line, but not me. Just today I commented
it out because I didn't want '256GB' showing up in the GUI file
manager when it wasn't even plugged in. The device is a USB
flash drive.>

I don't see where Movies is mounted, which lsblk sees on /dev/sdc1/. I see
/media/jjj in fstab, but not the subdirectory Movies.

Post by John Jason Jordan
Any ideas how to get 'mount' to mount sda1 on /media/jjj/Data where I
tell it to instead of creating a new Data1 folder and mounting it there?

More knowledgeable folks than I can better interpret this information and
help you toward an answer.

Regards,

Rich

[John Jason Jordan]

On Wed, 17 Oct 2018 13:25:42 -0700 (PDT)

Post by Rich Shepard
I meant to ask what mount moints you have on /mnt.

None on /mnt. Everything is on /media/jjj. Except maybe the optical
drives; I'm not actually sure where they go. But they are not a problem
so I ignore them.

I think I have a solution. The man page for mount says that it goes
to /etc/fstab to find where it is supposed to mount things, so I
decided to do some serious editing of fstab. Here is my final version:

# / and /home were installed on /dev/sdb because it was faster than /dev/sda
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=27c11f6b-b443-417e-9853-12c99789d8d9 / ext4 errors=remount-ro,user 0 1
UUID=9a201393-e364-4d11-b372-877cded3b9cc /home ext4 defaults,user 0 2
192.168.1.115:/volume1/Synology /media/jjj/Synology nfs auto,user 0 0
#so clients can see nfs share
/media/jjj /export/users none bind 0 0
#This line not added by me:
#/dev/disk/by-label/256GB-1 /media/jjj/256GB-1 auto
nosuid,nodev,nofail,noauto,x-gvfs-show,x-gvfs-name=256GB-1 0 0
#For Data drive
UUID=f8b85f57-d7a6-4454-9939-7e21fb355bb4 /media/jjj/Data ext4
errors=remount-ro,user 0 1
#For Movies USB device
UUID=50b66cfb-01ba-4c15-9f3c-5e9718c6f604 /media/jjj/Movies ext4
errors=remount-ro,user 0 1

After saving fstab where I added the Data and Movies drives, I unmounted
both Data and Movies, and then did 'sudo mount -a'. It worked - both
drives were mounted where they belonged, not in Data1 or Movies1 as
sometimes happened in the past.

I still don't know why mount would often take it upon itself to make a
new folder to mount the drive in, ignoring the folder that I specified
in the command. Like 'hey mount, what part of /media/jjj/Data did you
not understand?'

[Larry Brigman]

Is it possible that there was a pending mount from the GUI that was waiting
for the sudo permissions and it did the mount not your command?

Post by John Jason Jordan
On Wed, 17 Oct 2018 13:25:42 -0700 (PDT)

Post by Rich Shepard
I meant to ask what mount moints you have on /mnt.

None on /mnt. Everything is on /media/jjj. Except maybe the optical
drives; I'm not actually sure where they go. But they are not a problem
so I ignore them.
I think I have a solution. The man page for mount says that it goes
to /etc/fstab to find where it is supposed to mount things, so I
# / and /home were installed on /dev/sdb because it was faster than /dev/sda
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=27c11f6b-b443-417e-9853-12c99789d8d9 / ext4 errors=remount-ro,user 0 1
UUID=9a201393-e364-4d11-b372-877cded3b9cc /home ext4 defaults,user 0 2
192.168.1.115:/volume1/Synology /media/jjj/Synology nfs auto,user 0 0
#so clients can see nfs share
/media/jjj /export/users none bind 0 0
#/dev/disk/by-label/256GB-1 /media/jjj/256GB-1 auto
nosuid,nodev,nofail,noauto,x-gvfs-show,x-gvfs-name=256GB-1 0 0
#For Data drive
UUID=f8b85f57-d7a6-4454-9939-7e21fb355bb4 /media/jjj/Data ext4
errors=remount-ro,user 0 1
#For Movies USB device
UUID=50b66cfb-01ba-4c15-9f3c-5e9718c6f604 /media/jjj/Movies ext4
errors=remount-ro,user 0 1
After saving fstab where I added the Data and Movies drives, I unmounted
both Data and Movies, and then did 'sudo mount -a'. It worked - both
drives were mounted where they belonged, not in Data1 or Movies1 as
sometimes happened in the past.
I still don't know why mount would often take it upon itself to make a
new folder to mount the drive in, ignoring the folder that I specified
in the command. Like 'hey mount, what part of /media/jjj/Data did you
not understand?'
_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

[John Jason Jordan]

On Wed, 17 Oct 2018 17:14:41 -0700

Post by Larry Brigman
Is it possible that there was a pending mount from the GUI that was
waiting for the sudo permissions and it did the mount not your command?

I don't see how that could be.

First, the Movies drive is USB, which doesn't require sudo permissions,
and it was often mounted at Movies1 instead of Movies. More
importantly, I rarely try to mount something with the GUI, but if I did,
it mounted right away - just not in the right folder, the same as when I
mounted something from the command line.

The only theory I can come up with is that mount can't mount something
to an existing folder, therefore it makes up a new one. But that makes
little sense too, because now that the mount point is specified in
fstab, mount happily mounts the drives into existing folders.

If I executed the command 'mount /dev/sdc /media/jjj/Movies' the
command would execute immediately and without error, but /dev/sdc would
usually be mounted in /media/jjj/Movies1.

[Tomas Kuchta]

Mount doesn't make missing mount points. It prints error and fails.

It is either hotplug ( not sure if Ubuntu still uses it ) or more likely
systemd. I'd start checking systemd and dmesg first.

Actually, I'd .... nevermind.

Post by John Jason Jordan
On Wed, 17 Oct 2018 17:14:41 -0700

Post by Larry Brigman
Is it possible that there was a pending mount from the GUI that was
waiting for the sudo permissions and it did the mount not your command?

I don't see how that could be.
First, the Movies drive is USB, which doesn't require sudo permissions,
and it was often mounted at Movies1 instead of Movies. More
importantly, I rarely try to mount something with the GUI, but if I did,
it mounted right away - just not in the right folder, the same as when I
mounted something from the command line.
The only theory I can come up with is that mount can't mount something
to an existing folder, therefore it makes up a new one. But that makes
little sense too, because now that the mount point is specified in
fstab, mount happily mounts the drives into existing folders.
If I executed the command 'mount /dev/sdc /media/jjj/Movies' the
command would execute immediately and without error, but /dev/sdc would
usually be mounted in /media/jjj/Movies1.
_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

[Ben Koenig]

The mount command requires root for all storage mediums. You are horribly
misinformed in more ways than one.

Post by Tomas Kuchta
Mount doesn't make missing mount points. It prints error and fails.
It is either hotplug ( not sure if Ubuntu still uses it ) or more likely
systemd. I'd start checking systemd and dmesg first.
Actually, I'd .... nevermind.

Post by John Jason Jordan
On Wed, 17 Oct 2018 17:14:41 -0700

Post by Larry Brigman
Is it possible that there was a pending mount from the GUI that was
waiting for the sudo permissions and it did the mount not your command?

I don't see how that could be.
First, the Movies drive is USB, which doesn't require sudo permissions,
and it was often mounted at Movies1 instead of Movies. More
importantly, I rarely try to mount something with the GUI, but if I did,
it mounted right away - just not in the right folder, the same as when I
mounted something from the command line.
The only theory I can come up with is that mount can't mount something
to an existing folder, therefore it makes up a new one. But that makes
little sense too, because now that the mount point is specified in
fstab, mount happily mounts the drives into existing folders.
If I executed the command 'mount /dev/sdc /media/jjj/Movies' the
command would execute immediately and without error, but /dev/sdc would
usually be mounted in /media/jjj/Movies1.
_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

[Denis Heidtmann]

Please lighten up and be more helpful.

Post by Ben Koenig
The mount command requires root for all storage mediums. You are horribly
misinformed in more ways than one.

Post by Tomas Kuchta
Mount doesn't make missing mount points. It prints error and fails.
It is either hotplug ( not sure if Ubuntu still uses it ) or more likely
systemd. I'd start checking systemd and dmesg first.
Actually, I'd .... nevermind.

Post by John Jason Jordan
On Wed, 17 Oct 2018 17:14:41 -0700

Post by Larry Brigman
Is it possible that there was a pending mount from the GUI that was
waiting for the sudo permissions and it did the mount not your

command?

Post by Tomas Kuchta

Post by John Jason Jordan
I don't see how that could be.
First, the Movies drive is USB, which doesn't require sudo permissions,
and it was often mounted at Movies1 instead of Movies. More
importantly, I rarely try to mount something with the GUI, but if I

did,

Post by Tomas Kuchta

Post by John Jason Jordan
it mounted right away - just not in the right folder, the same as when

I

Post by Tomas Kuchta

Post by John Jason Jordan
mounted something from the command line.
The only theory I can come up with is that mount can't mount something
to an existing folder, therefore it makes up a new one. But that makes
little sense too, because now that the mount point is specified in
fstab, mount happily mounts the drives into existing folders.
If I executed the command 'mount /dev/sdc /media/jjj/Movies' the
command would execute immediately and without error, but /dev/sdc would
usually be mounted in /media/jjj/Movies1.
_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

[Ben Koenig]

/media is the folder where Ubuntu automounts removable media. When a USB
storage device is inserted, 2 things happen.

1) It creates a folder in /media
2) It mounts the volume to the folder it just created.

IF you already have a folder that you manually created, then the
automounter will ignore it, and use a different name.

That's why your system is creating a new folder '/media/jjj/Data1'. It's
not the mount command doing this. the "user friendly" nature of Ubuntu is
to automatically mount such devices and is conflicting with your
mountpoints in fstab.

Solution? Move all of your manual mountpoints to /mnt. /mnt is a legacy
mountpoint folder that applications these days don't use, and is perfect
for your application.

You will notice significant improvements in the way your devices are
mounted if you use a proper folder to mount them in.

Post by Denis Heidtmann
Please lighten up and be more helpful.

Post by Ben Koenig
The mount command requires root for all storage mediums. You are horribly
misinformed in more ways than one.
On Wed, Oct 17, 2018 at 8:15 PM Tomas Kuchta <

Post by Tomas Kuchta
Mount doesn't make missing mount points. It prints error and fails.
It is either hotplug ( not sure if Ubuntu still uses it ) or more

likely

Post by Ben Koenig

Post by Tomas Kuchta
systemd. I'd start checking systemd and dmesg first.
Actually, I'd .... nevermind.

Post by John Jason Jordan
On Wed, 17 Oct 2018 17:14:41 -0700

Post by Larry Brigman
Is it possible that there was a pending mount from the GUI that was
waiting for the sudo permissions and it did the mount not your

command?

Post by Tomas Kuchta

Post by John Jason Jordan
I don't see how that could be.
First, the Movies drive is USB, which doesn't require sudo

permissions,

Post by Ben Koenig

Post by Tomas Kuchta

Post by John Jason Jordan
and it was often mounted at Movies1 instead of Movies. More
importantly, I rarely try to mount something with the GUI, but if I

did,

Post by Tomas Kuchta

Post by John Jason Jordan
it mounted right away - just not in the right folder, the same as

when

Post by Ben Koenig
I

Post by Tomas Kuchta

Post by John Jason Jordan
mounted something from the command line.
The only theory I can come up with is that mount can't mount

something

Post by Ben Koenig

Post by Tomas Kuchta

Post by John Jason Jordan
to an existing folder, therefore it makes up a new one. But that

makes

Post by Ben Koenig

Post by Tomas Kuchta

Post by John Jason Jordan
little sense too, because now that the mount point is specified in
fstab, mount happily mounts the drives into existing folders.
If I executed the command 'mount /dev/sdc /media/jjj/Movies' the
command would execute immediately and without error, but /dev/sdc

would

Post by Ben Koenig

Post by Tomas Kuchta

Post by John Jason Jordan
usually be mounted in /media/jjj/Movies1.
_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

[Denis Heidtmann]

Thanks. Now this is an explanation that even I can understand!

Post by Ben Koenig
/media is the folder where Ubuntu automounts removable media. When a USB
storage device is inserted, 2 things happen.
1) It creates a folder in /media
2) It mounts the volume to the folder it just created.
IF you already have a folder that you manually created, then the
automounter will ignore it, and use a different name.
That's why your system is creating a new folder '/media/jjj/Data1'. It's
not the mount command doing this. the "user friendly" nature of Ubuntu is
to automatically mount such devices and is conflicting with your
mountpoints in fstab.
Solution? Move all of your manual mountpoints to /mnt. /mnt is a legacy
mountpoint folder that applications these days don't use, and is perfect
for your application.
You will notice significant improvements in the way your devices are
mounted if you use a proper folder to mount them in.

Post by Denis Heidtmann
Please lighten up and be more helpful.

Post by Ben Koenig
The mount command requires root for all storage mediums. You are

horribly

Post by Denis Heidtmann

Post by Ben Koenig
misinformed in more ways than one.
On Wed, Oct 17, 2018 at 8:15 PM Tomas Kuchta <

Post by Tomas Kuchta
Mount doesn't make missing mount points. It prints error and fails.
It is either hotplug ( not sure if Ubuntu still uses it ) or more

likely

Post by Ben Koenig

Post by Tomas Kuchta
systemd. I'd start checking systemd and dmesg first.
Actually, I'd .... nevermind.

Post by John Jason Jordan
On Wed, 17 Oct 2018 17:14:41 -0700

Post by Larry Brigman
Is it possible that there was a pending mount from the GUI that

was

Post by Denis Heidtmann

Post by Ben Koenig

Post by Tomas Kuchta

Post by John Jason Jordan

Post by Larry Brigman
waiting for the sudo permissions and it did the mount not your

command?

Post by Tomas Kuchta

Post by John Jason Jordan
I don't see how that could be.
First, the Movies drive is USB, which doesn't require sudo

permissions,

Post by Ben Koenig

Post by Tomas Kuchta

Post by John Jason Jordan
and it was often mounted at Movies1 instead of Movies. More
importantly, I rarely try to mount something with the GUI, but if I

did,

Post by Tomas Kuchta

Post by John Jason Jordan
it mounted right away - just not in the right folder, the same as

when

Post by Ben Koenig
I

Post by Tomas Kuchta

Post by John Jason Jordan
mounted something from the command line.
The only theory I can come up with is that mount can't mount

something

Post by Ben Koenig

Post by Tomas Kuchta

Post by John Jason Jordan
to an existing folder, therefore it makes up a new one. But that

makes

Post by Ben Koenig

Post by Tomas Kuchta

Post by John Jason Jordan
little sense too, because now that the mount point is specified in
fstab, mount happily mounts the drives into existing folders.
If I executed the command 'mount /dev/sdc /media/jjj/Movies' the
command would execute immediately and without error, but /dev/sdc

would

Post by Ben Koenig

Post by Tomas Kuchta

Post by John Jason Jordan
usually be mounted in /media/jjj/Movies1.
_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

_______________________________________________
PLUG mailing list
http://lists.pdxlinux.org/mailman/listinfo/plug

[John Jason Jordan]

On Sat, 20 Oct 2018 08:54:25 -0700

Post by Ben Koenig
1) It creates a folder in /media
2) It mounts the volume to the folder it just created.
IF you already have a folder that you manually created, then the
automounter will ignore it, and use a different name.
That's why your system is creating a new folder '/media/jjj/Data1'.
It's not the mount command doing this. the "user friendly" nature of
Ubuntu is to automatically mount such devices and is conflicting with
your mountpoints in fstab.

That explains what is happening, but not how to stop it from happening.
I started by trying to figure out how to turn off the automounter
(autofs, actually), but I didn't succeed. But then 'man mount' told me
that mount starts by looking for a mount point for the device in fstab
and uses that if there is one, so I added lines to fstab with UUIDs and
the mount points.

To back up a moment, there are two drives that bug me; normal flash
drives have never been a problem. One is an internal 1TB drive that I
had given the label Data. The other is an external USB drive that I had
given the label Movies.

When I opened fstab I noted that / and /home were identified by UUIDs,
so I used lsblk to find the UUIDs of Data and Movies, then created the
mount information for them, specifying /media/jjj/Data
and /media/jjj/Movies. Having done so I rebooted, and it worked. That
was Saturday morning.

On Sunday I took the computer to the Clinic, where I shut it down for
the journey. When I got to Free Geek it would not boot. The obvious
culprit was what I had done to fstab, so I edited it by commenting out
the two new lines. Note that the Movies drive was still at home, but
the internal Data drive was there in the computer, so I started by just
commenting out the line for the Movies drive. But it still would not
boot, and even after commenting out the line for the Data drive, it
continued to error out on boot. It took Wes' help to solve the problem
(about an hour of poking at things), until finally Wes commented out
the lines for / and /home and rewrote them with /dev/sdb1 for /
and /dev/sdb2 for /home, instead of the UUIDs. At that point it finally
booted.

At that time lsblk showed that the UUIDs for the two lines were
perfectly correct, but the boot process apparently didn't agree. The
only thing I can conclude is that UUIDs are evil.

Having gotten the computer to boot I uncommented my lines for Data and
Movies and rebooted, and all went well. Note that I left the UUIDs in
place for those two devices. This was still at Free Geek.

For the journey home again I shut the computer down, and when I got
home, once more it would not boot. So once again I edited fstab and
commented out my lines for Data and Movies, and then it booted. But
that left Data and Movies unmounted, so I mounted them by clicking on
them in the GUI (Nautilus), and when I did so, as before, they were
mounted in Data1 and Movies1. So I unmounted them, uncommented the
lines for them in fstab, and then mounted them from the command line,
and this time they were mounted in /media/jjj/Data and .../Movies.

But my whole purpose of all of this was to get these two devices to
automount when the computer was booted, and to be mounted where I
wanted them mounted. So I started searching the web for 'Ubuntu
automount' and similar things, and finally found the solution.

It turns out the Ubuntu has for a long time included a little GUI
utility called 'Disks' that has some of the features of Gparted. I have
used it in the past to create and label partitions. According to one
helpful fellow on Ubuntu forums, you can use it to edit the mount
options for a partition. When I did so I had the option to turn off
automount (Yes!), specify the mount point, tell it to be mounted at
startup, and even how to identify it. For the latter one of the options
was 'Label=Data' and 'Label=Movies.' When I set up each drive, as I
clicked on OK I noted that the Disks utility added a line to fstab for
the device. Here are the two new lines that it created:

LABEL=Data /media/jjj/Data auto nosuid,nodev,nofail,x-gvfs-show 0 0
LABEL=Movies /media/jjj/Movies auto nosuid,nodev,nofail,x-gvfs-show 0 0

And the best part of all is that it works, and the devices are
automatically mounted where I want them, although boot time is kind of
long now.

So my problem is solved, except that I still want to know why Ubuntu
suddenly decided not to recognize UUIDs. Not that I will ever use one
again, mind you.