Reducevg - my mistake! H70 - 5.3.3

[GFGMojo]

I was getting ready to run a reducevg command on hdisk1 on a server after unmirroring it in preparation for an alt_disk_migration

Problem is - I was on another screen and ran the reducevg command on hdisk1 on a server with rootvg mirrrored and running. Not too bad, except the dump area was not mirrrored and the command errored - still not too bad, except now lspv shows
[server1:me]> lspv
hdisk0 000170280e854766 old_rootvg
hdisk1 00017028300f1aba rootvg active
hdisk3 00017028dbfde1ef optvg active
hdisk4 000170286c20ff2c bkupvg active
hdisk5 00017028507d1725 optvg active
hdisk6 0001702871fd6633 bkupvg active
hdisk8 00017028b945cc22 vg01 active

Notice that hdisk0 is now listed as old_rootvg

and to compound the issue whomever originally set this up did not run a boot volume on hdisk1 after mirroring -

[server1:me]> lspv -l hdisk1
hdisk1:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
hd6 168 168 00..108..60..00..00 N/A
hd8 1 1 00..00..01..00..00 N/A
hd4 30 30 00..00..30..00..00 /
hd2 150 150 20..00..17..108..05 /usr
hd9var 60 60 60..00..00..00..00 /var
hd3 60 60 00..00..00..00..60 /tmp

Notice no hd5 -

When I tried to run bosboot command to force it -

# bosboot -ad /dev/hdisk1
0516-306 lslv: Unable to find hd5 in the Device
Configuration Database.

0301-168 bosboot: The current boot logical volume, /dev/hd5,
does not exist on /dev/hdisk1.

Since hdisk0 is sitting in a state of old_rootvg, I cannot do anything with it until I vary it on.

I have changed the bootlist back to hdisk0 so in case the system does reboot it might actually come back up. It is up and running now.

What steps can I take to get this server back in shape? I would have suspected that hdisk1 would be the problem disk and I could have removed it, then reattached it to rootvg.

Two weeks ago I migrated the system from 5.2.4 to 5.3.3. I DID NOT use an alt_disk_migration.

Thank you

Potentially Toasted!

 

[p5wizard]

NO GUARANTEE FOR SUCCESS, but you might try and create a new hd5 in your rootvg (depending on PP size of your rootvg, specify 1 or 2 partitions, also I believe it is best to create this LV on the first - or first and second - PP of the disk, you might want to create a mapfile first and possibly you may have to move away some other LPs)

/tmp/mapfile
hdisk1:1-2

mklv -y hd5 -t boot -m /tmp/mapfile rootvg 1

or

mklv -y hd5 -t boot -m /tmp/mapfile rootvg 2

then run your bosboot command again.

You als want to have an mksysb tape/CD/DVD handy, perhaps you can even create a new one now from your "still running" system.

HTH,

p5wizard

 

[hirschaj]

It looks like alt_disk_install was already run on this server. old_rootvg is what the original rootvg is called when you boot off of alt_rootvg. Your output is sort of baffling since hd5 would be needed for boot. If you want to look at what is in old_rootvg you can wake it up by using "alt_disk_install -W old_rootvg". This will rename old_rootvg to altinst_rootvg then you can varyonvg (if needed) and "lspv -l altinst_rootvg". If that rootvg is completely intact you can put it back to sleep using "alt_disk_install -S altinst_rootvg" and change your bootlist to hdisk0. I would be ready to recover from mksysb if you attempt the reboot though in case something is messed up.


Jim Hirschauer

http://www.aixexpert.com

 

[GFGMojo]

Fixed it - thanks all -

# mklv -y hd5 -t boot -a e rootvg 1 hdisk1

# bosboot -a

# bootlist -m normal -o hdisk1

Thanks to all! I will have to be much more careful next time.

Off to mirror the disks!