What I/O perfomace can I expect on a single ESXi h...

swinster · ‎11-04-2014

Hi all,

As with a lot of techie users out there, I have a homebrew ESXi host running at home for messing around with and testing. This comprises:

Tyan S5510 M/B which uses the Intel C204 chipset and SATA controller

24 GB EEC RAM

Intel Xenon E3-1235 CPU

3 x WD250 Caviar 16 RE SATA drive for datastores connected to the onboard SATA controller

+ Adaptec 5405 RAID Controller (no battery backup) with 4 x 1.5 TB SATA drive as RAID 5 for Data only - the controller is setup in passthough mode.

Now, I have been having some issue with the WD250 drives (they are a little old now) and have found that they keep disappearing from the controller, thus the VMs stop. In fact I ran 'voma' recently to check for metadata errors and it returned over 127,000 errors!!!! I am replacing the drives hopefully today. However, the drive performance even with on one VM running is pretty pants with a maximum read rate or only 20MB/s, and an average of only 2M/B/s (see the graph below showing the start up of just one VM). As a result the single VM (SBS 2011, which is based on Windows 2008R2) take around 15 minuets to boot. Now, the drive maybe only, but running on the host without ESXi (i.e. an OS load directly onto them) results in much, much, much better performances.

I do understand that with such a system compromises are enviable, but what should I realistically be seeing as read and write rates on SATA drives used for data store connected directly to the M/B controller?

Cheers

Chris

SG1234 · ‎11-04-2014

do you see any errors from vmware.log on the guest or in the vmkernel

are there any limits at the VM or resource pool level...

JarryG · ‎11-04-2014

You have to understand there is one BIG performance-related difference in running any server on physical hardware (with cheap sata-drives attached to on-board controller), and running VM on ESXi using sata-drive attached to on-board controller: it is called "disk-caching".

Any "mature", complete OS does disk-caching (yes, even windows): some part of RAM is used for disk-cache and i/o-buffers. Depending on current memory-load, it could easily be a few GB, even more than half of physical RAM (checking task-manager on my windows7-workstation: right now out of 12GB RAM, 8GB is used as disk-cache). And it really does speed up reading/writing tremendously, especially non-sequential (random).

ESXi, on the other side, does NOT do disk-caching. It does not sacrifice single byte of physical memory for it. Instead, it relies on controller to do it. But on-board sata-controller does not have any cache, so you are running VM on basically un-cached disk (except for a few MB of in-drive cache). This is severe performance-penalty, and your results correspond with it.

I personally would not use on-board (non-cached) controller for anything but backup, or as pass-through. Sure not for VMFS-storage, not even with single VM.

_____________________________________________ If you found my answer useful please do *not* mark it as "correct" or "helpful". It is hard to pretend being noob with all those points! 😉

swinster · ‎11-04-2014

Hi,

I have two resource pools created previously, but at this point in time all VM's were just place in the root hos the host so the resource pool actually house nothing.

I have looked through the 'vmware.log' file in the guest and scanned through for the word 'error'. I must say I have never really read these logs so don't entirely know what I'm looking for, but the guest did blue screen at one point with the following:

2014-11-03T15:58:41.366Z| mks| I120: SVGA disabling SVGA

2014-11-03T15:58:41.374Z| svga| I120: WinBSOD: ( 1) `A problem has been detected and Windows has been shut down to prevent damage    '

2014-11-03T15:58:41.374Z| svga| I120: WinBSOD: ( 2) `to your computer.                                                               '

2014-11-03T15:58:41.374Z| svga| I120: WinBSOD: ( 4) `DRIVER_IRQL_NOT_LESS_OR_EQUAL                                                   '

2014-11-03T15:58:41.375Z| svga| I120: WinBSOD: ( 6) `If this is the first time you've seen this Stop error screen,                   '

2014-11-03T15:58:41.375Z| svga| I120: WinBSOD: ( 7) `restart your computer. If this screen appears again, follow                     '

2014-11-03T15:58:41.375Z| svga| I120: WinBSOD: ( 😎 `these steps:                                                                    '

