New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: "The flag 'boot' is not available for loop disk labels" #2363
Comments
I fixed this by creating a new GPT table with fdisk |
The Chosen configuration section of the log shows the manual partitioning option is being used to install to the device
Examining the Disk states before installing section of the log, the device you are installing to is set up as a partitionless disk.
It is not possible to add partitions without there being a partition table. What happens is a |
IIRC I tried to create an empty GPT table at some point. Or maybe not; I'm not a 100% sure since this was some weeks ago (in the end I just installed Arch manually). I did try some stuff, but all without getting Archinstall to run successfully. In any case, shouldn't Archinstall just create a GPT table when partitioning a disk in the case one does not already exist on a disk? |
My conclusion is based on the log. In the Disk states before installing section of the log the I have also verified my conclusion in reproducing the issue.
I think this scenario should be handled while warning the user that a file system signature was detected and it will be removed. @svartkanin, would you mind reopening the issue? Thank you. |
When trying to install, I get the following error when the install script is partitioning my NVMe SSD:
Complete log:
The text was updated successfully, but these errors were encountered: