Boot from Ubuntu 16.04 live iso failed

[amir3161]

@Tom-Elliott Thanks Tom. Did that but nothing changed!

[Tom Elliott]

How about example from iPXE themselves?

http://ipxe.org/appnote/ubuntu_live

[amir3161]

@george1421 Finally got it working for the Ubuntu! using the instruction you provided!

Regarding Hiren I still have problem. I have changed permissions as @Tom-Elliott suggested but for the /var/www/html/iso/hiren/ (hirens.iso is in this folder)
Now it gets stuck with this message:

Loading  boot sector... booting ...

Btw for the reference and in case someone needs it later I will post what I did here in another post.

[Sebastian Roth]

@amir3161 said in Boot from Ubuntu 16.04 live iso failed:

http://${fog-ip}/iso/hirens.iso

Are you able to access this URL from your browser and download the ISO file (just for testing)?

[amir3161]

@Sebastian-Roth good point. I just tested it. I can access the iso file from the FOG server machine : 127.0.0.1/iso/hiren/hirens.iso
but from other machines if I do : 192.168.18.28/iso/hiren/hirens.iso I get to the FOG
server management page. Seems like no matter what I type after the ip address it forwards me to the FOG login page.
I have checked the permissions for the iso folder and changed it to “-R 777” (I’m not sure if this is a good practice!) but still the same.

[Sebastian Roth]

@amir3161 Yeah this is a bit tricky. Newer FOG versions are pretty much taking over apache as it does rewrite/forward requests to make the FOG API work.

That said there is still room for what you want to do if you put your files straight into /var/www subdirectories (but not /var/www/html sub dirs!). For example you can have /var/www/isos/hirens.iso and should be able to download via http://${fog-ip}/isos/hirens.iso from a remote PC.

Be aware that getting a directory listing (URL http://${fog-ip}/isos/) won’t work as the rewrite engine is kicking in again. This is because DirectoryIndex is set and apache forwards your directory request to /isos/index.html internally. As this file does not exist the rewrite rules forward to the FOG API and from there to the management interface again.

[amir3161]

@Sebastian-Roth One again spot on Sebastian
I can now boot from the iso but this is not the end of it yet! When it goes through the boot process I get this error :

This happens if I choose the Linux rescue environment . If I choose mini windows xp, everything works fine!
Any suggestion for this one ?
I also have a general question: How do I know how to treat a iso file to be able to boot from it on FOG? There is a wiki page for some (which I think is not updated in a while).
Is there any instructions to follow or it changes every now and then?

[Wayne Workman]

@amir3161 I’m going to say re-download the ISO and do the checksum afterwards too. “Can’t read superblock” is a typical message from mounting a corrupt file system.

[amir3161]

@Wayne-Workman I have checked the md5 checksum of the iso file and it matches the one on the website. Do you still think I need to re download?

[Sebastian Roth]

@amir3161 Unfortunately it’s not possible to provide a general tutorial on how to include boot ISOs as every ISO is a bit different. Some may boot as ISO using the memdisk helper and others need to be extracted and need fiddling with the parameter till it works. When you extract the Hirens ISO check out the file HBCD/menu-custom.lst. It’s a huge list of how different systems can be booted (using GRUB instead of iPXE though). See, they are all different.

I can confirm the error you posted as picture and I partly figured out what’s going wrong. But I don’t know how to fix it yet. I am sure we’ll figure it out at some point but I need to do other things now so I just report my findings so far. The picture below explains pretty much everything:

After some fiddling with this I thought I might just compare the md5 hashes of the squashfs images (one within the booted ISO and the other one I extracted from the ISO on my host system). They should match as they are the same files. Turns out md5sum can’t even read to the end of the file and fails in the booted live system. dmesg reveals that the memdisk/mtdblock device (ISO in RAM) seems to be too small.

Note to myself: Try PXE booting with pxelinux or grub to see if those show the same issue…

[Sebastian Roth]

@amir3161 Are you still interested in this? I’ve lost track of this issue. Or maybe you figured it out yourself?