<?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: corrupt filesystem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212604#M586965</link>
    <description>You should never boot from LM mode to any higher level - do always a reboot.&lt;BR /&gt;Did you run any lvlnboot (-d -r -b) command?&lt;BR /&gt;&lt;BR /&gt;Maybe this is the problem.&lt;BR /&gt;&lt;BR /&gt;IMHO you should start over now.</description>
    <pubDate>Sun, 08 Jun 2008 12:23:32 GMT</pubDate>
    <dc:creator>Torsten.</dc:creator>
    <dc:date>2008-06-08T12:23:32Z</dc:date>
    <item>
      <title>corrupt filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212599#M586960</link>
      <description>i have a server with hpux 11.11 installed. i did an lvextend to the root "/" filesystem on maintenance mode "hpux -lm". This is the procedure i followed:&lt;BR /&gt;1- interrupt BCH&lt;BR /&gt;2- bo&lt;BR /&gt;3- interact with IPL/ISL: y&lt;BR /&gt;   hpux -lm&lt;BR /&gt;4- pvmove /dev/dsk/c0t5d0 /dev/dsk/c0t6d0 /dev/vg00/lvol4&lt;BR /&gt;where lvol4 is the "/tmp" and both disk belong to the same volume group vg00&lt;BR /&gt;5- lvextend -L 500 /dev/vg00/lvol3&lt;BR /&gt;6- extendfs /dev/vg00/lvol3&lt;BR /&gt;7- i was forced to run an fsck and it said filesystem clean and all is well, and it was successfully extended, i moved up to run level 3 and made an lvdisplay and lvlnboot -v and found everything normal and mounted. &lt;BR /&gt;when i made a reboot "shutdown -ry 0" the system crashed made a crash dump and displayed several errors and warnings one of the is that the super block size is wrong and a full fsck need to be run. and the server reboots.&lt;BR /&gt;i tried logging in single user mode but i couldn't. is there any way i can log in to the system and fix this? thank you.</description>
      <pubDate>Sun, 08 Jun 2008 09:26:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212599#M586960</guid>
      <dc:creator>Sherif A. Louis</dc:creator>
      <dc:date>2008-06-08T09:26:23Z</dc:date>
    </item>
    <item>
      <title>Re: corrupt filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212600#M586961</link>
      <description>You can recover it and extend root (/) with  the latest Ignite archive.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;ivan</description>
      <pubDate>Sun, 08 Jun 2008 11:56:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212600#M586961</guid>
      <dc:creator>Ivan Krastev</dc:creator>
      <dc:date>2008-06-08T11:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: corrupt filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212601#M586962</link>
      <description>it was a fresh installation, and i installed oracle and was preparing for the OVO installation. but needed to extend the root for the OVO. i know i should of taken an ignite!!&lt;BR /&gt;any other solution?</description>
      <pubDate>Sun, 08 Jun 2008 11:59:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212601#M586962</guid>
      <dc:creator>Sherif A. Louis</dc:creator>
      <dc:date>2008-06-08T11:59:59Z</dc:date>
    </item>
    <item>
      <title>Re: corrupt filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212602#M586963</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You could try to boot from dvd and try to repair the root filesystem, but it could be faster to reinstall from scratch. I would go for the second option.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Sun, 08 Jun 2008 12:15:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212602#M586963</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2008-06-08T12:15:37Z</dc:date>
    </item>
    <item>
      <title>Re: corrupt filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212603#M586964</link>
      <description>i am preparing for the second option!!&lt;BR /&gt;&lt;BR /&gt;so what went exactly wrong? did i corrupt the superblock data by initiating an init 3?&lt;BR /&gt;or was it something in the extension steps?</description>
      <pubDate>Sun, 08 Jun 2008 12:22:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212603#M586964</guid>
      <dc:creator>Sherif A. Louis</dc:creator>
      <dc:date>2008-06-08T12:22:38Z</dc:date>
    </item>
    <item>
      <title>Re: corrupt filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212604#M586965</link>
      <description>You should never boot from LM mode to any higher level - do always a reboot.&lt;BR /&gt;Did you run any lvlnboot (-d -r -b) command?&lt;BR /&gt;&lt;BR /&gt;Maybe this is the problem.&lt;BR /&gt;&lt;BR /&gt;IMHO you should start over now.</description>
      <pubDate>Sun, 08 Jun 2008 12:23:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212604#M586965</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2008-06-08T12:23:32Z</dc:date>
    </item>
    <item>
      <title>Re: corrupt filesystem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212605#M586966</link>
      <description>Hi Louis,&lt;BR /&gt;&lt;BR /&gt;Booting to lvm maintenance mode, hpux -lm, is only done in very specific (recovery) cases and not developed with "increasing" the rootfilesystem in mind, ignite on the otherhand was specifically developed as a way to increase the rootfilesystem in a supported way.  &lt;BR /&gt;&lt;BR /&gt;So yeah, ignite is, the way to go..&lt;BR /&gt;&lt;BR /&gt;Greetz,&lt;BR /&gt;Chris&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Jun 2008 08:53:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/corrupt-filesystem/m-p/4212605#M586966</guid>
      <dc:creator>chris huys_4</dc:creator>
      <dc:date>2008-06-16T08:53:00Z</dc:date>
    </item>
  </channel>
</rss>

