Partimage: "Can't Read Block 0 from Image"

ebedosu · 07-14-2006, 03:05 PM

This error occurs on recovery at the point partimage tries to read the second file (.001) of the divided image file I made with Partimage.

I've seen this fix here: http: // pittman.ws/articles/howto/partimage . html

However, I don't know how to apply it to my case which does not involve a network. I simply saved the image of an old Win 98 PC to an external hard drive. Now, I have the original external hard drive and a second external hard drive that I'm trying to restore the image to via Partimage in Knoppix.

Can I concatenate the .000, .001, and .002 image files and run Partimage again, or can I use some workaround?

Thanks.

jschiwal · 07-14-2006, 03:23 PM

From the error message, it sounds like the hard drive that contains the .001 file is corrupt. You might try simply copying this file to /dev/null. If you get an IO error again, you will also get it trying to cat the file. There may be a option to the dd program that ignores IO errors and copies what it can. You could try A) renaming the .001 file to something else; B) using dd to copy from this file to a new .001 file. Then cat it together, hopefully to a different hard drive, and see if you can mount the drive using a loopback device. You may be able to recover some of the contents if you are lucky.

ebedosu · 07-14-2006, 05:04 PM

I want to try this solution but I'm new to shell and don't know how to translate this to fit my Ubuntu environment. I don't know when to keep things capitalized and when to leave the $ in and what needs to be substituted.

From the partimage.org forum:

Code:

# this bash-code expects the backup files as $BACKUPSET.000,
# $BACKUPSET.001, etc. Modify to match your environment.
toskip=0
{
  for partfile in $BACKUPSET.*; do
    zcat $pertfile | dd skip=$toskip 2>/dev/null
    toskip=1
  done;
} | partimage $RESTORE_OPTS restore $DEVICE stdin

ebedosu · 07-15-2006, 10:38 AM

If you search the forums for partimage.org you'll find another solution was to press the scroll-lock key every .5 or 1GB or so.

After getting some help with the shell script, it still wasn't working, so I tried scroll-lock.

It required manual attention, but, damn, it worked.