Morten B. Christensen
2012-Mar-29 11:23 UTC
[syslinux] Defect ISO generation after yum upgrade
[cid:9FBAC256-5A30-4061-B74E-53A6B7B3D7BA at c-team.local] Hi all, Our own appliance is a Linux Kernel and 2 initrd files for filesystem - one system and one config partition. After the yum upgrade on our build machine ISO files are generated but useless. I you are able to see the picture I would like to know "who" writes the - Loading /system.igz? failed! Is it the kernel already loading the cpio+gzip'ed file or is it still isolinux. This script generates new ISO files #!/bin/bash BUILDPATH=/proxygen GENERATEDPATH=/var/www/html/proxy/generated # if build command contains buildsystem a new system is build if [[ $@ = *buildsystem* ]]; then # Build initramfs rm -f $BUILDPATH/boot/system.igz chown -R 0:0 $BUILDPATH/system cd $BUILDPATH/system find . -print0 | cpio --null -ov --format=newc | gzip > $BUILDPATH/boot/system.igz fi # Build file containing config rm -f $BUILDPATH/boot/config.igz cd $BUILDPATH/config find . -print0 | cpio --null -ov --format=newc | gzip > $BUILDPATH/boot/config.igz # Build ISO cd $BUILDPATH/boot mkisofs -o $GENERATEDPATH/$1.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -r -l -boot-load-size 4 -boot-info-table . isolinux.cfg prompt 0 default 1 label 1 kernel /isolinux/linux.c32 append /KERNEL/26372 mem=256M retain_initrd rw INITRD /system.igz,/config.igz Screenshot from an open ISO file system.igz is there, I have tried gunzip the file and cpio extracted it, everything is perfect. [cid:F508840C-747D-4B9E-BD68-9A9D55BA8D58 at c-team.local] What has happened that breaks our ISO build process ? Thanks Morten -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-3.png Type: image/png Size: 11826 bytes Desc: PastedGraphic-3.png URL: <http://www.zytor.com/pipermail/syslinux/attachments/20120329/f30bf539/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-4.png Type: image/png Size: 24196 bytes Desc: PastedGraphic-4.png URL: <http://www.zytor.com/pipermail/syslinux/attachments/20120329/f30bf539/attachment-0001.png>
Hello Morten, Hrm.. I'll say that that sure *looks* like an ISOLINUX "boot:" prompt. Not being of any particular expertise on this type of problem, my gut says there's something a little silly going on somewhere here... maybe a BIOS bug or a 3.XX -> 4.XX migration problem... just not quite sure what it is, exactly. The ISOLINUX doc suggests trying a debug build of ISOLINUX, isolinux-debug.bin. You may want to give it a try, see if it can point out any potential problems. You can probably grab a binary from the website, but I didn't see any instructions for building from source. Might already be on your system. Alternatively, and if you're willing to troubleshoot a little more in depth, try booting your package with various builds from the 3.XX tree and the 4.XX tree, and if your boots are successful up to a point, the developers might be able to narrow it down for you. Some magical "git bisect" command I can never get a grip on ;) Also, it's worth mentioning that many boot problems can be unforeseen consequences of a poorly-written BIOS. It could be worth a shot testing this on a physical machine or a different hypervisor. Granted, I would venture a guess that you're using VMware, which is *usually* pretty-well behaved, but it's worth a shot if you'd like to collect more troubleshooting info! Best Regards, Andrew Bobulsky On Thu, Mar 29, 2012 at 7:23 AM, Morten B. Christensen <mbc at c-team.dk> wrote:> [cid:9FBAC256-5A30-4061-B74E-53A6B7B3D7BA at c-team.local] > > Hi all, > > Our own appliance is a Linux Kernel and 2 initrd files for filesystem - one system and one config partition. After the yum upgrade on our build machine ISO files are generated but useless. I you are able to see the picture I would like to know "who" writes the - > > Loading /system.igz? failed! > > Is it the kernel already loading the cpio+gzip'ed file or is it still isolinux. > > > > This script generates new ISO files > #!/bin/bash > BUILDPATH=/proxygen > GENERATEDPATH=/var/www/html/proxy/generated > > # if build command contains buildsystem a new system is build > if [[ $@ = *buildsystem* ]]; then > ?# Build initramfs > ?rm -f $BUILDPATH/boot/system.igz > ?chown -R 0:0 $BUILDPATH/system > ?cd $BUILDPATH/system > ?find . -print0 | cpio --null -ov --format=newc | gzip > $BUILDPATH/boot/system.igz > fi > > # Build file containing config > rm -f $BUILDPATH/boot/config.igz > cd $BUILDPATH/config > find . -print0 | cpio --null -ov --format=newc | gzip > $BUILDPATH/boot/config.igz > > # Build ISO > cd $BUILDPATH/boot > mkisofs -o $GENERATEDPATH/$1.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -r -l -boot-load-size 4 -boot-info-table . > > > isolinux.cfg > prompt 0 > default 1 > > label 1 > ? ?kernel /isolinux/linux.c32 > ? ?append /KERNEL/26372 mem=256M retain_initrd rw > ? ?INITRD /system.igz,/config.igz > > Screenshot from an open ISO file > system.igz is there, I have tried gunzip the file and cpio extracted it, everything is perfect. > [cid:F508840C-747D-4B9E-BD68-9A9D55BA8D58 at c-team.local] > > > What has happened that breaks our ISO build process ? > > Thanks > > Morten > > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > >