<?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: The specified path does not correspond to physical volume in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275045#M548992</link>
    <description>Hi Jose&lt;BR /&gt;&lt;BR /&gt;Can you please show me how to update the settings in SAN zone with new fibercard?&lt;BR /&gt;&lt;BR /&gt;Regard&lt;BR /&gt;Tien</description>
    <pubDate>Fri, 25 Feb 2011 11:44:25 GMT</pubDate>
    <dc:creator>Joakim Rudén</dc:creator>
    <dc:date>2011-02-25T11:44:25Z</dc:date>
    <item>
      <title>The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275039#M548986</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We're using HP-UX 11.23. Efter we changed a fibercard which was not working all paths are recognized with ioscan but we 're having problems updating the vg'swe got error when we run vgdisplay&lt;BR /&gt;vgdisplay -v /dev/vgnetapp_tnpt&lt;BR /&gt;vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c31t1d2":&lt;BR /&gt;The specified path does not correspond to physical volume attached to&lt;BR /&gt;this volume group&lt;BR /&gt; &lt;BR /&gt;After that , we ran the following command:&lt;BR /&gt;$cp /etc/lvmtbab /etc/lvmtab.old &lt;BR /&gt;$ vgscan -av&lt;BR /&gt;&lt;BR /&gt;Physical Volume "/dev/dsk/c0t0d0" contains no LVM information&lt;BR /&gt;Physical Volume "/dev/dsk/c21t2d0" is not part of a Volume Group&lt;BR /&gt;Physical Volume "/dev/dsk/c21t2d4" is not part of a Volume Group&lt;BR /&gt;Physical Volume "/dev/dsk/c29t2d0" is not part of a Volume Group&lt;BR /&gt;Physical Volume "/dev/dsk/c29t2d4" is not part of a Volume Group&lt;BR /&gt;&lt;BR /&gt;$vgchange -a y&lt;BR /&gt;&lt;BR /&gt;Volume group "/dev/vg00" has been successfully changed.&lt;BR /&gt;vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c31t0d3":&lt;BR /&gt;The path of the physical volume refers to a device that does not&lt;BR /&gt;exist, or is not configured into the kernel.&lt;BR /&gt;vgchange: The path of the physical volume refers to a device that does not&lt;BR /&gt;exist, or is not configured into the kernel.&lt;BR /&gt;&lt;BR /&gt;$lvlnboot -R&lt;BR /&gt;&lt;BR /&gt;lvlnboot: Warning: couldn't query physical volume "/dev/dsk/c31t0d3":&lt;BR /&gt;The specified path does not correspond to physical volume attached to&lt;BR /&gt;this volume group&lt;BR /&gt;vgcfgbackup: /etc/lvmtab is out of date with the running kernel:Kernel indicates 4 disks for "/dev/vgnetapp_erptest"; /etc/lvmtab has 8 disks.&lt;BR /&gt;Cannot proceed with backup.&lt;BR /&gt;&lt;BR /&gt;Sorry if this sounds confusing.&lt;BR /&gt;Please help&lt;BR /&gt;Regard&lt;BR /&gt;Tien</description>
      <pubDate>Fri, 25 Feb 2011 09:15:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275039#M548986</guid>
      <dc:creator>Joakim Rudén</dc:creator>
      <dc:date>2011-02-25T09:15:11Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275040#M548987</link>
      <description>for correcting issue  vg00&lt;BR /&gt;try;&lt;BR /&gt;&lt;BR /&gt;vgimport -v /dev/vg00 /dev/dsk/c31t0d3&lt;BR /&gt;&lt;BR /&gt;and do same for /dev/vgnetapp_tnpt&lt;BR /&gt;also&lt;BR /&gt;&lt;BR /&gt;vgimport -v  /dev/vgnetapp_tnpt dev/dsk/c31t1d2&lt;BR /&gt; &lt;BR /&gt;can you post &lt;BR /&gt;vgdisplay -v vg00&lt;BR /&gt;and lvlnboot -v&lt;BR /&gt;strings /etc/lvmtab&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Feb 2011 10:17:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275040#M548987</guid>
      <dc:creator>nijokj</dc:creator>
      <dc:date>2011-02-25T10:17:34Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275041#M548988</link>
      <description>Hi Nijoko&lt;BR /&gt;&lt;BR /&gt;Thanks for you reply&lt;BR /&gt;I've haven't run vgimport yet .&lt;BR /&gt; &lt;BR /&gt;$ vgdisplay -v /dev/vg00&lt;BR /&gt;--- Volume groups ---&lt;BR /&gt;VG Name                     /dev/vg00&lt;BR /&gt;VG Write Access             read/write&lt;BR /&gt;VG Status                   available&lt;BR /&gt;Max LV                      255&lt;BR /&gt;Cur LV                      9&lt;BR /&gt;Open LV                     9&lt;BR /&gt;Max PV                      16&lt;BR /&gt;Cur PV                      2&lt;BR /&gt;Act PV                      2&lt;BR /&gt;Max PE per PV               4384&lt;BR /&gt;VGDA                        4&lt;BR /&gt;PE Size (Mbytes)            16&lt;BR /&gt;Total PE                    8748&lt;BR /&gt;Alloc PE                    6042&lt;BR /&gt;Free PE                     2706&lt;BR /&gt;Total PVG                   0&lt;BR /&gt;Total Spare PVs             0&lt;BR /&gt;Total Spare PVs in use      0&lt;BR /&gt;&lt;BR /&gt;   --- Logical volumes ---&lt;BR /&gt;   LV Name                     /dev/vg00/lvol1&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            1792&lt;BR /&gt;   Current LE                  112&lt;BR /&gt;   Allocated PE                224&lt;BR /&gt;   Used PV                     2&lt;BR /&gt;&lt;BR /&gt;   LV Name                     /dev/vg00/lvol2&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            8192&lt;BR /&gt;   Current LE                  512&lt;BR /&gt;   Allocated PE                1024&lt;BR /&gt;   Used PV                     2&lt;BR /&gt;&lt;BR /&gt;   LV Name                     /dev/vg00/lvol3&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            2048&lt;BR /&gt;   Current LE                  128&lt;BR /&gt;   Allocated PE                256&lt;BR /&gt;   Used PV                     2&lt;BR /&gt;&lt;BR /&gt;   LV Name                     /dev/vg00/lvol4&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            2192&lt;BR /&gt;   Current LE                  137&lt;BR /&gt;   Allocated PE                274&lt;BR /&gt;   Used PV                     2&lt;BR /&gt;&lt;BR /&gt;   LV Name                     /dev/vg00/lvol5&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            8192&lt;BR /&gt;   Current LE                  512&lt;BR /&gt;   Allocated PE                1024&lt;BR /&gt;   Used PV                     2&lt;BR /&gt;&lt;BR /&gt;   LV Name                     /dev/vg00/lvol6&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            8000&lt;BR /&gt;   Current LE                  500&lt;BR /&gt;   Allocated PE                1000&lt;BR /&gt;   Used PV                     2&lt;BR /&gt;&lt;BR /&gt;   LV Name                     /dev/vg00/lvol7&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            7168&lt;BR /&gt;   Current LE                  448&lt;BR /&gt;   Allocated PE                896&lt;BR /&gt;   Used PV                     2&lt;BR /&gt;&lt;BR /&gt;   LV Name                     /dev/vg00/lvol8&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            8704&lt;BR /&gt;   Current LE                  544&lt;BR /&gt;   Allocated PE                1088&lt;BR /&gt;   Used PV                     2&lt;BR /&gt;&lt;BR /&gt;   LV Name                     /dev/vg00/ISO&lt;BR /&gt;   LV Status                   available/syncd&lt;BR /&gt;   LV Size (Mbytes)            4096&lt;BR /&gt;   Current LE                  256&lt;BR /&gt;   Allocated PE                256&lt;BR /&gt;   Used PV                     1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;   --- Physical volumes ---&lt;BR /&gt;   PV Name                     /dev/dsk/c2t1d0&lt;BR /&gt;   PV Status                   available&lt;BR /&gt;   Total PE                    4374&lt;BR /&gt;   Free PE                     1225&lt;BR /&gt;   Autoswitch                  On&lt;BR /&gt;   Proactive Polling           On&lt;BR /&gt;&lt;BR /&gt;   PV Name                     /dev/dsk/c3t0d0&lt;BR /&gt;   PV Status                   available&lt;BR /&gt;   Total PE                    4374&lt;BR /&gt;   Free PE                     1481&lt;BR /&gt;   Autoswitch                  On&lt;BR /&gt;   Proactive Polling           On&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;lvlnboot -v&lt;BR /&gt;&lt;BR /&gt;Boot Definitions for Volume Group /dev/vg00:&lt;BR /&gt;Physical Volumes belonging in Root Volume Group:&lt;BR /&gt;        /dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk&lt;BR /&gt;        /dev/dsk/c3t0d0 (0/1/1/1.0.0) -- Boot Disk&lt;BR /&gt;Boot: lvol1     on:     /dev/dsk/c2t1d0&lt;BR /&gt;                        /dev/dsk/c3t0d0&lt;BR /&gt;Root: lvol3     on:     /dev/dsk/c2t1d0&lt;BR /&gt;                        /dev/dsk/c3t0d0&lt;BR /&gt;Swap: lvol2     on:     /dev/dsk/c2t1d0&lt;BR /&gt;                        /dev/dsk/c3t0d0&lt;BR /&gt;Dump: lvol2     on:     /dev/dsk/c2t1d0, 0&lt;BR /&gt;&lt;BR /&gt;lvlnboot: Couldn't query physical volume "/dev/dsk/c31t0d3":&lt;BR /&gt;The specified path does not correspond to physical volume attached to&lt;BR /&gt;this volume group&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;$ strings /etc/lvmtab&lt;BR /&gt;/dev/vg00&lt;BR /&gt;/dev/dsk/c2t1d0&lt;BR /&gt;/dev/dsk/c3t0d0&lt;BR /&gt;/dev/vgnetapp_ent&lt;BR /&gt;/dev/dsk/c31t0d3&lt;BR /&gt;/dev/dsk/c29t0d3&lt;BR /&gt;/dev/dsk/c25t0d3&lt;BR /&gt;/dev/dsk/c21t0d3&lt;BR /&gt;/dev/dsk/c31t2d2&lt;BR /&gt;/dev/dsk/c29t2d2&lt;BR /&gt;/dev/dsk/c21t2d2&lt;BR /&gt;/dev/dsk/c25t2d2&lt;BR /&gt;/dev/vgnetapp_omnix&lt;BR /&gt;/dev/dsk/c25t1d0&lt;BR /&gt;/dev/dsk/c21t1d0&lt;BR /&gt;/dev/dsk/c31t1d0&lt;BR /&gt;/dev/dsk/c29t1d0&lt;BR /&gt;/dev/dsk/c25t2d1&lt;BR /&gt;/dev/dsk/c21t2d1&lt;BR /&gt;/dev/dsk/c31t2d1&lt;BR /&gt;/dev/dsk/c29t2d1&lt;BR /&gt;/dev/vgnetapp_opt_dev&lt;BR /&gt;/dev/dsk/c21t0d4&lt;BR /&gt;/dev/dsk/c25t0d4&lt;BR /&gt;/dev/dsk/c31t0d4&lt;BR /&gt;/dev/dsk/c29t0d4&lt;BR /&gt;/dev/vgnetapp_opt_tibco&lt;BR /&gt;/dev/dsk/c21t0d1&lt;BR /&gt;/dev/dsk/c25t0d1&lt;BR /&gt;/dev/dsk/c31t0d1&lt;BR /&gt;/dev/dsk/c29t0d1&lt;BR /&gt;/dev/vgnetapp_rep&lt;BR /&gt;/dev/dsk/c31t1d1&lt;BR /&gt;/dev/dsk/c29t1d1&lt;BR /&gt;/dev/dsk/c31t1d7&lt;BR /&gt;/dev/dsk/c29t1d7&lt;BR /&gt;/dev/dsk/c25t1d7&lt;BR /&gt;/dev/dsk/c21t1d7&lt;BR /&gt;/dev/dsk/c25t1d1&lt;BR /&gt;/dev/dsk/c21t1d1&lt;BR /&gt;/dev/vgnetapp_tnpt&lt;BR /&gt;/dev/dsk/c31t1d2&lt;BR /&gt;/dev/dsk/c29t1d2&lt;BR /&gt;/dev/dsk/c25t1d2&lt;BR /&gt;/dev/dsk/c21t1d2&lt;BR /&gt;/dev/dsk/c31t1d5&lt;BR /&gt;/dev/dsk/c29t1d5&lt;BR /&gt;/dev/dsk/c25t1d5&lt;BR /&gt;/dev/dsk/c21t1d5&lt;BR /&gt;/dev/vgnetapp_teleca&lt;BR /&gt;/dev/dsk/c21t1d3&lt;BR /&gt;/dev/dsk/c25t1d3&lt;BR /&gt;/dev/dsk/c31t1d3&lt;BR /&gt;/dev/dsk/c29t1d3&lt;BR /&gt;/dev/vgnetapp_opt_oracle&lt;BR /&gt;/dev/dsk/c21t0d0&lt;BR /&gt;/dev/dsk/c25t0d0&lt;BR /&gt;/dev/dsk/c31t0d0&lt;BR /&gt;/dev/dsk/c29t0d0&lt;BR /&gt;/dev/vgnetapp_ems&lt;BR /&gt;/dev/dsk/c21t0d7&lt;BR /&gt;/dev/dsk/c21t0d6&lt;BR /&gt;/dev/dsk/c25t0d7&lt;BR /&gt;/dev/dsk/c25t0d6&lt;BR /&gt;/dev/dsk/c31t0d7&lt;BR /&gt;/dev/dsk/c29t0d7&lt;BR /&gt;/dev/dsk/c31t0d6&lt;BR /&gt;/dev/dsk/c29t0d6&lt;BR /&gt;/dev/dsk/c21t1d6&lt;BR /&gt;/dev/dsk/c25t1d6&lt;BR /&gt;/dev/dsk/c31t1d6&lt;BR /&gt;/dev/dsk/c29t1d6&lt;BR /&gt;/dev/vgnetapp_interbc&lt;BR /&gt;/dev/dsk/c21t0d2&lt;BR /&gt;/dev/dsk/c25t0d2&lt;BR /&gt;/dev/dsk/c31t0d2&lt;BR /&gt;/dev/dsk/c29t0d2&lt;BR /&gt;/dev/vgnetapp_erptest&lt;BR /&gt;/dev/dsk/c29t0d5&lt;BR /&gt;/dev/dsk/c29t1d4&lt;BR /&gt;/dev/dsk/c31t1d4&lt;BR /&gt;/dev/dsk/c31t0d5&lt;BR /&gt;/dev/dsk/c25t1d4&lt;BR /&gt;/dev/dsk/c21t1d4&lt;BR /&gt;/dev/dsk/c25t0d5&lt;BR /&gt;/dev/dsk/c21t0d5&lt;BR /&gt;/dev/vgnetapp_tnptplan&lt;BR /&gt;OMIUV&lt;BR /&gt;/dev/dsk/c29t2d3&lt;BR /&gt;/dev/dsk/c21t2d3&lt;BR /&gt;&lt;BR /&gt;Regard&lt;BR /&gt;Tien</description>
      <pubDate>Fri, 25 Feb 2011 10:36:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275041#M548988</guid>
      <dc:creator>Joakim Rudén</dc:creator>
      <dc:date>2011-02-25T10:36:26Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275042#M548989</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;After running vgimport I got this issue :&lt;BR /&gt;&lt;BR /&gt;vgimport -v /dev/vg00 /dev/dsk/c31t0d3&lt;BR /&gt;&lt;BR /&gt;Beginning the import process on Volume Group "/dev/vg00".&lt;BR /&gt;vgimport: Volume group "/dev/vg00" already exists in the "/etc/lvmtab" file.&lt;BR /&gt;&lt;BR /&gt;lvlnboot -v&lt;BR /&gt;&lt;BR /&gt;Boot Definitions for Volume Group /dev/vg00:&lt;BR /&gt;Physical Volumes belonging in Root Volume Group:&lt;BR /&gt;        /dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk&lt;BR /&gt;        /dev/dsk/c3t0d0 (0/1/1/1.0.0) -- Boot Disk&lt;BR /&gt;Boot: lvol1     on:     /dev/dsk/c2t1d0&lt;BR /&gt;                        /dev/dsk/c3t0d0&lt;BR /&gt;Root: lvol3     on:     /dev/dsk/c2t1d0&lt;BR /&gt;                        /dev/dsk/c3t0d0&lt;BR /&gt;Swap: lvol2     on:     /dev/dsk/c2t1d0&lt;BR /&gt;                        /dev/dsk/c3t0d0&lt;BR /&gt;Dump: lvol2     on:     /dev/dsk/c2t1d0, 0&lt;BR /&gt;&lt;BR /&gt;lvlnboot: Couldn't query physical volume "/dev/dsk/c31t0d3":&lt;BR /&gt;The specified path does not correspond to physical volume attached to&lt;BR /&gt;this volume group&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;/Tien</description>
      <pubDate>Fri, 25 Feb 2011 11:02:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275042#M548989</guid>
      <dc:creator>Joakim Rudén</dc:creator>
      <dc:date>2011-02-25T11:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275043#M548990</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;When you replace a fibercard also changes the WWN. Then zoning and lun masking will need to be updated.&lt;BR /&gt;&lt;BR /&gt;Rgds.</description>
      <pubDate>Fri, 25 Feb 2011 11:10:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275043#M548990</guid>
      <dc:creator>Jose Mosquera</dc:creator>
      <dc:date>2011-02-25T11:10:03Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275044#M548991</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;In other words, if you not update the settings in your SAN zone with the new fibercard World Wide Name (WWN), you can not access the disk again.&lt;BR /&gt;&lt;BR /&gt;Rgds.</description>
      <pubDate>Fri, 25 Feb 2011 11:38:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275044#M548991</guid>
      <dc:creator>Jose Mosquera</dc:creator>
      <dc:date>2011-02-25T11:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275045#M548992</link>
      <description>Hi Jose&lt;BR /&gt;&lt;BR /&gt;Can you please show me how to update the settings in SAN zone with new fibercard?&lt;BR /&gt;&lt;BR /&gt;Regard&lt;BR /&gt;Tien</description>
      <pubDate>Fri, 25 Feb 2011 11:44:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275045#M548992</guid>
      <dc:creator>Joakim Rudén</dc:creator>
      <dc:date>2011-02-25T11:44:25Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275046#M548993</link>
      <description>Hi Tien,&lt;BR /&gt;&lt;BR /&gt;No easy task, depends on brand and model of SAN switches, usually requires the knowledge of these devices (specialized staff).&lt;BR /&gt;&lt;BR /&gt;Additionally you can check the following?&lt;BR /&gt;The fibercard is CLAIMED and online?&lt;BR /&gt;# ioscan-fnCfc (should show both devices CLAIMED)&lt;BR /&gt;Which of the two devices was replaced (/ dev/td0 or / dev/td1)?&lt;BR /&gt;# fcmsutil / dev / td? (replaced device)&lt;BR /&gt;What is the "Driver state=" content?&lt;BR /&gt;&lt;BR /&gt;Rgds.</description>
      <pubDate>Fri, 25 Feb 2011 12:33:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275046#M548993</guid>
      <dc:creator>Jose Mosquera</dc:creator>
      <dc:date>2011-02-25T12:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275047#M548994</link>
      <description>1st issue&lt;BR /&gt;&lt;BR /&gt;vgdisplay -v /dev/vgnetapp_tnpt&lt;BR /&gt;vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c31t1d2":&lt;BR /&gt;The specified path does not correspond to physical volume attached to&lt;BR /&gt;this volume group&lt;BR /&gt;&lt;BR /&gt;/dev/vgnetapp_tnpt&lt;BR /&gt;/dev/dsk/c31t1d2&lt;BR /&gt;/dev/dsk/c29t1d2&lt;BR /&gt;/dev/dsk/c25t1d2&lt;BR /&gt;/dev/dsk/c21t1d2&lt;BR /&gt;/dev/dsk/c31t1d5&lt;BR /&gt;/dev/dsk/c29t1d5&lt;BR /&gt;/dev/dsk/c25t1d5&lt;BR /&gt;/dev/dsk/c21t1d5&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;2nd issue&lt;BR /&gt;&lt;BR /&gt;vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c31t0d3":&lt;BR /&gt;/dev/vgnetapp_ent&lt;BR /&gt;/dev/dsk/c31t0d3&lt;BR /&gt;/dev/dsk/c29t0d3&lt;BR /&gt;/dev/dsk/c25t0d3&lt;BR /&gt;/dev/dsk/c21t0d3&lt;BR /&gt;/dev/dsk/c31t2d2&lt;BR /&gt;/dev/dsk/c29t2d2&lt;BR /&gt;/dev/dsk/c21t2d2&lt;BR /&gt;/dev/dsk/c25t2d2&lt;BR /&gt;&lt;BR /&gt;do one thing&lt;BR /&gt;&lt;BR /&gt;mv /etc/lvmtab /etc/lvmtab.org&lt;BR /&gt;&lt;BR /&gt;vgscan -av &lt;BR /&gt;&lt;BR /&gt;it will create new /etc/lvmtab&lt;BR /&gt;&lt;BR /&gt;this will solve your problem.Before that please confirm /dev/dsk/c31t1d2 ,/dev/dsk/c31t0d3 disks are available through ioscan -fnC disk |egrep -i "/dev/dsk/c31t1d2|/dev/dsk/c31t0d3"</description>
      <pubDate>Fri, 25 Feb 2011 12:43:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275047#M548994</guid>
      <dc:creator>nijokj</dc:creator>
      <dc:date>2011-02-25T12:43:10Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275048#M548995</link>
      <description>Ooops, previous post have some extra blank spaces, the correct syntax is:&lt;BR /&gt;&lt;BR /&gt;Which of the two devices was replaced (/dev/td0 or /dev/td1)?&lt;BR /&gt;# fcmsutil /dev/td? (replaced device)&lt;BR /&gt;What is the "Driver state=" content?&lt;BR /&gt;&lt;BR /&gt;Rgds.</description>
      <pubDate>Fri, 25 Feb 2011 13:07:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275048#M548995</guid>
      <dc:creator>Jose Mosquera</dc:creator>
      <dc:date>2011-02-25T13:07:40Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275049#M548996</link>
      <description>Hi Jose&lt;BR /&gt;&lt;BR /&gt;$ ioscan -fknC fc&lt;BR /&gt;Class     I  H/W Path  Driver S/W State   H/W Type     Description&lt;BR /&gt;=================================================================&lt;BR /&gt;fc        0  0/2/1/0   td   CLAIMED     INTERFACE    HP Tachyon XL2 Fibre Channel Mass Storage Adapter&lt;BR /&gt;                      /dev/td0&lt;BR /&gt;fc        1  0/6/1/0   td   CLAIMED     INTERFACE    HP Tachyon XL2 Fibre Channel Mass Storage Adapter&lt;BR /&gt;                      /dev/td1&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;$ fcmsutil /dev/td1 replace_dsk&lt;BR /&gt;Error: nport_id () is not a valid number.&lt;BR /&gt;&lt;BR /&gt;My question is which portid I have to issue here. ?&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Feb 2011 13:25:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275049#M548996</guid>
      <dc:creator>Joakim Rudén</dc:creator>
      <dc:date>2011-02-25T13:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275050#M548997</link>
      <description>Hi Nojoki&lt;BR /&gt;&lt;BR /&gt;I don't find any  /dev/dsk/c31t1d2 and /dev/dsk/c31t0d3 disks when i run ioscan -fnC disk &lt;BR /&gt;&lt;BR /&gt;Regard &lt;BR /&gt;Tien</description>
      <pubDate>Fri, 25 Feb 2011 13:28:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275050#M548997</guid>
      <dc:creator>Joakim Rudén</dc:creator>
      <dc:date>2011-02-25T13:28:28Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275051#M548998</link>
      <description>let me know your all vgs are activated or not?&lt;BR /&gt;You have any issue with any of the filesystem which can be mounted.?&lt;BR /&gt;Before doing this activity have you create the map file of vgs.&lt;BR /&gt;Reply pls.</description>
      <pubDate>Fri, 25 Feb 2011 14:48:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275051#M548998</guid>
      <dc:creator>nijokj</dc:creator>
      <dc:date>2011-02-25T14:48:12Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275052#M548999</link>
      <description>Thank for your reply, Nijoko&lt;BR /&gt;&lt;BR /&gt;All of Vg are activated with filesystem&lt;BR /&gt;Filesystem          kbytes    used   avail %used Mounted on&lt;BR /&gt;/dev/vg00/lvol3    2097152  845432 1242024   41% /&lt;BR /&gt;/dev/vg00/lvol1    1776056   54488 1543960    3% /stand&lt;BR /&gt;/dev/vg00/lvol8    8912896 4598384 4284856   52% /var&lt;BR /&gt;/dev/vgnetapp_teleca/lvol1&lt;BR /&gt;                   3375104 1975755 1311921   &lt;BR /&gt;........&lt;BR /&gt;&lt;BR /&gt;And I see that we have 2 fibercards : 0/2/1/0(old) and  0/6/1/0( new) but when I run ioscan -fnC disk the result i got is there is only fibercard 0/2/1/0 is accessing disks while the new fibercard doesn't contact with disks although it's on .  &lt;BR /&gt;&lt;BR /&gt;ioscan -fknC fc&lt;BR /&gt;Class     I  H/W Path  Driver S/W State   H/W Type     Description&lt;BR /&gt;=================================================================&lt;BR /&gt;fc        0  0/2/1/0   td   CLAIMED     INTERFACE    HP Tachyon XL2 Fibre Channel Mass Storage Adapter&lt;BR /&gt;                      /dev/td0&lt;BR /&gt;fc        1  0/6/1/0   td   CLAIMED     INTERFACE    HP Tachyon XL2 Fibre Channel Mass Storage Adapter&lt;BR /&gt;                      /dev/td1&lt;BR /&gt;ios&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;ioscan -fnC disk ( all disks are in 'claimed' status with 0/2/1/0)&lt;BR /&gt;Class     I  H/W Path        Driver     S/W State   H/W Type     Description&lt;BR /&gt;=============================================================================&lt;BR /&gt;disk      0  0/0/3/0.0.0.0   sdisk      CLAIMED     DEVICE       TEAC    DW-224E&lt;BR /&gt;                            /dev/dsk/c0t0d0   /dev/rdsk/c0t0d0&lt;BR /&gt;disk      2  0/1/1/0.1.0     sdisk      CLAIMED     DEVICE       HP 73.4GHUS153073VL3800&lt;BR /&gt;                            /dev/dsk/c2t1d0   /dev/rdsk/c2t1d0&lt;BR /&gt;disk      1  0/1/1/1.0.0     sdisk      CLAIMED     DEVICE       HP 73.4GST373454LC&lt;BR /&gt;                            /dev/dsk/c3t0d0   /dev/rdsk/c3t0d0&lt;BR /&gt;disk    163  0/2/1/0.1.34.0.0.0.0  sdisk      CLAIMED     DEVICE       NETAPP  LUN&lt;BR /&gt;                            /dev/dsk/c21t0d0   /dev/rdsk/c21t0d0&lt;BR /&gt;disk    184  0/2/1/0.1.34.0.0.0.1  sdisk      CLAIMED     DEVICE       NETAPP  LUN&lt;BR /&gt;                            /dev/dsk/c21t0d1   /dev/rdsk/c21t0d1&lt;BR /&gt;disk    167  0/2/1/0.1.34.0.0.0.2  sdisk      CLAIMED     DEVICE       NETAPP  LUN&lt;BR /&gt;                            /dev/dsk/c21t0d2   /dev/rdsk/c21t0d2&lt;BR /&gt;disk    186  0/2/1/0.1.34.0.0.0.3  sdisk      CLAIMED     DEVICE       NETAPP  LUN&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regard&lt;BR /&gt;Tien</description>
      <pubDate>Fri, 25 Feb 2011 15:10:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275052#M548999</guid>
      <dc:creator>Joakim Rudén</dc:creator>
      <dc:date>2011-02-25T15:10:05Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275053#M549000</link>
      <description>So the issue is alternate path to disks are missing.&lt;BR /&gt;Once you change the fc card you need to recreate the www zoning.If you have storage team  please contact  them.</description>
      <pubDate>Fri, 25 Feb 2011 16:33:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275053#M549000</guid>
      <dc:creator>nijokj</dc:creator>
      <dc:date>2011-02-25T16:33:51Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275054#M549001</link>
      <description>Hi Tien,&lt;BR /&gt;&lt;BR /&gt;The command must be:&lt;BR /&gt;#fcmsutil /dev/td1&lt;BR /&gt;&lt;BR /&gt;My post (replaced device) to indicate you that the device correspond to replaced fibercard. :)&lt;BR /&gt;&lt;BR /&gt;Rgds.</description>
      <pubDate>Fri, 25 Feb 2011 17:13:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275054#M549001</guid>
      <dc:creator>Jose Mosquera</dc:creator>
      <dc:date>2011-02-25T17:13:12Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275055#M549002</link>
      <description>Hi. &lt;BR /&gt;Thank you for your advices.&lt;BR /&gt;&lt;BR /&gt;To solve this prolem I think IÂ´'ll invite a specialized staff to come our company and can help us out as both of you suggested.&lt;BR /&gt;&lt;BR /&gt;Best Regard&lt;BR /&gt;Tien&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Feb 2011 08:13:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275055#M549002</guid>
      <dc:creator>Joakim Rudén</dc:creator>
      <dc:date>2011-02-28T08:13:02Z</dc:date>
    </item>
    <item>
      <title>Re: The specified path does not correspond to physical volume</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275056#M549003</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;We got advices from HP support that we need&lt;BR /&gt;&lt;BR /&gt;Regard&lt;BR /&gt;Tien</description>
      <pubDate>Mon, 28 Feb 2011 08:17:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/the-specified-path-does-not-correspond-to-physical-volume/m-p/5275056#M549003</guid>
      <dc:creator>Joakim Rudén</dc:creator>
      <dc:date>2011-02-28T08:17:19Z</dc:date>
    </item>
  </channel>
</rss>

