LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   X2-compressed data is corrupt (http://www.linuxquestions.org/questions/slackware-14/x2-compressed-data-is-corrupt-4175477571/)

Jati 09-18-2013 04:11 AM

X2-compressed data is corrupt
 
Hi all, i got a problem when i upgrade my slackware kernel. i've compiled the kernel (3.11), and i dont update the lilo(when i update the lilo, the system miss the glibc). then i rebooted it. so i got this error when startup.

"X2-compressed data is corrupt
--system halted"

and the system hang.

here i use slackware64 14.

please help me

TobiSGD 09-18-2013 06:27 AM

When you don't update Lilo your new kernel will not be booted, it will start the old one. So your problem can't be a problem with the new kernel, but rather with your system, which is also indicated by the error you get regarding the missing glibc.
Is this the recommended full install?

Jati 09-19-2013 09:49 PM

so, could i use my old kernel again? how to do that?

here the output of my error in GLIBC
Code:

#lilo
lilo: /lib/libc.so.6: version 'GLIBC_2.3' not found (required by lilo)
#


TobiSGD 09-19-2013 10:46 PM

When you have not removed your old kernel than lilo will boot that kernel if you don't upgrade lilo.
Regarding the glibc, do you by any chance have changed that also?

rknichols 09-19-2013 11:10 PM

A common cause of boot failure with lilo is that at some time in the (perhaps distant) past someone moved some of the boot files but did not re-run the lilo installer. The system can continue to boot just fine for quite a while because lilo is actually loading data that continues to exist in what is now marked as free space on the disk. Eventually, something new gets stored in some of those disk blocks, and suddenly the old, reliable kernel that you didn't change fails to boot.

Recovery requires booting from rescue media and running the lilo installer.

Jati 09-20-2013 03:27 AM

Quote:

Originally Posted by TobiSGD (Post 5031087)
When you have not removed your old kernel than lilo will boot that kernel if you don't upgrade lilo.
Regarding the glibc, do you by any chance have changed that also?

Quote:

Originally Posted by rknichols (Post 5031098)
A common cause of boot failure with lilo is that at some time in the (perhaps distant) past someone moved some of the boot files but did not re-run the lilo installer. The system can continue to boot just fine for quite a while because lilo is actually loading data that continues to exist in what is now marked as free space on the disk. Eventually, something new gets stored in some of those disk blocks, and suddenly the old, reliable kernel that you didn't change fails to boot.

Recovery requires booting from rescue media and running the lilo installer.

actually i have replaced my old kernel configuration and i forgot to backup them.
then, for my question, can i place/install a new kernel or old kernel in my slackware in this situation?
should i use chroot?

TobiSGD 09-22-2013 06:24 AM

Quote:

Originally Posted by Jati (Post 5031219)
actually i have replaced my old kernel configuration and i forgot to backup them.
then, for my question, can i place/install a new kernel or old kernel in my slackware in this situation?
should i use chroot?

Just install (or copy) a new kernel into the system, generate a new initrd, if necessary, chrrot into the system, update /etc/lilo.conf and run lilo.

Jati 09-22-2013 08:30 PM

Quote:

Originally Posted by TobiSGD (Post 5032469)
Just install (or copy) a new kernel into the system, generate a new initrd, if necessary, chrrot into the system, update /etc/lilo.conf and run lilo.

how to do that?
should i use slackware live cd?
or other distro isn't a problem?

TobiSGD 09-22-2013 08:50 PM

With the Slackware DVD it is easiest to do that, you don't even need to chroot, just follow the instructions on the bootloader's page of the DVD to boot the installed system, the just install/configure the system as you would do normally with your system.


All times are GMT -5. The time now is 05:47 AM.