2014-11-03T15:58:41.375Z| svga| I120: WinBSOD: (10) `Check to make sure any new hardware or software is properly installed.          '

2014-11-03T15:58:41.375Z| svga| I120: WinBSOD: (11) `If this is a new installation, ask your hardware or software manufacturer       '

2014-11-03T15:58:41.375Z| svga| I120: WinBSOD: (12) `for any Windows updates you might need.                                         '

2014-11-03T15:58:41.375Z| svga| I120: WinBSOD: (14) `If problems continue, disable or remove any newly installed hardware            '

2014-11-03T15:58:41.375Z| svga| I120: WinBSOD: (15) `or software. Disable BIOS memory options such as caching or shadowing.          '

2014-11-03T15:58:41.376Z| svga| I120: WinBSOD: (16) `If you need to use Safe Mode to remove or disable components, restart           '

2014-11-03T15:58:41.376Z| svga| I120: WinBSOD: (17) `your computer, press F8 to select Advanced Startup Options, and then            '

2014-11-03T15:58:41.376Z| svga| I120: WinBSOD: (18) `select Safe Mode.                                                               '

2014-11-03T15:58:41.376Z| svga| I120: WinBSOD: (20) `Technical information:                                                          '

2014-11-03T15:58:41.376Z| svga| I120: WinBSOD: (22) `*** STOP: 0x000000D1 (0x0000000000000000,0x0000000000000002,0x0000000000000000,0'

2014-11-03T15:58:41.376Z| svga| I120: WinBSOD: (23) `xFFFFF8800189456B)                                                              '

2014-11-03T15:58:41.377Z| svga| I120: WinBSOD: (26) `***     tcpip.sys - Address FFFFF8800189456B base at FFFFF88001800000, DateStamp'

2014-11-03T15:58:41.377Z| svga| I120: WinBSOD: (27) ` 533f5bd4                                                                       '

2014-11-03T15:58:41.377Z| svga| I120: WinBSOD: (30) `Collecting data for crash dump ...                                              '

2014-11-03T15:58:41.377Z| svga| I120: WinBSOD: (31) `Initializing disk for crash dump ...                                            '

2014-11-03T15:58:45.464Z| svga| I120: WinBSOD: (32) `Beginning dump of physical memory.                                              '

2014-11-03T15:58:45.464Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 0                                             '

2014-11-03T15:58:46.436Z| svga| I120: WinBSOD: (33) `D                                                                               '

2014-11-03T15:58:46.453Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 5                                             '

2014-11-03T15:58:47.929Z| svga| I120: WinBSOD: (33) `Dumping physical memo                                                           '

2014-11-03T15:58:47.945Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 10                                            '

2014-11-03T15:58:49.320Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 15                                            '

2014-11-03T15:58:50.226Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 20                                            '

2014-11-03T15:58:50.863Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 25                                            '

2014-11-03T15:58:51.500Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 30                                            '

2014-11-03T15:58:52.171Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 35                                            '

2014-11-03T15:58:53.680Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 40                                            '

2014-11-03T15:58:55.122Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 45                                            '

2014-11-03T15:58:56.598Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 50                                            '

2014-11-03T15:58:58.030Z| vmx| I120: GuestRpcSendTimedOut: message to toolbox timed out.

2014-11-03T15:58:58.031Z| vmx| I120: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

2014-11-03T15:58:58.073Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 55                                            '

2014-11-03T15:58:59.516Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 60                                            '

2014-11-03T15:59:00.186Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 65                                            '

2014-11-03T15:59:00.840Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 70                                            '

2014-11-03T15:59:01.612Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 75                                            '

2014-11-03T15:59:02.534Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 80                                            '

2014-11-03T15:59:03.171Z| svga| I120: WinBSOD: (33) `Du                                                                              '

2014-11-03T15:59:03.188Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 85                                            '

2014-11-03T15:59:03.515Z| vmx| I120: Tools: Tools heartbeat timeout.

2014-11-03T15:59:03.825Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 90                                            '

2014-11-03T15:59:04.462Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 95                                            '

2014-11-03T15:59:05.100Z| svga| I120: WinBSOD: ( 0) `A problem has been detected and Windows has been shut down to prevent damage    '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: ( 1) `to your computer.                                                               '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: ( 2) `                                                                                '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: ( 3) `DRIVER_IRQL_NOT_LESS_OR_EQUAL                                                   '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: ( 4) `                                                                                '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: ( 5) `If this is the first time you've seen this Stop error screen,                   '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: ( 6) `restart your computer. If this screen appears again, follow                     '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: ( 7) `these steps:                                                                    '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: ( 😎 `                                                                                '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: ( 9) `Check to make sure any new hardware or software is properly installed.          '

2014-11-03T15:59:05.101Z| svga| I120: WinBSOD: (10) `If this is a new instyllationr ask our hardware orpsoptwaye manufacturer       '

2014-11-03T15:59:05.104Z| svga| I120: WinBSOD: (33) `Dumping physical memory to disk: 100                                           '

2014-11-03T15:59:05.117Z| svga| I120: WinBSOD: ( 0) `to your computer.                                                               '

2014-11-03T15:59:05.117Z| svga| I120: WinBSOD: ( 1) `                                                                                '

2014-11-03T15:59:05.117Z| svga| I120: WinBSOD: ( 2) `DRIVER_IRQL_NOT_LESS_OR_EQUAL                                                   '

2014-11-03T15:59:05.117Z| svga| I120: WinBSOD: ( 3) `                                                                                '

2014-11-03T15:59:05.118Z| svga| I120: WinBSOD: ( 4) `If this is the first time you've seen this Stop error screen,                   '

2014-11-03T15:59:05.118Z| svga| I120: WinBSOD: ( 5) `restart your computer. If this screen appears again, follow                     '

2014-11-03T15:59:05.118Z| svga| I120: WinBSOD: ( 6) `these steps:                                                                    '

2014-11-03T15:59:05.118Z| svga| I120: WinBSOD: ( 7) `                                                                                '

2014-11-03T15:59:05.118Z| svga| I120: WinBSOD: ( 😎 `Check to make sure any new hardware or software is properly installed.          '

2014-11-03T15:59:05.118Z| svga| I120: WinBSOD: ( 9) `If this is a new installation, ask your hardware or software manufacturer       '

2014-11-03T15:59:05.118Z| svga| I120: WinBSOD: (10) `for any Windows updates you might need.                                         '

2014-11-03T15:59:05.118Z| svga| I120: WinBSOD: (11) `                                                                                '

2014-11-03T15:59:05.118Z| svga| I120: WinBSOD: (12) `If problems continue, disable or remove any newly installed hardware            '

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (13) `or software. Disable BIOS memory options such as caching or shadowing.          '

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (14) `If you need to use Safe Mode to remove or disable components, restart           '

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (15) `your computer, press F8 to select Advanced Startup Options, and then            '

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (16) `your computer, press F8 to select Advanced Startup Options, and then            '

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (17) `select Safe Mode.                                                               '

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (18) `                                                                                '

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (19) `Technical information:                                                          '

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (20) `                                                                                '

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (21) `*** STOP: 0x000000D1 (0x0000000000000000,0x0000000000000002,0x0000000000000000,0'

2014-11-03T15:59:05.119Z| svga| I120: WinBSOD: (22) `xFFFFF8800189456B)                                                              '

2014-11-03T15:59:05.120Z| svga| I120: WinBSOD: (23) `                                                                                '

2014-11-03T15:59:05.120Z| svga| I120: WinBSOD: (25) `***     tcpip.sys - Address FFFFF8800189456B base at FFFFF88001800000, DateStamp'

2014-11-03T15:59:05.120Z| svga| I120: WinBSOD: (26) ` 533f5bd4                                                                       '

2014-11-03T15:59:05.120Z| svga| I120: WinBSOD: (27) `                                                                                '

2014-11-03T15:59:05.120Z| svga| I120: WinBSOD: (29) `Collecting data for crash dump ...                                              '

2014-11-03T15:59:05.120Z| svga| I120: WinBSOD: (30) `Initializing disk for crash dump ...                                            '

2014-11-03T15:59:05.120Z| svga| I120: WinBSOD: (31) `Beginning dump of physical memory.                                              '

2014-11-03T15:59:05.120Z| svga| I120: WinBSOD: (32) `Dumping physical memory to disk: 100                                           '

2014-11-03T15:59:05.121Z| svga| I120: WinBSOD: (33) `Physical memory dump complete.                                                  '

2014-11-03T15:59:05.134Z| svga| I120: WinBSOD: (16) `select Safe Mode.                                                               '

2014-11-03T15:59:05.134Z| svga| I120: WinBSOD: (17) `                                                                                '

2014-11-03T15:59:05.134Z| svga| I120: WinBSOD: (18) `Technical information:                                                          '

2014-11-03T15:59:05.134Z| svga| I120: WinBSOD: (19) `                                                                                '

2014-11-03T15:59:05.134Z| svga| I120: WinBSOD: (20) `*** STOP: 0x000000D1 (0x0000000000000000,0x0000000000000002,0x0000000000000000,0'

2014-11-03T15:59:05.134Z| svga| I120: WinBSOD: (21) `xFFFFF8800189456B)                                                              '

2014-11-03T15:59:05.134Z| svga| I120: WinBSOD: (22) `                                                                                '

2014-11-03T15:59:05.134Z| svga| I120: WinBSOD: (24) `***     tcpip.sys - Address FFFFF8800189456B base at FFFFF88001800000, DateStamp'

2014-11-03T15:59:05.134Z| svga| I120: WinBSOD: (25) ` 533f5bd4                                                                       '

2014-11-03T15:59:05.135Z| svga| I120: WinBSOD: (26) `                                                                                '

2014-11-03T15:59:05.135Z| svga| I120: WinBSOD: (28) `Collecting data for crash dump ...                                              '

2014-11-03T15:59:05.135Z| svga| I120: WinBSOD: (29) `Initializing disk for crash dump ...                                            '

2014-11-03T15:59:05.135Z| svga| I120: WinBSOD: (30) `Beginning dump of physical memory.                                              '

2014-11-03T15:59:05.135Z| svga| I120: WinBSOD: (31) `Dumping physical memory to disk: 100                                           '

2014-11-03T15:59:05.135Z| svga| I120: WinBSOD: (32) `Physical memory dump complete.                                                  '

2014-11-03T15:59:05.135Z| svga| I120: WinBSOD: (33) `Contact your system admin or technical support group for further assistance.    '

However, the 'vmkernal.log' do show an error on the ATA device - which would be roughly when it drops out. As mentioned, I'm replacing the drive but am hoping that there isn't something unlaying that is wrong. there are some other error reference to 'sitpua' not being supported, but I have no idea what this might be.

H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-11-04T06:31:21.491Z cpu6:32795)ScsiDeviceIO: 2337: Cmd(0x412e807fb600) 0x1a, CmdSN 0x1ba9 from world 0 to dev "mpx.vmhba34:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-11-04T06:31:40.007Z cpu7:35902)World: 14296: VC opID hostd-7501 maps to vmkernel opID 25f3b899

2014-11-04T06:32:00.007Z cpu4:34000)World: 14296: VC opID hostd-0f5c maps to vmkernel opID ab435d68

2014-11-04T06:32:20.007Z cpu6:34007)World: 14296: VC opID hostd-0f5c maps to vmkernel opID ab435d68

