<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Tape Drive in Mount Verification in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537005#M68199</link>
    <description>is the tape drive allocated to a process that does not exist?</description>
    <pubDate>Wed, 04 May 2005 04:20:34 GMT</pubDate>
    <dc:creator>Ian Miller.</dc:creator>
    <dc:date>2005-05-04T04:20:34Z</dc:date>
    <item>
      <title>Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537002#M68196</link>
      <description>VMS 7.2-1 using a TL891 library.&lt;BR /&gt;&lt;BR /&gt;I've run into the annoying situation of a tape drive going into mount verification, the allocating process is dead, and I can't get mount verify to cancel.  I've tried the suggestions in the System Management manual to no avail.  These were dismount/abort, waiting for TAPE_MVTIMEOUT and using IPC from the console to cancel the verification. &lt;BR /&gt;&lt;BR /&gt;I've resigned myself to rebooting the system now, but I was wondering if there is really no other way around this?  Seems like this has been a problem since 1985, at least.  &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 03 May 2005 16:17:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537002#M68196</guid>
      <dc:creator>Michael Hogarty</dc:creator>
      <dc:date>2005-05-03T16:17:52Z</dc:date>
    </item>
    <item>
      <title>Re: Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537003#M68197</link>
      <description>I think the last resort before you reboot is to power off/on the tape library.&lt;BR /&gt;Phil</description>
      <pubDate>Wed, 04 May 2005 01:01:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537003#M68197</guid>
      <dc:creator>Phil.Howell</dc:creator>
      <dc:date>2005-05-04T01:01:46Z</dc:date>
    </item>
    <item>
      <title>Re: Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537004#M68198</link>
      <description>Micheal,&lt;BR /&gt;did you try follow before reboot?&lt;BR /&gt;$ DISM/OVER=CHECK &lt;TAPE&gt;&lt;BR /&gt; &lt;BR /&gt;Antonio Vigliotti&lt;BR /&gt;&lt;/TAPE&gt;</description>
      <pubDate>Wed, 04 May 2005 01:46:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537004#M68198</guid>
      <dc:creator>Antoniov.</dc:creator>
      <dc:date>2005-05-04T01:46:51Z</dc:date>
    </item>
    <item>
      <title>Re: Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537005#M68199</link>
      <description>is the tape drive allocated to a process that does not exist?</description>
      <pubDate>Wed, 04 May 2005 04:20:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537005#M68199</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-05-04T04:20:34Z</dc:date>
    </item>
    <item>
      <title>Re: Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537006#M68200</link>
      <description>I did not try DISM /OVER=CHECKS (thought that was only relevant to disks), but when I tried with /ABORT it told me device not mounted, so I wasn't very hopeful.&lt;BR /&gt;&lt;BR /&gt;I also did not power down the library; maybe worth a try next time.&lt;BR /&gt;&lt;BR /&gt;Ian, yes, the tape drive is allocated to a process that does not exist. &lt;BR /&gt;&lt;BR /&gt;As an update, what I am doing is restoring a disk that was trashed somehow by a faulty hsz50.  I was able to get this restore going last night.  This morning I arrive to see the red fault light illuminated on the library, and the message displayed is "DLT timeout, press enter to continue or reboot to clear".  I checked my restore job, and it's still going.  Very strange, but my experience with libs has been that strange = normal.&lt;BR /&gt;&lt;BR /&gt;Thanks for the help.</description>
      <pubDate>Wed, 04 May 2005 09:02:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537006#M68200</guid>
      <dc:creator>Michael Hogarty</dc:creator>
      <dc:date>2005-05-04T09:02:40Z</dc:date>
    </item>
    <item>
      <title>Re: Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537007#M68201</link>
      <description>I won't make friends by writing this ;-) , but tape handling has always been troublesome - welcome to the club!&lt;BR /&gt;&lt;BR /&gt;It is sometimes possible to work around this by giving the tape drive a new SCSI ID and then:&lt;BR /&gt;&lt;BR /&gt;$ run sys$system:sysman&lt;BR /&gt;SYSMAN&amp;gt; IO AUTOCONFIGURE&lt;BR /&gt;&lt;BR /&gt;to create a new device entry that can be used until it is convenient to reboot the system and get rid of the inconsistent system state.</description>
      <pubDate>Wed, 04 May 2005 09:15:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537007#M68201</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-05-04T09:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537008#M68202</link>
      <description>I hear ya Uwe.&lt;BR /&gt;&lt;BR /&gt;Thanks for the replies all.</description>
      <pubDate>Thu, 05 May 2005 13:42:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537008#M68202</guid>
      <dc:creator>Michael Hogarty</dc:creator>
      <dc:date>2005-05-05T13:42:51Z</dc:date>
    </item>
    <item>
      <title>Re: Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537009#M68203</link>
      <description>Michael,&lt;BR /&gt;&lt;BR /&gt;the underlying problem in OpenVMS has been finally fixed in patches VMS731_MOUNT96-V0100 and VMS732_MOUNT96-V0100 (released in AUG-2004)&lt;BR /&gt;&lt;BR /&gt;See my reply to the following thread&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=738204" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=738204&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Sat, 07 May 2005 13:34:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537009#M68203</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-05-07T13:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537010#M68204</link>
      <description>Unfourtunally the patches mentioned do not apply to the unsupported version of VMS that you are currently running (V7.2-1)&lt;BR /&gt;</description>
      <pubDate>Sat, 07 May 2005 15:00:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537010#M68204</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2005-05-07T15:00:41Z</dc:date>
    </item>
    <item>
      <title>Re: Tape Drive in Mount Verification</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537011#M68205</link>
      <description>Ian,&lt;BR /&gt;&lt;BR /&gt;sure, that's the price you'll have to pay for using older and now unsupported versions of OpenVMS.&lt;BR /&gt;&lt;BR /&gt;I just wanted to provide the information, that this longstanding problem has now been solved. Maybe an incentive for considering an upgrade to a current version ?!&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Mon, 09 May 2005 01:45:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tape-drive-in-mount-verification/m-p/3537011#M68205</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-05-09T01:45:24Z</dc:date>
    </item>
  </channel>
</rss>

