<?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 vgimport in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510687#M625142</link>
    <description>A system has had its disk array moved from one machine to another but the same os loaded&lt;BR /&gt;&lt;BR /&gt;The hardware paths for the disks have changed so /etc/lvmtab still contains the old hardware paths. ie /dev/dsk/c6t0d0, /dev/dsk/c6t0d1, /dev/dsk/c6t0d1&lt;BR /&gt;&lt;BR /&gt;vgexport -m /tmp/vg01.map /dev/vg01 was run &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;How when they have tried to do an import by running&lt;BR /&gt;mkdir /dev/vg01&lt;BR /&gt;mknod /dev/vg01/group c 64 0x010000&lt;BR /&gt;&lt;BR /&gt;vgimport -m /tmp/vg01.map /dev/vg01       &lt;BR /&gt;/dev/dsk/c8t0d0 /dev/dsk/c8t0d1 /dev/dsk/c8t0d2&lt;BR /&gt;&lt;BR /&gt;is being run to import the disks with the new path the following error occurs&lt;BR /&gt;&lt;BR /&gt;vgimport: Physical volume "/dev/dsk/c8t0d0" is not a block special file.&lt;BR /&gt;vgimport: Physical volume "/dev/dsk/c8t0d1" is not a block special file.&lt;BR /&gt;vgimport: Physical volume "/dev/dsk/c8t1d2" is not a block special file.</description>
    <pubDate>Wed, 23 Mar 2005 14:09:10 GMT</pubDate>
    <dc:creator>Darren Murray_1</dc:creator>
    <dc:date>2005-03-23T14:09:10Z</dc:date>
    <item>
      <title>vgimport</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510687#M625142</link>
      <description>A system has had its disk array moved from one machine to another but the same os loaded&lt;BR /&gt;&lt;BR /&gt;The hardware paths for the disks have changed so /etc/lvmtab still contains the old hardware paths. ie /dev/dsk/c6t0d0, /dev/dsk/c6t0d1, /dev/dsk/c6t0d1&lt;BR /&gt;&lt;BR /&gt;vgexport -m /tmp/vg01.map /dev/vg01 was run &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;How when they have tried to do an import by running&lt;BR /&gt;mkdir /dev/vg01&lt;BR /&gt;mknod /dev/vg01/group c 64 0x010000&lt;BR /&gt;&lt;BR /&gt;vgimport -m /tmp/vg01.map /dev/vg01       &lt;BR /&gt;/dev/dsk/c8t0d0 /dev/dsk/c8t0d1 /dev/dsk/c8t0d2&lt;BR /&gt;&lt;BR /&gt;is being run to import the disks with the new path the following error occurs&lt;BR /&gt;&lt;BR /&gt;vgimport: Physical volume "/dev/dsk/c8t0d0" is not a block special file.&lt;BR /&gt;vgimport: Physical volume "/dev/dsk/c8t0d1" is not a block special file.&lt;BR /&gt;vgimport: Physical volume "/dev/dsk/c8t1d2" is not a block special file.</description>
      <pubDate>Wed, 23 Mar 2005 14:09:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510687#M625142</guid>
      <dc:creator>Darren Murray_1</dc:creator>
      <dc:date>2005-03-23T14:09:10Z</dc:date>
    </item>
    <item>
      <title>Re: vgimport</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510688#M625143</link>
      <description>You're going to need to run vgscan to get more out of this... see man vgscan</description>
      <pubDate>Wed, 23 Mar 2005 14:27:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510688#M625143</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2005-03-23T14:27:27Z</dc:date>
    </item>
    <item>
      <title>Re: vgimport</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510689#M625144</link>
      <description>Check your /dev/dsk folder, are the devices actually listed there?  (c8t0d0, etc) You would get that error if the devices didn't exist.&lt;BR /&gt;&lt;BR /&gt;It's probably too late but if you had done a vgexport on the old machine with the -s option, finding the new disk would be much easier.&lt;BR /&gt;&lt;BR /&gt;Run ioscan -fnC disk to see if you can see the disk.  If not, try an insf -e &lt;BR /&gt;&lt;BR /&gt;The problem is the mapping may not end up being as clean as c6t0d0 --&amp;gt; c8t0d0 on the new machine.&lt;BR /&gt;&lt;BR /&gt;Jim&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Mar 2005 14:27:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510689#M625144</guid>
      <dc:creator>Jim Mallett</dc:creator>
      <dc:date>2005-03-23T14:27:44Z</dc:date>
    </item>
    <item>
      <title>Re: vgimport</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510690#M625145</link>
      <description>Oh, and after vgscan'ing it back in , you're going to need to run vgchange.</description>
      <pubDate>Wed, 23 Mar 2005 14:28:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510690#M625145</guid>
      <dc:creator>TwoProc</dc:creator>
      <dc:date>2005-03-23T14:28:21Z</dc:date>
    </item>
    <item>
      <title>Re: vgimport</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510691#M625146</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;You can look at the following threads&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=92067" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=92067&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=748366" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=748366&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Rgds&lt;BR /&gt;&lt;BR /&gt;HGN</description>
      <pubDate>Wed, 23 Mar 2005 14:29:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510691#M625146</guid>
      <dc:creator>HGN</dc:creator>
      <dc:date>2005-03-23T14:29:38Z</dc:date>
    </item>
    <item>
      <title>Re: vgimport</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510692#M625147</link>
      <description>&lt;BR /&gt;ioscan -fn -C disk&lt;BR /&gt;&lt;BR /&gt;shows what?&lt;BR /&gt;&lt;BR /&gt;live free or die&lt;BR /&gt;harry d brown jr</description>
      <pubDate>Wed, 23 Mar 2005 14:30:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510692#M625147</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2005-03-23T14:30:06Z</dc:date>
    </item>
    <item>
      <title>Re: vgimport</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510693#M625148</link>
      <description>First make absolutely certain that your new /dev/vg01/group device node has a unique minor device number. 0x010000 might already be in use by another VG and chaos will result. You probably need to do a new ioscan -fn and then an insf so that the disk device nodes get created. What does ls -l /dev/dsk/c8* display?&lt;BR /&gt;</description>
      <pubDate>Wed, 23 Mar 2005 14:31:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/vgimport/m-p/3510693#M625148</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-03-23T14:31:42Z</dc:date>
    </item>
  </channel>
</rss>

