> -----Ursprüngliche Nachricht----- > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im > Auftrag von John Summerfield > Gesendet: Dienstag, 29. Juli 2008 15:03 > An: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list > Betreff: Re: AW: [rhelv5-list] RAMDISK : ran out of compressed > datainvalidcompressed format (err=1) > > Schmidt, Florian wrote: > > > >> -----Urspr�ngliche Nachricht----- > >> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Im > >> Auftrag von Mogens Kjaer > >> Gesendet: Montag, 28. Juli 2008 15:48 > >> An: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list > >> Betreff: Re: [rhelv5-list] RAMDISK : ran out of compressed datainvalid > compressed > >> format (err=1) > >> > >> Schmidt, Florian wrote: > >>> Hello everyone, > >>> > >>> For checking cluster functionality I did reset one of the servers. > >>> Not that good idea, because he does not boot now anymore. > >>> > >>> He stops with this Kernel panic: > >>> > >>> RAMDISK : ran out of compressed data > > That suggests to me that the initrd file is shorter than it should be. > > >>> invalid compressed format (err=1) > >>> Kernel panic - not syncing: VFS: Unable to mount root fs on > >>> unknown-block (0,0) > >>> > >>> Did something destroy the initrd-image? Or what did happen? > >> Is the /boot partition full? Can you boot an old kernel? > > > > I don't think so. I actually make an image of the HDDs. After that I'll > > check this. > > > > No there's no old kernel to boot. It's a pretty fresh installation of RHEL5 > > Kernel > 2.6.18-53. > > > > I'll try if I can copy an image of the /boot-partition from the second > > server to this > one. They should be the same. > > > > Any idea, what could have caused this? > > > > Regards > > Florian > > I would install the install media in rescue mode and do a filesystem check.
Thanks for your reply, Here's what I did until now: The machine is a HP DL320G5p Server with HP embedded SATA-RAID-controller. This one is really shit. I already had huge problems with it before. After the hard reset of the server, the problem I described above occurred. I tried to modifiy the grub-boot-parameters...without any success. Next I made a backup of the boot partitions of the second machine, which should be exactly the same and restored it on the failing machine -> result was: booting from hard disk wasn't possible anymore. Only cryptic signs and a frozen machine... After that I made a super-grub-floppy and started grub from that and told him exactly which kernel and which initrd from which disc to boot. I saw the boot-process again, but with failing on exactly the same place. Next, I booted from the RHEL5-DVD and went into rescue mode. I tried to run fsck on /dev/sda1 but that wasn't possible for some reason, so I extracted the kernel from the rpms and copied it into /boot to make sure he is working. But also that failed. So I will now try your advice. What steps are neccesary to check the filesystem on that device? I'll boot into rescue mode and then I have 3 possibilities: Skip Readonly Normal=readwrite? Which possibility should I choose? I always chose readwrite, but with this one fsck went wrong! But I didn' chroot in. May that have been the failure? > I would then mount the system rw (still running the CD), chroot in, then > rebuilt the initrd. OK, i'll even try this one. Thanks for any advice. Time is running out :( Florian > A command modeled on this will show an adequate command: > rpm -qf /boot/vmlinuz-2.6.9-34.EL --scripts > > > -- > > Cheers > John > > -- spambait > [EMAIL PROTECTED] [EMAIL PROTECTED] > -- Advice > http://webfoot.com/advice/email.top.php > http://www.catb.org/~esr/faqs/smart-questions.html > http://support.microsoft.com/kb/555375 > > You cannot reply off-list:-) > > _______________________________________________ > rhelv5-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
