Quick troubleshooting view
A virtual machine refuses to start after an error or inconsistency from the company.
- Incoherent record chain
- Missing parent file
- Saturated Data Store.
- Do not change files at random
- Control l,datastore space
- Examining the chain of philanthropies
- Free from space if necessary
- Consolidate with tools provided by the hypervisor
- Rename from backup if string is unrecoverable
Contextual technician plan
Keep the situation safe before handling.
“Do not change files at random” should produce an observation that clearly confirms or rules out “Incoherent record chain”.
If the observation is normal, lower “Incoherent record chain” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Incoherent record chain” first. Related action: Free from space if necessary.
A lack of space can block and consolidate.
“Control the datastore space” should produce an observation that clearly confirms or rules out “Missing parent file”.
If the observation is normal, lower “Missing parent file” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Missing parent file” first. Related action: Consolidate with tools provided by the hypervisor.
Use native tools from the hypervisor.
“Examining the chain of philanthropies” should produce an observation that clearly confirms or rules out “Saturated Data Store.”.
If the observation is normal, lower “Saturated Data Store.” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “Saturated Data Store.” first. Related action: Rename from backup if string is unrecoverable.
Remove the file or disk mentioned.
“Check VM events” should produce an observation that clearly confirms or rules out “S Narratively deleted”.
If the observation is normal, lower “S Narratively deleted” in the ranking and continue with the next distinct check.
If the observation is abnormal, keep the evidence and investigate “S Narratively deleted” first.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Scramble before any manual changes to descriptors or VMDK strings.
A virtual machine refuses to start after an error or inconsistency from the company.
Causes probables
- Incoherent record chain
- Missing parent file
- Saturated Data Store.
- S Narratively deleted
- Invalid VMDK descriptor
Diagnostic étape par étape
- 1
Do not change files at random
Keep the situation safe before handling.
- 2
Control the datastore space
A lack of space can block and consolidate.
- 3
Examining the chain of philanthropies
Use native tools from the hypervisor.
- 4
Check VM events
Remove the file or disk mentioned.
Solutions possibles
- Free from space if necessary
- Consolidate with tools provided by the hypervisor
- Rename from backup if string is unrecoverable
Scramble before any manual changes to descriptors or VMDK strings.