fedora-kickstarts

Clone
Source Code
GIT

#69 move arm boot partition back to ext4 from ext3
Closed 7 years ago by pbrobinson. Opened 7 years ago by socminarch.
socminarch/fedora-kickstarts master  into  master

file modified
+1 -1 
@@ -8,7 +8,7 @@ 
 

  bootloader extlinux
 

  

  part /boot/fw --size=30 --fstype vfat --asprimary
 

- part /boot --size=512 --fstype ext3 --asprimary
 

+ part /boot --size=512 --fstype ext4 --asprimary --mkfsoptions="-O ^64bit,^metadata_csum"
 

  part swap --size=512 --fstype swap --asprimary
 

  part / --size=3584 --fstype ext4 --asprimary

file modified
+1 -1 
@@ -1,6 +1,6 @@ 
 

  %include fedora-arm-base.ks
 

  

- part /boot --size=512 --fstype ext3
 

+ part /boot --size=512 --fstype ext4 --mkfsoptions="-O ^64bit,^metadata_csum"
 

  part swap --size=256 --fstype swap
 

  part / --size=1279 --fstype ext4

Switch the boot filesystem back to ext4 from ext3

64bit and metadata_csum have to be disabled for u-boot to work

NAK. There's issues with ext4 and 64bit features enabled by default that stops it from booting.

helps if I look properly at the patch. There's also upstream movement in u-boot to fix this issue

has this had any testing? I am not sure that appliance-creator knows how to pass on the options

The fix is taken from the cloud Kickstart's. Surely they'd also be using appliance-creator?

The fix is taken from the cloud Kickstart's. Surely they'd also be using appliance-creator?

No, they use imagefactory, completely different codebase.

Sorry, my mistake

Right, so u-boot 2016.11 has a proper fix for this. I've done a PR for f-26 now it's there. Reviewing the proper fix for F-25

Pull-Request has been closed by pbrobinson
7 years ago
Metadata
None
No Tags
Changes Summary 2
+1 -1
file changed
fedora-arm-base.ks
+1 -1
file changed
fedora-arm-minimal.ks
Powered by Pagure 5.14.1
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.