2014-11-04T06:32:28.148Z cpu5:35900)World: 14296: VC opID hostd-9b72 maps to vmkernel opID a70cd117

2014-11-04T06:32:40.004Z cpu2:35900)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

2014-11-04T06:33:00.007Z cpu2:34007)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

2014-11-04T06:33:14.477Z cpu4:32793)ScsiDeviceIO: 2337: Cmd(0x412e807bd480) 0x2a, CmdSN 0x152e9 from world 32781 to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x5 0x20 0$

2014-11-04T06:33:15.477Z cpu0:32789)ScsiDeviceIO: 2337: Cmd(0x412e807bd480) 0x2a, CmdSN 0x152ea from world 32781 to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x5 0x20 0$

2014-11-04T06:33:15.549Z cpu5:32794)ScsiDeviceIO: 2306: Cmd(0x412e80819300) 0x28, CmdSN 0x80000050 from world 35914 to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" failed H:0x8 D:0x0 P:0x0

2014-11-04T06:33:15.549Z cpu5:32794)ScsiDeviceIO: 2306: Cmd(0x412e807b0840) 0x28, CmdSN 0x80000058 from world 35914 to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" failed H:0x8 D:0x0 P:0x0

2014-11-04T06:33:15.549Z cpu5:32794)ScsiDeviceIO: 2306: Cmd(0x412e807eec00) 0x2a, CmdSN 0x80000065 from world 35914 to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" failed H:0x8 D:0x0 P:0x0

