Custom Query (684 matches)

Hello-

Running MondoRescue V2.2.9.3-r2622. My system is Fedora Core 12 (2.6.32 kernel) on an IBM System x3650 M2. This is a clean system just built, and I wanted to test backup and restore to an identical machine.

I used Mondo to back the system up to 2 CD's, and this seemed to go fine, but upon restoral ("nuke") to an identical system, the bootable CD boots up, starts Linux, and then stops with the error: "can't access tty; job control turned off"

Please advise - this is similar to what was happening in Ticket 256.

Thanks Scott S

I'm trying to restore a physical image to a VM. The image is from an HP DL380 G9 running RHEL 7.3. The VM host is running ESX. The VM guest is configured with a 32GB virtual disk and 8GB RAM, and the SCSI controller is set to "LSI Integrated".

When I run mondorestore, for some reason all of the filesystems in the mountlist other than /boot and /dev/sda2 show size 0. I have to modify the mountlist so they are large enough to "fit" the actual filesystem usage.

FYI: There is only one data iso, and it is < 2GB.

mondo-3.2.2-1.rhel7.x86_64 mindi-3.0.2-1.rhel7.x86_64 mindi-busybox-1.21.1-1.rhel7.x86_64

The restore seems to go fine, until the very end when "largefiles" are being recovered. Then I see:

"Working on DVD #1, file X, slice Y full?"

Cannot openout outfile_fname - hard disk full? Errors occurred while data was being restored. You will now edit multipath.conf (really?) Initialize the boot loader y/n? y Re-generate initd? y/n? n Did you change mountlist y/n? n Label partitions y/n? n

Exits to shell. Cannot find mount-me nor grub.

# exit (reboot) "Grub loading stage 1.5

Grub loading please wait

Error 22"

Reported to me:

I made a mondoarchive to a DVD. (Proliant DL380 G5). Booting from that DVD goes fine, I can launch the "compare" that completes fine but when typing 'exit' to reboot, it goes wrong: this causes a Kernel panic...

Idem if I boot DVD and select "expert" mode, selecting 'exit' from cli gives a Kernel panic as well...

Is there another way to 'nicely' reboot the box from the normal harddisk after such operation other than power-cycling the box or selecting "Reset" from the ilo-power button?

I've also seen that with test on RHEL 6 in a QEMU VM.