Opened 3 years ago

Last modified 23 months ago

#817 new defect

Mondo/mindi creating unbootable ISOs

Reported by: Craig E Johnson Owned by: Bruno Cornec
Priority: normal Milestone: 3.3.0
Component: mondo Version: 3.0.2
Severity: normal Keywords:
Cc:

Description (last modified by Bruno Cornec)

When attempting to boot/restore from the image(s), I get:

ISOLINUX 3.82 3.82 ETCD Copyright (C) 1994-2009 H. Peter Anvin et al
Could not find kernel image: linux
boot:

Info from source server:

# uname -a
Linux j700s014 3.0.101-0.47.52-default #1 SMP Thu Mar 26 10:55:49 UTC 2015 (0e3c7c8) x86_64 x86_64 x86_64 GNU/Linux
# rpm -qa | grep -i mondo
perl-MondoRescue-3.2.2-1.sles11
mondo-3.2.2-1.sles11
# rpm -qa | grep -i mindi
mindi-busybox-1.21.1-1.sles11
mindi-3.0.2-1.sles11

Attachments (1)

mindi.logs.tgz (62.2 KB) - added by Craig E Johnson 3 years ago.

Download all attachments as: .zip

Change History (7)

Changed 3 years ago by Craig E Johnson

Attachment: mindi.logs.tgz added

comment:1 Changed 3 years ago by Craig E Johnson

My gzipped mondoarchive.log file is 4.7MB and I can't attach/upload it. Help.

comment:2 Changed 3 years ago by Bruno Cornec

Version: 3.2.23.0.2

Try compressing it with bzip2/xy and send it by mail to me if you still can not attach it here.

comment:3 Changed 3 years ago by Craig E Johnson

Done. Please check e-mail. Here is some more info from the boot ISO itself. I mounted it at /mnt on a Linux server so I can poke around. It looks pretty good to me. Doesn't work though!:

s091s012:/mnt/syslinux # ll /mnt total 46397 dr-xr-xr-x 2 root root 2048 Jun 4 02:39 archives -r-xr-xr-x 1 root root 1717 Jun 4 02:39 autorun dr-xr-xr-x 2 root root 2048 Jun 4 02:39 images -r-xr-xr-x 1 root root 43520695 Jun 4 02:39 initrd.img -r-xr-xr-x 1 root root 15278 Jun 4 04:39 ldlinux.sys dr-xr-xr-x 2 root root 2048 Jun 4 02:39 syslinux dr-xr-xr-x 2 root root 2048 Jun 4 02:39 tmp -r-xr-xr-x 1 root root 3963680 Jun 4 02:39 vmlinuz

s091s012:/mnt/syslinux # cat syslinux.cfg 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=203568 interactive devfs=nomount noresume selinux=0 barrier=off udevtimeout=10

label expert

kernel /vmlinuz append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203568 expert devfs=nomount noresume selinux=0 barrier=off udevtimeout=10

label compare

kernel /vmlinuz append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203568 compare devfs=nomount noresume selinux=0 barrier=off udevtimeout=10

label iso

kernel /vmlinuz append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203568 iso devfs=nomount noresume selinux=0 barrier=off udevtimeout=10

label nuke

kernel /vmlinuz append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203568 nuke devfs=nomount noresume selinux=0 barrier=off udevtimeout=10

label isonuke

kernel /vmlinuz append initrd=/initrd.img root=/dev/ram0 rw ramdisk_size=203568 isonuke devfs=nomount noresume selinux=0 barrier=off udevtimeout=10

Version 0, edited 3 years ago by Craig E Johnson (next)

comment:4 Changed 3 years ago by Craig E Johnson

Hi Bruno. I was able to work around this issue by doing the following at the prompt after it failed:

boot:  /vmlinuz initrd=/initrd.img

Then it would boot into the mondo restore environment. I would like to know why these ISOs are failing to boot correctly though.

Last edited 23 months ago by Bruno Cornec (previous) (diff)

comment:5 Changed 23 months ago by Bruno Cornec

Description: modified (diff)

comment:6 Changed 23 months ago by Bruno Cornec

The strange error is that it said to you it tries to find a "linux" kernel image, which is not a label used by MondoRescue?.

So I wonder whether the isolinux.bin file finds the right conf file to read from in your env...

Or whether that version of isolinux has an issue...

Note: See TracTickets for help on using tickets.