Wrong proxmox cd-id

[DynFi User]

We are trying to install Proxmox-VE on an AMD based server.
We have engraved the USB key from a Macintosh, and after engraving the key and booting, we have ended up with the following problem :

found ISO9660 FS but no or wrong proxmox cd-id, skipping

We have followed Proxmox official guide to engrave the key :

Download the PVE ISO :

# hdiutil convert -format UDRW -o proxmox-ve_*.dmg proxmox-ve_*.iso
# sudo dd if=proxmox-ve_*.dmg of=/dev/rdiskX bs=1m


And upon boot, I ended up with this problem :

found ISO9660 FS but no or wrong proxmox cd-id, skipping


Do you know if there is any way to have a properly booting key using Mac OS ?

 

[dcsapak]

why do you first convert it to a dmg file? just do a simple dd of the iso ?

 

[DynFi User]

Well, I followed your guide !

If It is not "ok", you should consider editing this section.
It is quite confusing.

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#installation_prepare_media

2.2.3. Instructions for macOS​

Open the terminal (query Terminal in Spotlight).
Convert the .iso file to .img using the convert option of hdiutil for example.
# hdiutil convert -format UDRW -o proxmox-ve_*.dmg proxmox-ve_*.iso

macOS tends to automatically add .dmg to the output file name.

To get the current list of devices run the command:
# diskutil list
Now insert the USB flash drive and run this command again to determine which device node has been assigned to it. (e.g., /dev/diskX).
# diskutil list
# diskutil unmountDisk /dev/diskX

replace X with the disk number from the last command.

# sudo dd if=proxmox-ve_*.dmg of=/dev/rdiskX bs=1m

rdiskX, instead of diskX, in the last command is intended. It will increase the write speed.

 

[dcsapak]

ok, mhmm... maybe that are leftover old instructions... can you try without converting? or using another tool to do it (e.g. etcher)

 

[DynFi User]

It worked like a charm !

Thanks for the tip and,… you know what you have to do

 

[dcsapak]

well i just tried the method described in the docs here, and it worked without problems...
could you try again and in the shell give the output of the command 'blkid' ?

 

[DynFi User]

I don't understand why you want to convert the ISO to another media type.
Just raw bit to bit engraving of your image is enough.

We have used this with two different Mac (OS 11.3.1 and 10.14).
We had problem at the real end of the install, not in the first stages of the boot / install.

There is no "blkid" command on OS X.

 

[dcsapak]

We had problem at the real end of the install, not in the first stages of the boot / install.

this is not what you wrote in your first post

There is no "blkid" command on OS X.

i meant in the installer environment when it does not work

 

[fiveangle]

Same problem on Dell R420 w/192GB RAM… so flakey

 

[sorind]

I had the same issue @DynFi User, but I actually created the bootable USB using dd without converting the image sudo dd if=/home/sorind/Downloads/proxmox-ve_7.0-2.iso of=/dev/sdi bs=1M status=progress.
The only difference is that I did this from a Kubuntu 20.04
After I read this thread I installed and used etcher to create the bootable USB which worked.
Let me know guys if you need more info, so you get to the bottom of this issue.

 

[lennahht]

Having the exact same issue right now.
Trying to install on an HP Prodesk 400 G2 mini with I5-6500T.
I followed the instructions for creating a bootable USB-Stick very closely, trying dd and etcher on an Ubuntu 22.04 machine.
Entering the blkid command in the installer gives the following result:

/dev/sdc3: LABEL="PVE" TYPE="hfsplus"
/dev/sdc2: UUID="XXXX-XXXX" TYPE="vfat"
/dev/sdc: LABEL="PVE" TYPE="iso9660"

Fast Boot and Secure Boot are disabled.
I tried UEFI and Legacy boot mode.
I tried USB 2 and 3.

I'll try creating the boot drive with windows and will update if that helps.

Edit: tried it with Rufus on WIndows and it immediately worked...
So if anyone is in a similar situation, give Windows a try.