General
Showing results for 
Search instead for 
Do you mean 

Problems with an USB-drive

Frequent Advisor

Problems with an USB-drive

I have a problem with an USB-drive:

 

If I plug in the USB-cable if the system is up then the drive is recognized and the dndriver is loaded,

but if I reboot the machine and the USB-drive is still switch on the drive gets a different unit number

and is marked as offline in the "show device dna" command.

 

I ran several test and I'm sure that the EHCIDRIVER makes these problem. If I'm using the (slow) USB 1.1

driver and disable the EHDRIVER the drive is online after a reboot.

 

I made some investigations and I have found an indicator where the driver goes wrong.

 

If you add a new USB-drive the data are stored in a file named sys$specific:[sysexe]USB$UCM_DEVICES.DAT.

 

I see two entries for the same drive. The only difference are two lines. The PATH and the SERIAL_NUMBER are different:

 

OK:

PATH    = 4.0.0.0.0.0

SERIAL_NUMBER   = PROLIFICMP0000000FC

WRONG (OFFLINE)

PATH    = 2.0.0.0.0.0

SERIAL_NUMBER   = PROLIFICMP0000000FC0

                                                                                      ^

                                                                                      that's the strange character!!!

 

I explain this as follows: if the USB-system starts the SERIAL_NUMBER is evaluated wrong and then it tries to load the dndriver and finds a different SERIAL_NUMBER (without the 0 at the end). There is no chance to cure this problem. An unplug and plug in process does not chance the status of the drive. A restart of the UCM-server process has no effect, too.

 

I did not try to use analyse/system to get rid off a wrong entrance of the dn-device (if this is possible after all).

 

I am very thankful for any ideas who to solve this problem!

 

thanks

Eberhard

 

======================================

DEVICE  = "USB Mass storage "
NAME    = DNA
DRIVER  = SYS$DNDRIVER.EXE
BEGIN_PRIVATE
USB_CONFIG_TYPE = INTERFACE
UNIT_NUMBER     = 18
VENDOR_ID       = 1659
PRODUCT_ID      = 10097
RELEASE_NUMBER  = 256
BUS_NUMBER      = 1
PATH    = 2.0.0.0.0.0
DEVICE_CLASS    = 0
DEVICE_SUB_CLASS        = 0
DEVICE_PROTOCOL = 0
NUMBER_OF_INTERFACES    = 1
CONFIGURATION_VALUE     = 1
NUMBER_OF_CONFIGURATIONS        = 1
SERIAL_NUMBER   = PROLIFICMP0000000FC0
MANUFACTURER_STRING     = Prolific Technology Inc.
PRODUCT_STRING  = USB-SATA Bridge
CONFIGURATION_NUMBER    = 0
BEGIN_INTERFACE
INTERFACE_CLASS = 8
INTERFACE_SUB_CLASS     = 6
INTERFACE_PROTOCOL      = 80
END_INTERFACE
END_PRIVATE
END_DEVICE



DEVICE  = "USB Mass storage "
NAME    = DNA
DRIVER  = SYS$DNDRIVER.EXE
BEGIN_PRIVATE
USB_CONFIG_TYPE = INTERFACE
UNIT_NUMBER     = 19
VENDOR_ID       = 1659
PRODUCT_ID      = 10097
RELEASE_NUMBER  = 256
BUS_NUMBER      = 2
PATH    = 4.0.0.0.0.0
DEVICE_CLASS    = 0
DEVICE_SUB_CLASS        = 0
DEVICE_PROTOCOL = 0
NUMBER_OF_INTERFACES    = 1
CONFIGURATION_VALUE     = 1
NUMBER_OF_CONFIGURATIONS        = 1
SERIAL_NUMBER   = PROLIFICMP0000000FC
MANUFACTURER_STRING     = Prolific Technology Inc.
PRODUCT_STRING  = USB-SATA Bridge
CONFIGURATION_NUMBER    = 0
BEGIN_INTERFACE
INTERFACE_CLASS = 8
INTERFACE_SUB_CLASS     = 6
INTERFACE_PROTOCOL      = 80
END_INTERFACE
END_PRIVATE
END_DEVICE
==============================================

 

4 REPLIES
Honored Contributor Honored Contributor

Re: Problems with an USB-drive

Eberhard,

can you supply us with your OpenVMS version and patch status?

PROD SHOW PROD VMS/FULL would be handy!

Thanks
Frequent Advisor

Re: Problems with an USB-drive

OpenVMS 8.4 + all patches

 

eberhard

Honored Contributor Honored Contributor

Re: Problems with an USB-drive

That doesn't actually look like all patches.  Specifically, VMS84I_USB-V0100 has not been included in any update kit yet according to the master ECO list, and I don't see it in your list of what you've installed.  The release notes for the USB patch don't describe anything about USB-attached storage, but it might be worth a try anyway.

Highlighted
Frequent Advisor

Re: Problems with an USB-drive

I have another machine with this USB-patch installed. The problem still exists.

 

Eberhard