l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
January 6: Social gathering
Next Installfest:
TBD
Latest News:
Nov. 18: Club officer elections
Page last updated:
2003 May 17 08:55

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] un-tar failing on large job
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] un-tar failing on large job



Avoid using the built-in uncompression part of tar:
$ zcat filename.tar.gz | tar xvf -
(Or if .bz2 file:)
$ bzcat filename.tar.bz2

If that fails...

See if the error comes up when you just list the contents of the tarbal:
$ zcat filname.tar.gz | tar txv -

(Watch where it fails to read)

Also, is the tarball a ".Z" or ".gz" or ".bz " file?

Try to repeat the extract multiple times. If the error comes up at
different points, then this suggests hardware. If the the same points,
that suggests hardware. (Of course these are not absolute rules, just
common associations.)

Since you say the md5 checksums are correct, it is not an issue of
transfer (8-bit image vs 7 bit ASCII.)


-ME


> Halloall;
>
> I'm finally putting to use one of the dump-boxen that I've picked up
> (166mhz, 64megs ram, 2gig drive, partridge in pear tree, etc.), for
> experimenting with a Gentoo install.
>
> And of course, nothing goes according to plan.  After formatting the
> drive,
> setting up mount points, etc. the next step I'm on to un-tar the install
> files onto the drive in what eventually will become the root directory.
> This has failed 3 out of 3 times, using 2 different copies of the Stage3
> tar.gz (100megs approx) and one version of the Stage2 tar.gz (50-80megs
> approx).
>
> The final time I tried this, tar finally gave me a list of what might be
> going wrong:
>   - bad compressed file (This is doubtful - the last time I pulled it down
> from Gentoo, I ran an MD5 check to make sure the file was intact.)
>   - bad hardware - either memory or cache hardware.  (I've got new SIMMS
> on
> order--will try this soon.)
>
> Those were the avenues I've checked so far.  Anyone have a suggestion as
> to
> what ELSE I might look in to?
>
> Danke
>
>
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
>
>

_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech



LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.