Upgrade problem from 3.4 to 4

[Gio]

Hi,

i tried to upgrade proxmox version 3.4 to version 4 using this guide: https://pve.proxmox.com/wiki/Upgrade_from_3.x_to_4.0

Everything seems correct untill the point where reboot is required. "Reboot the system in order to activate the new kernel."

When I rebooted the server it loads the proxmox blue startup screen as usual, after that it is stuck at the point showed in the image.


Any idea about how to resolve that?

 

[Alwin]

Does the boot continue if you use an older kernel (advanced section on the blue startup screen)?

 

[Gio]

I Alwin,

thanks for your answer, I can try to fix up this installation but I think this installation (that I inherited) it was already messed up...
I'm not so expert about Proxmox I was thinking about reinstall proxmox by scratch using latest version 5.
My doubt are about loosing all vm that are inside datastore. (however I have backups...)
My configuration now is Proxmox v 3.4 installed on two raid1 disks and Datastore inside 4 disks raid5.
Do you think that if I completely reinstall Proxmox (using latest version) I will lose all VM's inside separate Datastores?

 

[Alwin]

You can reinstall Proxmox and select the proper disk to install onto. If you do this, you should backup your config files under /etc/pve/, especially the lxc/qemu-server config files, so you don't have to recreate all VM configs.

In any case, to have a backup is never a bad idea!

 

[Gio]

HI, Alwin I choose to reinstall everything.
I've baked up all Proxmox intallation files but I cannot find /etc/pve/ and lxc/qemu-server folders.

 

[Alwin]

/etc/pve/ is a fuse filesystem that is mounted when the pve-cluster.service starts.

 

[Gio]

I used a Ubuntu live to recover files so that is why the service did not start.
How I can recover that files if proxmox is not running?

 

[Alwin]

Not really, you could try to get the process that the services starts to run, but this needs more effort then recovering from a backup. The VM configs are stored inside the backups, so you can extract them from there. Only a restore of the VMs is straight forward.