Quasi sempre. Capitava che lo saltasse, ma era abbastanza raro.
Ecco:
#1
[root@localhost-live ~]# fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 840
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B07BFC85-C7AA-4613-B686-41127F2B1252
Device Start End Sectors Size Type
/dev/sda1 2048 976895 974848 476M EFI System
/dev/sda2 976896 2928639 1951744 953M Linux filesystem
/dev/sda3 2928640 976769023 973840384 464.4G Linux filesystem
Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Hitachi HDS72404
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 8A18345F-0873-4C5D-BDF2-CF6ED22796D2
Device Start End Sectors Size Type
/dev/sdb1 2048 7814035455 7814033408 3.7T Linux filesystem
Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: Hitachi HDS72404
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5D16ADFF-A28D-410F-A5F8-4D5F50B19FF4
Device Start End Sectors Size Type
/dev/sdc1 2048 7814035455 7814033408 3.7T Linux filesystem
Disk /dev/sdd: 7.5 GiB, 8029470208 bytes, 15682559 sectors
Disk model: Cruzer
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x4985011e
Device Boot Start End Sectors Size Id Type
/dev/sdd1 * 0 3691935 3691936 1.8G 0 Empty
/dev/sdd2 172 20119 19948 9.8M ef EFI (FAT-12/16/32)
/dev/sdd3 20120 62103 41984 20.5M 0 Empty
Disk /dev/loop0: 1.7 GiB, 1788923904 bytes, 3493992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 6.4 GiB, 6817841152 bytes, 13316096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/live-rw: 6.4 GiB, 6817841152 bytes, 13316096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/live-base: 6.4 GiB, 6817841152 bytes, 13316096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[root@localhost-live ~]#
poi:
#2
[root@localhost-live ~]# parted -l
Model: ATA Samsung SSD 840 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 500MB 499MB fat16 EFI System Partition boot, esp
2 500MB 1499MB 999MB ext4
3 1499MB 500GB 499GB ext4
Model: ATA Hitachi HDS72404 (scsi)
Disk /dev/sdb: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 4001GB 4001GB btrfs
Model: ATA Hitachi HDS72404 (scsi)
Disk /dev/sdc: 4001GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 4001GB 4001GB btrfs
Model: SanDisk Cruzer (scsi)
Disk /dev/sdd: 8029MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 88.1kB 10.3MB 10.2MB primary fat16 esp
Warning: Unable to open /dev/sr1 read-write (Read-only file system). /dev/sr1
has been opened read-only.
Error: /dev/sr1: unrecognised disk label
Model: Unknown (unknown)
Disk /dev/sr1: 25.2MB
Sector size (logical/physical): 2048B/2048B
Partition Table: unknown
Disk Flags:
[root@localhost-live ~]#
indi:
#3
[root@localhost-live ~]# blkid
/dev/sdd1: UUID="2019-04-26-02-16-46-00" LABEL="Fedora-KDE-Live-30-1-2" TYPE="iso9660" PTUUID="4985011e" PTTYPE="dos" PARTUUID="4985011e-01"
/dev/sda1: SEC_TYPE="msdos" LABEL_FATBOOT="boot-efi" LABEL="boot-efi" UUID="8346-825C" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="f5b42f40-91f9-40ba-9b16-1eefd598f85a"
/dev/sda2: LABEL="boot" UUID="a5a7201c-b4a0-4bf3-a630-969d639a67df" TYPE="ext4" PARTUUID="9708bc4e-b954-40e9-a5af-e520b37b7a8c"
/dev/sda3: LABEL="root" UUID="9c2e31ca-9455-4337-b054-4b7d86086081" TYPE="ext4" PARTUUID="42d59b53-eda8-43f9-aa5e-72ad6d08c9cc"
/dev/sdb1: LABEL="giampaolo-ws" UUID="1690e979-2773-4cbe-af41-e028f89b969c" UUID_SUB="292c5537-56a2-4909-81a5-d4062d8bef1d" TYPE="btrfs" PARTUUID="becbe8b5-f00b-46e7-b481-495e2b243d59"
/dev/sdc1: LABEL="giampaolo-ws" UUID="1690e979-2773-4cbe-af41-e028f89b969c" UUID_SUB="37d22457-00ef-490b-89c6-bceff2fdeda0" TYPE="btrfs" PARTUUID="3df06bfe-c554-4096-b312-f5c119634a65"
/dev/sr1: UUID="2008-05-06-12-26-42-" LABEL="U3 System" TYPE="iso9660"
/dev/sdd2: SEC_TYPE="msdos" LABEL_FATBOOT="ANACONDA" LABEL="ANACONDA" UUID="A017-9B2F" TYPE="vfat" PARTUUID="4985011e-02"
/dev/sdd3: UUID="e114322d-8bf1-32e2-b5a1-e0473f3122d3" LABEL="ANACONDA" TYPE="hfsplus" PARTUUID="4985011e-03"
/dev/loop0: TYPE="squashfs"
/dev/loop1: LABEL="Anaconda" UUID="e7d44174-86fb-4f96-b5eb-d2f82e280b10" TYPE="ext4"
/dev/mapper/live-rw: LABEL="Anaconda" UUID="e7d44174-86fb-4f96-b5eb-d2f82e280b10" TYPE="ext4"
/dev/mapper/live-base: LABEL="Anaconda" UUID="e7d44174-86fb-4f96-b5eb-d2f82e280b10" TYPE="ext4"
/dev/pktcdvd/pktcdvd1: UUID="2008-05-06-12-26-42-" LABEL="U3 System" TYPE="iso9660"
[root@localhost-live ~]#
infine:
#4
[root@localhost-live ~]# efibootmgr -v
EFI variables are not supported on this system.
[root@localhost-live ~]#
[quote=bebo_sudo]
Una volta controllati questi valori, entreremo in un chroot e verificheremo lo stato dei pacchetti di grub e efi, e infine riconfigureremo grub.
(sto seguendo quanto suggerito da arkanoid qua, giusto per ricordarmi https://forum.fedoraonline.it/viewtopic.php?pid=244113#p244113 )[/quote]
Grazie. A prima vista non mi sembrava di capirci molto, ma lo guardo meglio.
Post scriptum
Una cosa che non ho capito è questa:
http://static.kjuicer.com/G/tmp/photo_2019-08-26_08-10-48.jpg
Edit: http://static.kjuicer.com/G/tmp/photo_2019-08-26_08-10-48.jpg perchè non la mostra sempre (dalla live si ma dal laptop no).
Cosa ci fa un boot Anaconda là in mezzo? Passi che siano tutti doppi (anche il fatto che ci siano versione Uefi, e non Uefi, un pochino mi lascia perplesso), ma è possibile che Anaconda, che poi è una Ide che uso per i virtual environment e in passato per sviluppare su Python, abbia installato un suo boot loader?
(Anche il SEC_TYPE=“msdos” sulla SSD mi sembra strano. Questa macchina non ha mai visto Windows.)