- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: MSL 6000 "Medium is Write-Protected Error"
StoreEver Tape Storage
1745833
Members
4310
Online
108723
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
тАО05-22-2008 08:58 PM
тАО05-22-2008 08:58 PM
MSL 6000 "Medium is Write-Protected Error"
Hello...
I have a MSL 6000 Library configured as a Fibre interface SCSI device with two Ultrium drives. I am using DP 5.
When the backup starts, the medium (tape) is loaded from the slot to drive. However once the tape is in the drive, DP gives an error
CANNOT OPEN DEVICE (MEDIUM IS WRITE - PROTECTED)
The write-protect catch on the tape has been verified...it is in no-write-protect position.
Next the DP does head verification and says OK...
Then it says
CANNOT EJECT MEDIUM ([1117] THE REQUEST COULD NOT BE PERFORMED BECAUSE OF AN I/O ERROR)
then it says
CANNOT CLOSE DEVICE (DETAILS UNKNOWN)
CANNOT UNLOAD EXCHANGER MEDIUM (DETAILS UNKNOWN)
Any ideas/solutions...
Thanx
I have a MSL 6000 Library configured as a Fibre interface SCSI device with two Ultrium drives. I am using DP 5.
When the backup starts, the medium (tape) is loaded from the slot to drive. However once the tape is in the drive, DP gives an error
CANNOT OPEN DEVICE (MEDIUM IS WRITE - PROTECTED)
The write-protect catch on the tape has been verified...it is in no-write-protect position.
Next the DP does head verification and says OK...
Then it says
CANNOT EJECT MEDIUM ([1117] THE REQUEST COULD NOT BE PERFORMED BECAUSE OF AN I/O ERROR)
then it says
CANNOT CLOSE DEVICE (DETAILS UNKNOWN)
CANNOT UNLOAD EXCHANGER MEDIUM (DETAILS UNKNOWN)
Any ideas/solutions...
Thanx
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2008 10:26 PM
тАО05-22-2008 10:26 PM
Re: MSL 6000 "Medium is Write-Protected Error"
there may be several situation causing a tape to be reported as write protected:
- if you are trying to write a cartridge that is two generation less than the drive ( lto1 in a lto3)
- if the CM (cartridge Memory) is damamged
- if the cartridge or the tape is bad
the other messages are more related to the path communication rather than to the single cartridge.
I suggest you to use L&TT to troubleshoot the drive, the cartridges and the data path
- if you are trying to write a cartridge that is two generation less than the drive ( lto1 in a lto3)
- if the CM (cartridge Memory) is damamged
- if the cartridge or the tape is bad
the other messages are more related to the path communication rather than to the single cartridge.
I suggest you to use L&TT to troubleshoot the drive, the cartridges and the data path
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-23-2008 12:06 AM
тАО05-23-2008 12:06 AM
Re: MSL 6000 "Medium is Write-Protected Error"
The reason for the trouble could also be a bad drive. Use LTT to pull a support ticket - this will give more information.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-03-2008 11:43 AM
тАО06-03-2008 11:43 AM
Re: MSL 6000 "Medium is Write-Protected Error"
# perform devbra -dev on host where the drive/changer controller media agent is used or library is configured on.
compare the setup in dataprotector whether the setup is the same -> correct.
most likely error:
since there are 2 tape drives and one changer -> the tape devices mapping can change after a sever or library reboot. The server does "walk the bus" during boot up phase and discovers and claims the tape devices in different order than these are configured in DP.
DP 5.5 has the ability to update the device paths since it uses serial number to point to the correct device. DP 5.0 or 5.1 doesn't have this ability
alternatively for future take a ride on sanconf -list -host xxx
or upgrade to dp 5.5-6
compare the setup in dataprotector whether the setup is the same -> correct.
most likely error:
since there are 2 tape drives and one changer -> the tape devices mapping can change after a sever or library reboot. The server does "walk the bus" during boot up phase and discovers and claims the tape devices in different order than these are configured in DP.
DP 5.5 has the ability to update the device paths since it uses serial number to point to the correct device. DP 5.0 or 5.1 doesn't have this ability
alternatively for future take a ride on sanconf -list -host xxx
or upgrade to dp 5.5-6
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