Re: Problem with restore in virtualbox
Marco Marino <[email protected]> Fri, 5 Apr 2019 11:22:15 +0200
| Newsgroups | gmane.linux.mondo.devel |
|---|---|
| Message-ID | <CAFHVVu+HReiTaiJM=9k2xBL3MYTdRt_q6XTVNuCvwYWAsfojgw@mail.gmail.com> |
It seems there is a problem with syslinux. Some detail here:
content of mondorescue-1.iso:
total 23M
dr-xr-xr-x. 6 root root 2.0K Jun 15 2017 .
drwxr-x--x. 3 ntt ntt 68 Apr 5 10:32 ..
dr-xr-xr-x. 2 root root 192K Jun 15 2017 archives
-r-xr-xr-x. 1 root root 1.7K Jun 15 2017 autorun
-r--r--r--. 1 root root 19 Jun 15 2017 HOSTNAME
dr-xr-xr-x. 2 root root 2.0K Jun 15 2017 images
-r--r--r--. 1 root root 21M Jun 15 2017 initrd.img
-r--r--r--. 1 root root 4 Jun 15 2017 LAST-FILELIST-NUMBER
dr-xr-xr-x. 2 root root 2.0K Jun 15 2017 syslinux <----- note this
folder !
dr-xr-xr-x. 3 root root 2.0K Jul 16 2011 usr
-r--r--r--. 1 root root 1.9M Jun 15 2017 vmlinuz
Content of the file syslinux/syslinux.cfg:
cat syslinux/syslinux.cfg
prompt 1
display message.txt
F1 message.txt
F2 boot1.txt
F3 boot2.txt
F4 pxe.txt
default iso
timeout 300
label interactive
kernel /vmlinuz
append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203368
interactive devfs=nomount noresume selinux=0 barrier=off udevtimeout=10
label expert
kernel /vmlinuz
append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203368 expert
devfs=nomount noresume selinux=0 barrier=off udevtimeout=10
label compare
kernel /vmlinuz
append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203368 compare
devfs=nomount noresume selinux=0 barrier=off udevtimeout=10
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
label nuke
kernel /vmlinuz
append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203368 nuke
devfs=nomount noresume selinux=0 barrier=off udevtimeout=10
label isonuke
kernel /vmlinuz
append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203368 isonuke
devfs=nomount noresume selinux=0 barrier=off udevtimeout=10
Current version of packages:
rpm -qa | grep mindi
mindi-busybox-1.21.1-1.rhel5
mindi-3.0.2-1.rhel5
rpm -qa | grep mondo
mondo-3.2.2-1.rhel5
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)
Should I give you other details?
Is there a way to fix this?
Thank you
Il giorno ven 5 apr 2019 alle ore 11:16 Bruno Cornec <[email protected]>
ha scritto:
> Hello,
>
> Marco Marino said on Fri, Apr 05, 2019 at 09:51:39AM +0200:
> >Hello, I'm trying to test my mondorescue backup through virtualbox (but I
> >I tried to create a new vm in virtualbox with boot from cdrom. in the
> cdrom
> >device I loaded the file mondorescue-1.iso but when the vm starts I see
> the
> >error message: "Could not find kernel image: linux"
>
> That's the correct procedure indeed. So your ISO file seems to be
> incorrect. Can you provide your /var/log/mondoarchive.log made on the
> original system please ?
>
> Best regards,
> 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
>
>
> _______________________________________________
> Mondo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>
_______________________________________________
Mondo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mondo-devel