Why does my Linux LPAR fail to boot from boot media?

SBAdmin Support

Need Help? We got you covered.

Why does my Linux LPAR fail to boot from boot media?

When booting from SBAdmin boot media (network boot or CDROM), I get the following error:

FILE: clone3.storix
FINAL Packet Count = 21262
FINAL File Size = 10886048 bytes.
CLAIM failed
Call History
throw – c3903c
$call-method – c46d48
(poplocals) – c3a758
(init-program) – c7e038
boot – c7ec7c
evaluate – c4a638
invalid pointer – d4578d
invalid pointer – 7
invalid pointer – 7
quit – c4ad0c
quit – c4aae0

My Fix Pt Regs:
00 0000000000000000 0000000000000000 00000000deadbeef 0000000000c46d44
04 0000000000c3fde8 0000000000000007 0000000000c11f60 0000000000c03010
08 0000000008000000 0000000000000000 0000000000000000 80000000001e42ac
0c 0000000000004000 0000000000c17100 0000000000c18000 000000000009c498
10 0000000000d7ab34 0000000000d7a8cd 0000000000c46d40 0000000000c46d48
14 fffffffffffffffe 0000000000004000 0000000000000000 0000000000000000
18 0000000000c13000 0000000000c38000 0000000000c14fc0 0000000000c16fc0
1c 0000000000c20000 0000000000c3fdf0 0000000000c11fa8 0000000000c10ff8
Special Regs:
%IV: 00000900 %CR: 24808000 %XER: 20000008 %DSISR: 00000000
%SRR0: 0000000000c3eae0 %SRR1: 800000000000b002
%LR: 0000000000c4604c %CTR: 0000000000c462f4
%DAR: 0000000000000000
PFW: Unable to send error log!


This error occurs when the size of the boot image is too large for the Open Firmware to support.

To resolve this issue go to the Open Firmware prompt and change the “real-base” size:

0 > setenv real-base 2000000
0 > reset-all

The system will reboot with the new “real-base” size.

To display the value of “real-base”:

0 > printenv real-base

*Note depending on the kernel that is being booted, “real-base” may need to be adjusted larger or smaller.