<?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: Activate volume group on boot in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062950#M6490</link>
    <description>Paulo's post makes it obvious that with lvm comes the vgchagne command.&lt;BR /&gt;&lt;BR /&gt;Thats how to activate the vg.&lt;BR /&gt;&lt;BR /&gt;It should stay active after 1 or 100 boots.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Wed, 03 Sep 2003 17:07:00 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2003-09-03T17:07:00Z</dc:date>
    <item>
      <title>Activate volume group on boot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062946#M6486</link>
      <description>I have a system (rs5670, Red Har AS 2.1) on which I have defined a 2TB logical volume.  The lv appears to be working, except that when I boot the server, the volume group is not activated and I get an error when I try to mount the volume.  I can boot without mounting the volume and use vgchange to activate the volume group.  I can then mount the logical volume.&lt;BR /&gt;&lt;BR /&gt;What am I missing in getting the group to activate properly on boot.  This is suppose to be the default as I understand it.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Tom</description>
      <pubDate>Wed, 03 Sep 2003 15:22:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062946#M6486</guid>
      <dc:creator>Thomas Soukup</dc:creator>
      <dc:date>2003-09-03T15:22:39Z</dc:date>
    </item>
    <item>
      <title>Re: Activate volume group on boot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062947#M6487</link>
      <description>take a look at /etc/fstab&lt;BR /&gt;&lt;BR /&gt;You probably need an entry there to insure that the vg and filesystems get mounted at boot time.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 03 Sep 2003 15:33:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062947#M6487</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-09-03T15:33:26Z</dc:date>
    </item>
    <item>
      <title>Re: Activate volume group on boot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062948#M6488</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I've never used LVM on Red Hat but I have on nearly everything else.  Start up scripts generally don't activate volume groups like they do on HP-UX.&lt;BR /&gt;&lt;BR /&gt;Every system I have seen on Linux does a vgscan somewhere in the startup scripts and then do a vgchange -ay to activate discovered volume groups.. &lt;BR /&gt;&lt;BR /&gt;Of course, you don't have to do it this way.  You could emulate other unix's by writing a script to look for filesystems in /etc/fstab and cross referencing them with /etc/lvmtab and activate the resulting volume  groups.  You could then put this script in the startup script directory.&lt;BR /&gt;&lt;BR /&gt;On the other hand, in many cases, with linux, the vgscan appraoch works fine.&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Wed, 03 Sep 2003 16:24:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062948#M6488</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2003-09-03T16:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: Activate volume group on boot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062949#M6489</link>
      <description>This is what Mandrake 9.1 does. It's in /etc/rc.d/sysinit:&lt;BR /&gt;&lt;BR /&gt;# LVM initialization&lt;BR /&gt;if [ -f /etc/lvmtab -a ! -e /proc/lvm ] ; then&lt;BR /&gt;        modprobe lvm-mod &amp;gt;/dev/null 2&amp;gt;&amp;amp;1&lt;BR /&gt;fi&lt;BR /&gt;if [ -e /proc/lvm -a -x /sbin/vgchange -a -f /etc/lvmtab ]; then&lt;BR /&gt;        action "Setting up Logical Volume Management:" /sbin/vgscan &amp;amp;&amp;amp; /sbin/vgchange -a y&lt;BR /&gt;fi&lt;BR /&gt;&lt;BR /&gt;Probably you have to modify your rc.sysinit or update your initscripts package.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;Paulo Fessel</description>
      <pubDate>Wed, 03 Sep 2003 16:30:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062949#M6489</guid>
      <dc:creator>Paulo A G Fessel</dc:creator>
      <dc:date>2003-09-03T16:30:39Z</dc:date>
    </item>
    <item>
      <title>Re: Activate volume group on boot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062950#M6490</link>
      <description>Paulo's post makes it obvious that with lvm comes the vgchagne command.&lt;BR /&gt;&lt;BR /&gt;Thats how to activate the vg.&lt;BR /&gt;&lt;BR /&gt;It should stay active after 1 or 100 boots.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 03 Sep 2003 17:07:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062950#M6490</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-09-03T17:07:00Z</dc:date>
    </item>
    <item>
      <title>Re: Activate volume group on boot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062951#M6491</link>
      <description>Tom,&lt;BR /&gt;are you using lvm + raid? AFAIK, this happen to me before, I got around it by hacking the startup script.  Apparently there's an error a bug in the start up script. LVM failed to activate because of if else clause which test for raid and lvm, it doesn't detect it correctly so it just wooosh over it. Hope this help.&lt;BR /&gt;</description>
      <pubDate>Wed, 03 Sep 2003 18:14:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062951#M6491</guid>
      <dc:creator>K.C. Chan</dc:creator>
      <dc:date>2003-09-03T18:14:46Z</dc:date>
    </item>
    <item>
      <title>Re: Activate volume group on boot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062952#M6492</link>
      <description>Hi Tom,&lt;BR /&gt;&lt;BR /&gt;Paulo hit on the problem - under RH there is no "modprobe lvm-mod" in the "/etc/rc.sysinit" file.&lt;BR /&gt;&lt;BR /&gt;Simply add the command as shown in the example by Paulo and this will work fine.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;&lt;BR /&gt;Ollie.</description>
      <pubDate>Tue, 09 Sep 2003 03:37:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/activate-volume-group-on-boot/m-p/3062952#M6492</guid>
      <dc:creator>Ollie R</dc:creator>
      <dc:date>2003-09-09T03:37:13Z</dc:date>
    </item>
  </channel>
</rss>

