Hi guys,

I have assigned two fc cards to 1 lpar and created 50GB logical volume
on the FAStT as rootvg. I managed to install AIX but after the
installation, it always go to SMS mode. It seems unable to find the
boot device.
Is there a procedure for installing/configuring and booting up a lpar
from SAN???

thanks

Did you change "Boot to SMS" to "Continue to operating system" in ASMI?
Just a hint. (Also, try to exit SMS and the box may boot up just fine.)

Hi,

That's the problem. Once i exit from SMS, it will boot up just fine but
whenver i reboot the lpar, it will go back to SMS mode again.

Where is the ASMI???
Thanks

I think i know what is ASMI ASM interface....
Thank

On 5 Feb 2006 10:14:12 -0800, "day88" <patrickkuah@gmail.com> wrote:

>Hi,
>
>That's the problem. Once i exit from SMS, it will boot up just fine but
>whenver i reboot the lpar, it will go back to SMS mode again.
>
>Where is the ASMI???
>Thanks


Don't worry about the ASMI, It sounds like you are starting the LPAR
with a profile that is set to start in SMS. Modify the profile your
using to start it so it boots normally.

Steven

Thanks Steven. The profile is configure to "Normal" boot. I will check
the ASM menu.

Steven is probably right. I missed the LPAR bit. If you did not use
ASMI to set boot mode, which is most likely the case, then your problem
is not caused by ASMI either. But if it isn't ASMI and your profile is
not set to SMS then I have no idea what may cause your system to start
SMS instead of booting AIX.

sbzx wrote:
> Steven is probably right. I missed the LPAR bit. If you did not use
> ASMI to set boot mode, which is most likely the case, then your problem
> is not caused by ASMI either. But if it isn't ASMI and your profile is
> not set to SMS then I have no idea what may cause your system to start
> SMS instead of booting AIX.

Was the profile originally set to SMS and then changed later on? If so,
you need to power off the lpar, not just reboot, to make it effective.

Thank guys,

I turned of multiboot in the SMS mode and this solved the problem

turn off multiboot