Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Crash after Message from localhost.localdomain: The redo  log of Server "NAME".vmdk is  corrupted. If the problem persists, discard the  redo log.

Posted on 2016-08-31
20
65 Views
Last Modified: 2016-10-05
Hello,

I hope I'm doing this in the right section,
as the title says, I have a problem with a ESXI Server where a virtual machine is running.
The problem is that the server crashes from time to time in a ruffly 5-10tays rhythm the messages what I get in the event viewer are the following:

Message from localhost.localdomain: The redo
log of Server "NAME"-000004.vmdk is
corrupted. If the problem persists, discard the
redo log.
info
18/08/2016 4:27:51 PM
Server "NAME"
User

and 8 minutes after this comes:

Virtual machine on localhost.localdomain is
powered off
info
18/08/2016 4:35:45 PM
Server "NAME"
User

it is always the same process first i get this message that the file is corrupted and after a few minutes it will shut down
so I can start it again and everything works fine for another 5-10 days until the same thing happens again.

As you probably can imagine, I'm not a professional I understand a fair bit but I'm far away from being a "pro" some other guy did set the hole server up and I just try to keep it alive and working. So any help or suggestion will be helpful to me and let me know if you need more information to support me with my problem.

Cheers and thanks in advance
Christian
0
Comment
Question by:Christian Tiefenbach
  • 9
  • 9
20 Comments
 
LVL 18

Expert Comment

by:Sushil Sonawane
ID: 41779238
0
 
LVL 119
ID: 41779338
You have a snapshot which maybe corrupted, which needs to be handled correctly.

I can work with you on your snapshot issue.

Can you screenshot your VM folder and confirm you have snapshots present.
0
 

Author Comment

by:Christian Tiefenbach
ID: 41784011
Thanks Andrew,

here is a screenshot from the VM folder attached.
VM-Folder.png
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 119
ID: 41784292
okay you have a VM possibly running on a snapshot.

HOW TO: VMware Snapshots :- Be Patient

and it's now possible that the VM may be corrupted. Can you check the VM properties and confirm, it is running on a snapshot disk. (See my EE Article)
0
 

Author Comment

by:Christian Tiefenbach
ID: 41785385
What exactly does it mean "running on a snapshot disk" I'm not 100% sure what to look for.

And I just saw that I described it a bit wrong,  so not the ESXI server it self  is crashing it is just the virtual machine what is crashing.  

Sorry for the confusion.
0
 
LVL 119
ID: 41785646
Did you read my EE Article on snapshots ?

Edit the VM Settings, look at the virtual disk properties, and screenshot it and upload here.
0
 

Author Comment

by:Christian Tiefenbach
ID: 41787196
Can you provide me a link to your article about snapshots? I could not find it.

here are the VM virtual Disk settings attached.
VM-Virtual-Disk-settings.png
0
 
LVL 119
ID: 41787317
it's here

HOW TO: VMware Snapshots :- Be Patient

your disk name is too long, can you scroll the hard disk....and see if it will show you
0
 

Author Comment

by:Christian Tiefenbach
ID: 41787327
If it will show me what?
0
 
LVL 119
ID: 41787330
if the VM is running on snapshot disks, so we can proceed with the repair if possible.
0
 

Author Comment

by:Christian Tiefenbach
ID: 41787333
Okay the ending is "name"-000004.vdmk
0
 
LVL 119

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points (awarded by participants)
ID: 41787376
okay, so this confirms what we need to know, the VM is running on a snapshot.

it is possible that the actually file -000004.vmdk is corrupted and there could be data loss, this is the danger of VMs running on snapshots when hosts fail.

so...can you attempt the following...

1. Take a new snapshot.
2. Wait 1 - 2 minutes
3. then select DELETE ALL...
4. Be Patient and WAIT...

snapshot merging (deleting) can take seconds, minutes, hours, days or weeks, depending on how large the snapshot, e.g. how many days the VM has been running on it, and the speed of datastore.

it may appear it's crashed, not doing anything, e.g. stuck at 90, 95, 100%, but it will complete, do not abort, or mess with the process.

BE Patient!
0
 

Author Comment

by:Christian Tiefenbach
ID: 41787396
Okay sounds good so far,  I will start the process on Saturday,  just a little question, can the vm run and be used at the same time where I delete the snapshots?
0
 
LVL 119
ID: 41787765
Yes, if you can start the VM, but remember performance can be worse when merging a snapshot.
0
 

Author Comment

by:Christian Tiefenbach
ID: 41788485
Okay yea I think that will be alright,  

Just a last question and then I won't disturb you any more for now ;)

should I do some kind of backup before I start merging?

If yes what method would you recommend?


I thank you very much for your support so far, you are one of a million and a very appreciate it.
0
 
LVL 119
ID: 41788586
Do you not currently have backups ?

the issue in it's current state, you may not be able to backup.

but you could always try something as simple as this in my EE Article

Part 10: HOW TO: Backup (Export) and Restore (Import) virtual machines to VMware vSphere Hypervisor 5.1 for FREE
0
 

Author Comment

by:Christian Tiefenbach
ID: 41788697
For sure there is an backup,  I just want to make sure that I don't have any or as less then possible on data loss :)
0
 
LVL 119
ID: 41788714
if you have a backup, then you are good to go.

if the snapshot is corrupted, you may have to restore you backup anyway.
0
 

Author Comment

by:Christian Tiefenbach
ID: 41788830
Okay  sweet thanks a lot I will report later on if it worked or if I had to restore again.
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

790 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question