Re: Does the installer detects when a distro have already created BLS?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 24/05/2020 19:56, Paul Dufresne via devel wrote:
> "These directories are defined below the placeholder file system $BOOT. This placeholder file system shall be determined during installation time, and an fstab entry for it shall be created mounting it to /boot. The installer program should pick $BOOT according to the following rules:
> 
>     If the OS is installed on a disk with MBR disk label, and a partition with the MBR type id of 0xEA already exists it should be used as $BOOT.
>     Otherwise, if the the OS is installed on a disk with MBR disk label, a new partition with MBR type id of 0xEA shall be created, of a suitable size (let's say 500MB), and it should be used as $BOOT.
>     If the OS is installed on a disk with GPT disk label, and a partition with the GPT type GUID of bc13c2ff-59e6-4262-a352-b275fd6f7172 already exists, it should be used as $BOOT.
>     Otherwise, if the OS is installed on a disk with GPT disk label, and an ESP partition (i.e. with the GPT type UID of c12a7328-f81f-11d2-ba4b-00a0c93ec93b) already exists and is large enough (let's say 250MB) and otherwise qualifies, it should be used as $BOOT.
>     Otherwise, if the OS is installed on a disk with GPT disk label, and if the ESP partition already exists but is too small, a new suitably sized (let's say 500MB) partition with GPT type GUID of bc13c2ff-59e6-4262-a352-b275fd6f7172 shall be created and it should be used as $BOOT.
>     Otherwise, if the OS is installed on a disk with GPT disk label, and no ESP partition exists yet, a new suitably sized (let's say 500MB) ESP should be created and should be used as $BOOT.
> 
> "

<various snips>
> One of the first problem I have, is /boot have not the correct GUID for
> BLS:
> 
> [paul@localhost /]$ cat /etc/fstab
> 
> #
> # /etc/fstab
> # Created by anaconda on Sun May 24 11:48:45 2020
> #
> # Accessible filesystems, by reference, are maintained under '/dev/disk/'.
> # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more
> info.
> #
> # After editing this file, run 'systemctl daemon-reload' to update systemd
> # units generated from this file.
> #
> /dev/mapper/myLVM-fedoraMain              /     ext4 defaults        1 1
> UUID=4a82a496-5316-4aca-9d27-8376197c8a6d /boot ext4 defaults        1 2
> UUID=62BD-AFFC             /boot/efi vfat umask=0077,shortname=winnt 0 2
> /dev/mapper/myLVM-fedoraSwap              none  swap defaults        0 0
> [paul@localhost /]$
> 
> Reading the BLS, it seems the installer did not generated a valid entry
> /boot... not the valid type (vfat, EFS)... nor a valid UUID.
> 
> Oh well, the other way of saying it is the installer did not force me to
> generate a valid /boot partition.
> 
> I have:
> 
> [paul@localhost /]$ sudo parted /dev/sda -- print
> [sudo] Mot de passe de paul :
> Modèle : ATA ST500LM021-1KJ15 (scsi)
> Disque /dev/sda : 500GB
> Taille des secteurs (logiques/physiques) : 512B/4096B
> Table de partitions : gpt
> Drapeaux de disque :
> 
> Numéro  Début   Fin    Taille  Système de fichiers Nom                  
> Drapeaux
>  1      1049kB  268MB  267MB   ext4
>  2      269MB   479MB  210MB fat16                                     
> démarrage, esp
>  3      479MB   701MB  222MB   fat16                EFI System
> Partition  démarrage, esp
>  4      701MB   194GB 193GB                                             
> lvm

Aside from the other stuff people have explained elsewhere, you're
conflating two different UUIDs/GUIDs here. The partition *type* UUID is
what's specified in the BLS etc., and everybody's EFI partition will
have the same partition type UUID, everybody's /boot partition (if
present) should have the same UUID, etc. It's what's translated by
parted and the like into 'ext4', 'fat16', etc., rather than displaying
the 36 character or so string.

But the just-*partition* UUID is for identifying that particular
partition, to distinguish it from any other, and no two should ever be
the same (this has bitten me a few times when cloning disks). And on top
of that, there's often also a filesystem UUID, which should also never
be the same (and has also bitten me a few times when dd'ing partition
images).

Either of the latter two can be used in fstab to identify that
particular partition, I believe much more commonly the filesystem UUID,
and that's what you see in your fstab there, rather than the partition
type UUID. So there's nothing to worry about with it not looking
anything like the BLS partition type UUIDs.

(Apologies if the formatting goes pear-shaped, I tried tidying up the
quotes a bit.)

-- 
J. Randall Owens | http://www.GhiaPet.net/

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux