: Sunday, November 17, 2019 9:33 PM
To: PLUG
Subject: [PLUG] What could cause /home partition not to be found
OK, y'all who tell me I must do a clean install can be happy.
At the Clinic today I tried to do a dist-upgrade from Xubuntu 16.04-6 to 18.04.
After massive efforts we failed due
There's a chance your /boot partition already does something like this:
https://www.thegeekdiary.com/centos-rhel-how-to-mount-file-systems-using-uuid/
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Sunday, November 17, 2019 10:36 PM, Reid wrote:
> > And I absolutely
> And I absolutely hate the Linux system of assigning letters to drives as it
> finds them so you can never be sure what you're dealing with.
Are you able to use UUIDs in fstab instead? UUIDs don't change between boots.
You can run `blkid ` to find the UUID.
Sent with ProtonMail Secure
OMG I fixed it (sort of)!
I unplugged the USB cable leading to the external USB drive (Movies)
and rebooted And here I am!
Thanks to all for listening to my wails of woe :)
___
PLUG mailing list
PLUG@pdxlinux.org
On Mon, 18 Nov 2019 05:58:30 +
Reid dijo:
>> I also noticed an error message that it could not mount Synology
>
>While this could be due to a number of issues (e.g., inability to
>connect to the NFS server or find the export there), I'm suspicious
>about your mount point
> I also noticed an error message that it could not mount Synology
While this could be due to a number of issues (e.g., inability to connect to
the NFS server or find the export there), I'm suspicious about your mount point
"/media/jjjSynology". Are the three j's supposed to be there?
- Reid
You have an extra field in your fstab line for /home.
/dev/sdb2 / /home ext4 defaults 0 2
Should be:
/dev/sdb2 /home ext4 defaults 0 2
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Sunday, November 17, 2019 9:49 PM, John Jason Jordan wrote:
> > On this computer
>On this computer /dev/sdb is a 512GB SSD with two partitions, / of 50GB
>and /home of 400GB (dev/sdb2). Of course, /home has tons of config
>files for software, so failing to boot the GUI without a /home folder
>is understandable. But why would the OS suddenly be unable to
>find /home?
Aha! I
OK, y'all who tell me I must do a clean install can be happy.
At the Clinic today I tried to do a dist-upgrade from Xubuntu 16.04-6
to 18.04. After massive efforts we failed due to the Update Manager
being unable to find files. When I got home I tried again, and this
time the update sailed
