Comment 7 for bug 179141

Pedro,
I have personally submitted multiple error logs in the past and never heard anything back. I just had a case in which mondorestore ate my system drive. It restored to 1% and then died with the fatal error message "MOMMY!" rendering my entire system unusable.

Both log files can be found as an attachment below. Is this everything you need? Can I be of any further assistance?

I have no idea how long it will take the dev gang to diagnose and fix it and to publish RPMs for my latest-n-gratest Suse 11.1 x86_64 and I would really like to get my image back.

I was going to write a Perl script to mount the ISO, decompress the .bz2 images and see if I could figure out how to mate the files listed in all.tar.gz to the images. Bunzip2 tells me:
brianp@godzilla:/tmp$ bunzip2 0.afio.bz2
bunzip2: 0.afio.bz2 is not a bzip2 file.

How can I decompress mondo's .bz2 files? Do I have any hope of reassembling the original image or am I just smoking rope? Last night, I tried mondo-2.2.6-2.3.x86_64.rpm on a victim system with a quick-n-dirty, minimal Suse 11.1 and got the same 1% "MOMMY!" fatal error. All of the prerequisites (afio, newt, etc.) were installed with stock, YAST modules.

Can you point me to a well behaved mondo which will work on Suse 11.1/64 bit running on an Intel core2 quad q9550 running on an Asus p5q3 with an intel p45/ich10r chipset? The latest version, mondo-2.2.8, appears only in the Asian releases and in SLES 10 on http://mondorescue.org -> download. I can't read Chinese. :-)

The Suse version only goes to 11.0. and is version 2.0.6. Will using an ancient version of mondo built for an old version of Suse be a Quixotic exercise without hope of success?

Grasping at straws,

    BrianP