mandriva LE2005 + mondo

[Guest IanG]

I'm trying to create some bootable backup CD's.

 

Anyone got mondo working using the Mandriva LE2005 supplied kernel?

(If so some tips please.)

 

Is it possible - or do you have to use the mindi failsafe kernel.

 

Thanks in advance,

 

Ian

[RVDowning]

I'm looking for an answer to the same question. Worked fine under 10.1 and worked fine after i upgraded to LE2005. But after a clean install of LE2005 I can't get it to work any more.

 

Rich

[tyme]

have you tried installing it in one form or another? if so, what errors do you get? if not, why not? :P

[RVDowning]

Following is the consol from an attempt at running the Mindi test. I'm using the version of mondoarchive downloaded from the LE2005 mirrors.

----------------

 

Do you want to use your own kernel to build the boot disk (y/n) ?y

Your kernel is /boot/vmlinuz-2.6.11-6mdk (v2.6.11-6mdk)

Would you like to use LILO (instead of syslinux)

for your boot CD/floppies (y/n) ?y

Analyzing dependency requirements Done.

Making complete dependency list Done.

Analyzing your keyboard's configuration.

Adding the following keyboard mapping tables: us qwerty-layout euro windowkeys compose linux-

with-alt-and-altgr linux-keys-bare Done.

Assembling dependency files.....................................Done.

The files have been subdivided into 5 directories.Your mountlist will look like this:-

DEVICE MOUNTPOINT FORMAT SIZE (MB)

/dev/hda1 / reiserfs 4698

/dev/hdb1 /home reiserfs 19539

/dev/hda10 /opt reiserfs 25281

/dev/hda8 /tmp reiserfs 1992

/dev/hda6 /usr reiserfs 9993

/dev/hda9 /usr/local reiserfs 4996

/dev/hda7 /var reiserfs 9993

/dev/hda5 swap swap 1678

Tarring and zipping the groups.................. Done.

Creating data disk #1...#2...#3...#4...#5... Done.

Making 1722KB boot disk...........................OK, you don't have a /boot/boot.b file,

which is oddbecause most _good_ Linux distributions come with one, even if it's only a softlink

Nor can I find it from your /etc/lilo.conf file. This is very odd.

I'm going to use '/boot/boot.0300'

Failed to copy /tmp/mindilinux/22240/mindi.rdz to /tmp/mindilinux/22240/mountpoint.22240

 

cat: /tmp/mindilinux/22240/mtpt.22240: No such file or directory

Please unload some of your modules and try again.

 

Cannot incorporate mindi.rdz in bootdisk (kernel / modules too big?)

1440+0 records in

1440+0 records out

mke2fs 1.36 (05-Feb-2005)

cp: writing `vmlinuz': No space left on device

Failed to copy /boot/vmlinuz-2.6.11-6mdk to ramdisk

Warning - failed to create 1.44MB boot/root floppies

Warning! Failed to create 1.72MB boot image. Please reduce your kernel's size

if you want to make a 1.72MB floppy floppy disk.

Making 2880KB boot disk...........................OK, you don't have a /boot/boot.b file,

which is oddbecause most _good_ Linux distributions come with one, even if it's only a softlink

Nor can I find it from your /etc/lilo.conf file. This is very odd.

I'm going to use '/boot/boot.0300'

1440+0 records in

1440+0 records out

mke2fs 1.36 (05-Feb-2005)

cp: writing `vmlinuz': No space left on device

Failed to copy /boot/vmlinuz-2.6.11-6mdk to ramdisk

Warning - failed to create 1.44MB boot/root floppies

Fatal error. Failed to create 2.88MB floppy disk image.

 

tar: -f-: Cannot stat: No such file or directory

tar: Error exit delayed from previous errors

Please e-mail a copy of /tmp/mindi.err.22240.tgz to the mailing list.

See http://www.mondorescue.org for more information.

WE CANNOT HELP unless you enclose that file.

[Guest fahs]

Any one have any answers yet. I have tried everything I can think of, find on google, invent, pull out of my ... well anyway, i can not get it to work ... all the way through.

 

Here is what I have managed so far:

 

First I have had the same results on 3 very different sets of hardware all running ML2005 LE.

 

