can't install 4.4 from USB

Ok, i solved this way: First i installed Linux Mint 18 on this PC. Then i used this command to burn the ISO for the pendrive:
dd if=proxmox-ve_*.iso of=/dev/XYZ bs=1M; sync. And worked. So let's begin the learning:)
Thank you for the help anyway :)
 
Same problem, I use rufus to burn the ISO to the USB, boot is ok but error at the "searching for cdrom" step, use USB to boot but why search cdrom ?

Hardware: Dell R420/R620
 
It is strange anyway. I bought a new PC, i installed Linux Mint 18.1. I tried the recommended way to burn the ISO for USB.
Then i did this on the target old 5 years PC on Linux Mint 18 and everything went well.
 
Last edited:
To prepare a flash drive from Windows I used ImageUSB.
Work fine for me.
Download link: h-t-t-p-s://yadi.sk/d/2pHrbT1p3GB9NB
(Please remove "-" from URL, I`m a new user :))
 
Save yourself lots of trouble. Burn a CD or use a Zalman VE350 or ISOStick. I never could get Proxmox to work reliably on plain USB thumb drives.
 
Your best option here is to skip the attempt to install via usb. I have servers which do not have dvd/cd drives and ran into the same issue. I tried multiple usb creation efforts of which zero were effective. The only time I've had a usb installer actually work is when i used it on a system that had a physical dvd/cd drive in the case!

If you run into this issue, your best option is to install Debian Jessie and do a manual install of Proxmox through that method. http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie

This works 100% of time.
 
...and it's not suitable either to use any 3rd part crappy usb-boot-copy-util, that might include malware (I don't trust the alternatives and don't have time to investigate)......so yes, Rufus seem to be the right choice :p
And yes it does seem to work using the above option.
Why are you making an ISO image, that's not supported by Rufus?
VMware can do it, Debian can do it, MS can do it......etc.etc.etc......
 
MrValvin said:
...and it's not suitable either to use any 3rd part crappy usb-boot-copy-util, that might include malware (I don't trust the alternatives and don't have time to investigate)......so yes, Rufus seem to be the right choice :p
And yes it does seem to work using the above option.
Why are you making an ISO image, that's not supported by Rufus?
VMware can do it, Debian can do it, MS can do it......etc.etc.etc......
Click to expand...

if you copy our iso directly to a device, it works as intended (this is what "dd mode" probably does). it probably does not work in "iso mode" (whatever that does) because the first phase of the installer does not know how to find the iso contents then. this is not an intentional limitation, but a side-effect of keeping our installer simple. while I would personally also like to a see a PVE iso with loopback support, it is not very high up on our list of things to do - especially since the work around (use a dd-like tool to copy the iso to your usb stick) is very simple.
 
MrValvin said:
...or is it a way of making extra money (are you supported by the alternatives)?
Click to expand...

of course not, and frankly, such a suggestion is pretty ridiculous if you take a look at what we do and how we do it...

it's not our fault windows does not have a built-in tool for copying contents of a file to a (block) device, that the amount of FLOSS software for the windows ecosystem is small compared to that for the Linux one (so there is a lack of good software to recommend) or that some people prefer windows over linux.
 
It is really interesting. I installed 4.4 couple month ago, but now i can not install on the same hardware.
I used this command again: dd if=proxmox-ve_*.iso of=/dev/XYZ bs=1M; sync
The problem is the same........the cursor just blinking or i get /boot/grub/x86_64-efi/normal.mod not found message.
 
Hello, I am getting crazy with this as I am quite exited to move to Proxmox but after 3h I can't move forward from the GRUB prompt blinking (frozen) or the grue rescue one (if I chose UEFI instead of normal USB boot).

I tried 4 USB sticks with the dd command from the wiki and with the sync option. None is working. I disabled the RST Intel raid from my motherboard (by doing the opposite of this rog.asus.com/articles/guides/how-to-install-two-m2-ssds-in-raid-0-on-maximus-ix-motherboards/ so in AHCI). My motherboard is an Asus PRIME-H270-PRO

Example 1:
Code: 
sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/nvme0n1: PTUUID="95c06c0c-6275-4c2b-9489-bef4fd0f2f17" PTTYPE="gpt"
/dev/nvme0n1p1: UUID="ad49efe4-4758-4cad-8e1b-e4e5314a9d06" TYPE="ext4" PARTUUID="05ad296d-51b3-4499-b629-97f256e4e766"
/dev/nvme0n1p2: UUID="be9710be-3440-42ab-840c-a5acccf5c452" TYPE="swap" PARTUUID="f6289437-9250-4ef5-8fd2-d33118505cc0"
/dev/nvme0n1p3: PARTUUID="d23c3e46-1b60-4235-ba28-0c7a6f927df1"
/dev/sda1: LABEL="Neutron" UUID="9921862c-332a-4fff-88bb-f7890028a1eb" TYPE="ext4" PARTUUID="675afef0-caa0-4597-891b-2bfea2ec0b51"
/dev/sdb1: UUID="3d4e0448-60ef-43ce-bca1-8b3eee721caf" TYPE="ext4" PARTLABEL="Camera" PARTUUID="adf0711f-b37c-49aa-97fe-8ea679aabcb9"
/dev/sdc1: LABEL="Samsung 840 EVO" UUID="33cc0e72-901d-4ca6-a3d8-25c2cad5a42e" TYPE="ext4" PARTUUID="1ea721f2-ace9-4759-92d9-7671f5fa9d97"
/dev/sdd1: LABEL="HGST 4To" UUID="64bb8698-ddb4-42be-b2dd-2bac3555159c" TYPE="ext4" PARTLABEL="HDD" PARTUUID="dfc96e66-93d2-4f10-96d2-dbb309a3bf02"
/dev/sde1: SEC_TYPE="msdos" LABEL="ATLAS" UUID="AEF4-37B0" TYPE="vfat" PARTUUID="00236c4c-01"

sudo dd if=/mnt/HDD/proxmox-ve_5.1-722cc488-1.iso of=/dev/sde1 bs=1M ; sync
589+1 records in
589+1 records out
618477568 bytes (618 MB, 590 MiB) copied, 3,69239 s, 168 MB/s

Example 2:
Code: 
/dev/sde1: SEC_TYPE="msdos" UUID="2A53-111B" TYPE="vfat" PARTUUID="4d423358-01"
sudo dd if=/mnt/HDD/proxmox-ve_5.1-722cc488-1.iso of=/dev/sde1 bs=4M ; sync
147+1 records in
147+1 records out
618477568 bytes (618 MB, 590 MiB) copied, 0,42106 s, 1,5 GB/s

Example 3:
Code: 
/dev/sde1: LABEL="FLASH" UUID="B248-55C0" TYPE="vfat" PARTUUID="09c7ac67-01"
xabix@SERVER:~$ sudo dd if=/mnt/HDD/proxmox-ve_5.1-722cc488-1.iso of=/dev/sde1 bs=1M ; sync
589+1 records in
589+1 records out
618477568 bytes (618 MB, 590 MiB) copied, 3,69136 s, 168 MB/s

Example 4:
Code: 
/dev/sde1: UUID="2017-10-23-10-48-57-00" LABEL="PVE" TYPE="iso9660" PTUUID="6a19dacc-41ed-410a-af86-855758f6840b" PTTYPE="gpt" PARTUUID="0008bfbf-01"
sudo dd if=/mnt/HDD/proxmox-ve_5.1-722cc488-1.iso of=/dev/sde1 bs=1M ; sync
589+1 records in
589+1 records out
618477568 bytes (618 MB, 590 MiB) copied, 2,88437 s, 214 MB/s

Any idea as I am really frustrated and don't understand why it so complex to install Proxmox vs an Ubuntu, Debian etc... usually bootable usb disks are pretty easy to do and here I did follow the wiki from Proxmox.

MERCI
 
you should use the full USB device as output, not the first partition..
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back