PVE won't start after a crash of VM an Host in the night

[hape]

Hello all,

after a crash of a VM in the night, the proxmox host won't start in the cluster.

What i see is, that the /etc/pve isn't mounted.

Does anybody have an idea what i can do?

 

[hape]

Hello again,

i found the following log-entries:

Jul 20 08:46:49 virtfarm-stpgp-3 pmxcfs[2147]: [database] crit: found entry with duplicate name (inode = 0000000015AA3F02, parent = 000000000000000B, name = '139.conf')
Jul 20 08:46:49 virtfarm-stpgp-3 pmxcfs[2147]: [database] crit: DB load failed
Jul 20 08:46:49 virtfarm-stpgp-3 pmxcfs[2147]: [database] crit: found entry with duplicate name (inode = 0000000015AA3F02, parent = 000000000000000B, name = '139.conf')
Jul 20 08:46:49 virtfarm-stpgp-3 pmxcfs[2147]: [database] crit: DB load failed
Jul 20 08:46:49 virtfarm-stpgp-3 pmxcfs[2147]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 20 08:46:49 virtfarm-stpgp-3 pmxcfs[2147]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
Jul 20 08:46:49 virtfarm-stpgp-3 pmxcfs[2147]: [main] notice: exit proxmox configuration filesystem (-1)
Jul 20 08:46:49 virtfarm-stpgp-3 pmxcfs[2147]: [main] notice: exit proxmox configuration filesystem (-1)

What can i do to start the pmxcfs again?

 

[hape]

Hello,

after renaming the "/var/lib/pve-cluster/config.db" to "/var/lib/pve-cluster/config.db.old" the pve starts normal and all VMs are running fine.

Do someone have any idea how this can happen?

Regards

Hans-Peter Straub