<?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: root lvm corrupted in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174521#M50745</link>
    <description>Go to rescue mode using the RHEL installation CD with the boot option:&lt;BR /&gt;&lt;BR /&gt;linux rescue&lt;BR /&gt;&lt;BR /&gt;if vg00 not getting mounted automaically.&lt;BR /&gt;&lt;BR /&gt;2.Try to activate the volume groups by running the commands below:&lt;BR /&gt;&lt;BR /&gt;lvmdiskscan&lt;BR /&gt;vgchange -ay&lt;BR /&gt;&lt;BR /&gt;3.If vg00 is acitaved Further fsck test can be done using:&lt;BR /&gt;&lt;BR /&gt;tune2fs -l /dev/vg00/lv01 | grep Block&lt;BR /&gt;&lt;BR /&gt;Take note of the Block size.&lt;BR /&gt;&lt;BR /&gt;e2fsck -b &lt;BLOCK_SIZE&gt; -n /dev/vg00/lv01&lt;BR /&gt;&lt;/BLOCK_SIZE&gt;</description>
    <pubDate>Wed, 13 May 2009 14:36:53 GMT</pubDate>
    <dc:creator>skt_skt</dc:creator>
    <dc:date>2009-05-13T14:36:53Z</dc:date>
    <item>
      <title>root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174514#M50738</link>
      <description>Hello friends,&lt;BR /&gt;&lt;BR /&gt;i am having system which configured with Lvm, somehow it has not shutdown properly and root file system has corrupted which is in lvm. &lt;BR /&gt;&lt;BR /&gt;the root file system is /dev/mapper/VolGroup00-LogVol00 /root&lt;BR /&gt;&lt;BR /&gt;when start it throw error /dev/mapper/VolGroup00-LogVol00 corrupted do fource fsck for this, &lt;BR /&gt;how we can do fsck for this and make it work.&lt;BR /&gt;&lt;BR /&gt;Os= Enterprise Linux WS release 4 &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 May 2009 02:29:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174514#M50738</guid>
      <dc:creator>avizen9</dc:creator>
      <dc:date>2009-05-12T02:29:24Z</dc:date>
    </item>
    <item>
      <title>Re: root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174515#M50739</link>
      <description>Hi Avizen,&lt;BR /&gt;1. Do not ever run forced FSCK on a mounted file system.&lt;BR /&gt;&lt;BR /&gt;2. Yes if it is a minor error fsck-ext3 will help you out most of the time.&lt;BR /&gt;&lt;BR /&gt;use install medial and boot this system to emergency mode.(type linux emergency on the splash screen prompt) this will bring the system up and by default it will not mount any file systems on fstab.&lt;BR /&gt;This is the safest way that you can fsck.&lt;BR /&gt;&lt;BR /&gt;Good Luck...!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 May 2009 02:44:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174515#M50739</guid>
      <dc:creator>Nuwan Alwis</dc:creator>
      <dc:date>2009-05-12T02:44:36Z</dc:date>
    </item>
    <item>
      <title>Re: root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174516#M50740</link>
      <description>so only fsck-ext3 will ok or we need to provide full path? &lt;BR /&gt;&lt;BR /&gt;fsck-ext3 /dev/hda etc...</description>
      <pubDate>Tue, 12 May 2009 02:47:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174516#M50740</guid>
      <dc:creator>avizen9</dc:creator>
      <dc:date>2009-05-12T02:47:30Z</dc:date>
    </item>
    <item>
      <title>Re: root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174517#M50741</link>
      <description>Hi,&lt;BR /&gt;Yes, it should.&lt;BR /&gt;my recomendation is first just run the fsck-ext3 and see if it works.&lt;BR /&gt;fsck -p was a good option for me when i had these kind of problems.&lt;BR /&gt;&lt;BR /&gt;any way its good to have a copy of /etc/lvm/*&lt;BR /&gt;&lt;BR /&gt;Good Luck..!</description>
      <pubDate>Tue, 12 May 2009 03:02:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174517#M50741</guid>
      <dc:creator>Nuwan Alwis</dc:creator>
      <dc:date>2009-05-12T03:02:51Z</dc:date>
    </item>
    <item>
      <title>Re: root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174518#M50742</link>
      <description>You don't need the installation media, you can just boot in emergency mode. As long the file system is mounted in read only mode, you have no risks.&lt;BR /&gt;&lt;BR /&gt;Boot appending the "emergency" option in GRUB.&lt;BR /&gt;&lt;BR /&gt;If you boot with the installation media, don't run fsck to the partition, you must activate the LVM volume group and run fsck to the logical volume.</description>
      <pubDate>Tue, 12 May 2009 05:31:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174518#M50742</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2009-05-12T05:31:11Z</dc:date>
    </item>
    <item>
      <title>Re: root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174519#M50743</link>
      <description>Dear Avizen&lt;BR /&gt;&lt;BR /&gt;I believe that you can do this in Linux rescue from your OS install disk if LVM is supported.&lt;BR /&gt;&lt;BR /&gt;Once Knoppix is booted, open a command prompt and type the following.&lt;BR /&gt;&lt;BR /&gt;# lvm vgchange --ignorelockingfailure -P -a y&lt;BR /&gt;&lt;BR /&gt;This will make this LVM volumes available. See the lvm(8) - Linux man page for a description of these switches. &lt;BR /&gt;&lt;BR /&gt;Then type&lt;BR /&gt;&lt;BR /&gt;# lvm lvs&lt;BR /&gt; to display the logical volumes.&lt;BR /&gt;&lt;BR /&gt;The devices should be listed in /dev ie: /dev/VolGroup00/LogVol100.&lt;BR /&gt;&lt;BR /&gt;At this point you should be able to run fsck on the logical volume by typing the following with your logical volume name of course.&lt;BR /&gt;&lt;BR /&gt;# fsck /dev/VolGroup00/LogVol100&lt;BR /&gt;Remember to always shutdown Linux properly so that the file systems donâ  t get corrupted.&lt;BR /&gt;&lt;BR /&gt;Use something like&lt;BR /&gt; &lt;BR /&gt;shutdown -h now&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 12 May 2009 10:12:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174519#M50743</guid>
      <dc:creator>Sajjad Sahir</dc:creator>
      <dc:date>2009-05-12T10:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174521#M50745</link>
      <description>Go to rescue mode using the RHEL installation CD with the boot option:&lt;BR /&gt;&lt;BR /&gt;linux rescue&lt;BR /&gt;&lt;BR /&gt;if vg00 not getting mounted automaically.&lt;BR /&gt;&lt;BR /&gt;2.Try to activate the volume groups by running the commands below:&lt;BR /&gt;&lt;BR /&gt;lvmdiskscan&lt;BR /&gt;vgchange -ay&lt;BR /&gt;&lt;BR /&gt;3.If vg00 is acitaved Further fsck test can be done using:&lt;BR /&gt;&lt;BR /&gt;tune2fs -l /dev/vg00/lv01 | grep Block&lt;BR /&gt;&lt;BR /&gt;Take note of the Block size.&lt;BR /&gt;&lt;BR /&gt;e2fsck -b &lt;BLOCK_SIZE&gt; -n /dev/vg00/lv01&lt;BR /&gt;&lt;/BLOCK_SIZE&gt;</description>
      <pubDate>Wed, 13 May 2009 14:36:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174521#M50745</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2009-05-13T14:36:53Z</dc:date>
    </item>
    <item>
      <title>Re: root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174522#M50746</link>
      <description>thanks</description>
      <pubDate>Fri, 22 May 2009 00:16:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174522#M50746</guid>
      <dc:creator>avizen9</dc:creator>
      <dc:date>2009-05-22T00:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174523#M50747</link>
      <description>what worked for u?</description>
      <pubDate>Fri, 22 May 2009 12:41:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174523#M50747</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2009-05-22T12:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: root lvm corrupted</title>
      <link>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174524#M50748</link>
      <description>&lt;BR /&gt;# lvm vgchange --ignorelockingfailure -P -a y&lt;BR /&gt;&lt;BR /&gt;# fsck /dev/VolGroup00/LogVol100&lt;BR /&gt;</description>
      <pubDate>Fri, 22 May 2009 14:06:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/root-lvm-corrupted/m-p/5174524#M50748</guid>
      <dc:creator>avizen9</dc:creator>
      <dc:date>2009-05-22T14:06:41Z</dc:date>
    </item>
  </channel>
</rss>

