I'm installing Fedora 30 on a system that has an existing linux installation. It is my intention to replace the existing linux.
I'm using custom partitioning.
When exiting the custom partitioning page (click Done) it says that there's an error, but does not elaborate. A second click on done gives me a summary page with three errors (ext4 partitions) and no explanation.
On the installation summary page, "begin installation" is not enabled.
FWIW, the boot loader is UEFI
Thoughts? Advice?
On 4/18/20 7:25 AM, Geoffrey Leach wrote:
When exiting the custom partitioning page (click Done) it says that there's an error, but does not elaborate. A second click on done gives me a summary page with three errors (ext4 partitions) and no explanation.
Isn't there a little bar at the bottom that you can click on for details?
On Sat, 18 Apr 2020 10:07:12 -0700 Samuel Sieb samuel@sieb.net wrote:
On 4/18/20 7:25 AM, Geoffrey Leach wrote:
When exiting the custom partitioning page (click Done) it says that there's an error, but does not elaborate. A second click on done gives me a summary page with three errors (ext4 partitions) and no explanation.
Isn't there a little bar at the bottom that you can click on for details?
There is. Alas, its boilerplate howto, not of much use.
On Sat, 18 Apr 2020 07:25:55 -0700 Geoffrey Leach geoff@hughes.net wrote:
I'm installing Fedora 30 on a system that has an existing linux installation. It is my intention to replace the existing linux.
I'm using custom partitioning.
When exiting the custom partitioning page (click Done) it says that there's an error, but does not elaborate. A second click on done gives me a summary page with three errors (ext4 partitions) and no explanation.
On the installation summary page, "begin installation" is not enabled.
FWIW, the boot loader is UEFI
The EFI partition *has* to be vfat, so that might be your issue. Hard to say without looking over your shoulder. When I installed an EFI system I had to create three extra partitions on the gpt disk before the install worked right. That was a while ago, and the details are vague to me now, but there was a partition for efi, a partition for keeping the disk layout, and a backup mbr partition. A search for EFI and gpt should get you the information. Or maybe someone else has it off the top of their head.
On 4/18/20 1:18 PM, stan via users wrote:
On Sat, 18 Apr 2020 07:25:55 -0700 Geoffrey Leach geoff@hughes.net wrote:
I'm installing Fedora 30 on a system that has an existing linux installation. It is my intention to replace the existing linux.
I'm using custom partitioning.
When exiting the custom partitioning page (click Done) it says that there's an error, but does not elaborate. A second click on done gives me a summary page with three errors (ext4 partitions) and no explanation.
On the installation summary page, "begin installation" is not enabled.
FWIW, the boot loader is UEFI
The EFI partition *has* to be vfat, so that might be your issue. Hard to say without looking over your shoulder. When I installed an EFI system I had to create three extra partitions on the gpt disk before the install worked right. That was a while ago, and the details are vague to me now, but there was a partition for efi, a partition for keeping the disk layout, and a backup mbr partition. A search for EFI and gpt should get you the information. Or maybe someone else has it off the top of their head.
And you have to assign it to "/boot/efi".
On Apr 18, 2020, at 16:19, stan via users users@lists.fedoraproject.org wrote:
That was a while ago, and the details are vague to me now, but there was a partition for efi, a partition for keeping the disk layout, and a backup mbr partition.
For EFI only systems, you only need an EFI volume (fat32) which is typically mounted to /boot/efi, a /boot partition and a root partition (or LVM PV). I’m not sure if you need /boot anymore or if GRUB2 is smart enough to read LVM.
The bios_boot partition is only if you want to use legacy/csm/bios boot on a GPT partitioned disk.
-- Jonathan Billings billings@negate.org
On Sun, Apr 19, 2020 at 6:08 AM Jonathan Billings billings@negate.org wrote:
On Apr 18, 2020, at 16:19, stan via users users@lists.fedoraproject.org wrote:
That was a while ago, and the details are vague to me now, but there was a partition for efi, a partition for keeping the disk layout, and a backup mbr partition.
For EFI only systems, you only need an EFI volume (fat32) which is typically mounted to /boot/efi, a /boot partition and a root partition (or LVM PV). I’m not sure if you need /boot anymore or if GRUB2 is smart enough to read LVM.
GRUB has been able to read LVM metadata for quite a long time; but support hasn't extended to supporting the newer features of LVM including now using the md driver for the backend (same kernel code as mdadm uses), and thin provisioning. So yeah, if it's limited to conventional linear LVM, GRUB can boot off that. In fact it can boot from a degraded mdadm raid6 with LVM on top, even if every drive is LUKS encrypted. (LUKS1 for now, LUKS2 support on the way). Also directly supports Btrfs booting, with all the supported compression types, raid5/6 even degraded, and the latest raid1c3 and raid1c4. It's no doubt a long list of things it can't support, but I would not be surprised if the supported list is way longer.
Funny enough one thing it doesn't support, and would be difficult to support, is journal replay following a crash. There are cases where if journal replay doesn't happen, the file system metadata doesn't have a correct view of its own state, so boot can fail. Whereas after journal replay, it'll work. Hence, the importance of making the last critical bootloader change atomic, so that there's always a fallback. This was improved quite a lot with recent BLS by default work.
-
Chris Murphy -
Geoffrey Leach -
Jonathan Billings -
Samuel Sieb -
stan