<?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: Replacing a failed mirrored root disk online in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025370#M605474</link>
    <description>here is what i do and always work well.&lt;BR /&gt;&lt;BR /&gt;To list and verify the config file&lt;BR /&gt;&lt;BR /&gt;root [/root]   vgcfgrestore -n /dev/vg00 -l&lt;BR /&gt;Volume Group Configuration information in "/etc/lvmconf/vg00.conf"&lt;BR /&gt;VG Name /dev/vg00&lt;BR /&gt; ---- Physical volumes : 2 ----&lt;BR /&gt;    /dev/rdsk/c0t0d0 (Bootable)&lt;BR /&gt;    /dev/rdsk/c3t0d0 (Bootable)&lt;BR /&gt;&lt;BR /&gt;mkboot /dev/rdsk/c0t0d0&lt;BR /&gt;&lt;BR /&gt;mkboot -b /usr/lib/uxbootlf /dev/dsk/c0t0d0&lt;BR /&gt;Pvchange -a n /dev/dsk/c0t0d0&lt;BR /&gt;vgcfgrestore -F -n vg00 /dev/rdsk/c0t0d0&lt;BR /&gt;Pvchange -a y /dev/dsk/c0t0d0&lt;BR /&gt;vgchange -a y vg00&lt;BR /&gt;vgsync vg00&lt;BR /&gt;&lt;BR /&gt;lvlnboot -R&lt;BR /&gt;&lt;BR /&gt;for lif_comp in `lifls /dev/dsk/c3t0d0` &lt;BR /&gt;do&lt;BR /&gt;/usr/bin/lifcp /dev/dsk/c3t0d0:${lif_comp} /dev/dsk/c0t0d0:${lif_comp}&lt;BR /&gt;</description>
    <pubDate>Sun, 24 Jun 2007 14:28:10 GMT</pubDate>
    <dc:creator>skt_skt</dc:creator>
    <dc:date>2007-06-24T14:28:10Z</dc:date>
    <item>
      <title>Replacing a failed mirrored root disk online</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025366#M605470</link>
      <description>Hello all,&lt;BR /&gt;   I had gone through the steps for &lt;BR /&gt;"replacing a failed mirrored root disk" posted by different members of this forum.&lt;BR /&gt;I would like to clarify the below :&lt;BR /&gt;1) Someone says after replacing the disk, do a "pvcreate" on the new disk and then "vgcfgrestore" and next steps (vgchange,vgsync etc )&lt;BR /&gt;2)Others say replace the disk, do a vgcfgrestore ( NO pvcreate) and next steps (vgchange,vgsync etc )&lt;BR /&gt;&lt;BR /&gt;         So which one is correct ? ( OR both are correct ? )&lt;BR /&gt;&lt;BR /&gt;      Will LVM allow to do a pvcreate as the disk entry is already there in /etc/lvmtab under vg00 ?( I am using a disk with same target number)&lt;BR /&gt;  If the answer is NO, then I am again confused as the man page for pvcreate says "Disks cannot be added to a volume group until they are properly initialized by pvcreate "&lt;BR /&gt;      All responses are appreciated</description>
      <pubDate>Sat, 23 Jun 2007 03:58:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025366#M605470</guid>
      <dc:creator>akg_1</dc:creator>
      <dc:date>2007-06-23T03:58:02Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a failed mirrored root disk online</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025367#M605471</link>
      <description>Look at the HP's official word about disk replacement:&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf" target="_blank"&gt;http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;(Chapter 6 is about replacing a failed disk. Note that chapter 5 is about removing a failed disk when you *don't* intend to replace it.)&lt;BR /&gt;&lt;BR /&gt;The essential question is, did you use lvreduce and/or vgreduce before removing the failed disk or not?&lt;BR /&gt;&lt;BR /&gt;(If your OS version and patchlevel is such that you have the LVM OLR functionality available, you can prevent the LVM from accessing the disk while you're replacing it with "pvchange -a N". If your OS is so old it does not have this facility, you should lvreduce &amp;amp; vgreduce the failed disk out of its volume group before hot-unplugging the actual disk.)&lt;BR /&gt;&lt;BR /&gt;If you did lvreduce &amp;amp; vgreduce the disk out of VG configuration before replacing the disk, "vgcfgrestore" is not going to do anything useful, as the saved configuration will not include this disk anymore. You must proceed just like when mirroring a root disk for the first time: &lt;BR /&gt;- "pvcreate" to make the new disk a LVM disk (don't forget the -B option for PA-RISC root disks!)&lt;BR /&gt;- "mkboot" to install the bootloader (the boot area is outside the LVM area, so it is not mirrored automatically)&lt;BR /&gt;You might install the off-line diagnostics to the boot area too, if you use them.&lt;BR /&gt;- "vgextend" to join the disk to the volume group&lt;BR /&gt;- "lvextend -m 1" to mirror each logical volume&lt;BR /&gt;- "lvlnboot" to update the LVM boot configuration&lt;BR /&gt;&lt;BR /&gt;If you did not lvreduce &amp;amp; vgreduce before replacing the disk, you can use vgcfgrestore.&lt;BR /&gt;In this case, vgcfgrestore will make the new disk configured exactly the same as the original was (from the LVM viewpoint): the VG membership and the mirror configuration of each LV will be restored to the new disk. However, the actual data will still be (extremely) out of sync: vgcfgrestore will restore just the LVM configuration, not the data.&lt;BR /&gt;&lt;BR /&gt;After the vgcfgrestore, you must enable LVM access to the disk with "pvchange -a y" (if it was disabled either manually or automatically because of the disk failure).&lt;BR /&gt;After that, the LVM should automatically start synchronizing the LVs. If that does not happen, you can use "vgsync" or "lvsync" to force the synchronization.&lt;BR /&gt;&lt;BR /&gt;The boot area must also be restored independently of LVM, just as above.&lt;BR /&gt;You should be able to run "mkboot" at any time after the vgcfgrestore, but the "lvlnboot" should be run only after the three boot-critical LVs (lvols 1-3: /stand, swap and root) have completed synchronization. &lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Sat, 23 Jun 2007 05:17:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025367#M605471</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2007-06-23T05:17:56Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a failed mirrored root disk online</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025368#M605472</link>
      <description>All was said already, I will just add - if that is itanium system, then do not forget about partitioning the drive (idisk, three partitions) and also about the fact, that lvm works with cXtYdZs2 partition and not the whole cXtYdZ as is on parisc systems.</description>
      <pubDate>Sun, 24 Jun 2007 07:16:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025368#M605472</guid>
      <dc:creator>MHudec</dc:creator>
      <dc:date>2007-06-24T07:16:42Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a failed mirrored root disk online</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025369#M605473</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Note that many newer Itanium systems offer hardware raid cards. If your system is configured with hardware raid, you need to merely replace the disk.&lt;BR /&gt;&lt;BR /&gt;I believe that which of your two steps in a software raid scenario are correct depends on what your response was when the disk went bad.&lt;BR /&gt;&lt;BR /&gt;If you caught it before it died and split the mirrors then you start with pvcreate and don't do vgcfgrestore at all.&lt;BR /&gt;&lt;BR /&gt;More commonly the pvcreate/vgcfgrestore path is what needs to be done because the disk was totally dead before any action was taken.&lt;BR /&gt;&lt;BR /&gt;pvcreate is needed to prepare the disk for any use t all. Option 2 will fail if pvcreate is required. Then go with option 1. I always go for some version of option 1. preparing the disk never hurts even if technically not needed.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Sun, 24 Jun 2007 13:21:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025369#M605473</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-06-24T13:21:53Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a failed mirrored root disk online</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025370#M605474</link>
      <description>here is what i do and always work well.&lt;BR /&gt;&lt;BR /&gt;To list and verify the config file&lt;BR /&gt;&lt;BR /&gt;root [/root]   vgcfgrestore -n /dev/vg00 -l&lt;BR /&gt;Volume Group Configuration information in "/etc/lvmconf/vg00.conf"&lt;BR /&gt;VG Name /dev/vg00&lt;BR /&gt; ---- Physical volumes : 2 ----&lt;BR /&gt;    /dev/rdsk/c0t0d0 (Bootable)&lt;BR /&gt;    /dev/rdsk/c3t0d0 (Bootable)&lt;BR /&gt;&lt;BR /&gt;mkboot /dev/rdsk/c0t0d0&lt;BR /&gt;&lt;BR /&gt;mkboot -b /usr/lib/uxbootlf /dev/dsk/c0t0d0&lt;BR /&gt;Pvchange -a n /dev/dsk/c0t0d0&lt;BR /&gt;vgcfgrestore -F -n vg00 /dev/rdsk/c0t0d0&lt;BR /&gt;Pvchange -a y /dev/dsk/c0t0d0&lt;BR /&gt;vgchange -a y vg00&lt;BR /&gt;vgsync vg00&lt;BR /&gt;&lt;BR /&gt;lvlnboot -R&lt;BR /&gt;&lt;BR /&gt;for lif_comp in `lifls /dev/dsk/c3t0d0` &lt;BR /&gt;do&lt;BR /&gt;/usr/bin/lifcp /dev/dsk/c3t0d0:${lif_comp} /dev/dsk/c0t0d0:${lif_comp}&lt;BR /&gt;</description>
      <pubDate>Sun, 24 Jun 2007 14:28:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025370#M605474</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-06-24T14:28:10Z</dc:date>
    </item>
    <item>
      <title>Re: Replacing a failed mirrored root disk online</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025371#M605475</link>
      <description>Thank you for your responses&lt;BR /&gt;I am aware of the official procedure to replace the disk (lvreduce,vgreduce,pvcreate......) and also about the "idisk" partitioning on itanium servers&lt;BR /&gt;&lt;BR /&gt;But I am confused about the procedures suggested by different forum members as I said first&lt;BR /&gt;The situation is that Disk is completely dead and hot swappable and no OLR is installed&lt;BR /&gt;&lt;BR /&gt;Someone in this forum said to unplug the disk and straight away do a "vgcfgrestore" followed by next steps&lt;BR /&gt; While others said to do a "pvcreate -fB" first and then "vgcfgrestore" followed by next steps&lt;BR /&gt;So my question is, in the above situation a pvcreate is possible or NOT as the disk entry is already there in /etc/lvmtab ?&lt;BR /&gt;and if pvcreate is not required, is it going to work ?</description>
      <pubDate>Sun, 24 Jun 2007 14:52:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replacing-a-failed-mirrored-root-disk-online/m-p/4025371#M605475</guid>
      <dc:creator>akg_1</dc:creator>
      <dc:date>2007-06-24T14:52:51Z</dc:date>
    </item>
  </channel>
</rss>

