- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: Tape drive access problem on MSL5052S2
StoreEver Tape Storage
1753512
Members
5414
Online
108795
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
Go to solution
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-04-2007 06:24 AM
тАО01-04-2007 06:24 AM
Any pointers to possible problem I'm having with a particular tape drive on MSL5052S2?
Thanks in advance,
Matt
Report Messages Other Than Normal [Common]:
[Critical]
From: "ZEMBO_DRIVE_3" Time: 1/3/2007 4:58:49 PM
[90:120]
_$2$MGA5: Cannot get device file status ([6] no such device or address) => aborting
[Critical]
From: "ZEMBO_DRIVE_3" Time: 1/3/2007 4:59:44 PM
[90:120]
_$2$MGA5: Cannot get device file status ([6] no such device or address) => aborting
[Major]
From: "ZEMBO_DRIVE_3" Time: 1/3/2007 4:59:45 PM
[90:180] Cannot rewind medium. (Details unknown.)
Thanks in advance,
Matt
Report Messages Other Than Normal [Common]:
[Critical]
From: "ZEMBO_DRIVE_3" Time: 1/3/2007 4:58:49 PM
[90:120]
_$2$MGA5: Cannot get device file status ([6] no such device or address) => aborting
[Critical]
From: "ZEMBO_DRIVE_3" Time: 1/3/2007 4:59:44 PM
[90:120]
_$2$MGA5: Cannot get device file status ([6] no such device or address) => aborting
[Major]
From: "ZEMBO_DRIVE_3" Time: 1/3/2007 4:59:45 PM
[90:180] Cannot rewind medium. (Details unknown.)
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2007 08:15 PM
тАО01-04-2007 08:15 PM
Solution
From the display it looks like you're running a Dataprotector media agent to an OVMS SAN attached Library. Needs a bit more info..........any errorlogs, SEA output ???
Is it a solid, or intermittant problem ??
Have there been any changes to the SAN configuration ??
Does the device show up OK on VMS ($show dev full, or SYSMAN)
Does a VMS backup run OK locally ??
Is it a solid, or intermittant problem ??
Have there been any changes to the SAN configuration ??
Does the device show up OK on VMS ($show dev full, or SYSMAN)
Does a VMS backup run OK locally ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-04-2007 11:56 PM
тАО01-04-2007 11:56 PM
Re: Tape drive access problem on MSL5052S2
Thanks Rich,
It has now become obvious that this tape drive was replaced recently. The sys$devices.dat file in sys$system no longer uses $2$MGA5: but $2$MGA0:. I'm not too familiar with DP so I will notify the folks monitoring our backups the change in the device name.
Regards,
Matt
It has now become obvious that this tape drive was replaced recently. The sys$devices.dat file in sys$system no longer uses $2$MGA5: but $2$MGA0:. I'm not too familiar with DP so I will notify the folks monitoring our backups the change in the device name.
Regards,
Matt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2007 01:34 PM
тАО12-04-2007 01:34 PM
Re: Tape drive access problem on MSL5052S2
Forgot to close thread.
-Matt
-Matt
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