From: unruh@invalid.ca
On 2017-05-16, Carlos E. R. wrote:
> On 2017-05-16 07:00, Sidney_Kotic wrote:
>> Sorry for the length. The examples are strange, 3 different computers
>> with 3 different post boot /dev layouts. Maybe I'm just over
>> complicating things.
>>
>>> Why did you think that fstab would be modified by login?
>>
>> I would think not. Part of the fstab looks like this:
>> UUID=c9b1c553-03b5-406d-bd1e-7591aa0c659f swap swap defaults
>> 0 0
>> UUID=ee9017b6-622c-42b9-b42e-f6a77981f1a7 / btrfs defaults
>> 0 0
>> UUID=ee9017b6-622c-42b9-b42e-f6a77981f1a7 /boot/grub2/i386-pc
>> btrfs subvol=@/boot/grub2/i386-pc 0 0
>>
>> Which is OK, a df says this:
>> /dev/sda7 41G 24G 15G 62% /
>> /dev/sda7 41G 24G 15G 62% /.snapshots
>> /dev/sda7 41G 24G 15G 62% /var/lib/mariadb
>> ...
>> /dev/sdb1 3.7T 2.7T 1.1T 72% /run/media/sidney/4TB
>>
>> Which should be swell, but sometimes during the boot process it takes
>> /dev/sdb and uses it instead of /dev/sda.
No idea what that means. Uses it for what? Booting-- but I assume you
have your boot on UUID not disk name.
>
> which the reason that you should not use names like /dev/sda on fstab.
> Instead you use UUID or LABEL.
He says he has UUID in fstab above.
>
>
>> Will tell me where the USBs are (mounted in this case), and then I can
>> use the after.local to mount the device on a known mount point. I'm not
>> sure what to put into the fstab, especially since things seem to change
>> during the boot process.:
>
> For instance:
>
> LABEL=PNY16GB /mnt/something auto lazytime,nofail 1 1
>
> or
>
> UUID=740C30A17C89431B /mnt/something auto lazytime,nofail 1 1
>
Yup.
>
>
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
