Originally posted by: Bancal

Hello,

I'm sort of stuck after importing rootvg group on a host with existing rootvg. As you know this leads to automatic renaming of logical volumes of the imported rootvg so what they do not overlap existing logical volumes.

In essense it looks as follows:
0516-530 synclvodm: Logical volume name hd5 changed to bootlv00.
0516-530 synclvodm: Logical volume name hd6 changed to pagelv00.
0516-530 synclvodm: Logical volume name hd8 changed to loglv01.
0516-712 synclvodm: The chlv succeeded, however chfs must now be
run on every filesystem which references the old log name hd8.
0516-530 synclvodm: Logical volume name hd4 changed to fslv01.
0516-530 synclvodm: Logical volume name hd2 changed to fslv02.
0516-530 synclvodm: Logical volume name hd9var changed to fslv03.
0516-530 synclvodm: Logical volume name hd3 changed to fslv04.
0516-530 synclvodm: Logical volume name hd1 changed to fslv05.
0516-530 synclvodm: Logical volume name hd10opt changed to fslv06.
0516-530 synclvodm: Logical volume name fwdump changed to fslv07.
imfs: Warning: mount point / already exists in /etc/filesystems.
imfs: Warning: mount point /usr already exists in /etc/filesystems.
imfs: Warning: mount point /var already exists in /etc/filesystems.
imfs: Warning: mount point /tmp already exists in /etc/filesystems.
imfs: Warning: mount point /home already exists in /etc/filesystems.
imfs: Warning: mount point /opt already exists in /etc/filesystems.
imfs: Warning: mount point /var/adm/ras/platform already exists in /etc/filesystems.

Now I'm unable to boot the LPAR from which I imported rootvg and get 0557 error code. My case is just the same as an issue described here http://www.unix.com/aix/212173-aix-0557-error-root-file-system-does-not-mount.html

My question is how should I revert to original logical volume names and make the LPAR bootable.

I try to boot the LPAR in SMS mode then select maintenance mode. Next I select to access rootvg. Now there is a fork in SMS menu. I've got two options: either import rootvg and start a shell or start a shell w/o importing rootvg.
Whenever I choose importing rootvg, I get an error about /usr. AIX can't find JFS log for it and, therefore, can't mount it. Once this error message is displayed, I got a quite restricted shell where I'm unable to do ls, mount, chlv, chfs etc. In short, I'm unable to rename logical volumes by using this shell.

If I opt to start a shell before mounting rootvg I get the same restricted shell where chlv and chfs are both unavailable. I can fsck all filesystems and mount them but this doesn't help to change logical volume names.

I need a step by step procedure on how should I rename logical volumes and make LPAR bootable again.

Originally posted by: dario_cinquetti

Hi,

woh did you manage ?

I am in the same situation, trying to reboot the 'shuffled' rootvg....

Let me know ...

 

tia

dario

Originally posted by: Wouter Liefting

Interesting problem. I've never actually done this myself, but I would try to fix things using the tools that are provided as part of the "alternate disk install" method of AIX.

In essence this method allows you to install to a "new rootvg" while the old system is running, or clone your existing system to a "new rootvg", performing updates in the process. Once you've done that, there are tools that allow you to mount your "new rootvg" in the old system, or your "old rootvg" in the new system. (Which rootvg is used to boot is determined at boot time through the SMS menu, or with the bootlist command.)

If you can manage to let your mangled rootvg look like a "new rootvg" in the context of the alt_disk_install commands, you may be able to fix things up to the point where the rootvg is bootable again. The AIX boot code knows about alt disk installs and will rename the LVs to their proper name on the fly.

More information here:

http://publib.boulder.ibm.com/infocenter/aix/v7r1/index.jsp?topic=%2Fcom.ibm.aix.install%2Fdoc%2Finsgdrf%2FHT_insgdrf_altdiskinstall_clone.htm

Specifically look for the alt_rootvg_op command.

As said, I haven't done this myself, but this is the way I would try to fix it initially.