- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: Surestore 2/20 new drive problems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО06-23-2005 02:40 AM
тАО06-23-2005 02:40 AM
Surestore 2/20 new drive problems
I removed the drive module, and removed the dead 230 and replaced it with the new 460 and reassembled. But now the library says it is only "partly" available, due to a firmware mismatch. And in Library & Tape Tools, the new drive is "seen" as a seperate drive, not as part of the library, and is complaining that it can't find the original drive.
Library is at Rev. 1720
Detailed Drive Information
Drive 1
Type: Ultrium 1-SCSI
Serial Number: IE71G01459
Firmware Revision: E3BR
Status: Empty
Activity: Idle
Cleaning Status: Ok
SCSI ID: 1
Drive 2
Type: Ultrium 1-SCSI
Serial Number:
Firmware Revision:
Status: Empty
Activity: Idle
Cleaning Status: Ok
SCSI ID: 2
Notice how Drive 2 is reported as LTO-1 when it is an LTO-2 drive.
Does anyone have any ideas what I should try next?
I tried updating the firmware on the new drive in Tape Tools, but it complains about the "wrong personality". I'm beginning to think I have the wrong sort of drive...
Kind regards
Anthony
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-24-2005 02:02 AM
тАО06-24-2005 02:02 AM
Re: Surestore 2/20 new drive problems
I don't know where you get this info, but I think that only LTO-1 is supported in Surestore 2/20
http://h20000.www2.hp.com/bc/docs/support/SupportManual/lpg28861/lpg28861.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2005 07:46 AM
тАО07-06-2005 07:46 AM
Re: Surestore 2/20 new drive problems
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2005 12:30 AM
тАО07-07-2005 12:30 AM
Re: Surestore 2/20 new drive problems
Please refer to following thread with similar issue:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=222363
Regards
Mahesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-07-2005 07:02 PM
тАО07-07-2005 07:02 PM
Re: Surestore 2/20 new drive problems
-the firware upgrade is showing "wrong personality" because you took a generic drive and put it in a canister for a library, the firmware is not compatible as the drive for the library implement communication in the internal bus with the lib controller. Changing the personality is not a field option.
-the Galactica never support LT02, and this may cause problem in the scsi chain (cable/terminator) and the controller will not be able to recognize the LTO2 as LTO2