Allow custom variables to be defined as 6th parameter on PART #85
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
not a bug
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DiamantTh/installimage!85
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "zytedata/patch-1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
For example the SWRAIDLEVEL can be changed for different partitions:
Not tested yet, done quickly on the Github UI, can test it later.
I had to do many adjustments but now it's working!
With this config file:
I was able to get the first 3 partitions with RAID1 and the last one with RAID0.
NOTE: I changed the logic for the "crypt" part.. before it was just checking if the 5th column had anything, now it must say "yes" to have crypt enabled (it can be changed to any other word, of course).
This is the result after running it on one real server:

hey @asciiprod , what do you think about this?
I have adapted my launch scripts to use my patched version, but it could be better if we can merge it and we just go back to use upstream version.
I'm open to comments!
Was able to create a RAID1+0 flawlessly with #85, thanks!
Cool, glad to hear that, @awsms ! 😊
Would something like this also work?
SWRAID 1
SWRAIDLEVEL 1
PART /boot ext3 1024M
PART lvm vg0 20G
PART lvm vg1 all array_raidlevel=0
LV vg0 root / ext4 20G
LV vg1 swap swap swap 4G
LV vg1 clusterstorage /var/lib/longhorn ext4 all
@lraphael sorry for the delay. Yes, I think it should work, but keep in mind that you need to populate the "encrypt" field before our custom variables.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.