Hello proxmox friends
this is the same post as:
http://forum.proxmox.com/threads/11...-get-ugrade-(bootet-nicht-mehr-(Proxmox-1-6))
but now i try it in English........
,
We have a Proxmox 1.6 setup that does not work anymore.
The Proxmox installation runs on a dedicated server host with a software-raid hard disk array.
Our kernel version: 2.6.32-4
The error messages start when the boot process tries to access device md1 with mentioned
“unknown partition table”. Finally, the Volume group “pve” cannot be found, so that the boot process drops to an emergency shell. Anyway, we are sure, that our volume group has a different name. In lvdisplay, we see that the relevant volume group is called "virt2". Is there maybe any config file that we can modify?
Due to that our system sometimes crashed, we wanted yesterday update our Proxmox instance to a stable 1.6.x version to get a higher uptime. Unfortunately, this caused the system to end up with the above mentioned errors, dropping to an emergency shell (see the attached screenshot for more details).
We already tried to get in touch with the official commercial Proxmox support, but they refused our ticket due to the out-dated version of Proxmox and additionally because we hosted the virtual machines in a software-raid environment.
We would like to fix this error, but we would be already happy if we are able to access our virtual machines to export them and migrate them to VMWare, so every help towards this would be very appreciated.
Best regards
this is the same post as:
http://forum.proxmox.com/threads/11...-get-ugrade-(bootet-nicht-mehr-(Proxmox-1-6))
but now i try it in English........
,
We have a Proxmox 1.6 setup that does not work anymore.
The Proxmox installation runs on a dedicated server host with a software-raid hard disk array.
Our kernel version: 2.6.32-4
The error messages start when the boot process tries to access device md1 with mentioned
“unknown partition table”. Finally, the Volume group “pve” cannot be found, so that the boot process drops to an emergency shell. Anyway, we are sure, that our volume group has a different name. In lvdisplay, we see that the relevant volume group is called "virt2". Is there maybe any config file that we can modify?
Due to that our system sometimes crashed, we wanted yesterday update our Proxmox instance to a stable 1.6.x version to get a higher uptime. Unfortunately, this caused the system to end up with the above mentioned errors, dropping to an emergency shell (see the attached screenshot for more details).
We already tried to get in touch with the official commercial Proxmox support, but they refused our ticket due to the out-dated version of Proxmox and additionally because we hosted the virtual machines in a software-raid environment.
We would like to fix this error, but we would be already happy if we are able to access our virtual machines to export them and migrate them to VMWare, so every help towards this would be very appreciated.
Best regards