I can get Mindi to create a bootable CD. I've applied the patches mentioned on http://forum.mondorescue.org for increasing the bootimage size and that got me over that hurdle.

 

I have gotten Mondoarchive to run both from the gui and command line and have made seemingly succesful iso's there as well. I am writing my iso files to a seperate drive that has been excluded in the mondoarchive (-E) options.

 

The BIG PROBLEM that I face now is after I burn those iso's to disk and boot, the whole thing winds upwith the following line:

sh: can't access tty; job control turned off

It doesn't matter if I use the mindi or the mondo, and it doesnt matter waht option i choose to boot to (nuke et al), I always gett he same result. Google did not shed any results on that message that I understood as a probable fix. I have been workign on this for 2 weeks and am googled out over it.

 

Any one have any ideas, or perhaps a set of succesful steps they followed.

 

Please!

 

Thanks

[RVDowning]

Well, you're ahead of me. I can't get the DVD to boot up. I get Kernel panic - not syncing - No init found. Try passing init= option to kernel. I've tried my own 2.6.11.6 kernel as well as the mindi kerlel (FAILSAFE). Same kind of result.

 

Rich

[Guest fahs]

Well I can't get at the computer that has the software running (its currently doing another mondarchive too) at the moment but here is what I can remember of what I have done.

 

I went through all the software dependencies listed on mondorescue.org (look at the cd they offer) and make sure they are all installed.

 

I upgraded the mindi program to the stable-cvs version and then applied the patch I mentioned earlier. It just adds some attempts at generating the boot disks at >2.5mb or whatever the size is. There are actually 2 patches now that do the same thing, but one now goes all the way up too 11mb. If you can't find it let me knwo and I'll hunt it down again.

 

This was not required to get it too actually make the iso's but in my last attempt I uninstalled the contrib mondo packages and installed the 'stable-cvs' of the mondo pakage. Thats whats running now so we'll se what luck I have.

 

Hope that helps in some way. I know I had to add several packages for the dependencies so defintely check into that.

[RVDowning]

Well, I'll give it a try. Nothing to lose at this point.

 

I was just about to restore from my last LE2005-upgraded-from-10.1 backup which still uses the 10.1 kernel and which ran mondo/mindi fine. That is what I was planning to do, but I guess I can spend one more evening trying to get this to work. I've spent about two weeks trying to get this working so far.

 

Thanks for the tip. I'll report back.

[RVDowning]

Come to think of it, I may have already tried this.

 

The latest stable CVS for Mandriva seems to be:

mondo-2.04_cvs_20050503-1mdk101.i586.rpm and

mindi-1.04_cvs_20050503-1mdk101.i586.rpm

 

I don't find any specific patch files for this mindi. I think I have already gone through a patch file and manually made similar changes to the mindi script. I just don't remember whether it was these files some of the other versions.

 

I also don't know if I should be using the AMD 64 version since I have an AMD64 3000+ processor.

 

There are two directories for 10.1.x86-64 which just to be duplicates.

 

I've always had to apply the patch to get around the floppy problem unless I used the FAILSAFE kernel option, for which I had to download and install mindi-kernel. The install of this also puts it into a different directory and has to be copied over to the same directory where the mindi script was located.

[RVDowning]

It worked!!!

 

Download and installed mondo-2.04_cvs_20050503-1mdk101.i586.rpm and

mindi-1.04_cvs_20050503-1mdk101.i586.rpm

 

I didn't apply any patches. The command I used to backup to my DVD was:

mondoarchive -Or -d /dev/hdc -9 -gF -s 4200m -k /boot/vmlinuz

 

Still one bizarre issue, however.

 

When I attempt to boot from the DVD I get the following message:

"Segmentation Fault

/dev/ht0 failed to act as an extended data disk for booting.

Please specify an alternate tape device

or hit Enter to boot from CD/Floppies"

 

That is odd. I don't have any tape drive and didn't indicate one in the mondoarchive command. Anyway, I hit the Enter key and it then booted from my DVD and all was normal after that. I selected "interactive" and restored a test file and it was fine.

 

I can certainly live with it the way it is, but am curious about the error.