<?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: replace root mirror drive in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748945#M257477</link>
    <description>&lt;BR /&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;  vgreduce cannot be performed if the volume group is activated in shared  mode.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.</description>
    <pubDate>Sat, 11 Mar 2006 04:11:04 GMT</pubDate>
    <dc:creator>Sivakumar TS</dc:creator>
    <dc:date>2006-03-11T04:11:04Z</dc:date>
    <item>
      <title>replace root mirror drive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748939#M257471</link>
      <description># uname -a ; model&lt;BR /&gt;HP-UX B.11.11 U 9000/800/A500-7X&lt;BR /&gt;+++++++++++++++++++++++++++++++++++&lt;BR /&gt;&lt;BR /&gt;Hello HP,&lt;BR /&gt;  &lt;BR /&gt;Can you delivery the correct information for replacing a faulty mirror drive ? I received information ( listed below ) indicating drive at H/W path :&lt;BR /&gt;disk      2  0/0/2/1.15.0   sdisk    CLAIMED     DEVICE       HP 36.4GMAM3367MC&lt;BR /&gt;                           /dev/dsk/c3t15d0   /dev/rdsk/c3t15d0&lt;BR /&gt;&lt;BR /&gt;needs to be replaced. Lbolt errors were received in the syslog.log&lt;BR /&gt;&lt;BR /&gt;+++++++++++++++++++++++++++++++++++++++++++++&lt;BR /&gt;&lt;BR /&gt;Feb 28 07:05:59 hohp08 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: 76593339, dev: 1f03f000, io_id: 30aa9f7&lt;BR /&gt;Feb 28 08:28:41 hohp08 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: 77089539, dev: 1f03f000, io_id: 30addfd&lt;BR /&gt;Mar  4 04:49:41 hohp08 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: 110335639, dev: 1f03f000, io_id: 31352d8&lt;BR /&gt;Mar  6 21:44:07 hohp08 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: 133702339, dev: 1f03f000, io_id: 31cafc2&lt;BR /&gt;Mar  6 23:31:06 hohp08 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: 134344239, dev: 1f03f000, io_id: 31cf059&lt;BR /&gt;Mar  7 07:28:33 hohp08 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: 137208939, dev: 1f03f000, io_id: 31e2607&lt;BR /&gt;root@hohp08[/var/adm/syslog]&lt;BR /&gt;# /etc/ioscan -nfC disk&lt;BR /&gt;Class     I  H/W Path       Driver   S/W State   H/W Type     Description&lt;BR /&gt;==========================================================================&lt;BR /&gt;disk      0  0/0/1/0.3.0    sdisk    CLAIMED     DEVICE       HP      DVD-ROM 305&lt;BR /&gt;                           /dev/dsk/c0t3d0   /dev/rdsk/c0t3d0&lt;BR /&gt;disk      1  0/0/1/1.15.0   sdisk    CLAIMED     DEVICE       HP 36.4GMAM3367MC&lt;BR /&gt;                           /dev/dsk/c1t15d0   /dev/rdsk/c1t15d0&lt;BR /&gt;disk      2  0/0/2/1.15.0   sdisk    CLAIMED     DEVICE       HP 36.4GMAM3367MC&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;+++++++++++++++++++++++++++++++++++++++++++&lt;BR /&gt;lbot errors on hohp08 is due to disk media error&lt;BR /&gt;0/0/2/1.15.0         SCSI Disk (HP36.4GMAM3367 Information Successful       &lt;BR /&gt;&lt;BR /&gt;Error log:&lt;BR /&gt;Product Id:       MAM3367MC         Vendor:           HP 36.4G&lt;BR /&gt;Device Type:      SCSI Disk         Firmware Rev:     HP00&lt;BR /&gt;Device Qualifier: HP36.4GMAM3367MC  Logical Unit:     0&lt;BR /&gt;Serial Number:    KP900290&lt;BR /&gt;Capacity (M Byte):          34732.89&lt;BR /&gt;   Block Size:              512&lt;BR /&gt;   Max Block Address:       71132959&lt;BR /&gt;Error Logs&lt;BR /&gt;   Total Retries:         609951    Buffer Overruns:        N/A&lt;BR /&gt;   Read Reverse Errors:      N/A    Buffer Underruns:       N/A&lt;BR /&gt;   Write Errors:               0    Non-Medium Errors:       18&lt;BR /&gt;   Verify Errors:              0&lt;BR /&gt;&lt;BR /&gt;+++++++++++++++++++++++++++++++++++++++++++&lt;BR /&gt;# lvlnboot -v&lt;BR /&gt;Boot Definitions for Volume Group /dev/vg00:&lt;BR /&gt;Physical Volumes belonging in Root Volume Group:&lt;BR /&gt;        /dev/dsk/c1t15d0 (0/0/1/1.15.0) -- Boot Disk&lt;BR /&gt;        /dev/dsk/c3t15d0 (0/0/2/1.15.0) -- Boot Disk&lt;BR /&gt;Boot: stand     on:     /dev/dsk/c1t15d0&lt;BR /&gt;                        /dev/dsk/c3t15d0&lt;BR /&gt;Root: root      on:     /dev/dsk/c1t15d0&lt;BR /&gt;                        /dev/dsk/c3t15d0&lt;BR /&gt;Swap: swap      on:     /dev/dsk/c1t15d0&lt;BR /&gt;                        /dev/dsk/c3t15d0&lt;BR /&gt;Dump: swap      on:     /dev/dsk/c1t15d0, 0&lt;BR /&gt;&lt;BR /&gt;Current path "/dev/dsk/c19t0d0" is an alternate link, skip.&lt;BR /&gt;+++++++++++++++++++++++++++++++++++++++++++&lt;BR /&gt;Replacing bad root mirror drive&lt;BR /&gt;1. Shutdown the server , replace the faulty disk.&lt;BR /&gt;2. Boot normally.If error because of quorum&lt;BR /&gt;&lt;BR /&gt;reboot &lt;BR /&gt;interrupt when "10 sec is allowed"&lt;BR /&gt;bo pri isl&lt;BR /&gt;interact with isl "y"&lt;BR /&gt;ISL&amp;gt; hpux -lm&lt;BR /&gt;&lt;BR /&gt;3. Identify the new disk , with ioscan.&lt;BR /&gt;4. vgcfgrestore -n /dev/vg00 /dev/rdsk/c2t6d0&lt;BR /&gt;5. vgchange -a y /dev/vg00&lt;BR /&gt;6. mkboot -l /dev/rdsk/c2t6d0&lt;BR /&gt;7. mkboot -a "hpux -lq (;0) /stand/vmunix" /dev/rdsk/c2t6d0&lt;BR /&gt;8. lvlnboot -R /dev/vg00&lt;BR /&gt;9. lvlnboot -v /dev/vg00 [ Verify ]&lt;BR /&gt;10. vgsync /dev/vg00&lt;BR /&gt;[ Wait till synchronizaion completes. ]&lt;BR /&gt;11. setboot &lt;BR /&gt;[ check , the pri and alt path. ]&lt;BR /&gt;12.reboot and check</description>
      <pubDate>Fri, 10 Mar 2006 15:04:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748939#M257471</guid>
      <dc:creator>Jerry_109</dc:creator>
      <dc:date>2006-03-10T15:04:19Z</dc:date>
    </item>
    <item>
      <title>Re: replace root mirror drive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748940#M257472</link>
      <description>You shouldn't have to reboot is it is hot swap!&lt;BR /&gt;&lt;BR /&gt;After failed disk has been replaced by HP (assuming the disk is c1t5d0):&lt;BR /&gt;&lt;BR /&gt;vgcfgrestore -n /dev/vg00 /dev/rdsk/c1t5d0&lt;BR /&gt;&lt;BR /&gt;mkboot /dev/rdsk/c1t5d0&lt;BR /&gt;&lt;BR /&gt;mkboot -a "hpux -lq (;0) /stand/vmunix" /dev/rdsk/c1t5d0&lt;BR /&gt;&lt;BR /&gt;vgchange -a y /dev/vg00&lt;BR /&gt;&lt;BR /&gt;lvlnboot -Rv /dev/vg00&lt;BR /&gt;&lt;BR /&gt;vgsync /dev/vg00&lt;BR /&gt;&lt;BR /&gt;NOTE:&lt;BR /&gt;1) If the disk is completely "dead", such as if you run ioscan and status is "no_hw" then you can hot swap the disk online.&lt;BR /&gt;&lt;BR /&gt;2) However in circumstances where the disk has not fully failed please do one of the following to avoid data corruption :&lt;BR /&gt;&lt;BR /&gt;a) reduce mirror before replacing the disk&lt;BR /&gt;b) deactivate VG before replacing the disk&lt;BR /&gt;c) shutdown system to replace the disk&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Mar 2006 15:08:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748940#M257472</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2006-03-10T15:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: replace root mirror drive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748941#M257473</link>
      <description>are we talking :&lt;BR /&gt;&lt;BR /&gt; lvreduce -m 0 /dev/vg00/lvolX /dev/dsk/cxtxdx&lt;BR /&gt;&lt;BR /&gt;all the lv's for vg00 ?</description>
      <pubDate>Fri, 10 Mar 2006 15:35:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748941#M257473</guid>
      <dc:creator>Jerry_109</dc:creator>
      <dc:date>2006-03-10T15:35:47Z</dc:date>
    </item>
    <item>
      <title>Re: replace root mirror drive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748942#M257474</link>
      <description>You only have to lvreduce if the disk isn't completly dead....&lt;BR /&gt;&lt;BR /&gt;I had a year and a half ago when we replaced a disk that wasn't completing dead - could not re-mirror until after a lot of pain/single user modes/etc....&lt;BR /&gt;&lt;BR /&gt;It is good practice to just lvreduce all the lvols and vgreduce the disk, then swap it out, then recreate the root mirror...&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Fri, 10 Mar 2006 16:19:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748942#M257474</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2006-03-10T16:19:22Z</dc:date>
    </item>
    <item>
      <title>Re: replace root mirror drive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748943#M257475</link>
      <description>Can I vgreduce the mirror drive while online?&lt;BR /&gt;I mean, I don't have to vgchange -y n /dev/vg00 before vgreduce ?</description>
      <pubDate>Fri, 10 Mar 2006 18:16:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748943#M257475</guid>
      <dc:creator>Jerry_109</dc:creator>
      <dc:date>2006-03-10T18:16:31Z</dc:date>
    </item>
    <item>
      <title>Re: replace root mirror drive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748944#M257476</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;No need to deactivate a VG before doing vgreduce.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.</description>
      <pubDate>Sat, 11 Mar 2006 04:08:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748944#M257476</guid>
      <dc:creator>Sivakumar TS</dc:creator>
      <dc:date>2006-03-11T04:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: replace root mirror drive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748945#M257477</link>
      <description>&lt;BR /&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;  vgreduce cannot be performed if the volume group is activated in shared  mode.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Siva.</description>
      <pubDate>Sat, 11 Mar 2006 04:11:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748945#M257477</guid>
      <dc:creator>Sivakumar TS</dc:creator>
      <dc:date>2006-03-11T04:11:04Z</dc:date>
    </item>
    <item>
      <title>Re: replace root mirror drive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748946#M257478</link>
      <description>Remember to use -k option when reducing a bad disk, it avoids hanging the command just in case the disk is not responding.&lt;BR /&gt;&lt;BR /&gt;From man: "-k This option should be used only in the special instance when you want to reduce a mirrored logical volume on a physical volume that is missing or has failed"&lt;BR /&gt;&lt;BR /&gt;I think it's a force mode.&lt;BR /&gt;&lt;BR /&gt;lvreduce -k -m 0 &lt;LV_PATH&gt;&lt;BR /&gt;&lt;BR /&gt;Regards.&lt;/LV_PATH&gt;</description>
      <pubDate>Sat, 11 Mar 2006 07:44:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748946#M257478</guid>
      <dc:creator>Tiziano Contorno _</dc:creator>
      <dc:date>2006-03-11T07:44:28Z</dc:date>
    </item>
    <item>
      <title>Re: replace root mirror drive</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748947#M257479</link>
      <description>Partially dead disks can be a pain but with hotswap disks, you can pull out the bad one. That gets rid of whatever hardware failure was occurring. Then check syslog to see that LVM has discovered the missing disk (now = dead/missing) so lvreduce -m 0 ... is not needed.</description>
      <pubDate>Sat, 11 Mar 2006 12:03:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/replace-root-mirror-drive/m-p/3748947#M257479</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2006-03-11T12:03:23Z</dc:date>
    </item>
  </channel>
</rss>

