f41 install to usb-disk can boot, but f42 install to usb-disk not find boot item
Your USB disk probably isn’t your “first” disk. Is it possible you are hitting some variation of this bug?
Does it work if you boot both the installer and the installed system in UEFI mode? You should be able to disable “legacy” mode in your BIOS settings. Also, I like to use the F12 key when booting to bring up the BIOS boot menu and make sure that I select the UEFI boot option.
@xiaguangbo please use the command sudo parted -l in terminal and paste the output here as pre-formatet text </> . Important is that all the devices you want to use are connected when doing the command.
This way we can see if you use the correct partition table and if you have an EFI partition to boot from.
2 Likes
sda is f41(can boot), sdc is f42(can’t boot)
$ sudo parted -l
Model: NVME USB 3.2 (scsi)
Disk /dev/sda: 256GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 630MB 629MB fat32 EFI System Partition boot, esp
2 630MB 1704MB 1074MB ext4 bls_boot
3 1704MB 256GB 254GB btrfs
Model: JMicron Tech (scsi)
Disk /dev/sdc: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: pmbr_boot
Number Start End Size File system Name Flags
1 1049kB 2097kB 1049kB bios_grub
2 2097kB 1076MB 1074MB ext4 bls_boot
3 1076MB 256GB 255GB btrfs
Model: Unknown (unknown)
Disk /dev/zram0: 8590MB
Sector size (logical/physical): 4096B/4096B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 8590MB 8590MB linux-swap(v1)
I use vmware run f42.iso, install f42 to usb-disk, f41 usb-disk also like this
sda appears to be configured for UEFI boot (it has an “EFI System Partition”), but sdc does not have its own EFI System Partition.
I would try disconnecting or disabling sda before installing F42 on the other disk. Also, be sure you select UEFI mode when booting the system (I’m not sure how that is done with vmware).
You should be able to re-enable sda after the installation is finished and then have the option to select which disk to boot on system startup.
I remember encountering the issue of the EFI partition disappearing before—it was because VMware defaults to BIOS mode instead of UEFI.
1 Like
It is also possible that the Anaconda installer is seeing the EFI System Partition on the first disk and trying to “share” it for both disks. The best way to be sure it doesn’t do that is to disable the first disk before attempting the installation on the second disk.
When running the image installer in VMware, you might select multiple hard disks during the disk selection step—but you should only check the one you actually intend to use. Is that what you mean?
2 Likes
You can also manually partition and select which partitions you want to use.
yes yes
The second Disk has this Disk Flag above and a partition flag like bls_boot? This I never saw on my installations. Is this something from vmware?
bios_grub sounds as it is legacy boot. Can it bee that you miss the boot flag on that partition?
vmware defalut use BIOS，install systeam also use BIOS mode，need manually change to UEFI
is ok，manully change vmware setup the BIOS to UEFI
2 Likes