Install Procmox VE 3.3 on other device than /dev/sda

[jasminj]

Hi, I would like to test Proxmox VE to get rid of ESXi.
So I decided to add a new disk to my ESXi host and use it for a Proxmox test installation for performance tests.

The new disks are on an LSI RAID controller. I created 3 volumes. One for the Proxmox system another for the virtual machine storage and one to map directly into the virtual machine for the WEB server data.

The Proxmox installer allow you to choose the installation drive. In my case /dev/sdd. The install stopped when writing the boot loader to the disk, because it does it to "(hd0)" (hardcoded in the installer script, I guess). To solve this, I started the installer again with "debug ext4" (without the "). Doing so, I was able to enter a console to install grub manually by pressing abort, when the error occurred.

When the installer failed, it already did unmount the required paths for chroot.
So I added them again:

 # mount -n /dev/sdd2 -o noatime,barrier=0 /target/boot
 # mount -n /dev/pve/data -o noatime,barrier=0 /target/var/lib/vz
 # mount -n -t tmpfs tmps /target/tmp
 # mount -n -t proc proc /target/proc
 # mount -n -t sysfs sysfs /target/sys
 # mount -n --bind /dev /target/dev

Now we can install grub:

 # chroot /target /usr/sbin/grub-install --no-floppy /dev/sdd
 # chroot /target /usr/sbin/update-grub

Then I pressed "<control>-d" to finish the installer.

After rebooting, Proxmox was started, but the web interface was not running.
There is no /var/log/syslog and no /var/log/daemon.log to look further into this problem.
Any hints why they are not there?

Searching on the net brought me into the direction of "/etc/pve" (see: http://forum.proxmox.com/threads/14141-web-interface-not-working-in-Proxmox-3).
The directory was not mounted. I did this by "pmxcfs" (see: http://forum.proxmox.com/threads/7528-cannot-access-etc-pve-Transport-endpoint-not-connected).
The directory /etc/pve/local was missing (symbolic link to /etc/pve/nodes/proxmox).

After a reboot the same problem happened again.

This might be caused by not installing to /dev/sda, but I can't change the RAID controller configuration, because I still need the ESXi installation.
Maybe someone can point me in the right direction.

Where can I find the installer script in the git repository. Maybe I can look there for installation issues, concerning a different disk.

BR
Jasmin

 

[dietmar]

Maybe someone can point me in the right direction.

I do not think that is related to not installing to /dev/sda

Where can I find the installer script in the git repository. Maybe I can look there for installation issues, concerning a different disk.

https://git.proxmox.com/?p=pve-installer.git;a=summary

 

[dietmar]

Note: I deleted your other post (delay was due to moderation queue).

 

[jasminj]

I do not think that is related to not installing to /dev/sda

I installed it to /dev/sda and it worked without any problem. So indeed it was related to the install drive!
THX Proxmox team for fixing it for the next release (see git)

For all who need to install it till the next release is out:

Because grub install did fail, the remaining commands were not executed:

# chroot /target /usr/sbin/grub-install --no-floppy '(hd0)'
# chroot /target /usr/sbin/update-grub
# umount /target/dev
# rm -rf /target/dead.letter
# mv /target//sbin/start-stop-daemon.distrib /target//sbin/start-stop-daemon;
# chroot /target dpkg-divert --remove /sbin/start-stop-daemon
# chroot /target /usr/sbin/chpasswd
# chroot /target /usr/bin/create_pmxcfs_db /tmp/pve /var/lib/pve-cluster/config.db
# rm -rf /target/tmp/pve
# umount /target/boot
# umount /target/var/lib/vz
# umount /target/tmp
# umount /target/proc
# umount /target/sys
# umount -d /target

The problem is in this command:

# chroot /target /usr/sbin/grub-install --no-floppy '(hd0)'

The '(hd0)' is hard coded and needs to be the real install device. In my case "/dev/sdd".

BR
Jasmin