Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AIX 4.1 rootvg problem.

Status
Not open for further replies.

Kanth17

Technical User
Nov 6, 2003
6
0
0
US
Greetings, I apologize if this seems missing some information. I am doing this over the phone. ;)

I have a system that had 2 disks in rootvg, hdisk0 and hdisk2. Hdisk0 was having errors so I was going to have it replaced. These were mirrored disks.

I ran rmlvcopy <LV> 1 hdisk0 for every logical volume in rootvg. I confirmed hdisk0 then had nothing on it. I ran reducevg rootvg hdisk0. I made sure hdisk2 was bosbooted, and in the boot list. I then removed hdisk0 with rmdev -dl hdisk0, and shut down the system.

My CE replaced hdisk0. The machine came up on hdisk2 (no problems) cfgmgr ran and found the new disk. (hdisk0).

I ran extendvg rootvg hdisk0
lspv now shows hdisk0 a part of rootvg.

But when I tried my mklvcopy -k hd5 hdisk0 it came out with errors about not being able to find a physical device AND mentions hd5 is already "copied"

When I run an lsvg -p rootvg, it says it can not find PVID:0000000000000000, although it finds hdisk2 just fine.

What's stranger, is now if I look at lspv the physical identifier on rootvg is the same number as it was BEFORE the disk was replaced.

It will not let me remove hdisk0 now, it claims it can't find the device.

I know sometime long ago I fixed this by finding the VGID and assigning that to the hdisk, and then reducing the vg, or something. But I need to get this vg back to normal.

If anyone can help me I would appreciate it a lot.
 
Addenum to the above. :

# lsvg -p rootvg
0516-304 lsvg: Unable to find device id 0000000000000000 in the Device
Configuration Database.
rootvg:
PV ID PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
0000000000000000 active 537 537 108..107..107..107..108
hdisk2 active 537 62 10..32..00..00..20

# lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd6 paging 32 32 1 open/syncd N/A
hd5 boot 1 1 1 closed/syncd N/A
hd8 jfslog 1 1 1 open/syncd N/A
hd4 jfs 24 24 1 open/syncd /
hd2 jfs 123 123 1 open/syncd /usr
hd9var jfs 38 38 1 open/syncd /var
hd3 jfs 49 49 1 open/syncd /tmp
hd1 jfs 10 10 1 open/syncd /home
lv00 jfs 197 197 1 open/syncd /pcn

# lsvg rootvg
VOLUME GROUP: rootvg VG IDENTIFIER: 000000129f3922bc
VG STATE: active PP SIZE: 4 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1074 (4296 megabytes)
MAX LVs: 256 FREE PPs: 599 (2396 megabytes)
LVs: 9 USED PPs: 475 (1900 megabytes)
OPEN LVs: 8 QUORUM: 1
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs 0
ACTIVE PVs: 2 AUTO ON: yes
 
reducevg rootvg 0000000000000000

Did you run 'chpv -c hdisk0" just before you shut down ? This removes the boot record from a hdisk. Normally "unmirrorvg" prompts you to do this, but it seems you did manual rmlvcopy's.

Reply to me directly at bverzal@komatsuna.com if you need more immediate responses.

BV
 
No, I did not.
unmirrorvg doesn't exist on 4.1, so I did it the old fashioned way. The system does prompt you to do a "chpv -c hdisk0" even if you do a "rmlvcopy hd5 1 hdisk0" on AIX 4.3.3 (I tested that).
Still as hdisk0 was removed and I have a completely new disk in the machine, it really should not need the boot record cleared, should it? (I mean I would be clearing the boot record for the disk being taken out..)
-K
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top