- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Tape alert 16
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
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
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
03-30-2005 11:01 PM
03-30-2005 11:01 PM
Tape alert 16
At this time I am getting an error when I try to read, write or scan the tape for the first time after changing.
==============================================
[Normal] From: MMA@webdmz1.friatec.de "LTO1-webdmz1" Time: 31.03.2005 13:36:54
STARTING Media Agent "LTO1-webdmz1"
[Critical] From: MMA@webdmz1.friatec.de "LTO1-webdmz1" Time: 31.03.2005 13:37:03
/dev/nst0
Tape Alert [16]: The operation has failed because the tape cartridge was manually ejected while the tape drive was actively writing or reading.
[Normal] From: MSM@hercule.friatec.de "LTO1-webdmz1" Time: 31.03.2005 13:37:03
Data Protector medium "webdmz1_März" found.
[Normal] From: MMA@webdmz1.friatec.de "LTO1-webdmz1" Time: 31.03.2005 13:37:05
COMPLETED Media Agent "LTO1-webdmz1
The second scan I can make without alerts.
=============================================
[Normal] From: MMA@webdmz1.friatec.de "LTO1-webdmz1" Time: 31.03.2005 13:40:40
STARTING Media Agent "LTO1-webdmz1"
[Normal] From: MSM@hercule.friatec.de "LTO1-webdmz1" Time: 31.03.2005 13:40:54
Data Protector medium "webdmz1_März" found.
[Normal] From: MMA@webdmz1.friatec.de "LTO1-webdmz1" Time: 31.03.2005 13:41:04
COMPLETED Media Agent "LTO1-webdmz1"
==============================================
And after a reboot, the system works well for the next few days again. Also the tape can be unload with only a short push at the unload button.
Any ideas?
Thanks!
Herbert Kinderma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2005 02:10 AM
04-01-2005 02:10 AM
Re: Tape alert 16
The message really means that a force eject was issued and the decoding or eject during read/write isn't quite correct.
You need to try a normal eject and wait. It is very unusual for these drives to fail to eject normally. The most common reason for an eject failure is that Windows Removable Storage Manager is running and has prevented eject. In rare cases the drive is in the process of an operation and will hold off before processing the eject.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2005 11:56 PM
04-01-2005 11:56 PM
Re: Tape alert 16
Backups and firewalls don't really mix all that well. If this is a backup through a firewall and no data is sent for a long enough period (probably because the backup process is walking the filesystem and hasn't found anything that's changed within a set period) then the firewall may just note that there's been no activity and shut down that connection, leaving things hanging on each side. You say this happens every few days: does this coincide with any particular level of backup, by any chance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2005 06:38 PM
04-03-2005 06:38 PM
Re: Tape alert 16
The Windows Removable Storage Manager is also running on at the SuSE Linux Enterprise Server 8 (SLES8)?
I also think that one process is using the drive and hold it, but which one is it and why it is only happen after few days?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2005 06:50 PM
04-03-2005 06:50 PM
Re: Tape alert 16
It is right, the system is placed in the DMZ. But the backup doesnâ t go through the firewall, because we are using an internal LTO Drive. Only the communication with the Cell Manager goes through.
The backup type is always the same. It is a complete backup every da
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2005 05:39 AM
04-04-2005 05:39 AM
Re: Tape alert 16
Some backup applications will always prevent media removal when using a device and you must use an interface provided by the application to remove the media. Is your backup software running when you issue the unload?
You can use L&TT (HP StorageWorks Library and Tape Tools) to pull a support ticket right after you attempt a normal unload then a forced unload. If you zip and attach that ticket there should be additional information that will help explain why. I expect that it will report the drive has been locked by an application.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2005 01:11 AM
04-05-2005 01:11 AM
Re: Tape alert 16
fuser probably exists in Linux, and doing fuser on the device file will tell you which process is using it. You *may* be able to get similar info using handle.exe from www.sysinternals.com (not sure about tape handles though). Figure out which process is using the tape drive and, if it's safe, kill off that process and see if your drive is still hung up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2005 02:42 AM
04-05-2005 02:42 AM
Re: Tape alert 16
Killing off a process using a drive will often leave the drive locked if that process has issued a SCSI prevent media removal command. If you are going to use that method to test make certain that you do not use a kill -9. Some processes will clean up if you use kill -3. If the drive is unlocked if after you kill a process you have found the problem. If the drive is still locked the problem could still be the process you just killed but it didn't clean up.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2005 11:16 PM
04-05-2005 11:16 PM
Re: Tape alert 16
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2005 03:40 AM
04-06-2005 03:40 AM
Re: Tape alert 16
I would recommend that you talk to your backup application provider and ask about drive reservations.