Aug 22 09:41:56: vmx| DISK: DISK/CDROM timeout of 561.747 seconds on ide0:0 (ok)
Aug 22 09:47:29: vmx| DISK: DISK/CDROM timeout of 302.445 seconds on ide0:0 (ok)
Aug 22 09:53:03: vmx| DISK: DISK/CDROM timeout of 273.913 seconds on ide0:0 (ok)
Aug 22 09:58:11: vmx| DISK: DISK/CDROM timeout of 302.786 seconds on ide0:0 (ok)
Aug 22 10:08:22: vmx| DISK: DISK/CDROM timeout of 276.464 seconds on ide0:0 (ok)
Aug 22 10:13:26: vmx| DISK: DISK/CDROM timeout of 298.269 seconds on ide0:0 (ok)
Aug 22 10:16:23: vmx| DISK: DISK/CDROM timeout of 160.233 seconds on ide0:0 (ok)
Aug 22 11:41:57: vmx| DISK: DISK/CDROM timeout of 1.086 seconds on ide0:0 (ok)
Aug 22 11:42:00: vcpu-0| DISKLIB-LIB :numIOs = 3250000 numMergedIOs = 0 numSplitIOs = 0
Aug 22 12:11:06: mks| MKS set guest selection request with invalid state 2
Aug 22 12:12:04: vmx| DISK: DISK/CDROM timeout of 1.202 seconds on ide0:0 (ok)
Aug 22 22:17:59: vmx| DISKLIB-LIB :numIOs = 3300000 numMergedIOs = 0 numSplitIOs = 0
...
Aug 26 03:47:44: vmx| LICENSE using: 'HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Server\License.vs.1.0-00'
Aug 26 05:54:39: vcpu-0| DISKLIB-LIB :numIOs = 3750000 numMergedIOs = 0 numSplitIOs = 0
Aug 26 07:36:27: vmx| DISK: DISK/CDROM timeout of 551.323 seconds on ide0:0 (ok)
Aug 26 07:46:35: vmx| DISK: DISK/CDROM timeout of 262.740 seconds on ide0:0 (ok)
Aug 26 07:51:44: vmx| DISK: DISK/CDROM timeout of 287.413 seconds on ide0:0 (ok)
Aug 26 07:56:48: vmx| DISK: DISK/CDROM timeout of 298.653 seconds on ide0:0 (ok)
Aug 26 08:01:51: vmx| DISK: DISK/CDROM timeout of 270.345 seconds on ide0:0 (ok)
Aug 26 08:06:55: vmx| DISK: DISK/CDROM timeout of 274.581 seconds on ide0:0 (ok)
Aug 26 08:11:59: vmx| DISK: DISK/CDROM timeout of 298.656 seconds on ide0:0 (ok)
Aug 26 08:16:38: vmx| DISK: DISK/CDROM timeout of 273.904 seconds on ide0:0 (ok)
Falls jemand mal solche hohen Werte in seinen Logs vorfindet, kann sich eines absolut sicher sein. Das darunterliegende Storage hat ein gewaltiges Problem, wenn man sich dagegen mal die Normalwerte ansieht.
In diesem Fall waren es beide Teilnehmer eines Raid1-Arrays, die ungefragt ihren Dienst einstellten.
![Shocked :shock:](./images/smilies/icon_eek.gif)