<?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: rootconf is corrupted in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074456#M439282</link>
    <description>Any change booting to single user works?&lt;BR /&gt;I found this doc on how to recreate it:&lt;BR /&gt;&lt;A href="http://h50069.www5.hp.com/e-Delivery3/Forum/Others/UpLoadFiles/99883/vfs_mountroot.txt" target="_blank"&gt;http://h50069.www5.hp.com/e-Delivery3/Forum/Others/UpLoadFiles/99883/vfs_mountroot.txt&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;But you have to get the server up to the point you can fix it.  &lt;BR /&gt;&lt;BR /&gt;Search for "Bad or old data in /stand/rootconf using JFS as root filesystem&lt;BR /&gt;"  within that document.&lt;BR /&gt;&lt;BR /&gt;Which version of hpux is it?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Ignite might be the only solution.  It sounds like it can happen for a few different reasons.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Tue, 16 Oct 2007 10:38:09 GMT</pubDate>
    <dc:creator>Dave Hutton</dc:creator>
    <dc:date>2007-10-16T10:38:09Z</dc:date>
    <item>
      <title>rootconf is corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074454#M439280</link>
      <description>ISL booting  hpux&lt;BR /&gt;&lt;BR /&gt;Boot&lt;BR /&gt;: disk(1/0/0/3/0.6.0.0.0.0.0;0)/stand/vmunix&lt;BR /&gt;10240000 + 1822720 + 7750944 start 0x1f5ce8&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;LVM: /stand/rootconf is corrupted&lt;BR /&gt;gate64: sysvec_vaddr = 0xc0002000 for 2 pages&lt;BR /&gt;NOTICE: autofs_link(): File system was registered at index 3.&lt;BR /&gt;NOTICE: cachefs_link(): File system was registered at index 5.&lt;BR /&gt;NOTICE: nfs3_link(): File system was registered at index 6.&lt;BR /&gt;&lt;BR /&gt;    System Console is on the Built-In Serial Interface&lt;BR /&gt;igelan0: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 1/0/1/0/0/4/0&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Oct 2007 10:31:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074454#M439280</guid>
      <dc:creator>Fernando Boza</dc:creator>
      <dc:date>2007-10-16T10:31:23Z</dc:date>
    </item>
    <item>
      <title>Re: rootconf is corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074455#M439281</link>
      <description>Do you have an ignite tape?  Might be time for that!!&lt;BR /&gt;&lt;BR /&gt;thx</description>
      <pubDate>Tue, 16 Oct 2007 10:37:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074455#M439281</guid>
      <dc:creator>Ron Irving</dc:creator>
      <dc:date>2007-10-16T10:37:01Z</dc:date>
    </item>
    <item>
      <title>Re: rootconf is corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074456#M439282</link>
      <description>Any change booting to single user works?&lt;BR /&gt;I found this doc on how to recreate it:&lt;BR /&gt;&lt;A href="http://h50069.www5.hp.com/e-Delivery3/Forum/Others/UpLoadFiles/99883/vfs_mountroot.txt" target="_blank"&gt;http://h50069.www5.hp.com/e-Delivery3/Forum/Others/UpLoadFiles/99883/vfs_mountroot.txt&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;But you have to get the server up to the point you can fix it.  &lt;BR /&gt;&lt;BR /&gt;Search for "Bad or old data in /stand/rootconf using JFS as root filesystem&lt;BR /&gt;"  within that document.&lt;BR /&gt;&lt;BR /&gt;Which version of hpux is it?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Ignite might be the only solution.  It sounds like it can happen for a few different reasons.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 16 Oct 2007 10:38:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074456#M439282</guid>
      <dc:creator>Dave Hutton</dc:creator>
      <dc:date>2007-10-16T10:38:09Z</dc:date>
    </item>
    <item>
      <title>Re: rootconf is corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074457#M439283</link>
      <description>The document you were pointed at is just the right one, i keep it on my desktop ever since i got into that situation.&lt;BR /&gt;&lt;BR /&gt;recovering the rootconf manually is a REALLY frustrating process, so if you have a backup, and it's not a comfy winter evening with much curiosity and nothing else to do, go straight for a recover. either using the rescue mode of the installation cd, or simply ignite.&lt;BR /&gt;&lt;BR /&gt;if you have a backup of the rootconf easily accessible and don't like the rescue mode, you could also attach your vg00 disks to another host and vgimport it to copy in the file.&lt;BR /&gt;&lt;BR /&gt;for your tests, boot to LVM mainteanance mode using hpux -lm at the ISL/EFI prompt to keep boot times low.</description>
      <pubDate>Tue, 16 Oct 2007 12:43:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074457#M439283</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2007-10-16T12:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: rootconf is corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074458#M439284</link>
      <description>Ummm, and for clarity, I think neither single user or LVM maint. mode will work now.&lt;BR /&gt;&lt;BR /&gt;Single user would need successful vg00 activation, and LVM maint. mode needs this very rootconf (and the bootconf if booting off a mirror disk) to mount /dev/root without activating vg00.&lt;BR /&gt;&lt;BR /&gt;any ideas on reaching the SHC people to add a check for rootconf and bootconf validity?</description>
      <pubDate>Tue, 16 Oct 2007 12:59:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074458#M439284</guid>
      <dc:creator>Florian Heigl (new acc)</dc:creator>
      <dc:date>2007-10-16T12:59:24Z</dc:date>
    </item>
    <item>
      <title>Re: rootconf is corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074459#M439285</link>
      <description>I chose the way more secure. I recovered ignite. &lt;BR /&gt;Thanks to all</description>
      <pubDate>Tue, 16 Oct 2007 13:16:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/rootconf-is-corrupted/m-p/5074459#M439285</guid>
      <dc:creator>Fernando Boza</dc:creator>
      <dc:date>2007-10-16T13:16:09Z</dc:date>
    </item>
  </channel>
</rss>

