Re: CentOS 7: restore fails

Nikolaos Milas <[email protected]>
Newsgroups gmane.linux.mondo.devel
Organization National Observatory of Athens
Message-ID <[email protected]>
On 3/5/2017 11:32 πμ, Nikolaos Milas wrote:

As
I know little about grub2 (and low-level linux) to troubleshoot
the issue, can you please help identify and correct the problem?

I tried to post the mondorestore.log of this VM in a
separate mail, but it obviously failed to be delivered to this
list ("message body too big").

You can find it here:
http://iweb.noa.gr/files/centos7/mondorestore.log

The following seems to be the most relevant part regarding
grub:

DBG4: [Main] libmondo-tools.c->read_cfg_var#1068:
Configuration item bootloader.device is /dev/vda

DBG4: [Main] libmondo-tools.c->read_cfg_var#1068:
Configuration item bootloader.name is GRUB

DBG2: [Main]
../src/mondorestore/mondo-rstr-tools.c->run_boot_loader#1300:
run_boot_loader: device='/dev/vda', name='GRUB'

INFO: Non-interactive mode: no way to give you the
keyboard so that you re-generate your initrd. Hope it's OK

DBG1: [Main]
../src/mondorestore/mondo-rstr-tools.c->offer_to_make_initrd#1257:
Non-interactive mode: no way to give you the keyboard so that
you re-generate your initrd. Hope it's OK

INFO: running: which mr-grub >
/tmp/mondo.tmp.ap2nqv/mondo-run-prog-thing.tmp 2>
/tmp/mondo.tmp.ap2nqv/mondo-run-prog-thing.err

INFO: --------------------------------start of
output-----------------------------

INFO: /bin/mr-grub

INFO: --------------------------------end of
output------------------------------

INFO: ...ran just fine. :-)

DBG1: [Main]
../src/mondorestore/mondo-rstr-tools.c->run_grub#1479: Yay!
mr-grub found...

DBG1: [Main]
../src/mondorestore/mondo-rstr-tools.c->run_grub#1481:
command = mr-grub /dev/vda /tmp/mountlist.txt

INFO: Running
GRUB...

DBG2: [Main]
../src/mondorestore/mondo-rstr-tools.c->run_grub#1488:
mr-grub /dev/vda /tmp/mountlist.txt

Now I'll use grub-install

Launching: chroot /mnt/RESTORING grub-install /dev/vda

chroot: can't execute 'grub-install': No such file or
directory

grub-install returned 127

Now I'll use grub2-install

Installing for i386-pc platform.

grub2-install: error: cannot find a GRUB drive for
/dev/vda1. Check your device.map.

grub2-install returned 1

Trying a hack

Checking usr/lib/grub/i386-pc

Cannot find BOOTPATHNAME

.............Cool.

device (hd0) /dev/vda

root (hd0,0)

setup (hd0)

quit

chroot: can't execute 'grub': No such file or directory

Hack returned res=0

INFO: running: mr-grub /dev/vda /tmp/mountlist.txt >
/tmp/mondo.tmp.ap2nqv/mondo-run-prog-thing.tmp 2>
/tmp/mondo.tmp.ap2nqv/mondo-run-prog-thing.err

INFO: --------------------------------start of
output-----------------------------

INFO: Checking usr/lib/grub/i386-pc

INFO: Cannot find BOOTPATHNAME

INFO: .............Cool.

INFO: --------------------------------end of
output------------------------------

INFO: ...ran just fine. :-)

INFO: Done.

INFO: Your boot loader ran OK

DBG1: [Main] mondorestore.c->nuke_mode#2180: Great!
Boot loader was installed. No need for msg at end.

In the meantime, I tried to fix the cloned VM using the rescatux
( https://sourceforge.net/projects/rescatux/ )
repair disk; it failed as well. See attached images.

The situation remains the same
(i.e. I can only boot using the super-grub2 disk).

How can we fix this cloned CentOS 7 installation to become
bootable?

Thanks,

Nick

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Mondo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mondo-devel
rescatux-scratchvm-20170504-01.png (image/png, 65.3 KB) - not displayed
rescatux-scratchvm-20170504-02.png (image/png, 16 KB) - not displayed
rescatux-scratchvm-20170504-03.png (image/png, 22.6 KB) - not displayed
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.