Proxmox VE 5.1 installation, booting "wrong" Debian

frank03

New Member
Dec 22, 2017
2
0
1
55
Moin,

I have a rented server for a lab environment containing one 2TB SATA disk and one 250GB SSD.
Server was delivered with preinstalled Debian 9 OS (didn't care, wanted to install it by myself anyway)

So I installed Proxmox VE 5.1 ISO Installer (3rd ISO release), as of today, on the single SATA disk ("RAID 0", ZFS), leaving the SSD alone at this time. After successfull installation I could ping and SSH the server but was unable to reach the web console, also SSH login as root was impossible (wtf, english / german keyboard issue?). It took me quite a while to figure out that the server booted into the Debian installation that was originally delivered with the server, on the SSD.

Below I copied some disk info, can someone please help me to figure out how to repair this? I work mostly with Windows, Citrix etc., this is my free time and I am not very familiar with how to grub...

Code:
root@sa057:~# fdisk -l
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x62628297

Device     Boot    Start       End   Sectors   Size Id Type
/dev/sda1           2048      4095      2048     1M 83 Linux
/dev/sda2           4096  16005119  16001024   7.6G 82 Linux swap / Solaris
/dev/sda3  *    16005120  18006015   2000896   977M 83 Linux
/dev/sda4       18006016 488396799 470390784 224.3G 83 Linux


Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 6524ABE9-FFCC-47F2-A3B5-88A63FAA9620

Device          Start        End    Sectors  Size Type
/dev/sdb1          34       2047       2014 1007K BIOS boot
/dev/sdb2        2048 3907012749 3907010702  1.8T Solaris /usr & Apple ZFS
/dev/sdb9  3907012750 3907029134      16385    8M Solaris reserved 1

Partition 1 does not start on physical sector boundary.
Partition 9 does not start on physical sector boundary.
root@sa057:~#
 
Hi,
you see that the ssd is sda and your pve-disk is sdb - mean your bios use the ssd as first drive.

Go into the bios and select the 2TB-Disks as boot-device, and then your pve-installation should boot.

Udo
 
Sorry, my bad. I worked with VMs for so long that I totally forgot some basics about bare metal install... Thank you
 
Last edited: