View Issue Details

IDProjectCategoryView StatusLast Update
0003816Kali LinuxGeneral Bugpublic2025-07-14 09:37
ReporterMorteryler Assigned Torhertzog  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version2016.2 
Summary0003816: XZ-compressed data is corrupt
Description

I downloaded kali linux with a graphical environment lxde. I recorded the ISO file to DVD and restart the computer. Clicking on any menu option pops up an error: XZ-compressed data is corrupt - System halted.
I booted into my system and checked the drive command:
Code:
root#:/media readcd dev=0,1,0 f=file.iso
Read speed: 8467 kB/s (CD 48x, DVD 6x, BD 1x).
Write speed: 8467 kB/s (CD 48x, DVD 6x, BD 1x).
Capacity: 1417816 Blocks = 2835632 kBytes = 2769 MBytes = 2903 prMB
Sectorsize: 2048 Bytes
Copy from SCSI (0,1,0) disk to file 'file.iso'
end: 1417816
addr: 1417816 cnt: 24
Time total: 214.389sec
Read 2835632,00 kB at 13226,6 kB/sec.
That's what gives the command file:
Code:
root#:/media file file.iso
file.iso: DOS/MBR boot sector ISO 9660 CD-ROM filesystem data 'Kali Live' (bootable); partition 1 : ID=0x17, active, start-CHS (0x0,2,1), end-CHS (0x3fc,166,32), startsector 64, 5456160 sectors; partition 2 : ID=0x1, start-CHS (0x3fd,0,1), end-CHS (0x3ff,166,32), startsector 5456224, 215040 sectors
I mount the drive and everything turned out without a single error:
Code:
root#:/media mount -t iso9660 -o loop,ro file.iso /mnt/iso
root#:/media ls /mnt/iso
autorun.inf dists g2ldr.mbr live setup.exe
boot firmware install md5sum.txt tools
debian g2ldr isolinux pool win32-loader.ini
root#:/media du -sh /mnt/iso/
2,6G /mnt/iso/
Could it be from the fact that I have an old motherboard? Computer specifications can write if necessary.

The exact fault output on the screen:
Probing EDD (edd=off to disable)... ok

XZ-compressed data is corrupt
-- System halted

Activities

rhertzog

rhertzog

2017-02-07 16:40

administrator   ~0006350

Looks like your ISO image has been corrupted in the process of downloading it or burning it. Not our fault.

Issue History

Date Modified Username Field Change
2017-01-03 16:28 Morteryler New Issue
2017-02-07 16:40 rhertzog Assigned To => rhertzog
2017-02-07 16:40 rhertzog Status new => closed
2017-02-07 16:40 rhertzog Resolution open => no change required
2017-02-07 16:40 rhertzog Note Added: 0006350
2025-07-14 09:17 g0tmi1k Priority urgent => normal
2025-07-14 09:37 g0tmi1k Severity block => minor