[ubuntu-za] Problems with fstab

Bill Cairns cairnsww at gmail.com
Mon Jun 15 07:42:03 UTC 2020


Hi Wesley,

Thanks for your reply.

I hope that I am talking sense here. (I am sometimes not sure that I am
using the right terminology.) Going back in time, I started with only the
hard disk which is now sda. I had boot, the OS, and everything else on it.
Then after a couple of years I added the ssd - now sba. Now I have
installed the OS on the ssd, but I still boot from my hard drive. (That is,
when I did the install, I specified '/' as being on sb2.) It seems to work
very well except for this problem of not being able to use fstab to specify
where /home is.

At the moment, I am manually mounting /home after startup. Again, it all
works well except that I have two /home directories - one on the ssd and
the one that I use.

Bill

On Mon, 15 Jun 2020 at 02:17, Wesley Werner <wesley.werner at gmail.com> wrote:

> Hi Bill
>
> You said the boot drive is sda1, but your SSD disk lists as sdb2
> (UUID=2e740efb). Perhaps the BIOS is booting the wrong drive?
>
> --
> Regards
> Wesley Werner
>
>
> On Mon, Jun 15, 2020 at 1:03 AM Bill Cairns <cairnsww at gmail.com> wrote:
>
>> I tried looking at the drive before mounting it as /home and this is what
>> it looks like with mount -v (I asked nautilus to mount the '960 Gb drive')
>> /dev/sda6 on /media/bill/b7092661-c008-4beb-9cdc-06c3dd036181 type ext4
>> (rw,nosuid,nodev,relatime,uhelper=udisks2)
>>
>> I can access it quite happily that way too.
>>
>> On Sun, 14 Jun 2020 at 16:19, Bill Cairns <cairnsww at gmail.com> wrote:
>>
>>> Thanks for your reply Paolo. I confess that I am not quite sure what I
>>> should be looking for. The mount -v gives me:
>>> /dev/sda6 on /home type ext4 (rw,relatime)
>>> While /proc/mounts has
>>> /dev/sda6 /home ext4 rw,relatime 0 0
>>>
>>> That would seem the same, but I am not sure I am looking at the right
>>> things.
>>>
>>> This is the ssd with the OS from mount -v:
>>> /dev/sdb2 on / type ext4 (rw,noatime,errors=remount-ro)
>>> and from /proc/mounts:
>>> /dev/sdb2 / ext4 rw,noatime,errors=remount-ro 0 0
>>>
>>>
>>> On Sat, 13 Jun 2020 at 22:34, Paolo Gigante <paolo.gigante.sa at gmail.com>
>>> wrote:
>>>
>>>> Not that it should cause a crash but are you sure its an ext4
>>>> filesystem on that device?
>>>> If the mount command works, you may want to try 'mount -v' to see what
>>>> mount is actually doing. Once you have used the mount command to attach the
>>>> FS, does the entry look like in /proc/mounts
>>>>
>>>> On Sat, Jun 13, 2020 at 2:38 PM Bill Cairns <cairnsww at gmail.com> wrote:
>>>>
>>>>> Boot is on the hard drive - sda1
>>>>>
>>>>>
>>>>> On Sat, 13 Jun 2020 at 15:30, Frans de waal <meesterarend at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Just a thought... What is the boot drive in the bios?
>>>>>>
>>>>>> On Sat, 13 Jun 2020 at 15:10, Bill Cairns <cairnsww at gmail.com> wrote:
>>>>>>
>>>>>>> Hello everybody,
>>>>>>>
>>>>>>> I am trying to run 20.04 with my OS on an SSD device and my home
>>>>>>> directory on my old hard drive.
>>>>>>>
>>>>>>> This mount command works perfectly:
>>>>>>> sudo mount UUID=b7092661-c008-4beb-9cdc-06c3dd036181 /home
>>>>>>>
>>>>>>> However, when I try to do the same thing in fstab -
>>>>>>> # /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/sdb2 during installation
>>>>>>> UUID=2e740efb-b15b-4bea-9ef8-a20dd7a87186 /         ext4
>>>>>>>  noatime,errors=remount-ro 0       1
>>>>>>> # swap was on /dev/sda5 during installation
>>>>>>> UUID=1c5e43a0-097c-4d68-90df-e544497323dd none            swap    sw
>>>>>>>              0       0
>>>>>>> #
>>>>>>> # Home is on sda6. Added 2020-06-13
>>>>>>> #
>>>>>>> UUID=b7092661-c008-4beb-9cdc-06c3dd036181 /home ext4
>>>>>>> nodev,nosuid,relatime  0  2
>>>>>>>
>>>>>>> The system crashes rather badly and says 'You are now in emergency
>>>>>>> mode' or something equivalent. (And I have no idea how to do anything in
>>>>>>> emergency mode!)
>>>>>>>
>>>>>>> I have used the example in https://help.ubuntu.com/community/Fstab
>>>>>>> (changing the UUID of course).
>>>>>>>
>>>>>>> I am sure that I am missing something very simple. Can anyone help
>>>>>>> please?
>>>>>>>
>>>>>>> Thanks, keep safe,
>>>>>>>
>>>>>>> Bill
>>>>>>>
>>>>>>> --
>>>>>>> ubuntu-za mailing list
>>>>>>> ubuntu-za at lists.ubuntu.com
>>>>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>>>>>>>
>>>>>> --
>>>>>> ubuntu-za mailing list
>>>>>> ubuntu-za at lists.ubuntu.com
>>>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>>>>>>
>>>>> --
>>>>> ubuntu-za mailing list
>>>>> ubuntu-za at lists.ubuntu.com
>>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>>>>>
>>>> --
>>>> ubuntu-za mailing list
>>>> ubuntu-za at lists.ubuntu.com
>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>>>>
>>> --
>> ubuntu-za mailing list
>> ubuntu-za at lists.ubuntu.com
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>>
> --
> ubuntu-za mailing list
> ubuntu-za at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-za
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-za/attachments/20200615/6fe222eb/attachment.html>


More information about the ubuntu-za mailing list