- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- DEC DLT4000 on home system
StoreEver Tape Storage
1753797
Members
7377
Online
108805
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2002 12:25 PM
04-18-2002 12:25 PM
DEC DLT4000 on home system
An inveterate hacker
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2002 02:23 PM
04-18-2002 02:23 PM
Re: DEC DLT4000 on home system
> This drive is actually a Dec DLT TZ88 upon which I have run the utility from the compaq to make it a DLT4000.
> Component Data:
Physical Device Path....: 28.4.0
Inquiry Vendor ID.......: DEC
Inquiry Product ID......: DLT4000
Firmware Version........: V052
For the DLT4000 drives supported on HP systems, we normally expect to see 'Quantum' as the Vendor ID. I'm not sure what would happen when the driver sees 'DEC'.
Also when we integrated the DLT4000, I think V60 was about the first firmware version we supported. Currently it is V150 for the standalone, and V126 or V130 for two HP library flavors of the drive.
Also, Quantum has many different variants of firmware for the DLT drives. Each one is tailored to the specific OEM/OS. The variants integrated specifically on HP-UX are OEM1, OML3, and OMX1 (these are reported in the personality/subpersonality bytes of the inquiry data).
The EMS event basically says the drive was sent a command with a parameter value in the command descriptor block, which it does not support. Unfortunately it does not show the command which was attempted.
I think the probable cause listed is probably correct:
The error most likely indicates that the device is not fully supported by
the current driver.
> Component Data:
Physical Device Path....: 28.4.0
Inquiry Vendor ID.......: DEC
Inquiry Product ID......: DLT4000
Firmware Version........: V052
For the DLT4000 drives supported on HP systems, we normally expect to see 'Quantum' as the Vendor ID. I'm not sure what would happen when the driver sees 'DEC'.
Also when we integrated the DLT4000, I think V60 was about the first firmware version we supported. Currently it is V150 for the standalone, and V126 or V130 for two HP library flavors of the drive.
Also, Quantum has many different variants of firmware for the DLT drives. Each one is tailored to the specific OEM/OS. The variants integrated specifically on HP-UX are OEM1, OML3, and OMX1 (these are reported in the personality/subpersonality bytes of the inquiry data).
The EMS event basically says the drive was sent a command with a parameter value in the command descriptor block, which it does not support. Unfortunately it does not show the command which was attempted.
I think the probable cause listed is probably correct:
The error most likely indicates that the device is not fully supported by
the current driver.
The journey IS the reward.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP