Fuel ISO image has a no MBR

[Marc Koderer]

The MBR of the ISO image of the fuel installer is not present. Some servers cannot be booted.

Check disk partion with gdisk and fdisk:

gdisk MirantisOpenStack-5.1.iso
GPT fdisk (gdisk) version 0.8.1

Partition table scan:
  MBR: not present
  BSD: not present
  APM: not present
  GPT: not present

fdisk MirantisOpenStack-5.1.iso
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x6c318196.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

[Matthew Mosesohn (raytrac3r)]

Why are you trying to treat the ISO like a real disk? There's a .img file that can be booted, but ISO is in CD format.

[Alexander Gordeev (a-gordeev)]

It shouldn't have MBR at all.

It uses another mechanism called El Torito
http://en.wikipedia.org/wiki/El_Torito_%28CD-ROM_standard%29

to check if the ISO is bootable, just use `isoinfo` tool.
Eg.:
isoinfo -d -i <filename.iso>

will show something like this:

Eltorito validation header:
    Hid 1
    Arch 0 (x86)
    ID ''
    Key 55 AA
    Eltorito defaultboot header:
        Bootid 88 (bootable)
        Boot media 0 (No Emulation Boot)
        Load segment 0
        Sys type 0
        Nsect 4
        Bootoff 1FA 506

[Marc Koderer (m-koderer)]

@Aleksandr: ok but why all other enterprise distro's have a MBR? All other ISO's are producing bootable USB sticks but OpenStack-Mirantis ISO don't:

>gdisk rhel-server-7.0-x86_64-boot.iso
GPT fdisk (gdisk) version 0.8.1

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: present

>gdisk ubuntu-14.04.1-server-amd64.iso
GPT fdisk (gdisk) version 0.8.1

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present

>gdisk CentOS-7.0-1406-x86_64-livecd.iso
GPT fdisk (gdisk) version 0.8.1

Partition table scan:
  MBR: MBR only
  BSD: not present
  APM: not present
  GPT: not present

[Nastya Urlapova (aurlapova)]

Marc, did you try img for you issue?

[Vladimir Kozhukalov (kozhukalov)]

Marc,

The reason for having two separate files: one is ISO image and another is the image for flash stick is that when we tried to put mbr into ISO image we had some issues related to inability to make installation fully automatic (it is one of our basic features). I don't remember exactly but maybe it was somehow connected to placing image file system UUID into kickstart so as to avoid anaconda dialog about source device. We had no time to go deeper and decided to make two separate files. Many things changed since that time and maybe now it is not a problem any more. If you have an obvious solution you are welcome to contribute. But if you just need to have a possibility to install a node from a flash stick you can just download .img file and put it into a stick and then use this stick as a bootable device.

[Ryan Moe (rmoe)]

Besides duplicating resources, maintaining separate img and iso files lead to a regression (see https://bugs.launchpad.net/fuel/+bug/1410333).

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/154960

[Stanislaw Bogatkin (sbogatkin)]

We don't port medium bugs to 6.0 branch, so closed for it.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/154960
Committed: https://git.openstack.org/cgit/stackforge/fuel-main/commit/?id=d6093811e73fb177195ef7374b45fd327367ae52
Submitter: Jenkins
Branch: master

commit d6093811e73fb177195ef7374b45fd327367ae52
Author: Stanislaw Bogatkin <email address hidden>
Date: Wed Feb 11 20:09:55 2015 +0300

    Add to ISO ability to boot from USB

    DocImpact
    Change-Id: I7b2dc2757c28881e02ed3bdb6edb7568af7bcf4d
    Closes-Bug: #1387033