Scientific Linux Forum.org



  Reply to this topicStart new topicStart Poll

> kernel panic on boot after update - RAMDISK incomplete write error (Partially solved)
sidney
 Posted: Nov 12 2012, 02:25 AM
Quote Post


SLF Newbie


Group: Members
Posts: 1
Member No.: 2044
Joined: 12-November 12









I just did a yum update of Scientific Linux 6.3. I don't recall when my last update was, but I see that the files in /boot for kernel 2.6.32-279-11.1 are dated Oct 17. The update installed kernel 2.6.32-279-14.1.

After the update rebooting died with a kernel panic. The strange thing about it was that the same panic happened booting kernel 2.6.32-279-14.1 and 2.6.32-279-11.1 but I was able to boot into the remaining older kernel that was still in /boot, 2.6.32-279.9.1. This in spite of the fact that kernel 2.6.32-279.11.1 booted fine before the update.

The error message before the panic said RAMDISK: incomplete write (929 != 32567)

(I don't exactly recall what the numbers were in my error messages)

I looked at the initrd images (the initramfs*.img files in /boot). Despite the files being named *.img, they are actually gzipped cpio files, so you look at them by gunzipping them and unpacking with cpio. I found that on the two files of the kernels that panic, gunzip produced a warning message that it was ignoring garbage characters at the end of the file. cpio unpacked all three uncompressed files to the same number of directories and files. I tried running the img file through gunzip then pipe it through gzip -9 to compress it again but without garbage characters at the end, putting the result back in /boot to boot from.

That fixed the kernel panic problem.

It looks like a combination of two problems: The initramfs*.img files installed with kernels 2.6.32-279-11 and 14 both have some extra characters at the end. But also it appears that whatever is used to unpack them during boot was updated in the recent upgrade and it now fails when there is garbage after the end of the gzip file, something that gzip handles and that it used to handle.

Has anyone else seen this? In any case if you get the kernel panic, that is the workaround.
PM
^
AndrewSerk
 Posted: Nov 13 2012, 11:34 AM
Quote Post


SLF Moderator
*****

Group: Moderators
Posts: 457
Member No.: 54
Joined: 14-April 11









Hello Sidney and welcome to SLF

I have never seen this issue, but thanks for posting the workaround. smile.gif
PM
^
JamesP
 Posted: Nov 19 2012, 02:57 PM
Quote Post


SLF Newbie


Group: Members
Posts: 1
Member No.: 2068
Joined: 19-November 12









I've just had this very problem and was about to reinstall my system when I found this solution. So a big thank you to sidney!

I had 3 kernels installed, all 3 related initramfs images had trailing garbage

2.6.32-279-14.1
2.6.32-279-11.1
2.6.32-220-4.1
PM
^
mrmrn
 Posted: Mar 19 2013, 07:40 PM
Quote Post


SLF Newbie


Group: Members
Posts: 1
Member No.: 2366
Joined: 19-March 13









I have the same problem!
I installed SL 6.3 just a few days befora.after installation I updated it but now I cant boot into it!
initramfs file does not exist in /boot folder!these are all files I have in /boot folder:
CODE
bridge@bridgelinux /run/media/bridge/_SL-63-x86_64-Li/boot % ls
config-2.6.32-279.5.1.el6.x86_64  symvers-2.6.32-279.5.1.el6.x86_64.gz
config-2.6.32-358.2.1.el6.x86_64  symvers-2.6.32-358.2.1.el6.x86_64.gz
efi/                              System.map-2.6.32-279.5.1.el6.x86_64
elf-memtest86+-4.10               System.map-2.6.32-358.2.1.el6.x86_64
extlinux/                         vmlinuz-2.6.32-279.5.1.el6.x86_64*
grub/                             vmlinuz-2.6.32-358.2.1.el6.x86_64*
memtest86+-4.10
bridge@bridgelinux /run/media/bridge/_SL-63-x86_64-Li/boot %


So, how can I sole this problem?
why the first kernels "2.6.32-279.5.1" initram file does not exit?where is it gone?
PMEmail Poster
^
gtaylormb
 Posted: Oct 21 2013, 03:44 PM
Quote Post


SLF Newbie


Group: Members
Posts: 1
Member No.: 2777
Joined: 21-October 13









Same exact problem as syndey, fixed it the same way. All three of my kernels were affected. Thank you! I don't know how you figured that out, but it worked.

PM
^
monsee
 Posted: Nov 20 2013, 11:43 AM
Quote Post


SLF Member
***

Group: Members
Posts: 56
Member No.: 539
Joined: 27-July 11









Same error for me sad.gif , today morning (and I have just updated my Kernel yersterday in the afternoon: first boot after update was good, but today my Scientific Linux 6.4 64-bit [XFCE desktop environment] don't start at all): appear the "kernel panic" message about a "RAMDISK incomplete write error" and all stuck... wacko.gif
I have not solved yet: I will attempt to solve (using the workaround and .maybe- a liveCD to operate) later in the afternoon...
PM
^
monsee
 Posted: Nov 21 2013, 03:05 AM
Quote Post


SLF Member
***

Group: Members
Posts: 56
Member No.: 539
Joined: 27-July 11









I tried to extract the file initramfs contains (before that, I had to change the file extension from .img to .gz, of course, using -as root- the "mv" command, and its go well) using, as root, the "gunzip" command, but fails! sad.gif
I had http://dl.dropbox.com/u/2835777/BangHead1.gif these error-messages, in return:

CODE
gzip: initramfs-2.6.32-358.23.2.el6.x86_64.gz: invalid compressed data--crc error


CODE
gzip: initramfs-2.6.32-358.23.2.el6.x86_64.gz: invalid compressed data--length error


So, maybe is not possible, for me, to make the indispensable workaround to repair my initramfs.

Better to reinstall?
... But, if a newer Kernel give me the same error, which way, for me, to put a remedy? blink.gif

PM
^
monsee
 Posted: Nov 22 2013, 11:41 PM
Quote Post


SLF Member
***

Group: Members
Posts: 56
Member No.: 539
Joined: 27-July 11









Really, I am not so expert to resolve the problem... sad.gif
So, I tried to reinstall my Scientific Linux System... and all work, now! http://dl.dropbox.com/u/2835777/egyptian.gif
PM
^
0 User(s) are reading this topic (0 Guests and 0 Anonymous Users)
0 Members:

Topic Options Reply to this topicStart new topicStart Poll