Hello Fedora Users list!
I sent this recently to our local LUG list, but no one was able to help. I looked to see if this has been talked about and as far as I know, it hasn't (outside of something similar with Fedora 15, but it seemed the solution there was incomplete).
I have 3 kernels installed on my Fedora 16 laptop -- kernel-3.2.2-1.fc16.i686, kernel-3.2.5-3.fc16.i686 and kernel-3.2.6-3.fc16.i686. When I try to boot 3.2.5-3 or 3.2.6-3, I get a kernel panic message with the message "initramfs unpacking failed uncompression error" followed by "not syncing, no init found". Both of these were installed via normal yum updating; nothing out of the ordinary for them.
In the beginning, booting into the oldest one, 3.2.2-1 has no problems, fortunately. Haven't seen anything helpful mentioned on the Interwebz about such an error, was wondering if anyone had seen something similar. Just to be sure, I removed the 2 newer kernels and then did a "yum install kernel" to see if something was corrupted the first time, but I'm still getting the same results.
The last time I reboot, *all* of the kernels would give the error message. I was able to first boot into single-user and then, when exiting, it boot properly. I just installed the latest kernel update and (3.2.7.x) and getting the same thing.
Thanks!
Brian
On 02/24/2012 10:58 AM, Brian Johnson wrote:
Hello Fedora Users list!
I sent this recently to our local LUG list, but no one was able to help. I looked to see if this has been talked about and as far as I know, it hasn't (outside of something similar with Fedora 15, but it seemed the solution there was incomplete).
I have 3 kernels installed on my Fedora 16 laptop -- kernel-3.2.2-1.fc16.i686, kernel-3.2.5-3.fc16.i686 and kernel-3.2.6-3.fc16.i686. When I try to boot 3.2.5-3 or 3.2.6-3, I get a kernel panic message with the message "initramfs unpacking failed uncompression error" followed by "not syncing, no init found". Both of these were installed via normal yum updating; nothing out of the ordinary for them.
In the beginning, booting into the oldest one, 3.2.2-1 has no problems, fortunately. Haven't seen anything helpful mentioned on the Interwebz about such an error, was wondering if anyone had seen something similar. Just to be sure, I removed the 2 newer kernels and then did a "yum install kernel" to see if something was corrupted the first time, but I'm still getting the same results.
The last time I reboot, *all* of the kernels would give the error message. I was able to first boot into single-user and then, when exiting, it boot properly. I just installed the latest kernel update and (3.2.7.x) and getting the same thing.
Thanks!
Brian
Brian,
What does your grub or grub2 config file look like?
Kevin
Thanks Kevin, and sorry...I should've had that at the ready.
I'm assuming you want the entirety of /etc/grub2.cfg? If not, I apologize for the length....
### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi set default="0" if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi
function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi }
function load_video { insmod vbe insmod vga insmod video_bochs insmod video_cirrus }
set timeout=5 ### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora (3.2.7-1.fc16.i686)' --class fedora --class gnu-linux --class gnu --class os { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod btrfs set root='(hd0,gpt2)' search --no-floppy --fs-uuid --set=root 0697abcb-b17a-4a12-8d13-412cff217b65 echo 'Loading Fedora (3.2.7-1.fc16.i686)' linux /vmlinuz-3.2.7-1.fc16.i686 root=/dev/mapper/vg_divebomb-lv_root ro rd.luks.uuid=luks-f85d3bfc-6995-4169-b243-8daa897e2cad rd.md=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rd.lvm.lv=vg_divebomb/lv_swap rhgb rd.lvm.lv=vg_divebomb/lv_root LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.2.7-1.fc16.i686.img } menuentry 'Fedora (3.2.6-3.fc16.i686)' --class fedora --class gnu-linux --class gnu --class os { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod btrfs set root='(hd0,gpt2)' search --no-floppy --fs-uuid --set=root 0697abcb-b17a-4a12-8d13-412cff217b65 echo 'Loading Fedora (3.2.6-3.fc16.i686)' linux /vmlinuz-3.2.6-3.fc16.i686 root=/dev/mapper/vg_divebomb-lv_root ro rd.luks.uuid=luks-f85d3bfc-6995-4169-b243-8daa897e2cad rd.md=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rd.lvm.lv=vg_divebomb/lv_swap rhgb rd.lvm.lv=vg_divebomb/lv_root LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.2.6-3.fc16.i686.img } menuentry 'Fedora (3.2.2-1.fc16.i686)' --class fedora --class gnu-linux --class gnu --class os { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod btrfs set root='(hd0,gpt2)' search --no-floppy --fs-uuid --set=root 0697abcb-b17a-4a12-8d13-412cff217b65 echo 'Loading Fedora (3.2.2-1.fc16.i686)' linux /vmlinuz-3.2.2-1.fc16.i686 root=/dev/mapper/vg_divebomb-lv_root ro rd.luks.uuid=luks-f85d3bfc-6995-4169-b243-8daa897e2cad rd.md=0 rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rd.lvm.lv=vg_divebomb/lv_swap rhgb rd.lvm.lv=vg_divebomb/lv_root LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.2.2-1.fc16.i686.img } ### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ### if [ -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/90_persistent ### ### END /etc/grub.d/90_persistent ###
On Fri, Feb 24, 2012 at 12:32 PM, Kevin Martin kevintm@ameritech.netwrote:
On 02/24/2012 10:58 AM, Brian Johnson wrote:
Hello Fedora Users list!
I sent this recently to our local LUG list, but no one was able to help. I looked to see if this has been talked about and as far as I know, it hasn't (outside of something similar with Fedora 15, but it seemed the solution there was incomplete).
I have 3 kernels installed on my Fedora 16 laptop -- kernel-3.2.2-1.fc16.i686, kernel-3.2.5-3.fc16.i686 and kernel-3.2.6-3.fc16.i686. When I try to boot 3.2.5-3 or 3.2.6-3, I get a kernel panic message with the message "initramfs unpacking failed uncompression error" followed by "not syncing, no init found". Both of these were installed via normal yum updating; nothing out of the ordinary for them.
In the beginning, booting into the oldest one, 3.2.2-1 has no problems, fortunately. Haven't seen anything helpful mentioned on the Interwebz about such an error, was wondering if anyone had seen something similar. Just to be sure, I removed the 2 newer kernels and then did a "yum install kernel" to see if something was corrupted the first time, but I'm still getting the same results.
The last time I reboot, *all* of the kernels would give the error message. I was able to first boot into single-user and then, when exiting, it boot properly. I just installed the latest kernel update and (3.2.7.x) and getting the same thing.
Thanks!
Brian
Brian,
What does your grub or grub2 config file look like?
Kevin
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On Fri, 24 Feb 2012 11:58:55 -0500 Brian Johnson wrote:
"initramfs unpacking failed uncompression error"
It is just a gzipped cpio archive, try running it through gzip -d < initramfsfile | cpio -t (or something like that, I'd check the options if I were you :-).
If that fails, the file is probably corrupted.
On 02/24/2012 11:45 AM, Brian Johnson wrote:
Thanks Kevin, and sorry...I should've had that at the ready.
I'm assuming you want the entirety of /etc/grub2.cfg? If not, I apologize for the length....
### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then load_env fi set default="0" if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi
function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi }
function load_video { insmod vbe insmod vga insmod video_bochs insmod video_cirrus }
set timeout=5 ### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ### menuentry 'Fedora (3.2.7-1.fc16.i686)' --class fedora --class gnu-linux --class gnu --class os { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod btrfs set root='(hd0,gpt2)' search --no-floppy --fs-uuid --set=root 0697abcb-b17a-4a12-8d13-412cff217b65 echo 'Loading Fedora (3.2.7-1.fc16.i686)' linux /vmlinuz-3.2.7-1.fc16.i686 root=/dev/mapper/vg_divebomb-lv_root ro rd.luks.uuid=luks-f85d3bfc-6995-4169-b243-8daa897e2cad rd.md http://rd.md=0 rd.dm http://rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rd.lvm.lv http://rd.lvm.lv=vg_divebomb/lv_swap rhgb rd.lvm.lv http://rd.lvm.lv=vg_divebomb/lv_root LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.2.7-1.fc16.i686.img } menuentry 'Fedora (3.2.6-3.fc16.i686)' --class fedora --class gnu-linux --class gnu --class os { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod btrfs set root='(hd0,gpt2)' search --no-floppy --fs-uuid --set=root 0697abcb-b17a-4a12-8d13-412cff217b65 echo 'Loading Fedora (3.2.6-3.fc16.i686)' linux /vmlinuz-3.2.6-3.fc16.i686 root=/dev/mapper/vg_divebomb-lv_root ro rd.luks.uuid=luks-f85d3bfc-6995-4169-b243-8daa897e2cad rd.md http://rd.md=0 rd.dm http://rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rd.lvm.lv http://rd.lvm.lv=vg_divebomb/lv_swap rhgb rd.lvm.lv http://rd.lvm.lv=vg_divebomb/lv_root LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.2.6-3.fc16.i686.img } menuentry 'Fedora (3.2.2-1.fc16.i686)' --class fedora --class gnu-linux --class gnu --class os { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod btrfs set root='(hd0,gpt2)' search --no-floppy --fs-uuid --set=root 0697abcb-b17a-4a12-8d13-412cff217b65 echo 'Loading Fedora (3.2.2-1.fc16.i686)' linux /vmlinuz-3.2.2-1.fc16.i686 root=/dev/mapper/vg_divebomb-lv_root ro rd.luks.uuid=luks-f85d3bfc-6995-4169-b243-8daa897e2cad rd.md http://rd.md=0 rd.dm http://rd.dm=0 KEYTABLE=us quiet SYSFONT=latarcyrheb-sun16 rd.lvm.lv http://rd.lvm.lv=vg_divebomb/lv_swap rhgb rd.lvm.lv http://rd.lvm.lv=vg_divebomb/lv_root LANG=en_US.UTF-8 echo 'Loading initial ramdisk ...' initrd /initramfs-3.2.2-1.fc16.i686.img } ### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ### ### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ### ### END /etc/grub.d/30_os-prober ### ### BEGIN /etc/grub.d/40_custom ### # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. ### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ### if [ -f $prefix/custom.cfg ]; then source $prefix/custom.cfg; fi ### END /etc/grub.d/41_custom ###
### BEGIN /etc/grub.d/90_persistent ### ### END /etc/grub.d/90_persistent ###
On Fri, Feb 24, 2012 at 12:32 PM, Kevin Martin <kevintm@ameritech.net mailto:kevintm@ameritech.net> wrote:
On 02/24/2012 10:58 AM, Brian Johnson wrote:
Hello Fedora Users list! I sent this recently to our local LUG list, but no one was able to help. I looked to see if this has been talked about and as far as I know, it hasn't (outside of something similar with Fedora 15, but it seemed the solution there was incomplete). I have 3 kernels installed on my Fedora 16 laptop -- kernel-3.2.2-1.fc16.i686, kernel-3.2.5-3.fc16.i686 and kernel-3.2.6-3.fc16.i686. When I try to boot 3.2.5-3 or 3.2.6-3, I get a kernel panic message with the message "initramfs unpacking failed uncompression error" followed by "not syncing, no init found". Both of these were installed via normal yum updating; nothing out of the ordinary for them. In the beginning, booting into the oldest one, 3.2.2-1 has no problems, fortunately. Haven't seen anything helpful mentioned on the Interwebz about such an error, was wondering if anyone had seen something similar. Just to be sure, I removed the 2 newer kernels and then did a "yum install kernel" to see if something was corrupted the first time, but I'm still getting the same results. The last time I reboot, *all* of the kernels would give the error message. I was able to first boot into single-user and then, when exiting, it boot properly. I just installed the latest kernel update and (3.2.7.x) and getting the same thing. Thanks! Brian
Brian, What does your grub or grub2 config file look like? Kevin -- users mailing list users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
So 3.2.2 isn't booting now either (at least, not until single-user mode and then exit)? Have you tried updating dracut and then rebuilding your initramfs with dracut -f?
Kevin
Am 24.02.2012 19:02 schrieb "Tom Horsley" horsley1953@gmail.com:
On Fri, 24 Feb 2012 11:58:55 -0500 Brian Johnson wrote:
"initramfs unpacking failed uncompression error"
It is just a gzipped cpio archive, try running it through gzip -d < initramfsfile | cpio -t (or something like that, I'd check the options if I were you :-).
# lsinitrd <file>
Thank you all for the responses. I went to reboot my laptop into the old 3.2.2 kernel to confirm that it was having the same issue, and it boot into it with no problem. I then reboot my laptop and let it start up with the latest 3.2.7 kernel, and it, too, started with no problem again.
There doesn't seem to be any consistency to it. Hadn't had a chance to make any of the suggested changes below....
On Fri, Feb 24, 2012 at 1:43 PM, Harald Hoyer harald.hoyer@gmail.comwrote:
Am 24.02.2012 19:02 schrieb "Tom Horsley" horsley1953@gmail.com:
On Fri, 24 Feb 2012 11:58:55 -0500 Brian Johnson wrote:
"initramfs unpacking failed uncompression error"
It is just a gzipped cpio archive, try running it through gzip -d < initramfsfile | cpio -t (or something like that, I'd check the options if I were you :-).
# lsinitrd <file>
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Brian Johnson wrote:
Thank you all for the responses. I went to reboot my laptop into the old 3.2.2 kernel to confirm that it was having the same issue, and it boot into it with no problem. I then reboot my laptop and let it start up with the latest 3.2.7 kernel, and it, too, started with no problem again.
There doesn't seem to be any consistency to it. Hadn't had a chance to make any of the suggested changes below....
One possible explanation is dodgy memory: do give it a check. The memtest86 on a Fedora install would be good for that. There’s also a chance that some other part of your system (possibly the processor) isn’t working quite properly: keep an eye out for that. (One traditional stress-test for processor and memory is a kernel compile).
Hope this helps,
James.
On 02/24/2012 03:00 PM, James Wilkinson wrote:
Brian Johnson wrote:
Thank you all for the responses. I went to reboot my laptop into the old 3.2.2 kernel to confirm that it was having the same issue, and it boot into it with no problem. I then reboot my laptop and let it start up with the latest 3.2.7 kernel, and it, too, started with no problem again.
There doesn't seem to be any consistency to it. Hadn't had a chance to make any of the suggested changes below....
One possible explanation is dodgy memory: do give it a check. The memtest86 on a Fedora install would be good for that. There’s also a chance that some other part of your system (possibly the processor) isn’t working quite properly: keep an eye out for that. (One traditional stress-test for processor and memory is a kernel compile).
Hope this helps,
James.
Hmm, yes, that is interesting. It boots into the newest kernel now with no changes from you when it wasn't before. Definitely sounds like it could be hardware related.
Kevin