Re: Problem with restore in virtualbox
Bruno Cornec <[email protected]> Fri, 5 Apr 2019 11:52:08 +0200
| Newsgroups | gmane.linux.mondo.devel |
|---|---|
| Message-ID | <[email protected]> |
Marco Marino said on Fri, Apr 05, 2019 at 11:22:15AM +0200: >It seems there is a problem with syslinux. Some detail here: Well, in fact on a CD the tool really used is isolinux. And you don't see the boot image used as it is not stored in this part. But what you see is what has been used to create that boot image. >content of mondorescue-1.iso: >-r--r--r--. 1 root root 21M Jun 15 2017 initrd.img >dr-xr-xr-x. 2 root root 2.0K Jun 15 2017 syslinux <----- note this folder ! >-r--r--r--. 1 root root 1.9M Jun 15 2017 vmlinuz >cat syslinux/syslinux.cfg >default iso > >label iso > kernel /vmlinuz > append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203368 iso devfs=nomount noresume selinux=0 barrier=off udevtimeout=10 So it seems that you have the correct setup and files in place. >Current version of packages: >mindi-busybox-1.21.1-1.rhel5 >mindi-3.0.2-1.rhel5 >mondo-3.2.2-1.rhel5 Looks good to me as well. >OS = Centos 5 (2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:37 EDT 2012 i686 i686 i386 GNU/Linux) If I were working for Red Hat, I'd say that you have a version which is not supported anymore (especially from a security perspective) But i'm not, so in fact from a MondoRescue perspective, I don't see a reason for not solving the issue. >Should I give you other details? Yes I'd still like to get the log file please (/var/log/mondoarchive.log). >Is there a way to fix this? Hopefully yes ;-) Will let you know with the log. I may need to do tests on my side as well to understand why isolinux is not working correctly for this combination. Bruno. -- HPE WW FLOSS Technology Strategist http://www.hpe.com/engage/opensource Open Source Profession, WW Linux Community Lead http://github.com/bcornec FLOSS projects: http://mondorescue.org http://project-builder.org Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org