Our NIM system becomes unresponsive while working. Look like first time that the root disk was missing. I cannot use many commands like lspv, lspath, ... ssh and other services are not operating.
I have rebooted the machine, and I can boot it to AIX, but it's an older AIX version 6.1 and not the current one 7.1
I also see that the OS is booted from hdisk0, while the current OS is booted from hdisk9. But now hdisk9 belongs to altinst_rootvg and varied off.
Look like the boot volume on hdisk9 was corrupted and system turns to the old one on hdisk0 to boot from it.
How can we re-create the boot volume on hdisk9? I tried to boot the system to single user mode on hdisk0 (old OS version), and try the bosboot command on hdisk9, but not success. It says the hd5 is already available in use.
I tried to use synclvodm and it changed my LVs on altinst_rootvg to new ones. Not sure that it just only renames the LV name, I hope it not overwrite the data on the altinst_rootvg.
Code:
# synclvodm -v altinst_rootvg
synclvodm: Physical volume data updated.
0516-530 synclvodm: Logical volume name hd6 changed to pagelv00.
synclvodm: Logical volume pagelv00 updated.
0516-530 synclvodm: Logical volume name hd8 changed to loglv02.
0516-712 synclvodm: The chlv succeeded, however chfs must now be
run on every filesystem which references the old log name hd8.
synclvodm: Logical volume loglv02 updated.
0516-530 synclvodm: Logical volume name hd4 changed to fslv01.
synclvodm: Logical volume fslv01 updated.
0516-530 synclvodm: Logical volume name hd2 changed to fslv02.
synclvodm: Logical volume fslv02 updated.
0516-530 synclvodm: Logical volume name hd9var changed to fslv03.
synclvodm: Logical volume fslv03 updated.
0516-530 synclvodm: Logical volume name hd3 changed to fslv04.
synclvodm: Logical volume fslv04 updated.
0516-530 synclvodm: Logical volume name hd1 changed to fslv05.
synclvodm: Logical volume fslv05 updated.
0516-530 synclvodm: Logical volume name hd10opt changed to fslv06.
synclvodm: Logical volume fslv06 updated.
0516-530 synclvodm: Logical volume name hd11admin changed to fslv07.
synclvodm: Logical volume fslv07 updated.
0516-530 synclvodm: Logical volume name loglv00 changed to loglv03.
0516-712 synclvodm: The chlv succeeded, however chfs must now be
run on every filesystem which references the old log name loglv00.
synclvodm: Logical volume loglv03 updated.
0516-530 synclvodm: Logical volume name livedump changed to fslv08.
synclvodm: Logical volume fslv08 updated.
0516-530 synclvodm: Logical volume name sec_dumplv changed to lv00.
synclvodm: Logical volume lv00 updated.
0516-530 synclvodm: Logical volume name pri_dumpdev changed to lv01.
synclvodm: Logical volume lv01 updated.
Now I'm downloading the ISO file and can boot into maintenance mode. Can we do the followings:
rename all the LVs to its original name
recreate the hd5 volume
rewrite the boot volume info with bosboot and reboot the system to boot from it.
The thing I'm not very clear is, what is altinst_rootvg? If I can create the boot volume and rename the LV successfully as above, I can boot from it?
With my research about altinst_rootvg, it's a technique to replicate the current OS, this is done by backup purpose. Still reading it for more info ...
Is it necessary to put system into single user mode for applying aix 5.3 TL8 on a aix 5.3.5.0 system ?
Is the TL8 installation not totally safe ?
thank you. (6 Replies)
Hi,
redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages.
- My system is ML11 :
oslevel –r
4330-11
- But xlC.rte is on wrong version :
lslpp -L xlC.rte
xlC.rte ... (3 Replies)
Using nimadm:
nimadm -j nimadmvg -c sap024 -s spot_6100 -l lpp_6100 -d "hdisk1" -Y
Initializing the NIM master.
Initializing NIM client sap024.
0505-205 nimadm: The level of bos.alt_disk_install.rte installed in SPOT
spot_6100 (6.1.3.4) does not match the NIM master's level (7.1.1.2).... (2 Replies)
Hi all,
I am trying to exchange hostname and IP address of two AIX machines.
But i am confused as how to change it ?
do i need to use "smitty mktcpip" or "smitty tcpip" ?
what is the difference between smitty mktcpip and smitty tcpip ?
Also anymore steps to follow or just updating... (3 Replies)
Hello,
I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior.
for example
1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert.
2) disk usage alerts
3)... (5 Replies)
I am new to AIX but not new to unix.
I have an interview for an AIX systems admin position and I know they want someone who has knowledge of High Availability, Failover and LPARs
From my research so far, It appear powerha is used to setup high availability and failover on Power systems but is... (2 Replies)
I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users.
The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)