stale root partiition - AIX 5.3



Just migrated a system from 5.1 to 5.3 which went just fine until I
decided to mirror rootvg. The system is at ML2. The mirroring seemed
to go fine:
0516-622 : Warning, cannot write lv control block data.
0516-1124 mirrorvg: Quorum requirement turned off, reboot
system for this
to take effect for rootvg.
0516-1126 mirrorvg: rootvg successfully mirrored, user should
perform
bosboot of system to initialize boot records. Then, user must
modify
bootlist to include: hdisk0 hdisk1.

But wonder what that first line means... I saw that when unmirroring it
to do the upgrade then when I did the unmirrorvg:
0516-622 rmlvcopy: Warning, cannot write lv control block
data.
0516-1135 unmirrorvg: The unmirror of the volume group failed.
The volume group is still partially or fully mirrored.

But when I ran the unmirror again it went fine:
0516-1132 unmirrorvg: Quorum requirement turned on, reboot
system for this
to take effect for rootvg.
0516-1144 unmirrorvg: rootvg successfully unmirrored, user
should perform
bosboot of system to reinitialize boot records. Then, user
must modify
bootlist to just include: hdisk0.

So I thought I better check it before I reboot. I did an 'lsvg -l
rootvg' and found that all of the logical volumes in rootvg were
open/stale. I then ran a 'syncvg -l rootvg' and got a series of errors
saying it couldn't syncronize each logical volume. But when I looked
again, all of the logical volumes were synchronized except / (root). I
tried 'syncvg -l hd4' but it said it couldn't synchronize and hd4 still
shows open/stale.

I can run rmlvcopy on hd4 fine. I can also run mklvcopy of hd4 onto
hdisk1 and it works but still shows as open/stale. When I 'lspv
hdisk0' there are no stale partitions but if I run 'lspv hdisk1' it
shows 88 stale partitions - which is the amount of partitions for /.

Everytime I run 'syncvg -l hd4' I also get DISK_ERR1 errors which IBM
says mean the disk is definitely going bad. But I ran a mksysb and run
TSM on the system all night and no disk errors popped up at all. I
removed the hd4 copy on hdisk1 so it would show as open/sync in case it
gets rebooted.

Problem is I can't do much with the root partition in a stale state. I
can't replace the disk and remirror it from hdisk1 because the root
mirror is apparently stale. I am wondering if this disk is really
going bad or is it something else since I only get errors when trying
to mirror hd4.

Am I screwed here or is there some way I can try to fix the root
partition so it will mirror? I saw synclvodm but not sure if that
would help. Any help is appreciated.

.



Relevant Pages

  • Re: Re-mirroring rootvg
    ... that we're sure all is well, we need to re-mirror rootvg again. ... I use the following commands if both disk have the same size and the ... Mirror rootvg using mirrorvg or mklvcopy. ...
    (comp.unix.aix)
  • Re: Question on unmirroring rootvg before mksysb
    ... So short of a customized image.data file, the rootvg will be ... you can customize the image.data file to ... restore it without a mirror. ... During he restore you can use a customized image.data file to ...
    (AIX-L)
  • HELP - stale partitions
    ... Last week "stale partition" messages began to appear for all rootvg lv's, and err msgs about hdisk0. ... Then we replaced hdisk0 after breaking the mirror, hoping to remirror after adding the new hdisk0 to rootvg. ... 9D035E4D 1214165306 P S SYSVMM DATA STORAGE INTERRUPT, ...
    (AIX-L)
  • Re: HELP - stale partitions
    ... Last week "stale partition" messages began to appear for all ... and err msgs about hdisk0. ... we tried to unmirror and then mirror rootvg. ... Then we replaced hdisk0 after breaking the mirror, ...
    (AIX-L)
  • Re: Break root mirror on AIX 4.3.3
    ... # unmirrorvg rootvg hdisk1 ... If hd5 is the boot logical volume, ... 0516-1132 unmirrorvg: Quorum requirement turned on, ... this to take effect for rootvg. ...
    (comp.unix.aix)