2014-11-04T06:33:15.549Z cpu5:32794)ScsiDeviceIO: 2306: Cmd(0x412e80839fc0) 0x2a, CmdSN 0x80000019 from world 35914 to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" failed H:0x8 D:0x0 P:0x0

2014-11-04T06:33:15.549Z cpu5:32808)<6>ahci_scsi_abort: cmd 0x28 (0x412e81772080), entering...

2014-11-04T06:33:15.549Z cpu5:32808)<7>ata4: ahci_port_reset, entering...

2014-11-04T06:33:17.785Z cpu0:32808)<6>ata4: ahci_port_reset, hard reseting port

2014-11-04T06:33:17.785Z cpu7:33454)<3>ata4.00: exception Emask 0x10 SAct 0x1 SErr 0x10000 action 0xa frozen

2014-11-04T06:33:17.785Z cpu7:33454)<3>ata4.00: irq_stat 0x00400000, hotplug handled, PHY RDY changed

2014-11-04T06:33:17.785Z cpu7:33454)<3>ata4: SError: { PHYRdyChg }

2014-11-04T06:33:17.785Z cpu7:33454)<3>ata4.00: cmd 60/30:00:08:7a:d3/00:00:18:00:00/40 tag 0 ncq 24576 in

res 80/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x12 (ATA bus error)

