Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Linux & AIX dual boot on RS6k IBM p650 7038-6M2

Status
Not open for further replies.

Val3r10

MIS
Jan 30, 2007
2
IT
Hi everybody. I'm ideally using the closed thread thread52-1099809 in this area to put my question.
I successfully installed a dual Linux-AIX system on a p650, with everything upgraded - thanks to the quoted thread - to latest microcode, so I shouldn't have any kernel-limit problem.

This is the snapshot of the WORKING system:
- hdisk0 (U0.1-P2/Z1-A8) Debian 'etch' v4.0 ppc64 Linux
- hdisk1 (U0.1-P2/Z1-A9) rootvg AIX v5.3(ml04)

(AIX is only used for maintenance purposes...)

Until now, everything's fine. If I would start AIX, my SMS boot sequence: ( or, bootlist -m normal -o )
1 hdisk1 blv=hd5
2 hdisk0
... everything's OK and Aix runs fine.

If I would start Linux, changing the normal boot sequence by bootlist, diag or SMS too, in:
1 hdisk0
2 hdisk1 blv=hd5
... AIX is started, not linux.
If hdisk1 is not available (for example, removed, or not in list), I got the well known !20EE000B! error.

On the other hand, if I enter SMS and manually choose hdisk0 (A8), linux runs like a charm. But manually, because even it's the first disk in the boot-chain, it isn't booted.

I found this strange workaround.
With this bootlist:
1 hdisk0
2 cd0
3 rmt0
4 hdisk1 blv=hd5
without entering SMS and manually booting from hdisk0, if there's a bootable cdrom in the device, hdisk0 is SOMETIMES correctly started...
Just like the boot sequence would double check itself when 'broken' by a bootable device between the disks.

Any help or hint how to solve this weird behavior ?

Thanks anybody.

Valerio

 
Thanks for your answer. YES, I did.
And it's almost exactly what I did in SMS configuration (above described), less setting the Multiboot option as <ON>, because I wouldn't the boot process stopped any given restart of the box:

"In order to boot a particular disk in the future, return to the Select Boot Options menu, and select option 3, Multiboot menu. This menu allows you to set the OpenFirmware to always pause at the Multiboot menu on startup (such that the 1 key does not have to be pressed). It also allows you to select from the disks you arranged in the method described above."

I simply would always start with hdisk0 (Linux), less sometimes in maintenance mode. I also could accept to press <1> at the SMS bootup when AIX is needed, but my problem is that the sequence
hdisk0
hdisk1
or simply
hdisk0
is NOT correctly followed without manual intervention

Thanks for any help
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top