Home > Cannot Write > Cannot Write To Device Medium Error Data Protector

Cannot Write To Device Medium Error Data Protector

Use the following syntax when using the Data Protector ]]>uma utility to manage the GRAU and STK library drives: uma -pol POLNUMBER -ioctl LIBRARYNAME -type MEDIATYPE where POLNUMBER is 8 thanks 0 Kudos Reply All Forum Topics Previous Topic Next Topic 3 REPLIES Scott McIntosh_2 Honored Contributor [Founder] Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email Your help is greatly appreciated. I've adjusted buffers and block sizes on the drives but this continues to occur. http://homeshareware.com/cannot-write/cannot-write-to-device-medium-error.html

Typically, the problem occurs when the SCSI device was accessed by more than one Media Agent at the same time or when the length of the transferred data defined by the Try running an OS-provided command, such as tar, to verify that the system and the device are communicating. Likely, the drive reported back sense key 3, medium error.What were the rest of the session messages?What debug.log entries are there on the tape drive host?What OS is this tape drive Example mchange -pool "Default DLT" -newtype "SuperDLT" The command changes media types for all media, drives, and libraries that use the specified media pool.

And all the problem layers are below the application.Thanks,ScottHP Support 0 Kudos Reply The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. Abort code 2.[Major] From: OB2BAR_Second Storage [email protected] "Microsoft Exchange Server (Microsoft Information Store)" Time: 8/04/2011 2:55:51 AM Received ABORT request from BSM (ERR: Error reading media.)[Major] From: OB2BAR_Mailbox [email protected] "Microsoft Exchange If I only back up a small amount of data (means a short-time job), then it will succeed.

Took me about 3 weeks cause the error was badly reproducable.. Install the mmd patch on the Cell Manager. Anyone have any suggestions 217553.rtf ‏1 KB 0 Kudos Reply All Forum Topics Previous Topic Next Topic 6 REPLIES Leif Halvarsson_2 Honored Contributor Options Mark as New Bookmark Subscribe Subscribe to Media used with DDS drives must comply with the Media Recognition System.

Go to Solution. 0 Kudos Reply All Forum Topics Previous Topic Next Topic 3 REPLIES Prashanth Waugh Esteemed Contributor [Founder] Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight The library configuration remains only partially created. Solved! You replaced the physical device without updating the corresponding logical device (reloading the new serial number).

For example, you cannot use 9940 devices that were configured as 9840 devices, 3592 devices that were configured as 3590 devices, or SuperDLT devices that were configured as DLT devices. Restart the system. You can only move media from the CAP to a slot and then to a drive using the devices robotics. When I run the backup to a stand alone tape drive, it works, but in the library, I get these [email protected] I said, I AM WORKING ON IT! 0 Kudos Reply

Restart OS/2 and when OS/2 is ready, the AMU log will display that the robotics is not ready. https://community.hpe.com/t5/Data-Protector-Practitioners/Cannot-write-to-device-5-I-O-error/td-p/5089720 Ensure that no other application is using this device. Check SNMP service configuration.[dccatalog_parseAndStore] Invalid catRec or NTcatRec = 0 I have cleaned the drive, updated firmware and used new tapes in testing but still get the same error even if Showing results for  Search instead for  Do you mean  Menu Categories Solutions IT Transformation Internet of Things Topics Big Data Cloud Security Infrastructure Strategy and Technology Products Cloud Integrated Systems Networking

If you have more than 1 drive then u can assign the diffrent drive by modifying the backup specfication. weblink Showing results for  Search instead for  Do you mean  Menu Categories Solutions IT Transformation Internet of Things Topics Big Data Cloud Security Infrastructure Strategy and Technology Products Cloud Integrated Systems Networking General device and media problems Cannot access exchanger control device on Windows SCSI device remains locked and session fails Device open problem Using unsupported SCSI HBAs/FC HBAs on Windows Library reconfiguration Showing results for  Search instead for  Do you mean  Menu Categories Solutions IT Transformation Internet of Things Topics Big Data Cloud Security Infrastructure Strategy and Technology Products Cloud Integrated Systems Networking

Board index The team • Delete all board cookies • All times are UTC Powered by phpBB Forum Software © phpBB Group

Troubleshooting Devices and Media Backup devices are subject Device open problem Problem Action When trying to use a DDS device, the following error displays: Cannot open device (not owner) Check whether you are using a medium that is incompatible Problems involving device SCSI addresses are explained in detail in Appendix B of the HP Data Protector Installation and Licensing Guide. navigate here To enable it, set the global option Ob2TapeStatistics to 1.

Try it again; same failure? You cannot see any drives Problem Action You cannot see any drives. Related task Library reconfiguration failure Problem Action Configuration errors are reported during modification of an existing library configuration using the sanconf command after the device list file has been altered.

As you can see, the picture is vastly more complicated than "90:51".

Click the Control tab and enable the Automatically discover changed SCSI address option. Before each medium is ejected from a drive, Data Protector uses the SCSI log sense command to query medium read and write statistical information. Add a client called OMNIBACK containing the IP address of the PC/robot. This can happen in the following cases: You misconfigured the device (for example, using the omniupload command, or if you configured an incorrect device file).

The following message is displayed: Cannot open device If there is a Media Agent failure, the reserved device cannot be released again. Data Protector may fail to unlock the SCSI drive or robotic control and the subsequent session cannot use it. By using this site, you accept the Terms of Use and Rules of Participation. End of content United StatesHewlett Packard Enterprise International CorporateCorporateAccessibilityCareersContact UsCorporate ResponsibilityEventsHewlett Packard LabsInvestor RelationsLeadershipNewsroomSitemapPartnersPartnersFind a PartnerPartner http://homeshareware.com/cannot-write/cannot-write-to-device-5-i-o-error.html If you add, remove, or modify the library later and configuration with the sanconf command fails, you can repeat the above procedure to restore the successful configuration.

From this point on, all objects on this medium will have logging switched to "No Log".[Normal] From: [email protected] "HP LTO-2 Drive" Time: 8/04/2011 2:55:18 AM Tape0:0:5:0C Medium header verification completed, 0 Various media problems Problem Action Various media problems. that is probably why it is showing zero. The media is new and I know nothing is wrong with it.

You did reselect the new scsi address in the device configuration in DP, right? Probably better to ask the question new than resurrect the dead.Thanks,Scott 0 Kudos Reply The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise.

Back to Top