2014-11-04T06:33:17.785Z cpu7:33454)<3>ata4.00: status: { Busy }

2014-11-04T06:33:18.537Z cpu7:33454)<6>ata4: soft resetting link

2014-11-04T06:33:18.537Z cpu7:33454)<6>ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

2014-11-04T06:33:18.598Z cpu7:33454)<6>ata4.00: configured for UDMA/133

2014-11-04T06:33:18.598Z cpu7:33454)<6>ata4: EH complete

2014-11-04T06:33:18.709Z cpu0:32808)<6>ata4: ahci_port_reset: SUCCEEDED

2014-11-04T06:33:18.709Z cpu0:32808)<6>ahci_scsi_abort: cmd 0x28 (0x412e81772080), SUCCEEDED

2014-11-04T06:33:18.709Z cpu5:35920)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x28 (0x412e807f6800, 35914) to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" on path "vmhba35:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense$

2014-11-04T06:33:18.709Z cpu5:35920)ScsiDeviceIO: 2324: Cmd(0x412e807f6800) 0x28, CmdSN 0x8000006f from world 35914 to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x47 0$

2014-11-04T06:33:18.831Z cpu0:32808)HBX: 255: Reclaimed heartbeat for volume 4f4aae60-f73239c8-aea8-00e081ca7d70 (Main): [Timeout] Offset 3858944

2014-11-04T06:33:18.831Z cpu0:32808)[HB state abcdef02 offset 3858944 gen 17 stampUS 114717351506 uuid 5456b330-47b84fe5-8001-00e081ca7d6e jrnl <FB 192138> drv 14.60]

2014-11-04T06:33:18.876Z cpu7:33454)<3>ata4.00: exception Emask 0x10 SAct 0x1 SErr 0x400100 action 0x6 frozen

2014-11-04T06:33:18.876Z cpu7:33454)<3>ata4.00: irq_stat 0x08000000, interface fatal error

2014-11-04T06:33:18.876Z cpu7:33454)<3>ata4: SError: { UnrecovData Handshk }

