- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- The library mechanism is having difficulty communi...
StoreEver Tape Storage
1753309
Members
6650
Online
108792
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
тАО01-14-2002 06:24 PM
тАО01-14-2002 06:24 PM
The library mechanism is having difficulty communicating with the drive
Hi,
this is the second time i facing this problem. Everytime i need to restart the tape drive to solve the problem. when this problem occur the scsi bus will reset. Anybody know the cause? I'm using DLT autoloader with omniback II 3.5.
Thanks.
this is the second time i facing this problem. Everytime i need to restart the tape drive to solve the problem. when this problem occur the scsi bus will reset. Anybody know the cause? I'm using DLT autoloader with omniback II 3.5.
Thanks.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-14-2002 07:11 PM
тАО01-14-2002 07:11 PM
Re: The library mechanism is having difficulty communicating with the drive
Hi,
There are a few things I would like
to suggest to you. DLT drives and autoloaders
do not like receiving SCSI resets at all.
You need to switch off the EMS monitoring for
SCSI tapes on your server. I have attached
a document that should help with doing this
task. Second thing is have a look your firmware
level for your autoloader.
Also have a look at the OmniBack patches.
HTH
-Michael
There are a few things I would like
to suggest to you. DLT drives and autoloaders
do not like receiving SCSI resets at all.
You need to switch off the EMS monitoring for
SCSI tapes on your server. I have attached
a document that should help with doing this
task. Second thing is have a look your firmware
level for your autoloader.
Also have a look at the OmniBack patches.
HTH
-Michael
Anyone for a Mutiny ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-15-2002 09:08 AM
тАО01-15-2002 09:08 AM
Re: The library mechanism is having difficulty communicating with the drive
A few comments on EMS: First, EMS only needs to be disabled (or alternatively have polling disabled) IF the tape devices are in a SAN environment, where multiple hosts can access the tape drives (through the SAN). In this case, the easiest solution is turn off polling (by setting POLLING_INTERVAL to 0 in the dm_stape.cfg file) if the EMS version is September 2001 or newer (IPR0109).
Second, the instructions provided are outdated, and will actually cause an additional problem of logtool failing to decode SCSI logs. The step stating to rename dm_stape [mv /usr/sbin/stm/uut/bin/tools/monitor/dm_stape
/usr/sbin/stm/uut/bin/tools/monitor/dm_stape.orig] should NOT be done. This monitor is also used as a decoder for the stape driver.
Regarding the original problem, more information on the product, configuration, error logs, etc would be needed to give you a good diagnoses.
Second, the instructions provided are outdated, and will actually cause an additional problem of logtool failing to decode SCSI logs. The step stating to rename dm_stape [mv /usr/sbin/stm/uut/bin/tools/monitor/dm_stape
/usr/sbin/stm/uut/bin/tools/monitor/dm_stape.orig] should NOT be done. This monitor is also used as a decoder for the stape driver.
Regarding the original problem, more information on the product, configuration, error logs, etc would be needed to give you a good diagnoses.
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