<?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: HP UX Possible Disk Errors in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189170#M164348</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;it sounds like a typo somewhere, I never heard that name for a device file before.&lt;BR /&gt;Otherwise&lt;BR /&gt;&lt;BR /&gt;# insf -e&lt;BR /&gt;# vgscan -v&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Ettore&lt;BR /&gt;</description>
    <pubDate>Wed, 11 Feb 2004 11:21:52 GMT</pubDate>
    <dc:creator>Fabio Ettore</dc:creator>
    <dc:date>2004-02-11T11:21:52Z</dc:date>
    <item>
      <title>HP UX Possible Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189166#M164344</link>
      <description>I ran script supplied by Steven Protter called disk.status(a nice tool). It returned several error indications. I then did the following and received these messages. My ultimate goal here is to invoke "make_recovery". We are running HP-UX 10.20 Please help.&lt;BR /&gt;&lt;BR /&gt;mv /etc/lvmtab /etc/lvmtab.backup&lt;BR /&gt;vgscan -a&lt;BR /&gt;&lt;BR /&gt;   Creating "/etc/lvmtab"&lt;BR /&gt;   vgscan: Physical volume "/dev/dsk/c1todo" is not a block special file.&lt;BR /&gt;   Couldn't stat physical volume "/dev/dsk/c1t0d0":&lt;BR /&gt;   Invalid argument&lt;BR /&gt;   Physical Volume "/dev/dsk/c1t2d0" contains no LVM information&lt;BR /&gt;   The Volume Group /dev/sqdeal/group was not matched with any Physical Volumes.</description>
      <pubDate>Wed, 11 Feb 2004 11:11:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189166#M164344</guid>
      <dc:creator>Ron Twiggs</dc:creator>
      <dc:date>2004-02-11T11:11:43Z</dc:date>
    </item>
    <item>
      <title>Re: HP UX Possible Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189167#M164345</link>
      <description>"/dev/dsk/c1todo" appears to be an invalid disk name.  Check /dev/dsk and compare this to ioscan.&lt;BR /&gt;# ll /dev/dsk/c1*&lt;BR /&gt;# ioscan -fnC disk&lt;BR /&gt;# diskinfo /dev/rdsk/c1todo</description>
      <pubDate>Wed, 11 Feb 2004 11:15:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189167#M164345</guid>
      <dc:creator>Cheryl Griffin</dc:creator>
      <dc:date>2004-02-11T11:15:37Z</dc:date>
    </item>
    <item>
      <title>Re: HP UX Possible Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189168#M164346</link>
      <description>Ron,&lt;BR /&gt;&lt;BR /&gt;I feel like I'm missing part of the picture here.  What errors did this "script" give you and from what commands in the script?  Why would this lead you to run "vgscan -a"?  What does "ioscan -f" tell you about /dev/dsk/c1t0d0 (I'm assuming that /dev/dsk/c1todo is a typo)?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Wed, 11 Feb 2004 11:16:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189168#M164346</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2004-02-11T11:16:21Z</dc:date>
    </item>
    <item>
      <title>Re: HP UX Possible Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189169#M164347</link>
      <description>I have had the same issue in the past.&lt;BR /&gt;&lt;BR /&gt;The fix was to run vgexport on the volume group and then vgimport it.&lt;BR /&gt;&lt;BR /&gt;If vgimport fails you may need to rebuild the volume group from scratch. Obviously a backup prior to starting this is critical.&lt;BR /&gt;&lt;BR /&gt;A few searches that might help.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support2.external.hp.com/emse/bin/doc.pl/sid=394512371cad33b60d?todo=search&amp;amp;searchtext=vgexport+vgimport+vgcreate&amp;amp;x=28&amp;amp;y=12&amp;amp;searchcriteria=allwords&amp;amp;searchtype=SEARCH_TRAINER&amp;amp;searchtype=SEARCH_FORUMS&amp;amp;searchcategory=ALL&amp;amp;rn=25&amp;amp;presort=rank" target="_blank"&gt;http://us-support2.external.hp.com/emse/bin/doc.pl/sid=394512371cad33b60d?todo=search&amp;amp;searchtext=vgexport+vgimport+vgcreate&amp;amp;x=28&amp;amp;y=12&amp;amp;searchcriteria=allwords&amp;amp;searchtype=SEARCH_TRAINER&amp;amp;searchtype=SEARCH_FORUMS&amp;amp;searchcategory=ALL&amp;amp;rn=25&amp;amp;presort=rank&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You should be able to cut and paste the necessary procedures out of any of the threads above.&lt;BR /&gt;&lt;BR /&gt;Proceed with caution and backups.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 11 Feb 2004 11:16:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189169#M164347</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-02-11T11:16:51Z</dc:date>
    </item>
    <item>
      <title>Re: HP UX Possible Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189170#M164348</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;it sounds like a typo somewhere, I never heard that name for a device file before.&lt;BR /&gt;Otherwise&lt;BR /&gt;&lt;BR /&gt;# insf -e&lt;BR /&gt;# vgscan -v&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;Ettore&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Feb 2004 11:21:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189170#M164348</guid>
      <dc:creator>Fabio Ettore</dc:creator>
      <dc:date>2004-02-11T11:21:52Z</dc:date>
    </item>
    <item>
      <title>Re: HP UX Possible Disk Errors</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189171#M164349</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I would go with Pete's analysis first.&lt;BR /&gt;&lt;BR /&gt;What errors did you originally see that prompted you to run vgscan?.&lt;BR /&gt;&lt;BR /&gt;Looks like the device files for the disk at c1t0d0 got messed up somehow.&lt;BR /&gt;&lt;BR /&gt;Running the following may help you as said before.&lt;BR /&gt;&lt;BR /&gt;#ioscan -f&lt;BR /&gt;#insf -e&lt;BR /&gt;#vgscan -v (as you already moved lvmtab)&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Wed, 11 Feb 2004 12:57:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/hp-ux-possible-disk-errors/m-p/3189171#M164349</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2004-02-11T12:57:23Z</dc:date>
    </item>
  </channel>
</rss>

