-
Notifications
You must be signed in to change notification settings - Fork 60
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
configure to create a partition after root partition on primary disk is ignored (only affects s390x) #1358
Comments
@jschintag or @LakshmiRavichandran1 - can you take a look at this? |
I can take a look at it, but I won't get to it before Christmas vacation... |
Wait, looking closer at the issue, |
I think maybe part of the problem is that our try adding |
Er,yes,the new partition is created and mounted, really sorry for the false alarm noise.
|
So what i know is that the partition number 3 and 4 for root and boot partitions are hardcoded in our build script. I think (but i'm not sure) what is happening is that GRUB uses the first 2 partitions on other arches, whereas on s390x we use zipl instead. |
Describe the bug
I'm following this page[1] to set up /var on a separate partition on the same primary disk,but it failed on s390x system
[1]https://docs.fedoraproject.org/en-US/fedora-coreos/storage/#_setting_up_separate_var_mounts
FYI:
1)I also tried Adding a /var/lib/containers partition to the primary disk,also failed.
2)remove the filesystems part of the bu file also failed.
3) change /dev/disk/by-partlabel/var to /dev/vda also failed.
Reproduction steps
Run the following command line:
Expected behavior
Actual behavior
System details
fedora-coreos-37.20221127.1.0-qemu.s390x.qcow2
Ignition config
Additional information
journal: https://lnie.fedorapeople.org/varjournal
The text was updated successfully, but these errors were encountered: