<?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: MOUNT-F-INVALIDSCB in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/mount-f-invalidscb/m-p/5140017#M91827</link>
    <description>Good to know for next time. &lt;BR /&gt;I looked through the docs and didn't find this note - somewhere in realease-notes, perhaps?</description>
    <pubDate>Sun, 09 Nov 2008 15:33:19 GMT</pubDate>
    <dc:creator>Willem Grooters</dc:creator>
    <dc:date>2008-11-09T15:33:19Z</dc:date>
    <item>
      <title>MOUNT-F-INVALIDSCB</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-f-invalidscb/m-p/5140014#M91824</link>
      <description>In preparation of installing patches, I did an image backup of my system disk (while logged in). After I lost connection, the process continued executing the backup, and it disappeared when done (I checked before reboot).&lt;BR /&gt;&lt;BR /&gt;Now I want to retrieve some files from that backup disk but I'm not able to MOUNT it:&lt;BR /&gt;&lt;BR /&gt;$ mount/over=id $116$dka103&lt;BR /&gt;%MOUNT-F-INVALIDSCB, I/O error with storage control block on relative volume 1,&lt;BR /&gt;location 6&lt;BR /&gt;&lt;BR /&gt;The disk can be mounted /FOREIGN; the HSZ-50 controller doesn't tell of any error.&lt;BR /&gt;&lt;BR /&gt;What does the error mean and how can I get to this disk's contents?&lt;BR /&gt;&lt;BR /&gt;(Reboot is not a real problem at the moment)&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 08 Nov 2008 18:56:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-f-invalidscb/m-p/5140014#M91824</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2008-11-08T18:56:54Z</dc:date>
    </item>
    <item>
      <title>Re: MOUNT-F-INVALIDSCB</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-f-invalidscb/m-p/5140015#M91825</link>
      <description>VMS 8.3, patched up-to-date (except last one). HSZ50 firmware V57Z (00)&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 08 Nov 2008 18:59:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-f-invalidscb/m-p/5140015#M91825</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2008-11-08T18:59:29Z</dc:date>
    </item>
    <item>
      <title>Re: MOUNT-F-INVALIDSCB</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-f-invalidscb/m-p/5140016#M91826</link>
      <description>The BACKUP didn't complete, and that's the expected error for that case.&lt;BR /&gt;&lt;BR /&gt;"A MOUNT command on a disk that was the target of a failed BACKUP restore operation does not fail, as it should. With the change included in this kit, MOUNT will now fail with a %MOUNT-F-INVALIDSCB error."&lt;BR /&gt;&lt;BR /&gt;An older OpenVMS release might be willing to mount this disk, but I don't know of a way to get at this disk (other than with brute-force techniques) with a more recent release. &lt;BR /&gt;&lt;BR /&gt;A trip through the source listings should turn up a way to patch the disk to get past the validation check to recover the disk, if this is important enough.  The DISKBLOCK tool might be useful here, and Jur's most excellent LD can potentially be used to trace I/O activity:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://64.223.189.234/node/1127" target="_blank"&gt;http://64.223.189.234/node/1127&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 08 Nov 2008 20:03:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-f-invalidscb/m-p/5140016#M91826</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2008-11-08T20:03:50Z</dc:date>
    </item>
    <item>
      <title>Re: MOUNT-F-INVALIDSCB</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/mount-f-invalidscb/m-p/5140017#M91827</link>
      <description>Good to know for next time. &lt;BR /&gt;I looked through the docs and didn't find this note - somewhere in realease-notes, perhaps?</description>
      <pubDate>Sun, 09 Nov 2008 15:33:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/mount-f-invalidscb/m-p/5140017#M91827</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2008-11-09T15:33:19Z</dc:date>
    </item>
  </channel>
</rss>

