Sponsored Content
Operating Systems AIX Stale PPs in AIX, failed disks.. how to replace? Post 302922680 by c3rb3rus on Monday 27th of October 2014 04:48:26 PM
Old 10-27-2014
Error Stale PPs in AIX, failed disks.. how to replace?

I have a AIX 7.1 system that has 3 failed disks, 1 in rootvg and 2 in vg_usr1.

Here is the output of lspv.
Code:
# lspv
hdisk0          00044d4dfbb11575                    vg_usr1         active
hdisk1          0000150179158027                    vg_usr1         active
hdisk2          00001501791582c2                    vg_usr1         active
hdisk3          000015013a9148db                    vg_usr1         active
hdisk4          00001501791587df                    vg_usr1         active
hdisk5          0000150179158a75                    vg_usr1         active
hdisk6          00001501792ff38b                    vg_usr1         active
hdisk7          00001501792ff659                    vg_usr1         active
hdisk8          000015019dbd4c34                    vg_usr1         active
hdisk9          0000150178bb04a2                    vg_usr1         active
hdisk10         0000150173c3f71f                    rootvg          active
hdisk11         000015015b329219                    rootvg          active
hdisk12         0000150115562195                    rootvg          active
hdisk13         0000150173c3f833                    rootvg          active
hdisk14         0000150173c3f860                    rootvg          active
hdisk15         00001501f260dea1                    rootvg          active
hdisk16         00001501791a37d9                    vg_usr2         active
hdisk17         00001501791a3a9d                    vg_usr2         active
hdisk18         00001501791a3d45                    vg_usr2         active
hdisk19         00001501791a3fea                    vg_usr2         active
hdisk20         00001501791a4288                    vg_usr3         active
hdisk21         00001501791a451e                    vg_usr3         active
hdisk22         000015019dbd4ed5                    vg_usr1         active
hdisk23         000015019dbd517b                    vg_paging       active
hdisk24         00001501791bf1c6                    vg_usr1         active
hdisk25         00001501791bf48f                    vg_usr1         active
hdisk26         00001501791bf72e                    vg_usr1         active
hdisk27         00001501791bfa40                    vg_usr1         active
hdisk28         00001501791bfce5                    vg_usr1         active
hdisk29         00001501791bff84                    vg_usr1         active
hdisk30         00001501792ff909                    vg_usr1         active
hdisk32         00001501caf49d70                    vg_usr1         active
hdisk33         0000150179310ec5                    vg_usr1         active
hdisk34         000015010dd840e2                    vg_usr1         active
hdisk35         00001501caf588da                    vg_paging       active
hdisk36         00001501793177ff                    vg_usr3         active
hdisk37         0000150179317ac0                    vg_usr3         active
hdisk38         0000150179317d6d                    vg_usr3         active
hdisk39         0000150179318031                    vg_usr3         active
hdisk40         000015019dc3fe46                    vg_usr3         active
hdisk42         00c55310ce0d3117                    None

Output of lsvg for rootvg and vg_usr1.
Code:
# lsvg vg_usr1
VOLUME GROUP:       vg_usr1                  VG IDENTIFIER:  000015010000d60000000141138f2577
VG STATE:           active                   PP SIZE:        128 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      12012 (1537536 megabytes)
MAX LVs:            256                      FREE PPs:       1 (128 megabytes)
LVs:                2                        USED PPs:       12011 (1537408 megabytes)
OPEN LVs:           2                        QUORUM:         12 (Enabled)
TOTAL PVs:          22                       VG DESCRIPTORS: 22
STALE PVs:          2                        STALE PPs:      768
ACTIVE PVs:         20                       AUTO ON:        yes
MAX PPs per VG:     32512
MAX PPs per PV:     1016                     MAX PVs:        32
LTG size (Dynamic): 128 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable
PV RESTRICTION:     none                     INFINITE RETRY: no
DISK BLOCK SIZE:    512
# lsvg rootvg
VOLUME GROUP:       rootvg                   VG IDENTIFIER:  000015010000d6000000013569180e7a
VG STATE:           active                   PP SIZE:        128 megabyte(s)
VG PERMISSION:      read/write               TOTAL PPs:      3276 (419328 megabytes)
MAX LVs:            256                      FREE PPs:       2346 (300288 megabytes)
LVs:                15                       USED PPs:       930 (119040 megabytes)
OPEN LVs:           13                       QUORUM:         4 (Enabled)
TOTAL PVs:          6                        VG DESCRIPTORS: 6
STALE PVs:          1                        STALE PPs:      9
ACTIVE PVs:         5                        AUTO ON:        yes
MAX PPs per VG:     32512
MAX PPs per PV:     1016                     MAX PVs:        32
LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no
HOT SPARE:          no                       BB POLICY:      relocatable
PV RESTRICTION:     none                     INFINITE RETRY: no
DISK BLOCK SIZE:    512

