<?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: Mirrored disc has crashed in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695942#M248262</link>
    <description>Hi Mark,&lt;BR /&gt; Procedure to replace a root disk is as follows&lt;BR /&gt;&lt;BR /&gt;ISL&amp;gt; hpux -lq&lt;BR /&gt;# pvcreate -f -B /dev/rdsk/cXtXd0&lt;BR /&gt;pvcreate: The physical volume "/dev/dsk/c4t6d0" is already recorded in&lt;BR /&gt;the "/etc/lvmtab" file.&lt;BR /&gt;&lt;BR /&gt;# vgcfgrestore -n /dev/vg00 /dev/rdsk/cXtXd0&lt;BR /&gt;vgcfgrestore: Couldn't query physical volume "/dev/dsk/c4t6d0":&lt;BR /&gt;&lt;BR /&gt;# mkboot /dev/rdsk/cXtXdX &lt;BR /&gt;&lt;BR /&gt;# mkboot -a "hpux -lq" /dev/rdsk/cXtXdX &lt;BR /&gt;&lt;BR /&gt;# vgchange -a y /dev/vg00&lt;BR /&gt;Volume group "/dev/vg00" has been successfully changed. &lt;BR /&gt;&lt;BR /&gt;#vgsync /dev/vg00&lt;BR /&gt;&lt;BR /&gt;To verify offline diagnostics are installed on root and mirror disks: &lt;BR /&gt;# lifls -il /dev/rdsk/cXtXd0 &lt;BR /&gt;&lt;BR /&gt;To download offline diagnostics:&lt;BR /&gt; # cd /usr/sbin/diag/lif &lt;BR /&gt;&lt;BR /&gt;if server is a K-Class: &lt;BR /&gt;# mkboot -b updatediaglif -p ISL -p HPUX -p LABEL -p AUTO /dev/rdsk/cXtXd0 &lt;BR /&gt;&lt;BR /&gt;if server is a L/N/V/RP Class: &lt;BR /&gt;# mkboot -b updatediaglif2 -p ISL -p HPUX -p LABEL -p AUTO /dev/rdsk/cXtXd0 &lt;BR /&gt;&lt;BR /&gt;# lvlnboot -Rv /dev/vg00&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Please find the attached documents also for reference..&lt;BR /&gt;&lt;BR /&gt;Hope this will help ..&lt;BR /&gt;&lt;BR /&gt;Shameer</description>
    <pubDate>Thu, 29 Dec 2005 06:35:10 GMT</pubDate>
    <dc:creator>Shameer.V.A</dc:creator>
    <dc:date>2005-12-29T06:35:10Z</dc:date>
    <item>
      <title>Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695932#M248252</link>
      <description>Hi everybody.&lt;BR /&gt;&lt;BR /&gt;Why does this happen just before Christmas?&lt;BR /&gt;&lt;BR /&gt;A disc in a Surestore SC10 has crashed. The disc is mirrored, so the users are still working without any problems, but I have made arrangements to have a replacement disc sent to my house (too late for it to be sent to work). When it arrives I am going to come into work to install it. I don't expect problems, but if I do have problems there may not be any people on the forum to help me, so I'll ask about the potential pitfalls in advance.&lt;BR /&gt;&lt;BR /&gt;I've read all sorts of things on here about breaking mirrors - I haven't broken the mirror on this system because the system seems to be working and I don't see the point in changing things that are working. Do I need to do this before I install the replacement disc?&lt;BR /&gt;&lt;BR /&gt;When I install the new disc, do I simply run ioscan and wait for the two mirrors to sync with each other or is there more to it than that?&lt;BR /&gt;&lt;BR /&gt;All attempts to help will be rewarded with points, but please be patient - you may have to wait till January so I can assess exactly how much help each answer has been.&lt;BR /&gt;&lt;BR /&gt;Mark Syder (like the drink but spelt different)</description>
      <pubDate>Wed, 21 Dec 2005 08:58:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695932#M248252</guid>
      <dc:creator>MarkSyder</dc:creator>
      <dc:date>2005-12-21T08:58:45Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695933#M248253</link>
      <description>Hi Mark,&lt;BR /&gt;&lt;BR /&gt;If the mirroring is done well, you can recreate is with&lt;BR /&gt;&lt;BR /&gt;pvcreate -f /dev/rdsk/cxtydz&lt;BR /&gt;vgcfgrestore /dev/vgxx&lt;BR /&gt;vgsync /dev/vgxx</description>
      <pubDate>Wed, 21 Dec 2005 09:06:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695933#M248253</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2005-12-21T09:06:41Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695934#M248254</link>
      <description>I assume it's a non-vg00 disk.  So:&lt;BR /&gt;&lt;BR /&gt;# vgcfgrestore -n vg?? /dev/rdsk/c?t?d?&lt;BR /&gt;# vgchange -a y vg??&lt;BR /&gt;# vgsync vg??</description>
      <pubDate>Wed, 21 Dec 2005 09:11:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695934#M248254</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2005-12-21T09:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695935#M248255</link>
      <description>Hi Mark:&lt;BR /&gt;&lt;BR /&gt;If you are sure about which mirror is failing, I'd break each logical volume's mirror:&lt;BR /&gt;&lt;BR /&gt;# lvreduce -m 0 /dev/vgNN/lvolN /dev/dsk/cXtYdZ'&lt;BR /&gt;&lt;BR /&gt;...and then 'vgreduce' the physical volume from the volume group.&lt;BR /&gt;&lt;BR /&gt;When you, replace the disk, 'vgextend' the new physical volume (after a 'pvcreate')  and 'lvextend' each logical volue to remirror.&lt;BR /&gt;&lt;BR /&gt;BTW, a new, execllent whitepaper on disk replacement is :&lt;BR /&gt;&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;Be sure that you install the appropriate LVM OLR (onlines-replacement) patches mentioned therein for optimal help.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 21 Dec 2005 09:11:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695935#M248255</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2005-12-21T09:11:47Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695936#M248256</link>
      <description>Since the disk has crashed (or otherwise not working), you are already unmirrored (stale extents in the terminology of lvdisplay -v). So with the SC10 (hot pluggble), you just pull out the bad disk, then put in the new one, make it available as an LVM disk with pvcreate, restore the LVM header information to the front of the disk with vgcfgrestore. Syncing won't occur automatically (except on a reboot) so you can manually sync each lvol with lvsync, or do it with one command: vgsync vgWhatever.</description>
      <pubDate>Wed, 21 Dec 2005 09:13:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695936#M248256</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-12-21T09:13:27Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695937#M248257</link>
      <description>Hi Mark&lt;BR /&gt;just in case, there is the DocId KBAN00000347&lt;BR /&gt;LVM: Procedure for replacing an LVM disk in HP-UX 10.x and 11.x DocId: KBAN00000347 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Excerpt:&lt;BR /&gt;CHAPTER 2 :     Replacing a NON-Boot disk WITH Mirroring&lt;BR /&gt;----------------------------------------------------------------------&lt;BR /&gt;&lt;BR /&gt;Mirroring introduces an interesting twist to the recovery process.&lt;BR /&gt;Because LVM keeps a map of 'stale' extents on each disk, it is only&lt;BR /&gt;aware of individual extents which are in need of update, and it does&lt;BR /&gt;not map this to entire disks.  This makes for quick mirror recovery in&lt;BR /&gt;the case that a disk has temporarily lost connection with the host, or&lt;BR /&gt;has lost power.  In addition, it can greatly speed up the recovery time&lt;BR /&gt;in the instance of a failed disk.&lt;BR /&gt;&lt;BR /&gt;Example configuration:&lt;BR /&gt;&lt;BR /&gt;  Volume group /dev/vg00 contains the three disks, with the logical&lt;BR /&gt;  volume configuration as shown:&lt;BR /&gt;&lt;BR /&gt;                          |---------|     |---------|     |---------|&lt;BR /&gt;                          | lvol 1  |     | lvol 4  |     | lvol 4  |&lt;BR /&gt;                          |---------|     |         |     | mirror  |&lt;BR /&gt;                          | lvol 2  |     |---------|     |---------|&lt;BR /&gt;                          |---------|     | lvol 5  |     | lvol 5  |&lt;BR /&gt;                          | lvol 3  |     |         |     | mirror  |&lt;BR /&gt;                          |---------|     |---------|     |---------|&lt;BR /&gt;&lt;BR /&gt;  hardware address          52.6.0          52.5.0          52.4.0&lt;BR /&gt;  device file (/dev/dsk/)   c0t6d0          c0t5d0          c0t4d0&lt;BR /&gt;&lt;BR /&gt;This involves a head crash on the disk at address 52.4.0.&lt;BR /&gt;&lt;BR /&gt;[Step 2.1]&lt;BR /&gt;&lt;BR /&gt;Have the customer engineer replace the faulty disk, and then boot the system.&lt;BR /&gt;You can boot the system into multi-user mode.  For logical volumes that&lt;BR /&gt;didn't have a mirror, and that resided on the replaced disk, you will&lt;BR /&gt;have to deny access to the filesystem.  Do this by unmounting the relevant&lt;BR /&gt;filesystems. (However, it's possible that they will not have been mounted as&lt;BR /&gt;part of the boot-up sequence anyway.)&lt;BR /&gt;&lt;BR /&gt;Note: If the disk being replaced is Hot-Pluggable (or Hot-Swappable) a&lt;BR /&gt;reboot may not be necessary.  Please inquire your customer engineer to&lt;BR /&gt;determine if a reboot is required.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;[Step 2.2]&lt;BR /&gt;&lt;BR /&gt;Restore the LVM configuration/headers onto the new disk from your&lt;BR /&gt;backup of the LVM configuration:&lt;BR /&gt;&lt;BR /&gt;  # vgcfgrestore -n [volume group name] /dev/rdsk/cXtYdZ&lt;BR /&gt;where X is the 'card instance number' of the scsi bus attached to&lt;BR /&gt;that card.  Y is the 'SCSI ID' of the disk (or array controller, in&lt;BR /&gt;the case of an array), and Z is the 'LUN number' (typically 0 for a&lt;BR /&gt;non-array type disk). Note that if an HP Customer Engineer replaces&lt;BR /&gt;the disk at the same address, the device file name will not change.&lt;BR /&gt;In that case the name will be what it was prior to the replacement.&lt;BR /&gt;For our example:&lt;BR /&gt;&lt;BR /&gt;  # vgcfgrestore -n /dev/vg00 /dev/rdsk/c0t4d0&lt;BR /&gt;&lt;BR /&gt;[Step 2.3]&lt;BR /&gt;&lt;BR /&gt;Reactivate the volume group so that the new disk can be attached,&lt;BR /&gt;since it wasn't configured in at boot time.  This should also resync&lt;BR /&gt;any mirrors that resided on the faulty disk.&lt;BR /&gt;&lt;BR /&gt;  # vgchange -a y [volume group name]&lt;BR /&gt;&lt;BR /&gt;For our example, the volume group vg00 will already be activated, but&lt;BR /&gt;it will not know of the replaced disk; therefore, this step is still&lt;BR /&gt;required so that LVM will now know that the disk is again available&lt;BR /&gt;and the resync will occur:&lt;BR /&gt;&lt;BR /&gt;  # vgchange -a y /dev/vg00&lt;BR /&gt;&lt;BR /&gt;Now check that the mirrors are syncronized, run this command for each&lt;BR /&gt;logical volume that resides on the replaced disk:&lt;BR /&gt;&lt;BR /&gt;    # lvdisplay -v /dev/vg00/lvol4 | more&lt;BR /&gt;    # lvdisplay -v /dev/vg00/lvol5 | more&lt;BR /&gt;&lt;BR /&gt;If any extents show up as being stale it is recommended to run a vgsync&lt;BR /&gt;or lvsync to force the syncronization of the mirrored extents using the&lt;BR /&gt;following commands:&lt;BR /&gt;&lt;BR /&gt;    # vgsync /dev/vg00&lt;BR /&gt;&lt;BR /&gt;or&lt;BR /&gt;&lt;BR /&gt;    # lvsync /dev/vg00/lvol4&lt;BR /&gt;    # lvsync /dev/vg00/lvol5&lt;BR /&gt;&lt;BR /&gt;[Step 2.4]&lt;BR /&gt;&lt;BR /&gt;For any file systems on the faulty disk that didn't have mirror copies,&lt;BR /&gt;you will have to rebuild the file systems and restore the data.  Follow&lt;BR /&gt;the steps 1.4 and 1.5 in chapter 1 for guidance.&lt;BR /&gt;&lt;BR /&gt;Step 2.5]&lt;BR /&gt;&lt;BR /&gt;If you booted your system into single-user mode in step 2.1, reboot&lt;BR /&gt;your system now and allow it to boot into multiuser mode.  If you were&lt;BR /&gt;already in multi-user mode, then no further action is required.&lt;BR /&gt;&lt;BR /&gt;At this stage, your system should be fully functioning.&lt;BR /&gt;&lt;BR /&gt;.....&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;All the best&lt;BR /&gt;Victor</description>
      <pubDate>Wed, 21 Dec 2005 09:15:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695937#M248257</guid>
      <dc:creator>Victor BERRIDGE</dc:creator>
      <dc:date>2005-12-21T09:15:34Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695938#M248258</link>
      <description>I agree will Bill on this.  I would add that after running vgcfgrestore, a vgchange -a y normally will kick off a vgsync automatically.  If not, certainly run vgsync.  If for some reason the disk is still 'claimed' in ioscan, I would break the mirror and reduce out the disk before replacing.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Eric</description>
      <pubDate>Wed, 21 Dec 2005 09:25:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695938#M248258</guid>
      <dc:creator>erics_1</dc:creator>
      <dc:date>2005-12-21T09:25:04Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695939#M248259</link>
      <description>Mark,&lt;BR /&gt;&lt;BR /&gt;If you haven't already, I'd look at&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;Deals w/ disk failures and LVM (from LVM team).&lt;BR /&gt;&lt;BR /&gt;I'd go ahead and break the mirror and remove the disk from the volume group, as recommended section 5.&lt;BR /&gt;&lt;BR /&gt;just my 2cents</description>
      <pubDate>Wed, 21 Dec 2005 12:44:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695939#M248259</guid>
      <dc:creator>OldSchool</dc:creator>
      <dc:date>2005-12-21T12:44:45Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695940#M248260</link>
      <description>Hi everybody.&lt;BR /&gt;&lt;BR /&gt;pvcreate fails because the disc is already in /etc/lvmtab. I follow the advice in the document and get the following result from pvdisplay /dev/dsk/c0t1d0:&lt;BR /&gt;&lt;BR /&gt;pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t1d0":&lt;BR /&gt;The specified path does not correspond to physical volume attached to &lt;BR /&gt;this volume group&lt;BR /&gt;pvdisplay: Warning: couldn't query all of the physical volumes.&lt;BR /&gt;pvdisplay: Couldn't retrieve the names of the physical volumes&lt;BR /&gt;belonging to volume group "/dev/vg03".&lt;BR /&gt;pvdisplay: Cannot display physical volume "/dev/dsk/c0t1d0".&lt;BR /&gt;&lt;BR /&gt;Guidance appreciated. I may be going home shortly - I've come in specially to do this - so I may not be able to act on your advice till tomorrow.&lt;BR /&gt;&lt;BR /&gt;Mark</description>
      <pubDate>Thu, 29 Dec 2005 05:48:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695940#M248260</guid>
      <dc:creator>MarkSyder</dc:creator>
      <dc:date>2005-12-29T05:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695941#M248261</link>
      <description>Hi Mark,&lt;BR /&gt;&lt;BR /&gt;I don't use to do this (that's HP job) but the process the HP Engineer runs its very similar to Bill's Hassel post.&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;&lt;BR /&gt;Eric Antunes&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Dec 2005 05:57:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695941#M248261</guid>
      <dc:creator>Eric Antunes</dc:creator>
      <dc:date>2005-12-29T05:57:04Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695942#M248262</link>
      <description>Hi Mark,&lt;BR /&gt; Procedure to replace a root disk is as follows&lt;BR /&gt;&lt;BR /&gt;ISL&amp;gt; hpux -lq&lt;BR /&gt;# pvcreate -f -B /dev/rdsk/cXtXd0&lt;BR /&gt;pvcreate: The physical volume "/dev/dsk/c4t6d0" is already recorded in&lt;BR /&gt;the "/etc/lvmtab" file.&lt;BR /&gt;&lt;BR /&gt;# vgcfgrestore -n /dev/vg00 /dev/rdsk/cXtXd0&lt;BR /&gt;vgcfgrestore: Couldn't query physical volume "/dev/dsk/c4t6d0":&lt;BR /&gt;&lt;BR /&gt;# mkboot /dev/rdsk/cXtXdX &lt;BR /&gt;&lt;BR /&gt;# mkboot -a "hpux -lq" /dev/rdsk/cXtXdX &lt;BR /&gt;&lt;BR /&gt;# vgchange -a y /dev/vg00&lt;BR /&gt;Volume group "/dev/vg00" has been successfully changed. &lt;BR /&gt;&lt;BR /&gt;#vgsync /dev/vg00&lt;BR /&gt;&lt;BR /&gt;To verify offline diagnostics are installed on root and mirror disks: &lt;BR /&gt;# lifls -il /dev/rdsk/cXtXd0 &lt;BR /&gt;&lt;BR /&gt;To download offline diagnostics:&lt;BR /&gt; # cd /usr/sbin/diag/lif &lt;BR /&gt;&lt;BR /&gt;if server is a K-Class: &lt;BR /&gt;# mkboot -b updatediaglif -p ISL -p HPUX -p LABEL -p AUTO /dev/rdsk/cXtXd0 &lt;BR /&gt;&lt;BR /&gt;if server is a L/N/V/RP Class: &lt;BR /&gt;# mkboot -b updatediaglif2 -p ISL -p HPUX -p LABEL -p AUTO /dev/rdsk/cXtXd0 &lt;BR /&gt;&lt;BR /&gt;# lvlnboot -Rv /dev/vg00&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;Please find the attached documents also for reference..&lt;BR /&gt;&lt;BR /&gt;Hope this will help ..&lt;BR /&gt;&lt;BR /&gt;Shameer</description>
      <pubDate>Thu, 29 Dec 2005 06:35:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695942#M248262</guid>
      <dc:creator>Shameer.V.A</dc:creator>
      <dc:date>2005-12-29T06:35:10Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695943#M248263</link>
      <description>You wrote:&lt;BR /&gt; &lt;BR /&gt;"pvcreate fails because the disc is already in /etc/lvmtab. I follow the advice in the document and get the following result from pvdisplay /dev/dsk/c0t1d0:&lt;BR /&gt; &lt;BR /&gt;pvdisplay: Warning: couldn't query physical volume "/dev/dsk/c0t1d0":&lt;BR /&gt;...&lt;BR /&gt; &lt;BR /&gt;pvcreate fails if the replacement disk has some LVM information. You have to force the LVM information with pvcreate -f. Then run vgcfgrestore to put back the correct information. The information above says pvdisplay "couldn't query" really means that this disk doesn't belong (yet) to the volume group. Once vgcfgrestore is complete, run vgchange to tie all the disks together and make sure vgsync is running.</description>
      <pubDate>Thu, 29 Dec 2005 06:48:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695943#M248263</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-12-29T06:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695944#M248264</link>
      <description>hi Mark,&lt;BR /&gt;&lt;BR /&gt;how about these steps;&lt;BR /&gt;mv /etc/lvmtab /etc/lvmtab.old&lt;BR /&gt;vgscan -av&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Dec 2005 07:39:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695944#M248264</guid>
      <dc:creator>Cem Tugrul</dc:creator>
      <dc:date>2005-12-29T07:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695945#M248265</link>
      <description>Don't do a pvcreate, because all information about the disk config is stored. Restore the config by&lt;BR /&gt;&lt;BR /&gt;# vgcfgrestore -n VGxx /dev/rdsk/cXtXdX&lt;BR /&gt;&lt;BR /&gt;and activate the vg:&lt;BR /&gt;&lt;BR /&gt;vgchange -a y vgxx&lt;BR /&gt;&lt;BR /&gt;now sync the vg:&lt;BR /&gt;&lt;BR /&gt;vgsync vgxx&lt;BR /&gt;&lt;BR /&gt;That's all, except your disk is a boot device. In this case don't forget to make it bootable by restoring the boot area:&lt;BR /&gt;&lt;BR /&gt;# mkboot -l /dev/rdsk/cXtXdX&lt;BR /&gt;&lt;BR /&gt;# lvlnboot -r /dev/&lt;ROOTVG&gt;/lvol3 &lt;BR /&gt;# lvlnboot -b /dev/&lt;ROOTVG&gt;/lvol1 &lt;BR /&gt;# lvlnboot -s /dev/&lt;ROOTVG&gt;/lvol2 &lt;BR /&gt;# lvlnboot -d /dev/&lt;ROOTVG&gt;/lvol2&lt;BR /&gt;&lt;BR /&gt;check:&lt;BR /&gt;&lt;BR /&gt;# lvlnboot -v&lt;BR /&gt;&lt;BR /&gt;&lt;/ROOTVG&gt;&lt;/ROOTVG&gt;&lt;/ROOTVG&gt;&lt;/ROOTVG&gt;</description>
      <pubDate>Thu, 29 Dec 2005 07:57:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695945#M248265</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2005-12-29T07:57:53Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695946#M248266</link>
      <description>&lt;BR /&gt;Hi Mark,&lt;BR /&gt;&lt;BR /&gt;vgchange -a n &lt;VG&gt;&lt;BR /&gt;&lt;BR /&gt;vgcfgrestore /dev/&lt;VG&gt; &lt;DISK&gt;&lt;BR /&gt;&lt;BR /&gt;vgchnage -a y &lt;VG&gt;&lt;BR /&gt;&lt;BR /&gt;if required,&lt;BR /&gt;&lt;BR /&gt;vgsync /dev/&lt;VG&gt;&lt;BR /&gt;&lt;BR /&gt;this should serve the purpose.&lt;BR /&gt;&lt;BR /&gt;With Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.&lt;/VG&gt;&lt;/VG&gt;&lt;/DISK&gt;&lt;/VG&gt;&lt;/VG&gt;</description>
      <pubDate>Thu, 29 Dec 2005 08:11:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695946#M248266</guid>
      <dc:creator>Sivakumar TS</dc:creator>
      <dc:date>2005-12-29T08:11:43Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695947#M248267</link>
      <description>Hi everybody and happy new year to you all.&lt;BR /&gt;&lt;BR /&gt;I raised a call with HP and eventually found that the problem was caused by an unused logical volume on the old disc. The system could see this lvol (I suspect as a result of the vgscan) and this was causing the error messages. Once I removed the lvol the pvcreate etc. went smoothly.&lt;BR /&gt;&lt;BR /&gt;Mark</description>
      <pubDate>Tue, 03 Jan 2006 03:21:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695947#M248267</guid>
      <dc:creator>MarkSyder</dc:creator>
      <dc:date>2006-01-03T03:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695948#M248268</link>
      <description>Mark,&lt;BR /&gt;&lt;BR /&gt;What steps did you take to find the unused logical volume?  I'm having the same problem at the moment.</description>
      <pubDate>Tue, 17 Jan 2006 13:16:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695948#M248268</guid>
      <dc:creator>Paul Coffey_1</dc:creator>
      <dc:date>2006-01-17T13:16:37Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695949#M248269</link>
      <description>Hi Paul.&lt;BR /&gt;&lt;BR /&gt;I logged a call with HP and they emailed me a script to run on the server. They then talked me through removing the incorrect lvol.&lt;BR /&gt;&lt;BR /&gt;I checked my notes yesterday because someone else had started a similar thread, but I can't find the command I used to delete it.&lt;BR /&gt;&lt;BR /&gt;Mark</description>
      <pubDate>Wed, 18 Jan 2006 03:33:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695949#M248269</guid>
      <dc:creator>MarkSyder</dc:creator>
      <dc:date>2006-01-18T03:33:44Z</dc:date>
    </item>
    <item>
      <title>Re: Mirrored disc has crashed</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695950#M248270</link>
      <description>Paul,&lt;BR /&gt;&lt;BR /&gt;I forgot to say: you can borrow my forum signature if you want.&lt;BR /&gt;&lt;BR /&gt;Mark Syder (like the drink but spelt different)</description>
      <pubDate>Wed, 18 Jan 2006 03:38:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/mirrored-disc-has-crashed/m-p/3695950#M248270</guid>
      <dc:creator>MarkSyder</dc:creator>
      <dc:date>2006-01-18T03:38:39Z</dc:date>
    </item>
  </channel>
</rss>

