I thought that Windows found it useful to request the drive vital product data from page 0x83 of the SCSI Inquiry data.
I am currently testing my storport driver on Server 2008R2 and I don’t see this request happening. How does Windows uniquely identify a disk without this information?
Are you seeing the page 80 fetch instead?
Mark Roddy
On Wed, Sep 22, 2010 at 12:49 PM, wrote:
> I thought that Windows found it useful to request the drive vital product
> data from page 0x83 of the SCSI Inquiry data.
>
> I am currently testing my storport driver on Server 2008R2 and I don’t see
> this request happening. How does Windows uniquely identify a disk without
> this information?
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>I am currently testing my storport driver on Server 2008R2 and I don’t see this request happening.
Do you specify page 0x83 in a replay from page 0 of EnableVitalProductData? If you do, you
should get a request on page 0x83.
How does Windows uniquely identify a disk without this information?
Despite a fact that WDK documentation says
“RAID Adapters that expose virtual logical units are required to support SCSI Inquiry Vital Product Data pages 00h, 80h, and 83h” I saw that some RAID adapters specify only 0 and 0x80 pages. In fact 0x83 page may be extra because an identifier could be set from VendorID+ProductID+serial_number. This data required from INQUIRY and page 0x80.
Igor Sharovar
I am not seeing any Inquiry page requests except for page 0.
There is no EVPD bit being set either.
All requests are issued by Windows and I know that I used to see VPD requests.
But I have not looked for them in quite some time.
I see INQUIRY, REPORT_LUNS, READ for each device.
>I am not seeing any Inquiry page requests except for page 0. There is no EVPD bit being set >either.
It is strange. Usually storport sends after INQUIRY with EVPD = 0 another INQUIRY with EVPD=1 for page 0. Storport even uses the same allocated SRB for both commands. Try to debug storport to see what could trigger such condition.
Igor Sharovar
I have no source code for storport. I think it will be difficult to debug.
>I have no source code for storport. I think it will be difficult to debug.
I mean debug disassembler code. Stop in your INQUIRY routine and see a stack. You should see some storport routines which called your driver BuildIO and StartIO. Put a breakpoint on return of the nearest storport function in the stack and continue to debug. Should be a condition which prevent storport of sending INQUIRY with EVPD.
Igor Sharovar
You have the source for the Disk.sys in the WDK, so you can see all the requests that it will send…
–Mark Cariddi
OSR Open Systems Resources Inc.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@pmc-sierra.com
Sent: Wednesday, September 22, 2010 4:06 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Does Windows still request disk VPD?
I am not seeing any Inquiry page requests except for page 0.
There is no EVPD bit being set either.
All requests are issued by Windows and I know that I used to see VPD requests.
But I have not looked for them in quite some time.
I see INQUIRY, REPORT_LUNS, READ for each device.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
I would like to add to Mark comment that busTrace may help you also.
Igor Sharovar