800xA Virtual Servers: Error in ESXi
Hello,
I have a server with ESXi and two virtual machine (Aspect and Connectivity server). They have been running correctly for one year and a half and there was not any error. Three months ago, one of the virtual machine stopped and I had to shutdown the full physical machine and start it again to restart the both virtual machine and they ran correctly. Now, I have again the same problem. All the datastore are saved into physical hard disk into the physical server machine. Which could be the problem? Could be a hard disk physical error? The errors that gave the VMware ESXi were the following:
- Device or filesystem with identifier HardDiskID has entered the All Paths Down state.
Warning 03/01/2017 1:08:30
- Lost connectivity to storage device HardDiskID. Path vmhba33:C0:T0:L0 is down, Affected datastore: DatastoreName Error 03/01/2017 1:08:30
- Lost access of volume VolumeID due to connectivity issues. Recovery attempt is in progress and outcome will be reported shortly. Info 03/01/2017 1:08:30
- Device or filesystem with identifier HardDiskID has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will be fast failed. Warning 03/01/2017 1:10:50
- Error message on VirtualMachineName: NVRAM: write failed. Error 03/01/2017 1:11:51
Thank you.
Answers
> "Could be a hard disk physical error?"
Yes, it could be. It could also be the disk controller or it could be a driver or firmware issue.
Before you go changing hardware, check if there are any known firmware or driver issues for your system and ensure all your drivers are up to date.
Aside from the above, it seems like the way you've arranged your Physical server isnt really giving you any protection or redundancy. If you're using Virtual machines, you really should also be using redundant RAID disks, separate datastores for each virtual machine and separate disks for each datastore. Otherwise you get problems like this, where the failure of a single components shuts down multiple VM's.
by itanvet Rank: 1386 on 5/5/2017 12:32:56 AM | Like (0) | Report
usually this kind of problem is related to path redundancy connectivity towards storage, but in your case you have server internal disks, so I think you should investigate better into esxi logs, and Hardware Logs (try to check with ILO or DRAC management, it's useful sometime)
A deep check on RAID management, storage controller etc worth too.
Have a check olso on these important esx logs:
Vpxd.log
vmkernel.log
usually are into this path /var/log/
Angelo Vetrano
Add new comment