Issues with Make_tape_recovery & LIF (2033 Views)
Reply
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 1 of 31 (2,033 Views)
Accepted Solution

Issues with Make_tape_recovery & LIF

[ Edited ]

Hi

 

I'm getting errors in the make tape recovery, see below:

 

      ** 0 - The Volume Group or Filesystem is Not included in the

             System Recovery Archive

      ** 1 - The Volume Group or Filesystem is Partially included in the

             System Recovery Archive

      ** 2 - The Volume Group or Filesystem is Fully included in the

             System Recovery Archive

 

WARNING: The make_sys_image failed to save the LIF volume.

       * Scanning system for IO devices...

       * Boot device is: 0/0/0/2/0.0x6.0x0

       * Creating local directories for configuration files and archive.

 

=======  08/17/12 20:00:08 BST  Started /opt/ignite/bin/make_tape_recovery.

         (Fri Aug 17 20:00:08 BST 2012)

         @(#)Ignite-UX Revision C.7.8.201

         @(#)ignite/net_recovery (opt) Revision:

         /branches/IUX_RA0903/ignite/src@76987 Last Modified: 2009-02-05

         15:45:55 -0700 (Thu, 05 Feb 2009)

 

       * Recovery Archive Description = Recovery Archive

        

       * Recovery Archive Location    = /dev/rmt/22mn

        

       * Number of Archives to Save   = 2

        

       * Pax type  = tar

        

     

      In?   dsk/vg      name              minor#      Associated disks/mountpoints

      2     v     /dev/vg00         0x00  /dev/disk/disk100 /dev/disk/disk103

                                    /dev/vg00/lvol1   /stand      2

                                    /dev/vg00/lvol2

                                    /dev/vg00/lvol3   /     2

                                    /dev/vg00/lvol5   /opt  2

                                    /dev/vg00/lvol6   /tmp  2

                                    /dev/vg00/lvol7   /usr  2

                                    /dev/vg00/lvol8   /var  2

      2     v     /dev/vg01         0x01  /dev/dsk/c2t6d0 /dev/dsk/c15t6d0

                                    /dev/vg01/home    /home 2

                                    /dev/vg01/vsifax  /opt/vsifax 2

                                    /dev/vg01/swap1

                                    /dev/vg01/swap2

                                    /dev/vg01/swap3

                                    /dev/vg01/swap4

                                    /dev/vg01/swap5

      0     v     /dev/vg06         0x02  /dev/disk/disk85

                                    /dev/vg06/scratch /scratch    0

      0     v     /dev/vg08         0x03  /dev/disk/disk118

      0     v     /dev/vg05         0x05  /dev/disk/disk84

                                    /dev/vg05/progtmp /progtmp    0

      0     v     /dev/vg09         0x07  /dev/disk/disk81 /dev/disk/disk87

                                    /dev/vg09/ror_bi  /opt/bi     0

      0     v     /dev/vg12         0x08  /dev/disk/disk89

                                    /dev/vg12/oatmp   /oatmp      0

      0     v     /dev/vg19         0x0a  /dev/disk/disk94

                                    /dev/vg19/coins_local_scripts /usr/local/scripts      0

      0     v     /dev/vg20         0x0b  /dev/disk/disk97

                                    /dev/vg20/lvol1

      0     v     /dev/vg21         0x0c  /dev/disk/disk88

                                    /dev/vg21/coinsai /opt/coins9/live/data/ai      0

      0     v     /dev/vg22         0x0d  /dev/disk/disk91

                                    /dev/vg22/coinsbi /opt/coins9/live/data/bi      0

      0     v     /dev/vg23         0x0e  /dev/disk/disk95

                                    /dev/vg23/ror_ai  /opt/ai     0

      0     v     /dev/vg24         0x0f  /dev/disk/disk93

                                    /dev/vg24/coinsai_save2 /opt/coins9/live/data/ai/save2      0

      0     v     /dev/vg25         0x10  /dev/disk/disk96

                                    /dev/vg25/ror_ai_save2  /opt/ai/prod/rorwork/save2    0

      0     v     /dev/vg26         0x11  /dev/disk/disk98

                                    /dev/vg26/coinsai_save  /opt/coins9/live/data/ai/save 0

      0     v     /dev/vg27         0x12  /dev/disk/disk99

                                    /dev/vg27/ror_ai_save   /opt/ai/prod/rorwork/save     0

      0     v     /dev/vg40         0x13  /dev/disk/disk120

                                    /dev/vg40/backup1 /probkup_weekly   0

      0     v     /dev/vg10         0x14  /dev/disk/disk122

                                    /dev/vg10/coinslive     /opt/coins9/live  0

      0     v     /dev/vg29         0x1d  /dev/disk/disk124

                                    /dev/vg29/C_ADMIN /opt/coins10/coinsadmin 0

      0     v     /dev/vg11         0x15  /dev/disk/disk139

                                    /dev/vg11/coinsdb /opt/coins9/live/data/db      0

      0     v     /dev/vg16         0x16  /dev/disk/disk144

                                    /dev/vg16/rorwork /opt/data   0

      0     v     /dev/vg30         0x04  /dev/dsk/c5t0d2

                                    /dev/vg30/probkup_500   /probkup    0

      0     v     /dev/vg31         0x06  /dev/disk/disk148

                                    /dev/vg31/coinsdb_400

       * Checking Versions of Ignite-UX filesets

read: No such device or address

read_blocks(lifvol): error on 1024 byte write

lifls: Can't list /dev/disk/disk100; not a LIF volume

WARNING: /dev/disk/disk100 is not a LIF volume.

         No LIF files on the boot disk will be archived.

         Check /stand/bootconf, man bootconf(4), and /dev/dsk to

         ensure that the bootconf file is set up correctly.

ERROR:   source_read failed: No such device or address (errno = 6).

ERROR:   sourcefile_open: source read: No such device or address (errno = 6).

       * Creating System Configuration.

       * /opt/ignite/bin/save_config -f

         /var/opt/ignite/recovery/2012-08-17,20:00/system_cfg vg00 vg01

       * Backing Up Volume Group /dev/vg00

       * /usr/sbin/vgcfgbackup /dev/vg00

       * Creating Map Files for Volume Group /dev/vg00

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00

 

       * Backing Up Volume Group /dev/vg01

       * /usr/sbin/vgcfgbackup /dev/vg01

       * Creating Map Files for Volume Group /dev/vg01

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg01.mapfile /dev/vg01

 

       * Backing Up Volume Group /dev/vg06

       * /usr/sbin/vgcfgbackup /dev/vg06

       * Creating Map Files for Volume Group /dev/vg06

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg06.mapfile /dev/vg06

 

       * Backing Up Volume Group /dev/vg08

       * /usr/sbin/vgcfgbackup /dev/vg08

       * Creating Map Files for Volume Group /dev/vg08

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg08.mapfile /dev/vg08

 

       * Backing Up Volume Group /dev/vg05

       * /usr/sbin/vgcfgbackup /dev/vg05

       * Creating Map Files for Volume Group /dev/vg05

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg05.mapfile /dev/vg05

 

       * Backing Up Volume Group /dev/vg09

       * /usr/sbin/vgcfgbackup /dev/vg09

       * Creating Map Files for Volume Group /dev/vg09

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg09.mapfile /dev/vg09

 

       * Backing Up Volume Group /dev/vg12

       * /usr/sbin/vgcfgbackup /dev/vg12

       * Creating Map Files for Volume Group /dev/vg12

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg12.mapfile /dev/vg12

 

       * Backing Up Volume Group /dev/vg19

       * /usr/sbin/vgcfgbackup /dev/vg19

       * Creating Map Files for Volume Group /dev/vg19

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg19.mapfile /dev/vg19

 

       * Backing Up Volume Group /dev/vg20

       * /usr/sbin/vgcfgbackup /dev/vg20

       * Creating Map Files for Volume Group /dev/vg20

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg20.mapfile /dev/vg20

 

       * Backing Up Volume Group /dev/vg21

       * /usr/sbin/vgcfgbackup /dev/vg21

       * Creating Map Files for Volume Group /dev/vg21

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg21.mapfile /dev/vg21

 

       * Backing Up Volume Group /dev/vg22

       * /usr/sbin/vgcfgbackup /dev/vg22

       * Creating Map Files for Volume Group /dev/vg22

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg22.mapfile /dev/vg22

 

       * Backing Up Volume Group /dev/vg23

       * /usr/sbin/vgcfgbackup /dev/vg23

       * Creating Map Files for Volume Group /dev/vg23

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg23.mapfile /dev/vg23

 

       * Backing Up Volume Group /dev/vg24

       * /usr/sbin/vgcfgbackup /dev/vg24

       * Creating Map Files for Volume Group /dev/vg24

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg24.mapfile /dev/vg24

 

       * Backing Up Volume Group /dev/vg25

       * /usr/sbin/vgcfgbackup /dev/vg25

       * Creating Map Files for Volume Group /dev/vg25

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg25.mapfile /dev/vg25

 

       * Backing Up Volume Group /dev/vg26

       * /usr/sbin/vgcfgbackup /dev/vg26

       * Creating Map Files for Volume Group /dev/vg26

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg26.mapfile /dev/vg26

 

       * Backing Up Volume Group /dev/vg27

       * /usr/sbin/vgcfgbackup /dev/vg27

       * Creating Map Files for Volume Group /dev/vg27

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg27.mapfile /dev/vg27

 

       * Backing Up Volume Group /dev/vg40

       * /usr/sbin/vgcfgbackup /dev/vg40

       * Creating Map Files for Volume Group /dev/vg40

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg40.mapfile /dev/vg40

 

       * Backing Up Volume Group /dev/vg10

       * /usr/sbin/vgcfgbackup /dev/vg10

       * Creating Map Files for Volume Group /dev/vg10

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg10.mapfile /dev/vg10

 

       * Backing Up Volume Group /dev/vg29

       * /usr/sbin/vgcfgbackup /dev/vg29

       * Creating Map Files for Volume Group /dev/vg29

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg29.mapfile /dev/vg29

 

       * Backing Up Volume Group /dev/vg11

       * /usr/sbin/vgcfgbackup /dev/vg11

       * Creating Map Files for Volume Group /dev/vg11

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg11.mapfile /dev/vg11

 

       * Backing Up Volume Group /dev/vg16

       * /usr/sbin/vgcfgbackup /dev/vg16

       * Creating Map Files for Volume Group /dev/vg16

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg16.mapfile /dev/vg16

 

       * Backing Up Volume Group /dev/vg30

       * /usr/sbin/vgcfgbackup /dev/vg30

       * Creating Map Files for Volume Group /       * Archive created and rewind the tape to beginning of tape.

        

       * Cleaning up old configuration file directories

dev/vg30

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg30.mapfile /dev/vg30

 

       * Backing Up Volume Group /dev/vg31

       * /usr/sbin/vgcfgbackup /dev/vg31

       * Creating Map Files for Volume Group /dev/vg31

       * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg31.mapfile /dev/vg31

 

       * Creating Control Configuration.

       * Creating Archive File List

       * Creating Archive Configuration

 

       * /opt/ignite/lbin/make_arch_config -c

         /var/opt/ignite/recovery/2012-08-17,20:00/archive_cfg -g

         /var/opt/ignite/recovery/2012-08-17,20:00/flist -n 2012-08-17,20:00 -r

         pa -b 64 -d Recovery\ Archive -t 1 -i 2 -m t

       * Saving the information about archive to

         /var/opt/ignite/recovery/previews

       * Creating The Tape Archive

       * Checking configuration file for Syntax

       * Writing boot LIF to tape

       * Complete writing boot LIF onto tape.

       * /opt/ignite/data/scripts/make_sys_image -c n -d /dev/rmt/22mn -t n -s

         local -n 2012-08-17,20:00 -m t -w

         /var/opt/ignite/recovery/2012-08-17,20:00/recovery.log -u -R -g

         /var/opt/ignite/recovery/2012-08-17,20:00/flist -a 35268920

        

       * Preparing to create a system archive.

read: No such device or address

read_blocks(lifvol): error on 1024 byte write

lifls: Can't list /dev/disk/disk100; not a LIF volume

WARNING: /dev/disk/disk100 is not a LIF volume.

         No LIF files on the boot disk will be archived.

         Check /stand/bootconf, man bootconf(4), and /dev/dsk to

         ensure that the bootconf file is set up correctly.

 

       * Archiving contents of apollo via tar image to local device /dev/rmt/22mn.

       * Creation of system archive complete.

NOTE:    The following files are in the list of files that were on the

         system, but they are no longer present.  These files are not

         included in the backup:

         /var/adm/cron/tty erase

         /var/tmp/ign_configure/make_sys_image.log

         /var/stm/logs/os/log339.raw.cur

         /var/opt/ignite/tmp/AAA019477

         /var/opt/ignite/tmp/BAA019477

 

 

=======  08/17/12 20:37:41 BST  make_tape_recovery completed with warnings

 

lvlnboot -v gives the following (after hanging for about 30 seconds)

 

lvlnboot -v lvlnboot: LIF information corrupt or not present on  "/dev/disk/disk100".

Use the "mkboot" command to initialize the LIF area.

Boot Definitions for Volume Group /dev/vg00:

Physical Volumes belonging in Root Volume Group:

        /dev/disk/disk100

        /dev/disk/disk103 -- Boot Disk

Boot: lvol1     on:     /dev/disk/disk100                         /dev/disk/disk103

Root: lvol3     on:     /dev/disk/disk100                         /dev/disk/disk103

Swap: lvol2     on:     /dev/disk/disk100                         /dev/disk/disk103

Dump: lvol2     on:     /dev/disk/disk100, 0

 

lvlnboot: LIF information corrupt or not present on  "/dev/disk/disk87".

Use the "mkboot" command to initialize the LIF area.

Boot Definitions for Volume Group /dev/vg09

Physical Volumes belonging in Root Volume Group:

        /dev/disk/disk81

        /dev/disk/disk87 -- Boot Disk

No Boot Logical Volume configured

No Root Logical Volume configured

No Swap Logical Volume configured

No Dump Logical Volume configured

 

You have mail in /var/mail/root

 

setboot gives:

 

Primary bootpath : 0/0/0/2/0.0x6.0x0 (/dev/rdisk/disk100)

HA Alternate bootpath : 0/0/0/3 (No dsf found)

Alternate bootpath : 1/0/0/2/0.0x6.0x0 (/dev/rdisk/disk103)

 

Autoboot is ON (enabled)

Autosearch is OFF (disabled)

 

Note: The interpretation of Autoboot and Autosearch has changed for systems that support hardware partitions. Please refer to the manpage.

 

Botton of vgdisplay -v vg00 shows:

 

 --- Physical volumes ---

   PV Name                     /dev/disk/disk100

   PV Status                   unavailable

   Total PE                    4375

   Free PE                     1927

   Autoswitch                  On

   Proactive Polling           On

 

   PV Name                     /dev/disk/disk103

   PV Status                   available

   Total PE                    4375

   Free PE                     1927

   Autoswitch                  On

   Proactive Polling           On

 

disk100 is showing as unavailable.

 

Can you help please?   I'm stumped!

 

Regards

 

Tariq

 

 

P.S. This thread has been moved from HP-UX >System Administration to HP-UX > ignite. -HP Forum moderator

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 2 of 31 (2,032 Views)

Re: Issues with Make_tape_recovery & LIF

[ Edited ]

/dev/disk/disk100
/dev/disk/disk103 -- Boot Disk

/dev/disk/disk81
/dev/disk/disk87 -- Boot Disk


is disk100 a mirror of disk103?


It is not bootable.



disk87 is bootable, but not considered as boot disk.





I think you asked this already some weeks ago, right???

 

 

 

PV Name /dev/disk/disk100

PV Status unavailable

 

 

disk100 is either dead or disabled.

 

If dead, you need to replace or unmirror.


Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 3 of 31 (2,025 Views)

Re: Issues with Make_tape_recovery & LIF

disk103 is the mirror, which the server is running.

disk100 is showing man stale extents, below (an example)

 

02863 current  /dev/vg00/lvol7         00383
   02864 stale    /dev/vg00/lvol8         00000
   02865 stale    /dev/vg00/lvol8         00001
   02866 stale    /dev/vg00/lvol8         00002
   02867 stale    /dev/vg00/lvol8         00003
   02868 stale    /dev/vg00/lvol8         00004
   02869 stale    /dev/vg00/lvol8         00005
   02870 stale    /dev/vg00/lvol8         00006
   02871 stale    /dev/vg00/lvol8         00007
   02872 current  /dev/vg00/lvol8         00008
   02873 current  /dev/vg00/lvol8         00009
   02874 stale    /dev/vg00/lvol8         00010
   02875 stale    /dev/vg00/lvol8         00011
   02876 stale    /dev/vg00/lvol8         00012

 

Should I unmirror (how?) and replace?

 

If I unmirror using lvreduce -m 0 ....., will server still run on disk 103 (good mirror)?

 

Regards

 

Tariq

 

 

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 4 of 31 (2,023 Views)

Re: Issues with Make_tape_recovery & LIF

Better replace it asap using the online replacement procedure (good_disks_go_bad_wp).

Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 5 of 31 (2,018 Views)

Re: Issues with Make_tape_recovery & LIF

This one (attached)?

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 6 of 31 (2,013 Views)

Re: Issues with Make_tape_recovery & LIF

When_Good_Disks_Go_Bad_WP
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01911837/c01911837.pdf


Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 7 of 31 (2,011 Views)

Re: Issues with Make_tape_recovery & LIF

diskinfo still shows disk has a size > 0

 

root@server at /var/adm/syslog =>diskinfo  /dev/rdisk/disk100
SCSI describe of /dev/rdisk/disk100:
             vendor: HP 73.4G
         product id: MAU3073NC
               type: direct access
               size: 71687369 Kbytes
   bytes per sector: 512

 

Also, see dd output

 

dd if=/dev/rdisk/disk100 of=/dev/null bs=1024k count=64 &
[1]     22398
root@server at /var/adm/syslog =>dd read error: No such device or address
0+0 records in
0+0 records out

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 8 of 31 (2,005 Views)

Re: Issues with Make_tape_recovery & LIF

Please provide

 

# ioscan -fnN


Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 9 of 31 (1,983 Views)

Re: Issues with Make_tape_recovery & LIF

Please find it attached.

Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 10 of 31 (1,979 Views)

Re: Issues with Make_tape_recovery & LIF

Engineer pulled disk and put in the new one, and it came up as no hardware.  He said it was OK to just pull, without running any prior LVM commands.  I'm not so sure myself, but I left it to him.  Tried insf -e, disk still showed NO_HW, so he's gone to get another one.

 

Regards

 

Tariq

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 11 of 31 (1,975 Views)

Re: Issues with Make_tape_recovery & LIF

If the disk is UNAVAILABLE in LVM already, you can pull the disk.

 

If not, you need to do a "pvchange -a n ..." before.

 

But after inserting the new disk you probably need to do a

 

# scsimgr replace_wwid –D /dev/rdisk/disk100

 

just do an ioscan after insertion and watch the syslog for related messages.


Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 12 of 31 (1,973 Views)

Re: Issues with Make_tape_recovery & LIF

Strange things are happening Torsten.

 

Before Eng. went away to get a new disk, he put in the failing one again just to prove it was CLAIMED, andf it was.  Now, it has become available in vgdisplay, no stale extents, but lvlnboot -v looks strange.  see attachment:

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 13 of 31 (1,971 Views)

Re: Issues with Make_tape_recovery & LIF

It looks good!

Test with "dd" again for errors.

The "strange" part is here:

lvlnboot: LIF information corrupt or not present on "/dev/disk/disk87".


This is a data disk with a boot area, but the area is empty.


You can use "vgmodify" to remove or just ignore.

Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 14 of 31 (1,970 Views)

Re: Issues with Make_tape_recovery & LIF

dd failed:

 

root@apollo at /var/adm/syslog =>dd if=/dev/rdisk/disk100 of=/dev/null bs=1024k count=64
dd read error: I/O error
1+0 records in
1+0 records out

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 15 of 31 (1,968 Views)

Re: Issues with Make_tape_recovery & LIF

So the disk is probably "half-dead".


AFAIR the newest LVM version has this "half-dead-detection", so it will disable the LVM access - this could be the reason why it was unavailable.


You should replace the disk.

Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 16 of 31 (1,966 Views)

Re: Issues with Make_tape_recovery & LIF

Should I

 

lvreduce -m 0 -A n /dev/vgoo/lvname /dev/disk100 (for each LV on that PV)? 

 

I'm not 100% sure whether this is necessary or not?

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 17 of 31 (1,964 Views)

Re: Issues with Make_tape_recovery & LIF

Don't reduce anything!

Just disable LVM access (follow the good_disk_go_bad document)!



BTW, see also

http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c03233055/c03233055.pdf

Half Dead Disk Detection

A physical disk that returns media error for write I/Os while allowing read I/Os to succeed (or
vice-versa) is termed a Half Dead Disk. The term also refers to a disk that returns media error for
certain regions while the rest is unaffected. When a disk is fully dead (i.e. both read and write
I/Os to any region of the disk fail), LVM detects it automatically and marks it as unavailable. But
LVM did not handle half dead disk conditions until this release. The half dead disk situation causes
significant performance impact to the system since LVM indefinitely attempts recovery of the affected
physical volumes. The new Half Dead Disk Detection feature can be used to detect and quickly
exclude such PVs from LVM usage.

Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 18 of 31 (1,956 Views)

Re: Issues with Make_tape_recovery & LIF

This get stranger and stranger.

 

Pulled our failing disk.  Tried 3 different new disks, all showed NO_HW.  'insf -e' did nothing!

 

Put the original failing disk back in, showed as claimed.

 

Our disk has firmware version HPC0, engineer brought 3 x disk with fw version HPC3.  They are ordering some HPC0 disks to see if that is the issue.

 

Put original disk back in until new one arrives.

 

Thanks for your help.

 

Will keep you posted.

 

Tariq

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 19 of 31 (1,954 Views)

Re: Issues with Make_tape_recovery & LIF

I don't think it is strange.

 

 

Did you watch the syslog file as I told you???


Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 20 of 31 (1,951 Views)

Re: Issues with Make_tape_recovery & LIF

oops

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 21 of 31 (1,947 Views)

Re: Issues with Make_tape_recovery & LIF

[ Edited ]

I never exchanged a parallel scsi disk in a 11.31 server yet, only sas disks.

 

WIth sas disks the system creates a new WWID, so you need to allow the system to access the disk, otherwise it appears as NO_HW.

 

I assume the same with your disk.

 

# scsimgr replace_wwid –D /dev/rdisk/disk100

 

will solve this (or a reboot).

 

 

 

From

When Good Disks Go Bad: Dealing with Disk Failures
Under LVM - page 36

 

4. Notify the mass storage subsystem that the disk has been replaced.
If the system was not rebooted to replace the failed disk, then run scsimgrbefore using the
new disk as a replacement for the old disk. For example:
# scsimgr replace_wwid –D /dev/rdisk/disk14
This command allows the storage subsystem to replace the old disk’s LUN World-Wide-Identifier (WWID) with the new disk’s LUN WWID. The storage subsystem creates a new
LUN instance and new device special files for the replacement disk.

 

...

 

6. Assign the old instance number to the replacement disk.
For example:
# io_redirect_dsf -d /dev/disk/disk14 -n /dev/disk/disk28
This assigns the old LUN instance number (14) to the replacement disk. In addition, the device
special files for the new disk are renamed to be consistent with the old LUN instance number.


Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 22 of 31 (1,905 Views)

Re: Issues with Make_tape_recovery & LIF

Hi Torsten

 

Hope you had a great weekend.

 

We replaced the disk and managed to get it online with a system restart.  By I am still experiencing LIF warnings in the make recovery output.

 

See attached.

 

Also, disk100 no longer exists,but was replaced by disk149 at path c0t6d0 after the reboot.

Acclaimed Contributor
Posts: 23,517
Registered: ‎10-02-2001
Message 23 of 31 (1,903 Views)

Re: Issues with Make_tape_recovery & LIF

disk100 is still part of vg00.

 

check

 

# strings /etc/lvmtab_p

 

# vgdisplay -v vg00


Hope this helps!
Regards
Torsten.

__________________________________________________

There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________

No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Regular Advisor
Posts: 196
Registered: ‎09-23-2011
Message 24 of 31 (1,899 Views)

Re: Issues with Make_tape_recovery & LIF

root@server at /scratch/tariq/sarcheck =>strings /etc/lvmtab
/dev/vg00
/dev/disk/disk103
/dev/disk/disk149
/dev/vg01
rL8:
/dev/dsk/c2t6d0
/dev/dsk/c15t6d0
/dev/vg06
/dev/disk/disk85
/dev/vg08
rL8p
/dev/disk/disk118
/dev/vg05
/dev/disk/disk84
/dev/vg09
/dev/disk/disk81
/dev/disk/disk87
/dev/vg12
/dev/disk/disk89
/dev/vg19
/dev/disk/disk94
/dev/vg20
/dev/disk/disk97
/dev/vg21
/dev/disk/disk88
/dev/vg22
/dev/disk/disk91
/dev/vg23
/dev/disk/disk95
/dev/vg24
/dev/disk/disk93
/dev/vg25
/dev/disk/disk96
/dev/vg26
/dev/disk/disk98
/dev/vg27
rJ}C
/dev/disk/disk99
/dev/vg40
/dev/disk/disk120
/dev/vg10
/dev/disk/disk122
/dev/vg29
/dev/disk/disk124
/dev/vg11
/dev/disk/disk139
/dev/vg16
/dev/disk/disk144
/dev/vg30
/dev/dsk/c5t0d2
/dev/vg31
/dev/disk/disk148

 

There is no output from strins /etc/lvmtab_p

 

 

Valued Contributor
Posts: 597
Registered: ‎05-24-2004
Message 25 of 31 (1,864 Views)

Re: Issues with Make_tape_recovery & LIF

and lvlnboot -v too.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.