Bug 1278260
| Summary: | F23 kickstart fails with "Kickstart file /run/install/ks.cfg is missing." and ENOSPC errors | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Saalwaechter <saalwaechter> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 23 | CC: | anaconda-maint-list, gansalmon, g.kaviyarasu, gordon.messmer, itamar, jonathan, kernel-maint, madhu.chinakonda, marhag87, marianne, mchehab, posti_roska, redhat-bugzilla, saalwaechter, vanmeeuwen+fedora, volcanowill | ||||
| Target Milestone: | --- | Flags: | saalwaechter:
needinfo-
|
||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-10-26 16:53:44 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
John Saalwaechter
2015-11-05 06:22:54 UTC
Related to #1259506 perchance? I do not think this is related to https://bugzilla.redhat.com/show_bug.cgi?id=1259506 because in my case I don't have %include in my ks file. In fact it seems that the contents of the ks file don't matter at all. I'm testing with a ks file that is just a couple comment lines. If I use the PAE kernel instead of the non-PAE one, then my kickstart works.
I was booting with fedora/releases/23/Server/i386/os/images/pxeboot/{vmlinuz,initrd.img}, and that resulted in the ENOSPC problems. Switching to fedora/releases/23/Server/i386/os/images/pxeboot/{vmlinuz-PAE,initrd-PAE.img} resulted in a working kickstart.
I used "rd.debug rd.break=pre-mount", and I found that the ramdisk had 352KB free at that point when I used the PAE kernel. The rootfs itself was size=485716k.
Reassigning to kernel based on comment 3. I wouldn't expect the ramdisk to have a different size between PAE and non-PAE at that amount of memory. I'm not sure this is a kernel issue per se. Seems more that space is so tight that the difference between PAE and non-PAE is enough to run out of space. Here's more details from my system. Booting with the PAE kernel/initrd: rootfs on / type rootfs (rw,size=485716k,nr_inodes=121429) Booting with non-PAE kernel/initrd: rootfs on / type rootfs (rw,size=485400k,nr_inodes=121350) A difference of 485716k - 485400k = 316k Unpacking the initrd.img and initrd-PAE.img files with "/usr/lib/dracut/skipcpio initrd.img | xzcat| cpio -dimv", the lib/modules non-PAE files are 1172k larger than the PAE files. Is there a way to explicitly control the size of the rootfs? I tried using the ramdisk_size kernel parameter, but it seemed to not have an effect. Ah, explicitly using ramfs, which has no size limit, solved the problem reported in this bug. That is, I was able to install with the non-PAE kernel/initrd by using "rootfstype=ramfs". Guys, after trying x86_6p Final DVD many hours, the only way I can get F23 anaconda with kickstart to work is to: - boot the installation media - edit the boot option to contain inst.ks=cdrom:myfile.ks or inst.ks=http://myfile.ks #these need to really point to a correct file - Anaconda always fails with message "Kickstart file /run/install/ks.cfg is missing.". - switch to console, and cp /run/install/repo/myfile.ks /run/install/ks.cfg - use fdisk (or some other tool) to wipe the disk partitions - type command /sbin/anaconda Quite pain in the ass to do this always, but it's still better than not be able to use your kickstart file. Same issue here with PXE install in x86_64 bits error message is "Kickstart file /run/install/ks.cfg is missing" *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs. Fedora 23 has now been rebased to 4.7.4-100.fc23. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. For reference if people find this bug report: 1GB of RAM is no longer sufficient to install some products, such as CentOS 7.3 (and presumably RHEL 7.3), and Fedora 23 by the looks of it. In earlier installers, the rootfs ram filesystem was not limited, so it provided as much space as total system memory - allocated memory. If too much data was written to the filesystem (in /tmp, for example), the kernel would panic. Newer installers limit the size of the filesystem to 50% of system memory. On a system with only 1GB of memory, the root filesystem will be too small to run the installer. There was a same bug report under CentOS 7.3 KS install: https://bugzilla.redhat.com/show_bug.cgi?id=1408882 |