-
Notifications
You must be signed in to change notification settings - Fork 543
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
How to use all remaining available space on a disk? #2755
Comments
Just adding that I tried this as well with 'percent' and with 'Percent' as unit. Both made archinstall fail before showing the TUI. |
Why not use the Arch install menu to select partitioning and then press the spacebar on the disk you want to use? This is not a bug, it's just pure laziness. Time, research, and the right .config or manually setting up with the menu will get you your answers. |
If you want to use the same configuration to install multiple identical hosts, you value the option to set an option to the desired value in a single config file and avoid human mistakes. |
Hmm maybe try using archinstall to setup and then copy the newely made .config it may have newer settings i dunno im no expert sorry for the way i spoke before |
I would like this option, too, so that we can setup servers with less effort on both virtual and physical platforms. It looks like this ability was removed last September at commit: b141609 |
Which ISO version are you using?
2024-10-01
The installation log
Irrelevant
describe the problem
Description of the issue
I wanted to use archinstall to install a host from scratch with 2 partitions. I found at least one config.json file which suggested I could set the 'size' key of a partition to a value of "100%". Using this value in a config.json with archinstall 2.8.6 results in an error referencing the 'size' key.
I also tried transposing this value into the new config format
... but that also failed. I then settled for using an absolute value in GiB that comes close to what I want to achieve.
I have submitted a PR to update the sample-config.json in the git repo - would make sense to document this option (if it is available) in that file as well, as probably others will want to use such option as well.
The text was updated successfully, but these errors were encountered: