partimage works, now it does not

[andre72]

Testing PartImage/SystemRescueCD on two systems that I was reconfiguring:

1. AMD64 machine, backed up the Win2K NTFS 20GB system partition to an ext3 backup partition. Restored it successfully later. System Rescue Disk established network connections correctly and allowed internet access.

2. Tried the same on a Dell Dimension WinXP machine. First issue, unable to connect to the network. Backed up the WInXP 60GB partition to an ext3 backup partition. Could not restore it later, recceived an "invalid compression level for file sysc.gz.000" message. Repeated the whole operation - save & restore - again, creating a new backup image, with the same result.

PartImage was exactly what I needed, but I am afraid there is an issue of dependability.

Why do I get an "invalid compression level" as I try to restore a file created by the very same utility? Why does it happen on one machine and not on the other?

[feffer]

Andre, as far as I know, partimage is not being actively developed, so I don't think you will get a definitive answer from anyone "in the know" on this project. While I continue to use partimage and have had no issues saving and restoring (mostly) linux ext3 partitions, I haven't used it on Windows NTFS systems. However, it should work. You might try using a different compression level. Also, be aware that if you are using gzip compression, you need to append ".gz" to your image file-name, like "mysavedimage.gz" You shouldn't add the ".000" which partimage automatically adds. Also try re-reading the partimage manual to be sure you haven't missed something.

If those efforts fail, you might try using clonezilla, an open-source project based on partimage. Or if you're willing to use the command line, there is a reliable and actively developed free app called "dd". Of course there are proprietary Windows specific cloning apps too.

PartImage was exactly what I needed, but I am afraid there is an issue of dependability.

It would be great if someone would restart the partimage project. As you imply, it fills a really useful niche.

feffer

[andre72]

Thank you for your reply. I am very sorry to read that PartImage is not being actively developed any longer.

For the record, in case someone taking up this project does read this:

1. On a Dell Dimension:

-> I saved the 60GB NTFS XP partition to an ext3 partition, as sysc.gz and PartImage did add the .000 itself. The compressed file was some 8.4GB which seems right, as only a very small portion of the partition was used.

-> Reading the sysc.gz.000 file failed with the "invalid compression level" message on two separate save-restore attempts. In addition, I tried removing the ".000" extension and restore from the resulting "sysc.gz" file. Same message.

-> This was not a failure to restore to the NTFS partition, but a failure when reading the backup file from the ext3 partition where it had been written to it earlier.

-> As far as can I remember, I used gzip - the default - in all cases. Did I accidentally change the compression level when attempting to restore?
It could have happened, of course, but I cannot see how it would have occured twice - 3 times actually, 2 attempts with the sysc.gz.000 and one with the renamed sysc.gz file.


2. Previously on my AMD64 machine:

-> PartImage worked perfectly the 1st time, saving the NTFS Win2K system partition to an ext3 backup file, and then restoring it correctly. In this case, the system partition was 20GB, and the gzip compressed backup file about 4.8GB.


3. It is sad that such a great project should be altogether abandoned, and I do wish I could contribute, it would have been a pleasure and an honour, but I am afraid this is far beyond my abilities.

Andre

[nvieville]

Hello to all,

Maybe this post should help!

http://www.partimage.org/forums/viewtopic.php?t=420

Be careful, it might need some tweaks!

Cordially


--
nvieville

[andre72]

nvieville, thanks for your tip. I understand however that the reference addresses the issue of restoring from split image files. I also note that:
"Sadly, his solution did not work with splits of 4GB due to limitations in the gzip file standard"

As mentioned in my previous post, I had only one 8.4GB image file, significantly larger that the 4GB mentioned. Could that have been the problem?

Honestly, considering the fact that there does not appear to be the active involvement of a developer, at this point I am not prepared to run tests to replicate the issue just after a clean - and lengthy - reinstall of my system.

Best regards

Andre

[nvieville]

Hello Andre72

I think your solution was explained in this post (sorry, found too late):

http://www.partimage.org/forums/viewtopic.php?t=213

The right command to use must be of this form:

gunzip -c imagefile | partimage restore partition stdin

I used this tip with success to restore large saved partitions (more than 4GB for the image file) stored on a ftp server, while booting the host to restore with SystemRescueCD. The command line was (on one line):

wget -qO - ftp://path_to_imagefile/imagefile | gunzip -q -c | partimage -f3 -b -e restore partition_to_restore stdin

Be careful to not forget the dash between two spaces after wget option -qO, unless the pipe to gunzip won't work.

Even if you got a just cleanly and lengthy installed system, I guess it would be safe to save it, now you've got the right tip to restore it later ;) (I hope).

Best regards,


--
nvieville

[andre72]

Hi nvieville.

Yes, the posts you referenced concern the very same issue, and it is clearly a partimage bug. Perhaps I should have spent more time scanning for previous issues before starting a new thread. Sorry about that.

The sad thing about this all is that the issue was reported first in 2004, and the following posts are dated 2005, 2006, 2007, 2008. I am surprised that the bug has not been reported more frequently over all these years. It is clear however that the chances of seeing a proper fix are slim.

I note that one poster reports that breaking down the backup file into smaller segments worked for him. Interesting.

To conclude, I will back up both to a single (large) image file, and to a another segmented backup. If the worst happens, I will be able to test both suggestions ie the command you gave me, and the segmented approach.

I dare hope that these tests will never be made.....

Thanks again

Andre