I would like to install the current software (according to the image “Fedora-Workstation-Live-x86_64-34-1.2.iso”) on another system.
I prepared the partitions on the storage device accordingly.
But the installation tool (Blivet GUI?) presented the following information (after I got the impression that the selected configuration setup would be complete enough for the next steps).
Error while checking the storage configuration:
A new file system must be created on the root medium.
The creation of a new file system on your /var partition is recommended.
The creation of a new file system on your /boot partition is recommended.
How can I convince the tool to accept the settings?
I am not sure if it should or shouldn’t but it seems clear that it doesn’t
I have never tested that but it is probably the name of the step. I would expect when it reaches that step it honors what you told it do in blivet. So if you didn’t select that mountpoint to be formatted, it probably doesn’t do so.
Blivet-GUI is a tool from Red Hat that’s extremely effective allowing easy setup for even sophisticated configurations … As a corporate designed tool, no risk, suggested way, hands off just click here and there for knowledgeable people. For custom mount points maybe you’re off the beaten track so dirty hands in the grit using manual configuration with a lot of documentation available … I find that just one logical volume spanning many storage devices with just EFI, boot and Btrfs partition is the way to go, LVM2 for other file systems … Fedora is in the right direction!
I have never had an issue doing a custom install with custom pre-partitioned drives. You simply need to select the partition and set the mount point. If it was not formatted with a file system previously then you also have to allow it to format that partition.
blivet just works that way.
You may have failed to format it when created or to designate the file system type for that partition during install.
I chose settings which looked usable for my needs in principle.
It might be nice if an extra reformatting can eventually be avoided (for two partitions in my case).
I would tolerate such steps if the pending actions would be really consistent for my system configuration requirements.
I got the impression that the software “Anaconda” performs additional safety checks which might trigger questionable side effects here.
Linux is a direct descendant of UNIX BSD going back decades ago still coded in C 89 … sophisticated mount points don’t make sense on everyday devices, simple unique logical partition leaves the system to dynamically sort things out just needing additional EFI and boot partitions. The question is completely different for a high end server leading to development of Btrfs file system, default choice of Fedora … Btrfs sends you to GitHub for up to date documentation, I’m not sure that Blivet-GUI is really a tool of choice for bleeding edge configuration … just tweaking needs hands on approach after or without automatized app configuration.