Happy Monday Morning 11-25-2013

So I woke up to all sorts of fun today. Several VMs were reporting to be down in my lab so when trying to connect to vCenter I was getting an error which lead me to looking at the vcsa management to make sure vCenter was running and here is what I found.



Well that is a new one for me. So I connected to my hosts using the viClient until I found my vcsa and rebooted it. I then opened up a console window. Here is what I was presented with next.



Oh this is going to be a fun morning I thought. So I proceeded to repair the file system and reboot.

09-15-11 09-17-25 09-17-57


After rebooting all was good with the vcsa. Now to figure out what exactly happened. So after digging for a few minutes I figured out that my Nexenta SAN/NAS decided to crash earlier in the morning which ended up corrupting several VMs which had to be repaired. After an hour or so all is back to normal.

Happy Monday to you!


2 thoughts on “Happy Monday Morning 11-25-2013

  1. Larry,

    we had same issues. From time to time and on random basis, our NexentaStor 3.1.3 (now 3.1.5) will crash or just reboot. After crash and if I am lucky enough, I will have a dump. I supplied Nexenta Support with plenty of dump and all point to one issue of memory allocation. it looks like in some situations, the NexentaStor system reads a piece of data that is in the memory, then flushes it and later on reads the same spot again, which results in a kernel panic and crashes the system. If you need exact explanation from Support, I will post here. This is a now known bug and Nexenta is working on a patch. The bug is set to priority high now, so I am not sure how long it will take them to fix this problem. We had this problem since the very beginning of the system, so I am not sure why it hits only us. I hope that help!

    Kind regards,

    Arturas Zalenekas

Leave a Reply

Your email address will not be published. Required fields are marked *