![]() ![]() That should almost always work, because to the VM, it's not an ISO file - it's a real CD on real CD hardware.īooting from an ISO file on bare metal is much harder. So the dead-simple-est way to boot from some random ISO file is to load it into a virtual machine (VirtualBox, VMware, or Virtual PC) as a virtual CD and boot it there. What would the loaded operating system do? It will most likely look for a CDROM, which it won’t find, and fail. But most people do not realize is “what then?”. It can for example load the first few sectors and boot it. As explained on Marco's blog regarding Grub 2 (emphasis mine): The bios manages to find the key and boot from it.The biggest problem with booting an ISO file is that ISOs that are designed to be booted are almost always designed to be booted from a CD. Sudo dd bs=440 count=1 conv=notrunc if=/usr/lib/syslinux/mbr/gptmbr.bin of=/dev/sdgĪnd it works. # MAGIC copy the MBR GPT the bios can read Sudo grub-install -no-uefi-secure-boot -removable -target=x86_64-efi -boot-directory=/tmp/usb-live/boot/ -efi-directory=/tmp/usb-efi /dev/sdg Sudo parted /dev/sdg -script set 1 msftdata on Sudo parted /dev/sdg -script mkpart EFI fat16 1MiB 10MiB Then I inserted a key, fdisk told me it was at /dev/sdg # create a GPT table Here are the steps I followed : # install grub EFI Number Start End Size File system Name FlagsĮrror: The primary GPT table is corrupt, but the backup appears OK, so that will be used.ġ 32.8kB 141kB 109kB Gap0 hidden, msftdataĢ 141kB 3090kB 2949kB EFI boot partition boot, hidden, espģ 3090kB 13.7MB 10.6MB hfs+ Gap1 hidden, msftdataīasically I removed some steps from this answer Sector size (logical/physical): 512B/4096B Number Start End Size Type File system FlagsĮrror: The primary GPT table is corrupt, but the backup appears OK, so that will Sector size (logical/physical): 512B/512B Sector size (logical/physical): 512 bytes / 4096 bytes The primary GPT table is corrupt, but the backup appears OK, so that will be used.ĭisk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors I'm quite ashamed, but that's it !ĭisk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectorsĭevice Boot Start End Sectors Size Id Type It used to work, like three days ago, but I formated the disk since and I can't figure what I dit that was working. Is there a way to boot directly without manual intervention ? depending on grub-install options, grub bootloader keys have one or two partitions like :ĭisk /dev/sdg: 3.8 GiB, 4009754624 bytes, 7831552 sectors.dev/sdf1 64 275 212 106K Microsoft basic data Sector size (logical/physical): 512 bytes / 512 bytes USB rescue Key and USB live keys have 3 partitions as shown below :.Why can I boot from a "rescue key" / "live key" but not from a grub specific install ? How can I create a bootable grub-key ? and what I noticed : It never worked directly, as I knew it wouldn't when I bought it back in 2016. Also I tried every usb port, internal, external and SD card. ![]() It also worked for years but now it doesn't. I tried AHCI, legacy sata, b120i and every other option I could find in the bios and iLO I always managed to boot from first SATA drive (with or without other disks installed). ![]() Whatever the grub-install options, the bios will never boot from it. This option is quite annoying, since this machine doesn't have a screen and I have to press 3 keys to boot. First option to format and install, second option to choose debian and boot. I can boot from a "live" usb key OR "Grub rescue key". I know it's not recommended but for many monthes I managed to boot directly to the first sata drive without the help of a grub usb boot key What works :
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |