[SOLVED] HELP - VM start fails since running package update

[cmonty14]

Hi,

I have just updated packages of PVE 3.3.
The update was interrupted and the server was not responsive.

Then I did hard reset of the server, and finished the package update via CLI with apt-get update.
However, I cannot start VMs.

In Syslog I can see latest entry for VM that is supposed to start up with host.
But the VM is effectively not starting, and I cannot find any indicator in Syslog for the failure.

What else should I check for additional information of the root cause?
What other logs are relevant?

My next step is to start the VM via CLI using qm start <vmid>.
Is there an option that could be used in order to get more details for the start up displaying errors etc.?

THX

Update:
LV /var/lib/vz (=data) was running out of disk space.
After releasing some disk space all VMs are running again.

 

[dietmar]

My next step is to start the VM via CLI using qm start <vmid>.

And there is no error message?

 

[cmonty14]

Hi!

I'm off and cannot execute the VM start command right now.

However, as the "automatic" start fails, I thought there should be some logging on that failure.
Where can I find those logs providing potential information for the start failure?

THX