LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-30-2012, 04:08 PM   #1
atelszewski
Member
 
Registered: Aug 2007
Posts: 47

Rep: Reputation: Disabled
Slackware 14.0 with generic kernel results in "LZMA data is corrupt"


Hi,

I'm running Slackware 14.0.
The huge kernel works fine without any problem.
The problem appears when I use generic kernel with initrd. For a few times the system boots properly, but eventually it stops booting with the message:
Code:
LZMA data is corrupt
-- System halted
Running LILO solves the problem for some time, but it comes back again at random time.
I don't remember having this problem with previous versions of Slackware.

Any ideas?

--
Best regards,
Andrzej Telszewski
 
Old 11-30-2012, 05:05 PM   #2
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 872

Rep: Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786
Quote:
Originally Posted by atelszewski View Post
Hi,

I'm running Slackware 14.0.
The huge kernel works fine without any problem.
The problem appears when I use generic kernel with initrd. For a few times the system boots properly, but eventually it stops booting with the message:
Code:
LZMA data is corrupt
-- System halted
Running LILO solves the problem for some time, but it comes back again at random time.
I don't remember having this problem with previous versions of Slackware.

Any ideas?
The "LZMA data is corrupt" error is most commonly caused when the block map used by LILO to load the kernel no longer aligns with the actual data blocks for the kernel file. Usually it happens when a new kernel is installed, but lilo is not run afterwards to rebuild the kernel map. But, since you say that running LILO again solves the issue temporarily, I suspect this isn't the case here. My best guess is that it's something to do with the filesystem that the kernel is on. Are you possibly using an unusual filesystem? Some filesystems can rearrange files through automatic defragmentation or for other reasons. If so, you might try creating a /boot partition using ext2 or ext3 and running LILO again.
 
1 members found this post helpful.
Old 12-01-2012, 03:33 AM   #3
atelszewski
Member
 
Registered: Aug 2007
Posts: 47

Original Poster
Rep: Reputation: Disabled
Hi,
Quote:
Are you possibly using an unusual filesystem?
Nope, I'm using ext4 (I believe it's not unusual). But anyway, then why would the huge kernel work all the time without this issue? If the generic kernel image can be corrupted, then I think in the same way the huge image could be corrupted.

For completeness here are my disk partitions:
Code:
/dev/sda1        swap             swap        defaults         0   0
/dev/sda3        /mnt/windows     ntfs-3g     defaults,noauto  0   0
/dev/sda5        /                ext4        defaults         1   1
/dev/sda6        /home            ext4        defaults         1   2
Any clue?

--
Best regards,
Andrzej Telszewski
 
Old 12-01-2012, 05:32 AM   #4
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Run memtest and maybe a SMART long test.
 
Old 12-02-2012, 03:41 PM   #5
atelszewski
Member
 
Registered: Aug 2007
Posts: 47

Original Poster
Rep: Reputation: Disabled
Hi,
Quote:
Run memtest and maybe a SMART long test.
SMART went fine, but memtest found one of my memory modules to be faulty.
I've replaced the module and will now see if this has fixed the problem.
I'll be back to this topic in one month to tell it's solved or earlier if the problem appears again

BTW, it is strange that it was happening with generic and not with huge kernel, because both of them need to be decompressed to the memory. Really strange. But anyway I think it was about the memory, because the faulty memory region was around ~20MB at the beginning, and I assume that's the region where the kernel is more less decompressed.

Thanks for now and I hope the one month test will succeed.

--
Best regards,
Andrzej Telszewski
 
Old 01-02-2013, 01:46 PM   #6
atelszewski
Member
 
Registered: Aug 2007
Posts: 47

Original Poster
Rep: Reputation: Disabled
Hi,

I'm back to report that so far everything is running smoothly, I mean the problem with loading the generic kernel seems to be not appearing any more after one month or so.

Thanks to everybody for your help!

--
Best regards,
Andrzej Telszewski
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Ubuntu 10.04 - missing "Build" directory for current kernel | 2.6.32-38-generic | floorripper Linux - Newbie 2 02-18-2012 06:27 AM
Confused about "generic" vs. "386" linux kernel SaintDanBert Linux - Software 6 09-29-2009 11:51 PM
"corrupt kernel image" when booting from disc 1 Ryupower Fedora 10 02-02-2007 07:23 AM
mkinitrd results in: "No module aic7xxx found for kernel 2.6.18.1" jim_cliff11 Red Hat 7 12-28-2006 05:40 PM
"corrupt kernel image" , Fedora Core Ryupower Linux - Newbie 1 11-26-2006 09:27 PM


All times are GMT -5. The time now is 03:45 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration