- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- 1705 again
StoreEver Tape Storage
1754020
Members
7553
Online
108811
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
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
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
тАО06-23-2003 03:08 AM
тАО06-23-2003 03:08 AM
1705 again
Quick question, I reciently replaced a drive in a TL891 which is attached to my CL380. I worked flawlessly before, now I'm getting a 1705 locked scsi bus error. The error happens like this: I start with both nodes off. I spin up the attached storage in the cluster. I turn on the TL891. I have one node in maintenance mode and off. I start the other node (which is not in maintenance mode). When Windows (2003) comes up, my cluster service fails and the drives are not accessible. When I reboot the node I get a 1705 locked scsi bus error after post. The error refers to slot 4 port 1 which is the slot my 64bit differential card is located and the port the library is connected to. The IDs are setup correctly. Previous to the drive replacement this worked fine.
I'm guessing that the drive is terminated when it shouldn't be. It's a DLT7000 and based on the QRG it should be the right replacement drive. I checked quantums website and it shows that the drive is indeed terminated by the number on the second pins from the right.
My question is, should this drive be terminated? I'm thinking that the termination would be handled by the connectors within the library and at the cards. I would test my theory but I broke off the drive loading lever before I put it back in (doh!). I'll have a new lever Tuesday. I'm just looking for confirmation on the termination issue in advance...
Thanks!
Chris
I'm guessing that the drive is terminated when it shouldn't be. It's a DLT7000 and based on the QRG it should be the right replacement drive. I checked quantums website and it shows that the drive is indeed terminated by the number on the second pins from the right.
My question is, should this drive be terminated? I'm thinking that the termination would be handled by the connectors within the library and at the cards. I would test my theory but I broke off the drive loading lever before I put it back in (doh!). I'll have a new lever Tuesday. I'm just looking for confirmation on the termination issue in advance...
Thanks!
Chris
If it ain't broke, leave it alone.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2003 08:03 AM
тАО06-27-2003 08:03 AM
Re: 1705 again
Well, termination or no I get the same error. I'm thinking now that the problem is Windows Server 2003 which has it's own driver and doesn't appear to support clustering.
If it ain't broke, leave it alone.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-10-2003 10:53 AM
тАО07-10-2003 10:53 AM
Re: 1705 again
The problem is indeed Windows Server 2003. In order for this to work with the cluster connectivity kit the library and drive have to be disabled in one server.
If it ain't broke, leave it alone.
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