LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices


Reply
  Search this Thread
Old 03-05-2016, 10:53 AM   #1
bruceam
Member
 
Registered: Nov 2008
Location: Atlanta, Georiga
Distribution: Debian, Ubuntu
Posts: 82

Rep: Reputation: 17
"XZ-compression data is corrupt -- system halted" Error on Boot Up


I have an X99 WS-E Motherboard with and Intel I7 5960X 3000MHz CPU, 64 GB RAM, an Nvidia Quadro M4000 with 8GB Video RAM, and 500 GB M.2 SSD upon which I have successfully installed Debian 8.3 Linux (which runs just fine, after the system finally boots up).

WHen I start the machine, after the computer has been "off" for a while, the boot up process halts (after the boot device selection, and the GRUB boot screen have successfully displayed). The boot stops with the error message "XZ-compression data is corrupt -- system halted". Once I restart, enter the BIOS Setup screen, save (even if I don't make any changes), then reboot (which for this system means the power goes completely off for about 5 to 10 seconds), the system will boot up normally and operates normally.

Does anyone have any insight into what is going on here?

Thank you for your assistance
 
Old 03-06-2016, 05:19 PM   #2
whansard
Senior Member
 
Registered: Dec 2002
Location: Mosquitoville
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,291

Rep: Reputation: 65
maybe memory error. lower your memory speed setting a little, and see if the error stops.
 
1 members found this post helpful.
Old 03-07-2016, 10:55 AM   #3
bruceam
Member
 
Registered: Nov 2008
Location: Atlanta, Georiga
Distribution: Debian, Ubuntu
Posts: 82

Original Poster
Rep: Reputation: 17
Quote:
Originally Posted by whansard View Post
maybe memory error. lower your memory speed setting a little, and see if the error stops.
whansard,
thank you for the insight. I will give that a try. I will keep you posted as to the result.
 
Old 03-07-2016, 03:49 PM   #4
jefro
Moderator
 
Registered: Mar 2008
Posts: 19,514

Rep: Reputation: 3017Reputation: 3017Reputation: 3017Reputation: 3017Reputation: 3017Reputation: 3017Reputation: 3017Reputation: 3017Reputation: 3017Reputation: 3017Reputation: 3017
Left over residual power to some chips or esd damage or just bad timing on some chips.
 
Old 03-08-2016, 09:26 AM   #5
bruceam
Member
 
Registered: Nov 2008
Location: Atlanta, Georiga
Distribution: Debian, Ubuntu
Posts: 82

Original Poster
Rep: Reputation: 17
Quote:
Originally Posted by jefro View Post
Left over residual power to some chips or esd damage or just bad timing on some chips.
jefro,
I did as you suggested, but unfortunately, it had no effect. I will continue looking around for for the answer to this, and post anything I come up with. Thanks again for the suggestion. I really hoped that it would work.
 
Old 03-08-2016, 09:46 AM   #6
sundialsvcs
LQ Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 9,078
Blog Entries: 4

Rep: Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179Reputation: 3179
This sounds to me like some kind of error in the device. Basically, an I/O error. If the system ever starts up normally, this suggests that the data in the compressed file is, in fact, "good."
 
Old 03-19-2016, 04:07 PM   #7
bruceam
Member
 
Registered: Nov 2008
Location: Atlanta, Georiga
Distribution: Debian, Ubuntu
Posts: 82

Original Poster
Rep: Reputation: 17
Quote:
Originally Posted by whansard View Post
maybe memory error. lower your memory speed setting a little, and see if the error stops.
Thank you everyone who helped diagnose this issue, especially "whansard". I believe I have finally found it!

When I went into the BIOS setup to check the memory (DRAM) settings, I found that the defaults (which were supposed to be auto detected by the motherboard, and based on the particular hardware installed) were not in close agreement with the specifications for the memory from the manufacturer. It took a lot of attempts to get thing to work reliably and the way I want them too, but FINALLY!!!

I suspect the autodetect feature of the motherboard was incorrectly loading memory settings on the initial boot up. Most likely having something to do with when in the bootup sequence the autodetect took place. As stated in the problems description, once I had gone into the BIOS saved and exited (even if I didn't change anything), the system would boot properly. I suspect that this "detour" to the BIOS settings during bootup, gave the autodetect function sufficient time to work properly or allowed the actual hardware sufficient time to respond correctly.

I used the manufacturer's DRAM settings, which I looked up earlier, in the BIOS setup. Actually, I still allow the motherboard to autodetect the the exact settings, but I have specified the correct type of memory and memory overall speed for the unit to query within. This narrowed the range of acceptable responses the autodetect could provide. Now when I boot up, everything works the way it is supposed to.

Once again, Thanks Everyone!!!!
 
1 members found this post helpful.
Old 03-21-2016, 02:31 PM   #8
whansard
Senior Member
 
Registered: Dec 2002
Location: Mosquitoville
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,291

Rep: Reputation: 65
thanks for the thanks.
 
Old 02-18-2020, 12:38 AM   #9
Devlin41
LQ Newbie
 
Registered: Feb 2020
Posts: 1

Rep: Reputation: Disabled
Solved XZ -compression data is corrupt--system halted

Hi, first I wanted to thank whansard for the tip. I have an old dell inspiron and wanted to put it to some good use so I chose linux to do the job. I kept getting this error. Thinking it was the cd that I kept burning I decided to use a usb. Figured that out. I then used some recycled RAM, the original ram was 1G total, now its 3G. The Linux loaded rather quickly onto the computer. So just changing out the RAM did the trick.
 
  


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
A Win8 "slave" disk is using "UEFI secure boot" - How to copy data from it with Linux ghost123uk Linux - Software 8 08-15-2015 07:28 AM
[SOLVED] Slackware 14.0 with generic kernel results in "LZMA data is corrupt" atelszewski Slackware 5 01-02-2013 02:46 PM
xend.err "Error creating domain: Boot loader didn't return any data!" mhgee Linux - Virtualization and Cloud 1 10-15-2009 03:50 AM
[SOLVED] problem booting from live cd "crc error system halted" jbarry36 Linux - Newbie 1 02-28-2009 05:51 PM
I always get the message "System is halted" MasterX Linux - Hardware 2 08-17-2004 08:00 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software

All times are GMT -5. The time now is 06:54 PM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration