Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

SecondLife_i686_1_18_1_2.tar.bz2 Install Error

Morbid Blackadder
Registered User
Join date: 24 Aug 2007
Posts: 33
08-24-2007 10:27
Hi!

I get the following error when attempting to install SecondLife_i686_1_18_1_2.tar.bz2 file:

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.

/bin/gtar: Unexpected EOF in archive
/bin/gtar: Error is not recoverable: exiting now

I've tried downloading the SecondLife_i686_1_18_1_2.tar.bz2 several times and always get the same error message when attempting to install.

I'm using the Fedora 7 Archive Manager.

Any suggestions?
Chrysocolla Rau
Registered User
Join date: 16 Feb 2007
Posts: 4
08-24-2007 11:41
Well, if the "bzip2 -tvv" agrees that the archive is corrupted, try downloading another way? Maybe wget the archive url directly.

If the archive's fine, then you ought to be able to just "tar jxf" it into opt, or wherever.
Morbid Blackadder
Registered User
Join date: 24 Aug 2007
Posts: 33
08-24-2007 21:16
It looks like the archive is corrupted, however, I wonder if a possible hardware problem (e.g. bad hard disk) is to blame because I had this same problem when trying to install Google Earth in Linux. All the smaller archives I have downloaded seem to install fine???

[root@server1 Desktop]# bzip2 -tvv SecondLife_i686_1_18_1_2.tar.bz2
SecondLife_i686_1_18_1_2.tar.bz2:
[1: huff+mtf rt+rld]
[2: huff+mtf rt+rld]
[3: huff+mtf rt+rld]
[4: huff+mtf rt+rld]
[5: huff+mtf rt+rld]
[6: huff+mtf rt+rld]
[7: huff+mtf rt+rld]
[8: huff+mtf rt+rld]
[9: huff+mtf rt+rld]
[10: huff+mtf rt+rld]
[11: huff+mtf rt+rld]
[12: huff+mtf rt+rld]
[13: huff+mtf rt+rld]
[14: huff+mtf rt+rld]
[15: huff+mtf rt+rld]
[16: huff+mtf rt+rld]
[17: huff+mtf rt+rld]data integrity (CRC) error in data

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

[root@server1 Desktop]#

I will try doing a wget and see if that works.

Thanks for your suggestion, Chrysocolla Rau!
Morbid Blackadder
Registered User
Join date: 24 Aug 2007
Posts: 33
08-24-2007 21:41
This is the output from wget:

[root@server1 Desktop]# wget http://s3.amazonaws.com/download-secondlife-com/SecondLife_i686_1_18_1_2.tar.bz2
--00:22:42-- http://s3.amazonaws.com/download-secondlife-com/SecondLife_i686_1_18_1_2.tar.bz2
=> `SecondLife_i686_1_18_1_2.tar.bz2'
Resolving s3.amazonaws.com... 72.21.203.129
Connecting to s3.amazonaws.com|72.21.203.129|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 51,746,585 (49M) []

100%[====================================>] 51,746,585 166.72K/s ETA 00:00

00:28:36 (142.83 KB/s) - `SecondLife_i686_1_18_1_2.tar.bz2' saved [51746585/51746585]

[root@server1 Desktop]#



And this is the output from bzip2 -tvv:

[root@server1 Desktop]# bzip2 -tvv SecondLife_i686_1_18_1_2.tar.bz2 SecondLife_i686_1_18_1_2.tar.bz2:
[1: huff+mtf rt+rld]
[2: huff+mtf rt+rld]
[3: huff+mtf rt+rld]
[4: huff+mtf rt+rld]
[5: huff+mtf rt+rld]
[6: huff+mtf rt+rld]
[7: huff+mtf rt+rld]
[8: huff+mtf rt+rld]
[9: huff+mtf rt+rld]
[10: huff+mtf rt+rld]
[11: huff+mtf rt+rld]
[12: huff+mtf rt+rld]
[13: huff+mtf rt+rld]
[14: huff+mtf rt+rld]
[15: huff+mtf rt+rld]
[16: huff+mtf rt+rld]
[17: huff+mtf rt+rld]
[18: huff+mtf rt+rld]data integrity (CRC) error in data

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

[root@server1 Desktop]#

Does anyone have an alternate download location or a checksum for a good SecondLife_i686_1_18_1_2.tar.bz2 file?

Any other suggestions?

Maybe I should defrag my hard disk???
Morbid Blackadder
Registered User
Join date: 24 Aug 2007
Posts: 33
08-24-2007 23:18
OK, I have found that running bzip2 -tvv SecondLife_i686_1_18_1_2.tar.bz2 multiple times finds errors in different file sections every time it's run.

Any ideas on why this might be happening?
Boroondas Gupte
Registered User
Join date: 16 Sep 2005
Posts: 186
just wondering ...
08-25-2007 06:34
If you copy the archive:
cp SecondLife_i686_1_18_1_2.tar.bz2 mycopy.tar.bz2
and then diff the original and the copy
diff SecondLife_i686_1_18_1_2.tar.bz2 mycopy.tar.bz2
does it report the two files to differ?
Morbid Blackadder
Registered User
Join date: 24 Aug 2007
Posts: 33
08-25-2007 10:22
Hi Boroondas!

No, diff reports nothing.

I tried doing a fsck during reboot and that reported no problems as well.

I've just finished replacing my (2) 512mb ddr1 ram with a 1gb ddr1 ram, and that didn't solve the problem either.

Are there any alternate sites for me to try downloading SecondLife_i686_1_18_1_2.tar.bz2 from, or does anyone know what the check sum should be for this one: http://s3.amazonaws.com/download-secondlife-com/SecondLife_i686_1_18_1_2.tar.bz2

Thanks for all your help!
Morbid Blackadder
Registered User
Join date: 24 Aug 2007
Posts: 33
Success!
08-25-2007 10:56
Yea!

I got Second Life client running in Linux!

I downloaded the tar.bz2 file to my Windows machine and unpacked it there with 7-zip to a tar file. Then, I copied the tar file over to my Linux machine and extracted it!

Yea for 7-zip that was nice enough to unpack the bz2 file on a Windows machine! Of course, Windows would have nothing to do with the bz2 file.

There must either be something wrong with my bzip2 or I have a hardware problem, but I am now running the Second Life client in Linux! Yea! Yea! Yea!
Boroondas Gupte
Registered User
Join date: 16 Sep 2005
Posts: 186
08-26-2007 03:39
From: Morbid Blackadder
I got Second Life client running in Linux!
woohoo! :-)
From: Morbid Blackadder

I downloaded the tar.bz2 file to my Windows machine and unpacked it there with 7-zip to a tar file. Then, I copied the tar file over to my Linux machine and extracted it!

Weird. When I wget and test the archive, just like you did it's reported to be intact. If it's also neither the hard disk nor buggy RAM, then the only thing I can imagine is a damaged bzip binary. Maybe reinstall bzip?