none
"ThinProvisioning Performance Test - NTFS(LOGO)" failed at registry key of ETW tracing RRS feed

  • Question

  • Hello,

     When we started "ThinProvisioning Performance Test - NTFS(LOGO)" for our storage product,
    we encountered an error message of "No ETW tracing is available". And the test had failed.

    The error messages are here:
    ----------------------------------------------------------------
    Warn: Please ensure the StorPort ETW Registry key is set.
     File=testsrc\driverstest\storage\wdk\trimperf\testcase.cpp, Line=990
    Error: 0x0, Error 0x00000000
     No ETW tracing is available.
     File=testsrc\driverstest\storage\wdk\trimperf\trimperf.cpp Line=242
    End: Fail, Set ETW Trace Information, TUID=, Repro=TrimPerf.exe  /DriveNumber 1 /LogDriveLetter F: /DeviceType StorEnterprise /Scenario Performance /DiskSize 0 /Cooldown 2
    ----------------------------------------------------------------

     During this test, we checked that StorPort ETW Registry key was set at Windows Registory Editer.
    So, we could not find out why we observed the above messages.

    Also, we did 'manual reporoduce' according to HCK help as below. And encountered the same error messages then failed.
    ----------------------------------------------------------------
    Examples:
     TrimPerf /DriveNumber 1 /LogDriveLetter E: /DeviceType StorConsumer /DiskSize 0 /Scenario Performance /Precondition T /TestCase 3 /Cooldown 2
    ----------------------------------------------------------------

     We are using HCK RTM(ver 8.100.25984) and Windows2012 R2 RTM(build 9600),
    but this error occurred at earlier version. We are now hoping that this problem would be solved by next version or filters.

     

    Monday, September 9, 2013 11:27 AM

All replies

  • Is MPIO configured on your TP LUN?

    If it is, you may run an alternative way as follows:

    1) Open regedit

    2) Go to

    "HKEY_LOCAL_MACHINE\SYSTEM\SYSTEM\CurrentControlSet\Enum\SCSI\Disk&Ven_Hitachi&ProdXXXX\"

    If MPIO is configured, then multiple instances will show under this. Expand each instance and go to

    "Device Parameters\Storport"

    3) Add a DWORD registry key EnableLogoETW and set the value to 1.

    4) Then rerun the test.

    Monday, September 9, 2013 10:58 PM
  • Yes, MPIO is configured on my TP LUN.
    I tried to change Registory key at Windows Registory Editer.
    And I saw that the result had changed.

    According the following log message,
    StorPort Miniport ETW tracing failed, but StorPort ETW tracing succeded.
    I think StorPort Miniport dirver itself did not work in my system.
    ----------------------------------------------------------------
    Start: Set ETW Trace Information, TUID=
    Checking the ETW trace type generated by driver.

    Trying StorPort Miniport ETW tracing.
     Spawning 1 threads.
     2300 - Random Trim 1 range 1 Slab on 500ms intervals thread started
     2300 - Stop event requested. Iterations: 5
     Start processing the ETW events.
      OpenTrace: Error code = 0x0
      ProcessTrace: Error code = 0x0
      CloseTrace: Error code = 0x0
     Processed 0 ETW entries, matched 0 entries.
     Warn: Please ensure the StorPort ETW Registry key is set.
     File=testsrc\driverstest\storage\wdk\trimperf\testcase.cpp, Line=990

    Trying StorPort ETW tracing.
     Spawning 1 threads.
     2272 - Random Trim 1 range 1 Slab on 500ms intervals thread started
     2272 - Stop event requested. Iterations: 5
     Start processing the ETW events.
      OpenTrace: Error code = 0x0
      ProcessTrace: Error code = 0x0
      CloseTrace: Error code = 0x0
     Processed 795 ETW entries, matched 795 entries.
     StorPort ETW tracing is available.

    End: Warn, Set ETW Trace Information, TUID=, Repro=TrimPerf.exe  /DriveNumber 1 /LogDriveLetter C: /DeviceType StorEnterprise /Scenario Performance /DiskSize 0 /Cooldown 2
    Test device ID: \\.\physicaldrive1, Log drive: C:
    ----------------------------------------------------------------

    Wednesday, October 2, 2013 8:47 AM