Custom Query (684 matches)

I received below message while restore mondorescue backup, When I boot from ISO. I am testing it on centos5 installed on virtualbox :

> No filesystem could mount root, tried ext2 iso 9660
> Kernel panic - not syncing VFS unable to mount root fs on unknown
> block(hd1,0)

Below is my syslinux/syslinux.cfg file content:

prompt 1
display message.txt
F1 message.txt
F2 boot1.txt
F3 boot2.txt
F4 pxe.txt
default interactive
timeout 300

label interactive
    kernel /vmlinuz
    append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=182964
interactive apm=0ff devfs=nomount noresume selinux=0 barrier=off
udevtimeout=10
label expert
    kernel /vmlinuz
    append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=182964 expert
apm=0ff devfs=nomount noresume selinux=0 barrier=off
udevtimeout=10
label compare
    kernel /vmlinuz
    append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=182964 compare
apm=0ff devfs=nomount noresume selinux=0 barrier=off
udevtimeout=10
label iso
    kernel /vmlinuz
    append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=182964 iso
apm=0ff devfs=nomount noresume selinux=0 barrier=off
udevtimeout=10
label nuke
    kernel /vmlinuz
    append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=182964 nuke
apm=0ff devfs=nomount noresume selinux=0 barrier=off
udevtimeout=10
label isonuke
    kernel /vmlinuz
    append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=182964 isonuke
apm=0ff devfs=nomount noresume selinux=0 barrier=off
udevtimeout=10

Kindly guide me how to get rid off this issue ? Moreover i have attached log files as well, please look into it. Below are the details of mondorescue versions:

Mindi-BusyBox v1.21.1-r3332 Mindi 3.0.2-r3578 Mondo-3.2.2-1.rhel5.x86_64 perl-ProjectBuilder 0.14.6-1

Regards, Osama

I see this in the messages file about 100 times every time mondobackup runs. Why?

See attached mondoarchive.log.

After mondobackup complete, we are seeing this mount get left behind. It's small and tends to be over 90% full, which causes our monitoring software to create a ticket.

SLES 12 SP1

# rpm -qa | grep -i mondo
mondo-3.2.2-1.sles12.x86_64
perl-MondoRescue-3.2.2-1.sles12.noarch

# rpm -qa | grep -i mindi
mindi-busybox-1.21.1-1.sles12.x86_64
mindi-3.0.2-1.sles12.x86_64

# df | grep loop
/dev/loop0                                 110766  100996      9770  92% /tmp/syslinux.mnt.10184.0

I've never seen this behavior before. Help?