This little gem will keep your head from spinning off your shoulders when you have a multibos fail to clean up (multibos -R).
This can happen when a multibos install gets interrupted, or something weird happens – it’ll hose up the whole multibos instance, and won’t let you remove it. Here is what it will look like:
user@computer:$ multibos -R
Initializing multibos methods ...
Initializing log /etc/multibos/logs/op.alog ...
Gathering system information ...
+-----------------------------------------------------------------------------+
Remove Operation
+-----------------------------------------------------------------------------+
Verifying operation parameters ...
+-----------------------------------------------------------------------------+
Boot Partition Processing
+-----------------------------------------------------------------------------+
multibos: 0565-084 Error processing primary boot partition.
multibos: 0565-002 ATTENTION: cleanup did not complete successfully.
Log file is /etc/multibos/logs/op.alog
Return Status: FAILURE
Initializing multibos methods ...
Initializing log /etc/multibos/logs/op.alog ...
Gathering system information ...
+-----------------------------------------------------------------------------+
Remove Operation
+-----------------------------------------------------------------------------+
Verifying operation parameters ...
+-----------------------------------------------------------------------------+
Boot Partition Processing
+-----------------------------------------------------------------------------+
multibos: 0565-084 Error processing primary boot partition.
multibos: 0565-002 ATTENTION: cleanup did not complete successfully.
Log file is /etc/multibos/logs/op.alog
Return Status: FAILURE
Here are some step to fix this:
1. Unmount the remaining multibos filesystems:
umount filesystem name
rmfs filesystem name
rmfs filesystem name
2. Once these have been cleaned up, remove the old rootvg volume group.
varyoffvg oldrootvg
exportvg oldrootvg
exportvg oldrootvg
3. Migrate your rootvg volume group from hdisk2 and 3 (or wherever there current location is) over to 0 and 1.
migratepv hdisk2 hdisk0
migratepv hdisk3 hdisk1
migratepv hdisk3 hdisk1
4. Remove the boot device.
Rmlv hd5
5. Next, you need to clear the boot information off of hdisk0, 1, 2 and 3 (the new location for rootvg and the old location for rootvg.
chpv –c hdisk0
chpv –c hdisk1
chpv –c hdisk2
chpv –c hdisk3
chpv –c hdisk1
chpv –c hdisk2
chpv –c hdisk3
6. Next, create a new boot logical volume. For the label, make sure you put “primary_bootlv”.
smitty lv
Or
mklv –y ‘hd5’ –t ‘boot’ –a ‘e’e –L ‘primary_bootlv’ rootvg 1
Or
mklv –y ‘hd5’ –t ‘boot’ –a ‘e’e –L ‘primary_bootlv’ rootvg 1
7. Then you will need to write bootcode to your boot device.
bosboot –ad hdisk0
bootlist –m normal hdisk0 blv=hd5
savebase
bootlist –m normal hdisk0 blv=hd5
savebase
8. Now you should be able to run the multibos –R to delete the multibos shell.