Installer option created unbootable installation #3334
Labels
Milestone
Comments
|
According to #2294 (comment) it is fixed in 4.0-rc4+. For 3.2 it is still an issue and should be addressed in 3.2.1. |
marmarek
added a commit
to marmarek/qubes-installer-qubes-os
that referenced
this issue
Mar 27, 2018
setDefaultPartitioning is called when executing kickstart "autopart" command - which is the case if one choose to not change disk partitioning. But in manual partitioning there is also an option to start with automatic layout and in that case setDefaultPartitioning isn't called at all. Which results in failed partitioning (missing '/' and bootable partition). Similar thing is already fixed in master commit 378cfc4. QubesOS/qubes-issues#2294 Fixes QubesOS/qubes-issues#3334
|
This issue is being closed because:
If anyone believes that this issue should be reopened, please let us know in a comment here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Qubes OS version:
Failed on both 3.2 and 4.0R2
Steps to reproduce the behavior:
In the installer part where you select which disks you want to install to,
change from lvm to the BtrFs option in the combobox.
Continue creating your partitions as normal.
Expected behavior:
A bootable OS.
Actual behavior:
A underline-cursor on a black screen immediately after bios screen. We never see the boot-loader.
It looks like this is an unfinished feature that nobody supports / owns. Much like #3327, maybe this option should just be removed?
The text was updated successfully, but these errors were encountered: