Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 234338 - tar failing to decompressing bzip2 stage3 file for x86 arch
Summary: tar failing to decompressing bzip2 stage3 file for x86 arch
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Stages (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: Gentoo Release Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-09 22:46 UTC by Enrique Domínguez
Modified: 2008-08-24 20:19 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Enrique Domínguez 2008-08-09 22:46:30 UTC
After downloaded all (3) stage3 files for x86, 2007.0 release didn't pass md5sum test, like this (2 times each):
#md5sum -c stage3-x86-2007.0.tar.bz2.DIGESTS
stage3-x86-2007.0.tar.bz2: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match

2008.0 did pass this test
All releases failed to decompress with tar like this:
#tar xjpf stage3-*.tar.bz2
Error was:
bzip2: Data integrity error when decompressing.
	Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

Reproducible: Always

Steps to Reproduce:
1.wget stage3 for x86
2.test md5sum
3.untar it

Actual Results:  
untar error for corrupted file

Expected Results:  
tar decompress sucessfully

Using stage3 (2008.0 version tested only) failing to emerge linux-headers-2.6.23-r3
Comment 1 Andrew Gaffney (RETIRED) gentoo-dev 2008-08-10 01:52:22 UTC
Have you tried this on another machine? This is the only complaint of this we've heard since the release over a month ago. It's possible that you just have a hardware issue that's manifesting itself this way.
Comment 2 Andrew Gaffney (RETIRED) gentoo-dev 2008-08-24 20:19:42 UTC
Please reopen this bug if you can reproduce this problem on another machine.