Output of lsvg -p rootvg and vg_usr1.
Code:
# lsvg -p vg_usr1
vg_usr1:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk0            active            546         0           00..00..00..00..00
hdisk1            active            546         0           00..00..00..00..00
hdisk2            active            546         0           00..00..00..00..00
hdisk3            missing           546         0           00..00..00..00..00
hdisk4            active            546         0           00..00..00..00..00
hdisk5            active            546         0           00..00..00..00..00
hdisk6            active            546         0           00..00..00..00..00
hdisk7            active            546         0           00..00..00..00..00
hdisk8            active            546         0           00..00..00..00..00
hdisk9            active            546         0           00..00..00..00..00
hdisk22           active            546         0           00..00..00..00..00
hdisk24           active            546         0           00..00..00..00..00
hdisk25           active            546         0           00..00..00..00..00
hdisk26           active            546         0           00..00..00..00..00
hdisk27           active            546         0           00..00..00..00..00
hdisk28           active            546         0           00..00..00..00..00
hdisk29           active            546         0           00..00..00..00..00
hdisk30           active            546         0           00..00..00..00..00
hdisk31           missing           546         0           00..00..00..00..00
hdisk32           active            546         0           00..00..00..00..00
hdisk33           active            546         0           00..00..00..00..00
hdisk34           active            546         1           00..00..00..00..01
# lsvg -p rootvg
rootvg:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk10           active            546         497         109..89..81..109..109
hdisk11           active            546         173         110..56..00..00..07
hdisk12           active            546         177         68..00..00..00..109
hdisk13           active            546         487         110..50..109..109..109
hdisk14           missing           546         511         109..89..95..109..109
hdisk15           active            546         501         110..109..64..109..109

When I query each VG, I found that the following PVs are in a missing state.
Code:
PV_NAME           PV STATE          TOTAL PPs   FREE PPs    FREE DISTRIBUTION
hdisk3            missing           546         0           00..00..00..00..00
hdisk14           missing           546         0           00..00..00..00..00
hdisk31           missing           546         0           00..00..00..00..00

It does look like I have a disk that is unassigned, "hdisk42", so I'd like to put this one in use while I get 2 other disks to replace with.

I was going to try and remove hdisk31 and put hdisk42 in its place..

My notes for removing, swapping the failed disk and adding a new one in for AIX 7.1 are as follows..

Quote:
1) Unmirror hdisk31
unmirrorvg -c 1 vg_usr1 hdisk31
2) Take the disk out of the VG
reducevg vg_usr1 hdisk31
3) Remove the disk from system configuration
rmdev -dl hdisk31
4) Replace the disk
5) Get the disk back to the system configuration
cfgmgr
6) Add the disk to the VG
extendvg vg_usr1 hdisk31
7) Mirror hdisk31 again
mirrorvg -S -c 2 vg_usr1
"-S" will synchronize the stale partitions in the background.
8) After some time "lsvg vg_usr1" should show "STALE PPs: 0"
However, something is not happy, I can't get passed the first step.

Code:
# unmirrorvg -c 1 vg_usr1 hdisk31
0516-1155 lreducelv: Last good copy of a partition cannot reside on a missing disk.
Try again after reactivating the disk using chpv and varyonvg.
0516-922 rmlvcopy: Unable to remove logical partition copies from
        logical volume lv_usr1.
