Skip to main content
12 events
when toggle format what by license comment
Mar 18, 2015 at 12:16 comment added goldilocks ...those S.U. answers are correct: the ESP is just for bootloaders (which I guess you could call "bootware" if you want, this seems to be what some people do WRT a windows install); the UEFI system will look for this based on path. So you create the partition, flag it correctly, then install an OS, and if the OS is UEFI aware/capable, it will install an appropriate piece of software in the correct path, etc. Since you are using some kind of custom bootloader, that might be something you have to investigate further.
Mar 18, 2015 at 12:11 comment added goldilocks To bicker: "Bootware: the embedded firmware...not to be confused with firmware" -- is an interesting phrase, lol. The "F" in UEFI is for "firmware", BTW. Hopefully my point was clear, and the point that I really don't know, I was just going by the SuperUser answers. By your definition of "bootware", I doubt it is anything you have to think about in this context. The hardware itself certainly doesn't need to install anything on the disk, so that's out. And by this description...
Mar 17, 2015 at 18:15 comment added JDługosz Bootware: the embedded firmware used at power-on, which is not a BIOS but only used for booting. Not to be confused with firmware which can refer to the read-only disk image of an OS+apps that defines the appliance (e.g. FreeNAS). Especially for those developing or installing the latter :)
Mar 17, 2015 at 18:11 comment added JDługosz Also, p and t worked, they just were not disclosed via m.
Mar 17, 2015 at 18:09 comment added JDługosz The VMWare 11 machine with legacy BIOS showed the full list of options. The real Supermicro X10-SAT with the same UBCD/partionMagic boot image was missing those two options at the least, and showed a warning.
Mar 17, 2015 at 14:32 comment added goldilocks WRT "EFI bootware" those answers on the Super User Q state pretty clearly the partition isn't actually used for firmware, just OS bootloaders -- if that's what you mean. I.e., if VMWare implements UEFI it should work without having seen the disk before (otherwise you have a chicken - egg problem). Another stupid thing that should be well documented somewhere obvious but perhaps is not. >_<
Mar 17, 2015 at 14:27 comment added goldilocks Hmmph. Well GPT is a pretty recent addition to fdisk, I don't know when the "experimental" warning was removed (because I remember seeing it, but then a while back noticed it wasn't there -- that could happen in one minor version 2.23 -> 2.24). The p and t options should definitely be there or something is very very wrong. That's part of the base functionality, unless maybe it thinks it cannot figure the device out at all and is refusing to mess with it. I haven't used it via VM's much, so...different issue?
Mar 17, 2015 at 10:52 comment added JDługosz It's especially unclear because fdisk's m help does not list everything, and is missing p and t in particular. It shows when I tested it in a VM. On the real machine, it adds a warning that GPT is experimental, and doesn't show the same options. I think the difference might be the EFI bootware? (I had to boot with BIOS in the VM since VMWare's UEFI has no fallback to legacy bootable media.
Mar 15, 2015 at 12:26 history edited goldilocks CC BY-SA 3.0
edited body
Mar 15, 2015 at 9:58 comment added JDługosz Thanks for the clear answer. The fdisk on the parted magic image is 2.23.2 so the menu was a little different, but I got it created and then set to the right type. I looked again in GParted and formatted as fat32 there. GParted doesn't show anything concerning the type anywhere, and (looking again with fdisk) did not mess it up either.
Mar 15, 2015 at 9:55 vote accept JDługosz
Mar 14, 2015 at 13:48 history answered goldilocks CC BY-SA 3.0