• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

ESX inaccessible

X

x_rufus_x

n00b
Joined
Feb 2, 2013
Messages
8
People,
Need some help here ;)

I've built an All in One Home Server last year. It worked flawlessly until three days ago some wierd problems ocurred.

Host Specification:
ESXi 5.1
Mobo: Intel DQ77MK
RAM: 4 x Corsair DDR3 1333 (32GB)
HD: 3x 2TB Seagate Barracuda ST2000DM001
HD: 1x Western Digital Caviar Blue WD5000AAKX 500GB (ESXi Datastore)
PSU: OCZ ZT550W
RAID: IBM ServeRAID M1015/LSI SAS9220-8i

My caviar blue is connected directly to the mobo, It's where my ESX is installed, and where my main VMs resids.
One of those VMs is my ZFS Fileserver, an 8GB + 4 vCPUS Open Indinana (with napp-it). I also have some Windows Server 2008 VMs.

Three days ago my OpenIndiana was inacessible, I tried to access it via vSphere console and I noticed that the OS stopped on its loading screen.
After some googling I was able to recover it, and it began to work as usual.

Yesterday I've found that my OpenIndiana was with the same problem, but also all my Windows Servers were crashed, with blue screens.
The windows VMS I could not even repair it nor use an early snapshot (same blue screen). I was able to recover my OpenIndiana again, but
it began to work veery slow and a lot of reading and checksum errors began to pop on my zpools.

So,
Anyone experienced something similar? I don't know if its my caviar blue that is with some issues, or if it's my ESX that is broken?

Any idea?
Sorry for the long post and bad english ;)
 
you could try checking the VMDK files to see if they're clean.

Go to the shell command
navigate to /vmfs/volumes/datastore/virtualmachine/

then run vmkfstools -x (check/repair) disk.vmdk

I notice that there are a lot more issues with white box machines running at home than branded servers running in a datacenter though.
Are you getting clean power to the box? You wouldn't believe how many weird issues i've seen that were power related.
 
0V3RC10CK3D said:
you could try checking the VMDK files to see if they're clean.

Go to the shell command
navigate to /vmfs/volumes/datastore/virtualmachine/

then run vmkfstools -x (check/repair) disk.vmdk

I notice that there are a lot more issues with white box machines running at home than branded servers running in a datacenter though.
Are you getting clean power to the box? You wouldn't believe how many weird issues i've seen that were power related.
Click to expand...

All that does is validate the structure of the file is intact - it's pretty useless to be honest (if it boots, it does the same thing at power on).

what's /var/log/vmkernel.log say?
 
You must log in or register to reply here.
Back
Top