{"id":423,"date":"2019-05-25T05:04:21","date_gmt":"2019-05-25T10:04:21","guid":{"rendered":"https:\/\/tanzeelkazi.com\/blog\/?p=423"},"modified":"2019-05-25T17:19:03","modified_gmt":"2019-05-25T22:19:03","slug":"proxmox-ve-installer-with-multibootusb","status":"publish","type":"post","link":"https:\/\/tanzeelkazi.com\/blog\/2019\/05\/25\/proxmox-ve-installer-with-multibootusb\/","title":{"rendered":"Proxmox VE installer with MultiBootUSB"},"content":{"rendered":"\n

tl;dr<\/strong> I have uploaded a mod<\/a> for Proxmox+multibootusb to make Proxmox handle ISO install images.<\/em><\/p>\n\n\n\n

This article is a brief look at my troubles with getting the Proxmox installer to work with MultiBootUSB, and, a solution that I cooked up to resolve it.<\/em><\/p>\n\n\n\n

The conventional process of using the Proxmox VE installer ISO is to either burn it to an optical disk (guaranteed to work), or, use a tool like dd<\/code> in linux to write the ISO image directly to a USB disk, and, hope it works.<\/p>\n\n\n\n

I like using USB disks because they are compact, and, have faster reads, which means a faster installation. But, I don’t like the idea of using an entire drive dedicated to just the installer.<\/p>\n\n\n\n

So, in comes MultiBootUSB<\/a>. I use it because it is designed to help with this specific problem, except… nothing is easy.<\/p>\n\n\n\n\n\n\n\n

Proxmox installer on USB drives<\/h2>\n\n\n\n

If you google “using the Proxmox installer on USB”, there are a lot of results, many of which are questions from people asking why it doesn’t work right.<\/p>\n\n\n\n

Consolidate the search results, and, the general rule of thumb that is revealed is, that, you need to use dd<\/code> to write the image to the entire USB drive. An image that is only ~688MiB. What a waste of drive-space, and, a waste of an entire drive! Another caveat to this is that the drive has to be detected as removable<\/code> during the initialization process, or you are going to have a bad time.<\/p>\n\n\n\n

Trying to add the ISO using MultiBootUSB’s conventional steps, got me nowhere. The Proxmox installer would abort on boot, complaining about a modified kernel.<\/p>\n\n\n\n

I like MultiBootUSB, and, I wanted to try and stick with it; so deep into the rabbit hole I went.<\/p>\n\n\n\n

The \/multibootusb\/iso<\/code> fallback<\/h2>\n\n\n\n

MultiBootUSB has a nifty fallback to try loading weird ISO images. You copy them to the \/multibootusb\/iso\/<\/code> directory of your USB drive. There also needs to be the correct grub configuration files under \/multibootusb\/grub\/menus\/<\/code> for your platform. Incidentally, MultiBootUSB does NOT have the menus pre-configured for the Proxmox ISOs.<\/p>\n\n\n\n

I would soon realize, that creating the new grub menu configs for Proxmox would be the easy part. Even with the menus configured to load the ISO image, Proxmox was hell bent on testing for cdrom<\/code>. That’s the message you see verbatim from the console. I still had got some more head-scratching to do.<\/p>\n\n\n\n

The initial RAM disk, for Proxmox<\/h2>\n\n\n\n

The initial RAM disk is responsible for detecting the correct installation medium and kicking off the actual install process.<\/p>\n\n\n\n

The initrd.img<\/code> used by Proxmox specifically looks for block devices, and, also filters them by removable<\/code> devices. This presented a few problems for me, which I could only resolve by modifying the initrd<\/code> image.<\/p>\n\n\n\n

When the initial RAM disk loads, it is like a blank slate. No devices are auto-mounted (except the RAM disk itself), and, it only has the kernel boot parameters to go by to load correctly.<\/p>\n\n\n\n

First, I had to check every block device that could potentially contain the ISO file. I did NOT want to filter by removable<\/code> for the device.<\/p>\n\n\n\n

Second, once I had the correct drive, I also needed a path for the ISO on the filesystem.<\/p>\n\n\n\n

I solved both problems by adding a new boot parameter isopath<\/code>, that gets passed to the kernel from the grub<\/code> menu.<\/p>\n\n\n\n

I coded it so that, when the initial RAM disk encounters the isopath<\/code> parameter, it branches off into a separate code-block. The code-block searches through all the block devices detected on the system (removable or otherwise).<\/p>\n\n\n\n

Once a match for isopath<\/code> is found on a device, it is mounted to \/mnt<\/code> first. It is then tested to see if it is a valid PVE installer. If everything checks out, the installation proceeds as it normally would. If not, the ISO is unmounted, and the script proceeds to the next device to continue looking for the correct file.<\/p>\n\n\n\n

Eureka! It works!<\/p>\n\n\n\n