<?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: Scary vgdisplay in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451806#M657237</link>
    <description>use ioscan -fnC disk to check that disks are&lt;BR /&gt;claimed by the system. If they are&lt;BR /&gt;Check that disk entries in /etc/lvmtab match the physical disk entries displayed by vgisplay.&lt;BR /&gt;If they match try reactivating the volume group&lt;BR /&gt;vgchange -a y &lt;VG&gt;&lt;BR /&gt;then run vgsync&lt;BR /&gt;&lt;/VG&gt;</description>
    <pubDate>Tue, 10 Oct 2000 06:31:34 GMT</pubDate>
    <dc:creator>Adrian Voysey</dc:creator>
    <dc:date>2000-10-10T06:31:34Z</dc:date>
    <item>
      <title>Scary vgdisplay</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451802#M657233</link>
      <description />
      <pubDate>Mon, 09 Oct 2000 21:03:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451802#M657233</guid>
      <dc:creator>Ashwani Kashyap</dc:creator>
      <dc:date>2000-10-09T21:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: Scary vgdisplay</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451803#M657234</link>
      <description>This looks like a hardware problem. EIther bad drives. bad controler, or bad cables.&lt;BR /&gt;&lt;BR /&gt;First try this command&lt;BR /&gt;ioscan -fnC disk&lt;BR /&gt;See if any of the drive are not CLAIMED&lt;BR /&gt;&lt;BR /&gt;Next try this command on each of the drives&lt;BR /&gt;diskinfo /dev/rdsk/c?t??d?&lt;BR /&gt;This should give you good info for each drive.&lt;BR /&gt;&lt;BR /&gt;Next try this command on each of the drives&lt;BR /&gt;dd if=/dev/rdsk/c?t??d? of=/dev/null bs=1024K&lt;BR /&gt;This will give read error on any bad drives. The dd command takes a LONG time to run so use it only on the suspect drives.</description>
      <pubDate>Mon, 09 Oct 2000 21:40:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451803#M657234</guid>
      <dc:creator>Lawrence Mahan</dc:creator>
      <dc:date>2000-10-09T21:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: Scary vgdisplay</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451804#M657235</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;just a note to Larry's reply:&lt;BR /&gt;add count=1 at the end of the dd command to prevent dd hanging longer.&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Tue, 10 Oct 2000 06:18:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451804#M657235</guid>
      <dc:creator>Andreas Voss</dc:creator>
      <dc:date>2000-10-10T06:18:05Z</dc:date>
    </item>
    <item>
      <title>Re: Scary vgdisplay</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451805#M657236</link>
      <description>use ioscan -fnC disk to check that disks are&lt;BR /&gt;claimed by the system. If they are&lt;BR /&gt;Check that disk entries in /etc/lvmtab match the physical disk entries displayed by vgisplay.&lt;BR /&gt;If they match try reactivating the volume group&lt;BR /&gt;vgchange -a y &lt;VG&gt;&lt;BR /&gt;then run vgsync&lt;BR /&gt;&lt;/VG&gt;</description>
      <pubDate>Tue, 10 Oct 2000 06:31:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451805#M657236</guid>
      <dc:creator>Adrian Voysey</dc:creator>
      <dc:date>2000-10-10T06:31:19Z</dc:date>
    </item>
    <item>
      <title>Re: Scary vgdisplay</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451806#M657237</link>
      <description>use ioscan -fnC disk to check that disks are&lt;BR /&gt;claimed by the system. If they are&lt;BR /&gt;Check that disk entries in /etc/lvmtab match the physical disk entries displayed by vgisplay.&lt;BR /&gt;If they match try reactivating the volume group&lt;BR /&gt;vgchange -a y &lt;VG&gt;&lt;BR /&gt;then run vgsync&lt;BR /&gt;&lt;/VG&gt;</description>
      <pubDate>Tue, 10 Oct 2000 06:31:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451806#M657237</guid>
      <dc:creator>Adrian Voysey</dc:creator>
      <dc:date>2000-10-10T06:31:34Z</dc:date>
    </item>
    <item>
      <title>Re: Scary vgdisplay</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451807#M657238</link>
      <description>Another thing to try is syncing one logical volume (lvsync /dev/vg09/lvol1) see if it suncs correctly ( try each one ) or do the whole lot vgsync (volgroup) and then check if you have any stale partitions. You could have a hard disk problem , check if any of the disks have been replaced before and which disks , because if your mirror copy disks have been replaced , the actual problem may be on the primary disk hence stale partitions ( if this is the case make sure you have good backups)&lt;BR /&gt;&lt;BR /&gt;The other thing to check is the firmware revison of the disks , ( nb:- what type of disk enclosure have you got installed )&lt;BR /&gt;&lt;BR /&gt;do diskinfo -v /dev/rdsk/c9t3d0 and note the rev level ( do for each disk ) , log a call with HP and confirm if disk firmware need upgrading .&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Oct 2000 15:22:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451807#M657238</guid>
      <dc:creator>Devbinder Singh Marway</dc:creator>
      <dc:date>2000-10-10T15:22:26Z</dc:date>
    </item>
    <item>
      <title>Re: Scary vgdisplay</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451808#M657239</link>
      <description>Devbinder may be on to something.&lt;BR /&gt;What you have to determine is what was the plan.  Who ever did this, they were either trying to set up mirror drives to first drives -OR- they were trying to add more drives to the original volgroup.&lt;BR /&gt;My guess looks like they messed up trying to add mirrors....and that is why I am leaning towards Devbinder's suggestion.  Obviously from the file you supplied these last 3 drives are doing 'diddly' right now...so you can either mirror them, then sync then up with the primaries...(which would be my choice for you may wonder what other problems you might encounter) or I'd remove them and put them back in (so I was sure they were solid..)&lt;BR /&gt;Just a thought,</description>
      <pubDate>Fri, 13 Oct 2000 13:20:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451808#M657239</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2000-10-13T13:20:04Z</dc:date>
    </item>
    <item>
      <title>Re: Scary vgdisplay</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451809#M657240</link>
      <description>Woops,,,,sorry,those 3 are in use. So don't reduce...I still lean for mirror.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Oct 2000 13:22:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/scary-vgdisplay/m-p/2451809#M657240</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2000-10-13T13:22:40Z</dc:date>
    </item>
  </channel>
</rss>

