USB error code 0x144?

[Fredrik Israelsson]

A system suddenly cannot access a USB disk anymore. The other USB disk on that box works perfectly.

I don't have physical access to it and I am trying to figure out if I need to declare it dead or if I can bring it back to life.

The device is detected in USM but not configured due to below error. I can see the information about serial etc so USM seams to have some connectivity to the device.

ucm show event:
12-NOV-2009 11:41:14.20 UCM NORMAL SYS$DNDRIVER.EXE
Message: Tentative device DNA2067032576 proposed... auto-loading driver.

12-NOV-2009 11:41:14.20 UCM NORMAL SYS$DNDRIVER.EXE
Message: Error from auto-load for DNA20670. - status 0x144.

12-NOV-2009 11:41:14.20 DRIVER NORMAL HUBDRIVER
Message: hub_configure_device Unable to find Interface Driver

[Hoff]

Which OpenVMS architecture and version?

Which box?

Which USB device?

$ exit %x144
%SYSTEM-F-IVDEVNAM, invalid device name
$

As a start, patch to current.

If this is OpenVMS I64, get to V8.3-1H1 and current USB bits, and patch to current. USB support was up-rated in V8.3-1H1.

Check the DEVICE_NAMING system parameter, too; that DN disk device unit number is past the old 9999 wrap.

http://labs.hoffmanlabs.com/node/1219

If you have support for this box with HP, then you'll want to log a call. (But HP will ask you to apply current patches)

[Fredrik Israelsson]

Thanks for your reply Hoff.

It's IA64, RX2660 and 8.3-1h1 fairly updated.

The disk is a LaCie, 750GB version of http://www.lacie.com/products/product.htm?pid=11014 Have 10 of those in use.

I will test the DEVICE_NAMING parameter during maintenance this weekend. I really don't get how come it picked such a big number though.

I do have support but I think that the official claim is that non-HP devices are not supported. I can always ask if the device naming does not do the trick.

The USB disk is identified as:
DEVICE USB Mass storage
DEVICE_TYPE PERMANENT
DEVICE_NAME_ROOT DNA
UNIT_NUMBER 77
DRIVER SYS$DNDRIVER.EXE
USB_CONFIG_TYPE INTERFACE
VENDOR_ID 5421
PRODUCT_ID 9017
RELEASE_NUMBER 256
BUS_NUMBER 2
PATH 5.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 90B87FFFFFFF
MANUFACTURER_STRING JMicron
PRODUCT_STRING USB to ATA/ATAPI Bridge
CONFIGURATION_NUMBER 0
BEGIN_INTERFACE
INTERFACE_CLASS 8
INTERFACE_SUB_CLASS 6
INTERFACE_PROTOCOL 80
END_INTERFACE
END_DEVICE

admds79103@jpcv01> prod sho hist
------------------------------------ ----------- ----------- --- -----------
PRODUCT KIT TYPE OPERATION VAL DATE
------------------------------------ ----------- ----------- --- -----------
HP I64VMS TCPIP V5.6-9ECO4 Full LP Install Val 19-OCT-2009
HP I64VMS TCPIP V5.6-9ECO3 Full LP Remove - 19-OCT-2009
HP I64VMS VMS831H1I_PTHREAD V1.0 Patch Install Val 19-OCT-2009
HP I64VMS VMS831H1I_TDF V1.0 Patch Install Val 19-OCT-2009
HP I64VMS VMS831H1I_IPC V3.0 Patch Install Val 19-OCT-2009
HP I64VMS VMS831H1I_SHADOWING V2.0 Patch Install Val 19-OCT-2009
HP I64VMS VMS831H1I_SYS V5.0 Patch Install Val 19-OCT-2009
HP I64VMS VMS831H1I_UPDATE V6.0 Patch Install Val 19-OCT-2009
HP I64VMS VMS831H1I_IPC V2.0 Patch Install Val 15-JUN-2009
HP I64VMS VMS831H1I_USB V1.0 Patch Install Val 15-JUN-2009
HP I64VMS VMS831H1I_XFC V1.0 Patch Install Val 15-JUN-2009
HP I64VMS VMS831H1I_UPDATE V5.0 Patch Install Val 15-JUN-2009
HP I64VMS VMS831H1I_FIBRE_SCSI V4.0 Patch Install Val 15-JUN-2009

[Hoff]

USB to ATA bridges can be really bad; I've seen several of those that were entirely hideous when you look at the USB bus traces. And no, you can't depend on two examples of the same model device using the same bridges.

What does UCM have for its known permanent configuration? UCM> SHOW DEVICE /PERMANENT /ALL /FULL

Try a different device. Try a different vendor. (Could be broken hardware; see if the widget works else-box.)

Also look for silly stuff like colliding device serial numbers here, too. (Some devices do clone the same serial number, and that's caused some confusion and general mayhem in some configurations.)

[Clarete Riana]

Hi,

This issue has been observed in the past and it is related to configuration manager.

We have also seen that a reboot has solved this issue in the past.

Please elevate this issue, and USB engineering will work on providing a fix for this.

Regards,
Clarete

[Fredrik Israelsson]

Hoff, you are right, there are two different models of controllers, one labeled LaCie and one labeled JMicron. Looks like this was the only JMicron I had in production but it used to work.

DEVICE_NAMING did not help so I booted from the OpenVMS DVD where I got a correct unit number (device name) and everything but I couldn't initialize the disk from there (init just froze) so I guess it is broken.

Clarete, I have also noticed USB devices not working now and then but coming back to live after a reboot.