2014-11-04T06:33:18.876Z cpu7:33454)<3>ata4.00: cmd 61/08:00:08:50:94/00:00:18:00:00/40 tag 0 ncq 4096 out

res 40/00:04:08:50:94/00:00:18:00:00/40 Emask 0x10 (ATA bus error)

2014-11-04T06:33:18.876Z cpu7:33454)<3>ata4.00: status: { DRDY }

2014-11-04T06:33:18.876Z cpu7:33454)<6>ata4: hard resetting link

2014-11-04T06:33:20.006Z cpu2:34007)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

2014-11-04T06:33:24.461Z cpu4:33454)<4>ata4: port is slow to respond, please be patient (Status 0x80)

2014-11-04T06:33:28.917Z cpu6:33454)<3>ata4: COMRESET failed (errno=-16)

2014-11-04T06:33:28.917Z cpu6:33454)<6>ata4: hard resetting link

2014-11-04T06:33:29.419Z cpu4:33454)<6>ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

2014-11-04T06:33:29.420Z cpu4:33454)<6>ata4.00: configured for UDMA/133

2014-11-04T06:33:29.420Z cpu4:33454)<6>ata4: EH complete

2014-11-04T06:33:29.420Z cpu7:32833)ScsiDeviceIO: 2324: Cmd(0x412e8088d440) 0x2a, CmdSN 0x80000060 from world 35914 to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x0 0x$

2014-11-04T06:33:29.477Z cpu4:32793)ScsiDeviceIO: 2337: Cmd(0x412e8081b9c0) 0x2a, CmdSN 0x152ee from world 32781 to dev "t10.ATA_____WDC_WD2500YD2D01NVB1__________________________WD2DWCANK4315451" failed H:0x5 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x$

2014-11-04T06:33:40.007Z cpu7:35900)World: 14296: VC opID hostd-7501 maps to vmkernel opID 25f3b899

2014-11-04T06:34:00.007Z cpu6:35902)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

2014-11-04T06:34:20.006Z cpu0:35902)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

2014-11-04T06:34:40.006Z cpu4:34000)World: 14296: VC opID hostd-925e maps to vmkernel opID fa5de904

2014-11-04T06:35:00.007Z cpu2:34007)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

2014-11-04T06:35:02.044Z cpu6:34000)World: 14296: VC opID hostd-dd62 maps to vmkernel opID 2f6bbb13

2014-11-04T06:35:40.006Z cpu1:34007)World: 14296: VC opID hostd-925e maps to vmkernel opID fa5de904

2014-11-04T06:36:20.006Z cpu4:34007)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

2014-11-04T06:36:21.488Z cpu3:32792)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e80856600, 0) to dev "mpx.vmhba34:C0:T0:L0" on path "vmhba34:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-11-04T06:36:21.488Z cpu3:32792)ScsiDeviceIO: 2337: Cmd(0x412e80856600) 0x1a, CmdSN 0x1bcc from world 0 to dev "mpx.vmhba34:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-11-04T06:36:26.486Z cpu7:35902)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

2014-11-04T06:36:40.006Z cpu7:35902)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

2014-11-04T06:37:20.004Z cpu0:34000)World: 14296: VC opID hostd-d275 maps to vmkernel opID 3fb9a95f

I have also attached the some the full log files just in case I've missed anything.

swinster · ‎11-04-2014

Cheers Jerry G. Hmm. Maybe I should have configure the Adaptec controller the other way round - i.e. use that for the data stores and SATA for pasthrough as you say. I was more interested in creating a redundant array form my data however. If only I had more money....

swinster · ‎11-04-2014

Just wondering, if I could get hold of a small SATA SSD (128GB perhaps), again directly connected to the M/B controller, can this be for "host cacheing", or does is simply not work the way I'm reading it?

swinster · ‎11-04-2014

Never mind on the above question. I have just read that this is an improvement on memory swap configuration, no I/O caching. Shame

TheUnF · ‎02-28-2016

BTW, does your ESXi being able to receive info from Ambient sensor on the motherboard ?

Mine is still on 200 celsius ;(

All

What I/O perfomace can I expect on a single ESXi host using SATA drives via on-board controller