Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am trying to boot lucid server on my new VPS but its giving me some problems. The boot gets to a point where it hangs. At this point it says:

No such file `modules-2.6.31-20-server-amd64.tar.bz2'

zip2: Compressed file ends unexpectedly

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

tar: Child returned status 2
tar: Exiting with failure status due to previous errors

Module installation failed.

Does anyone have any ideas how I might be able to fix this? Sorry that this is rather vague!

share|improve this question
Where is the VPS hosted? Does the provider have any instructions on how to build the server? – Matt Delves Feb 15 '11 at 1:04
I'm using GrokThis. You essentially in install one of their distributions from images. It was quite simple to do but I can't seem to work around this problem. The general documentation is here: – seadowg Feb 15 '11 at 1:09
up vote 1 down vote accepted

From my point of view this looks as if the file "modules-2.6.31-20-server-amd64.tar.bz2" has been compromised. The name indicates that it is used during the userspace boot-part. You could either try to reupload the server image for your vps or try to download-fix-reupload the file: after a quick look into their reference, i think instance storage peekfs get would be the appropriate command.

My guess would be that either the VPS' storage or the server image(possibly during transfer) could have been compromised. Another possible cause could be a failled update of your kernel which caused the zipping of your modules file to fail.

share|improve this answer
I've tried re-imaging my VPS several times. I don't really understand what you mean by using that command? I'm quite new to setting these things up... – seadowg Feb 15 '11 at 10:58
if re-imaging didn't solve the problem. either the vps' block storage or the image itself is corrupted. maybe you should contact your hosters' support team? – mschneider Feb 16 '11 at 13:39

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.