0516-1135 unmirrorvg: The unmirror of the volume group failed.
        The volume group is still partially or fully mirrored.

Then I tried varyonvg. no success.
Code:
# varyonvg vg_usr1
varyonvg # 0516-934 /usr/sbin/syncvg: Unable to synchronize logical volume lv_usr1.
0516-932 /usr/sbin/syncvg: Unable to synchronize volume group vg_usr1.

Any help is appreciated! Thank you.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Disks on AIX

Hello I've been working on AIX 5.3 ML3 on IBM pSeries520. That server has 6 HDD drives in 3 volume groups (1+mirror in each group). I must check which phisical disk is which disk in the system. For ex. I want to know that disk in 4th slot in the machine is marked as hdisk5 on AIX. Does anybody... (2 Replies)
Discussion started by: piooooter
2 Replies

2. AIX

Replace a Failed Root Disk in AIX

My root disk is failed and how to replace the root disk in AIX. Can u give a detailed explanation in step wise. Pls give the answer taking different scenarios. Regards Praveen (1 Reply)
Discussion started by: chinnu_mulakala
1 Replies

3. AIX

system disks on aix 5.3

hello i'm running on P570 box aix 5.3 8 cpus 24G ram there are 1850 users loged in to this box the problem is that the two sysytem disks busy all the time hdisk0 100% busy hdisk1 100% busy some one have an idea what writing to this disks? thanks ariec (9 Replies)
Discussion started by: ariec
9 Replies

4. AIX

Configurin EMC SAN disks on AIX

This may sound like an absolute rookie question, and it is. I have been working on Migrating our HP and Solaris servers to the new EMC SAN and know the routines backwards. Now we've suddenly got a new IBM server and I don't even know how to check if it is connected to the switch. Can someone... (1 Reply)
Discussion started by: ronellevan
1 Replies

5. AIX

Configuring new disks on AIX cluster

We run two p5 nodes running AIX 5L in a cluster mode (HACMP), both the nodes share external disk arrays. Only the primary node can access the shared disks at a given point of time. We are in the process of adding two new disks to the disk arrays so as to make them available to the existing... (3 Replies)
Discussion started by: dnicky
3 Replies

6. Solaris

Command to find the failed disks in SVM and VxVM

How to find & replace bad disks in solaris & VXVM?plz explain step by step? (2 Replies)
Discussion started by: xtreams
2 Replies

7. AIX

Issue with increasing size of SAN disks on AIX

HI, I have had an issue last night while trying to extend a filesystsem . chvg -g <vg> command cameback with an error 0516-1790 chvg: Failed bootinfo -s hdisk9. Ensure the physical volume is available and try again. 0516-732 chvg: Unable to change volume group u01vg. the VG has 1... (1 Reply)
Discussion started by: xmen01
1 Replies

8. AIX

How to reclaim hard disks and IP's in AIX?

Hello I recently received a request to reclaim hard disks and IP addresses within an AIX system(s). THe file systems are no longer in use and the client has indicated that it is OK to remove them and reclaim the disks and release the IP's. Now, since the file systems belong to a Volume group I... (8 Replies)
Discussion started by: Joseph Sabo
8 Replies

9. AIX

AIX - stale partition

Hi everybody, I have a little problem with my AIX 6.1, PowerHA 6.1 LVM mirror. After problem with SAN pathing of our one Datacenter, I have LV at stale state. # lsvg cpsdata2vg VOLUME GROUP: cpsdata2vg VG IDENTIFIER: 00fb518c00004c0000000169445f4c2c VG STATE: ... (6 Replies)
Discussion started by: Necronomic
6 Replies

10. UNIX for Beginners Questions & Answers

DISKs are gone after shutting down and replace an FC card

Hi there, I had issue with one of MY FC cards on T4-2 servers so system team replace it and start the machine but when launch FORMAT command so I don't see my shared disks coming from storage controller. i have checked at the Fabric switch so WWN numbers are visible and zones are ok and after... (1 Reply)
Discussion started by: janakors
1 Replies
All times are GMT -4. The time now is 07:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy