Freeze during boot

[astalavista]

Hi,

I transfered OS(AIX 5.3 P55A LPAR) local disk to SAN disk (alt_disk_copy)
everything seems OK
during boot on SAN disk I am freezed with LED 554
do you know what is the problem ?

Thanks in advance

[Bob M]

Post by astalavista
Hi,
I transfered OS(AIX 5.3 P55A LPAR) local disk to SAN disk (alt_disk_copy)
everything seems OK
during boot on SAN disk I am freezed with LED 554
do you know what is the problem ?
Thanks in advance

You most likely have an access/permissions problem with the SAN. Take a look
here:
http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/ipha6/diag1.htm

Good luck and post what the actual reason was once you solve it?

B

[astalavista]

Post by Bob M
You most likely have an access/permissions problem with the SAN. Take a look
http://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/ipha6/diag1.htm
Good luck and post what the actual reason was once you solve it?

OK but I did the alt_disk_copy with no problem
so I would think the rights are correct ...

[Uwe Auer]

Post by astalavista
Hi,
I transfered OS(AIX 5.3 P55A LPAR) local disk to SAN disk (alt_disk_copy)
everything seems OK
during boot on SAN disk I am freezed with LED 554
do you know what is the problem ?
Thanks in advance

Hi,

to my experience in that case (migrating to SAN disk) you most likely
are missing the appropriate SAN driver in your bootkernel ( i.e. in your
original system). I don't know your SAN device, but if e.g you use some
IBM devices like DS8000, SVC, then you need to customize your system
with the appropriate driver (SDDPCM in that case).

Regards,
Uwe Auer

[astalavista]

to my experience in that case (migrating to SAN disk) you most likely are
missing the appropriate SAN driver in your bootkernel ( i.e. in your
original system). I don't know your SAN device, but if e.g you use some
IBM devices like DS8000, SVC, then you need to customize your system with
the appropriate driver (SDDPCM in that case).

The SAN is a DMX 1000
the boot begin and freeze on 554

[Blazej Antczak]

Post by astalavista

to my experience in that case (migrating to SAN disk) you most likely are
missing the appropriate SAN driver in your bootkernel ( i.e. in your
original system). I don't know your SAN device, but if e.g you use some
IBM devices like DS8000, SVC, then you need to customize your system with
the appropriate driver (SDDPCM in that case).

The SAN is a DMX 1000
the boot begin and freeze on 554

Like Uwe said - you probably don't have correct driver for boot from
SAN. If you have EMC service contract - you can ask them which driver
should be used. I think - OS just can't get drive access. Can you go to
FC card BIOS when server boots? If yes - please check if you can see any
targets at all.

Try to troubleshoot 554 as well - e.g. using boot from CD to maintenance
- have a look into this:

http://www-01.ibm.com/support/docview.wss?rs=111&context=SWG10&uid=isg3T1000132&origin=pSeriesTechnicalBulletin

Look at this as well:

http://www.ibm.com/developerworks/wikis/display/WikiPtype/AIXV53SANBoot

Regards,
Blazej

[Uwe Auer]

Post by astalavista

to my experience in that case (migrating to SAN disk) you most likely are
missing the appropriate SAN driver in your bootkernel ( i.e. in your
original system). I don't know your SAN device, but if e.g you use some
IBM devices like DS8000, SVC, then you need to customize your system with
the appropriate driver (SDDPCM in that case).

The SAN is a DMX 1000
the boot begin and freeze on 554

Hi,

just to clarify - sorry if you already know. Starting boot (i.e. loading the
boot kernel into RAM) from you SAN disk is a matter of System p firmware.
Opening VGs / LV from accessible disks is a matter of boot kernel loaded. And
that's why a missing driver in your bootkernel can cause your problem, although
kernel could be loaded.

From Diag Info for Mult Bus Systems:
-------------------------------------------------------------------------------
554 - The boot device could not be opened or read, or unable to define NFS swap
device during network boot.
-------------------------------------------------------------------------------

My approach would be:
- Get the appropriate driver for your device (I'm not familiar with EMC devices,
but may be you need what is called "powerpath")
- Boot to maintenance
- Install driver
- boosboot -ad /dev/<your_boot_disk>
- Restart

Regards,
Uwe Auer

[Blazej Antczak]

Post by Uwe Auer

Post by astalavista

Post by Uwe Auer
to my experience in that case (migrating to SAN disk) you most likely
are missing the appropriate SAN driver in your bootkernel ( i.e. in
your original system). I don't know your SAN device, but if e.g you
use some IBM devices like DS8000, SVC, then you need to customize
your system with the appropriate driver (SDDPCM in that case).

The SAN is a DMX 1000
the boot begin and freeze on 554

Hi,
just to clarify - sorry if you already know. Starting boot (i.e. loading
the boot kernel into RAM) from you SAN disk is a matter of System p
firmware. Opening VGs / LV from accessible disks is a matter of boot
kernel loaded. And that's why a missing driver in your bootkernel can
cause your problem, although kernel could be loaded.
-------------------------------------------------------------------------------
554 - The boot device could not be opened or read, or unable to define
NFS swap device during network boot.
-------------------------------------------------------------------------------
- Get the appropriate driver for your device (I'm not familiar with EMC
devices, but may be you need what is called "powerpath")

PowerPath its a multipathing software - but really its as well a driver
with multipath functionality. If you'll use EMC PP - make sure that you
using hdiskpowerX as booting device (where X is number corresponding to
your LUN) --> check that with powermt display dev=all command.

Post by Uwe Auer
- Boot to maintenance
- Install driver
- boosboot -ad /dev/<your_boot_disk>
- Restart
Regards,
Uwe Auer

[astalavista]

OK thanks

Post by Uwe Auer
just to clarify - sorry if you already know. Starting boot (i.e. loading
the boot kernel into RAM) from you SAN disk is a matter of System p
firmware. Opening VGs / LV from accessible disks is a matter of boot
kernel loaded. And that's why a missing driver in your bootkernel can
cause your problem, although kernel could be loaded.
-------------------------------------------------------------------------------
554 - The boot device could not be opened or read, or unable to define NFS
swap device during network boot.
-------------------------------------------------------------------------------
- Get the appropriate driver for your device (I'm not familiar with EMC
devices, but may be you need what is called "powerpath")
- Boot to maintenance
- Install driver
- boosboot -ad /dev/<your_boot_disk>
- Restart
Regards,
Uwe Auer

[j***@yahoo.com]

Post by astalavista
Hi,
I transfered OS(AIX 5.3 P55A LPAR) local disk to SAN disk (alt_disk_copy)
everything seems OK
during boot on SAN disk I am freezed with LED 554
do you know what is the problem ?
Thanks in advance

You really need a copy of this EMC doc:

EMC PowerPath for AIX Version 2 5.1 Installation and Administration
Guide


It has a whole chapter on powerpath booting:

This chapter describes how to configure a PowerPath hdiskpower
device as the boot device for an AIX host.
$B"!(B Setting up a PowerPath boot
device ............................................... 36
$B"!(B The pprootdev
tool ............................................................................
38
$B"!(B PowerPath and the bosboot
tool...................................................... 39
$B"!(B Configuring a new PowerPath
installation.................................... 40
$B"!(B Configuring an existing PowerPath
installation ........................... 42
$B"!(B Adding additional
paths...................................................................
47
$B"!(B Disabling PowerPath on a storage system boot device................
48