Hide Forgot
System: FC 22 i686 PAE Kernel 4.4.4-200 does not boot on all systems. Both kernels 4.4.4. and 4.4.3 do not boot, with the same errormessage: The bootprocess stopped with "/sbin/init: Bad Exec Format'" while reinstalling the kernel i got this : Löschen : kernel-PAE-core-4.4.4-200.fc22.i686 4/4 Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]_EARLY!=y Überprüfung läuft: kernel-PAE-4.4.4-200.fc22.i686 ... grub.conf: title Fedora (4.4.4-200.fc22.i686+PAE) 22 (Twenty Two) root (hd0,0) kernel /boot/vmlinuz-4.4.4-200.fc22.i686+PAE ro root=UUID=dca7eea1-687e-476a-a9a0-c41ef0329113 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=de_DE.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=de-latin1 initrd /boot/initramfs-4.4.4-200.fc22.i686+PAE.img title Fedora (4.4.3-201.fc22.i686+PAE) 22 (Twenty Two) root (hd0,0) kernel /boot/vmlinuz-4.4.3-201.fc22.i686+PAE ro root=UUID=dca7eea1-687e-476a-a9a0-c41ef0329113 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=de_DE.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=de-latin1 initrd /boot/initramfs-4.4.3-201.fc22.i686+PAE.img Dracut is version 14.fc22 Things i tried out with not success: - reinstalling systemd - reinstalling kernel and kernel-core 4.4.4-200 INFOS: This happend TODAY on one ( i stopped trying it on more ) server: Pakete werden heruntergeladen: (1/2): kernel-PAE-4.4.4-200.fc22.i686.rpm 685 kB/s | 78 kB 00:00 (2/2): kernel-PAE-core-4.4.4-200.fc22.i686.rpm 9.7 MB/s | 20 MB 00:02 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Gesamt 6.3 MB/s | 20 MB 00:03 Transaktionsüberprüfung wird ausgeführt Transaktionsprüfung war erfolgreich. Transaktion wird getestet Transaktionstest war erfolgreich. Transaktion wird ausgeführt Neuinstallieren : kernel-PAE-core-4.4.4-200.fc22.i686 1/4 Neuinstallieren : kernel-PAE-4.4.4-200.fc22.i686 2/4 Löschen : kernel-PAE-4.4.4-200.fc22.i686 3/4 Löschen : kernel-PAE-core-4.4.4-200.fc22.i686 4/4 Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]_EARLY!=y Überprüfung läuft: kernel-PAE-4.4.4-200.fc22.i686 1/4 Überprüfung läuft: kernel-PAE-core-4.4.4-200.fc22.i686 2/4 Überprüfung läuft: kernel-PAE-4.4.4-200.fc22.i686 3/4 Überprüfung läuft: kernel-PAE-core-4.4.4-200.fc22.i686 4/4 Reinstalliert: kernel-PAE.i686 4.4.4-200.fc22 kernel-PAE-core.i686 4.4.4-200.fc22 Komplett!
CPU of the hostsystem: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 60 model name : Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz stepping : 3 cpu MHz : 3300.060 cache size : 8192 KB physical id : 3 siblings : 1 core id : 0 cpu cores : 1 apicid : 3 initial apicid : 3 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu de tsc msr pae mce cx8 apic sep mtrr mca cmov pat clflush acpi mmx fxsr sse sse2 ss ht nx constant_tsc nonstop_tsc aperfmperf pni pclmulqdq vmx est ssse3 fma sse4_1 sse4_2 x2apic movbe popcnt aes hypervisor abm ida arat tpr_shadow vnmi flexpriority ept vpid bogomips : 6634.70 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual
3 out of five, identical vms, did not boot with 4.4.4, 2 did. BTW: those stupid audit messages outputted to the console are utterly useless crap.
Generally that happens when 64-bit files have gotten mixed in on a 32-bit system. What's the output of 'file /sbin/init' (if there is a symlink, please run file on the symlink as well)
64bit files are not on the system. The kernels came normal via dnf updates. and /sbin/init is ok, it's the kernel installtion process that has the problem /sbin/init is part of systemd and got reinstalled, because i had the same idea as you. But that wasn't the problem, as the old kernel booted up normally. # file /sbin/init /sbin/init: symbolic link to `../lib/systemd/systemd'
confirmed for 4.4.6-200.fc22
(In reply to customercare from comment #5) > confirmed for 4.4.6-200.fc22 Confirmed means the problem is still present, or it is fixed? You're the only person to report this issue thus far.
confirmed as in "i can confirm, that i had this issue with a newer kernel also." Not all Vms had this problem, but some had. An reinstalling systemd and kernel, did not help. Booting the old kernel works, booting that named kernel, did not work ( with the above error message) And for the "your the only one" I find a lot of bugs in different programs, that others do not have :D That's normal, if your squeze out more of a system, than others do ;) Topic: Problem with reproducing it is, that we talk about production systems. The owners do not like to have such tests. My Testserver, that gets updates, before the systems get it, did work normales, same as several other production servers. We have no clue what could cause those kinds of problems. The vms im question are clones of the same basis fc15 ( and over the years patched up to f23 ) image. Technically, they are bothers and sisters with minor differencies like one or more addons for php. Question: What could cause the Exec format error. The kernel could be installed without errors, there is enough diskspace available, and it's the same update command as any other server had. Still, 3 vms encountered that exec error. out of 15. Any way to check that on a running system ?
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.