280R Fails to boot; krtld error

280R Fails to boot; krtld error

Post by d » Sat, 31 Aug 2002 13:42:41



Hello!

I would appreciate any advice.

I have a Sun Fire 280R (2 * 950MHz) with 4GB memory and 73GB disks.

I have a boot disk with a preconfigured version of Solaris 8 4/01 on
it and it should be patched pretty close up to date. I'm trying to
boot from this boot disk. my understanding is that the 280R is a
server version of the Blade 1000 -- of which I've used this same boot
disk, installed a qlc (fibre channel driver) for and it worked like a
charm. I was hoping to do the same with the 280R but i keep getting
the following errors and i don't undetstand why:


 File and args:
krtld: load_exec: fail to expand cpu/$CPU
krtld: error during initial load/link phase
panic - boot: exitto64 returned from client program
Program terminated
{0} ok

i spent a good amount of time on google looking for stuff -- and many
of the search results suggests that 7/01 fixes the problem. However, i
don't understand why it is necessary ..  I have read a product note
that ships with the Blade 1000 and 280R and it suggests to me that i
should be okay with 4/01.  I've tried searching for the meaning of
this error message to no avail. and moreover, the blade is operational
now with the OS software from the same boot disk!

It seems like others have been through this -- i'm hoping i don't have
to move to 7/01 -- can anyone make a suggestion as to why this is
happening?  Please share your experiences.

Thank you very very much!
-

 
 
 

280R Fails to boot; krtld error

Post by Jimm » Sat, 31 Aug 2002 15:30:12



> I have a Sun Fire 280R (2 * 950MHz) with 4GB memory and 73GB disks.

> [...]
> krtld: load_exec: fail to expand cpu/$CPU
> krtld: error during initial load/link phase

The problem is that the CPU's you've got require at least Solaris 8 10/01.

The error message (which isn't very clear) is basically the kernel's
runtime linker telling you it can't resolve the CPU type...because there
is no support for those modules in your boot image.

Sorry that isn't what you wanted to hear but you'll have to move to 10/01
at least.

Cheers
Jimmo

 
 
 

280R Fails to boot; krtld error

Post by Casper H.S. Di » Sat, 31 Aug 2002 17:27:36



>I have a Sun Fire 280R (2 * 950MHz) with 4GB memory and 73GB disks.

Do these CPUs announce themselves as UltraSPARC-III+?

>I have a boot disk with a preconfigured version of Solaris 8 4/01 on
>it and it should be patched pretty close up to date. I'm trying to
>boot from this boot disk. my understanding is that the 280R is a
>server version of the Blade 1000 -- of which I've used this same boot
>disk, installed a qlc (fibre channel driver) for and it worked like a
>charm. I was hoping to do the same with the 280R but i keep getting
>the following errors and i don't undetstand why:

> File and args:
>krtld: load_exec: fail to expand cpu/$CPU

Looks like you need the UltraSPARC-III+ CPU module.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

 
 
 

280R Fails to boot; krtld error

Post by d » Sat, 31 Aug 2002 21:16:59


Hello Jimmo and Casper and everyone!

Thank you for your very quick responses. I very much appreciate this.

Casper, by CPU announcement, i think they do announce themselves as
UltraSparc III+

This is from the boot screen:
Sun Fire 280R (2 X UltraSPARC-III+) , No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc.  All rights reserved.

Also, Casper, where may i get this UltraSPARC-III+ CPU module?

Jimmo,

thank you too for your response. your explaination sounds
reasonable...  from What Casper has noted, there may seem to be some
addition onto 4/01 that may breathe life into this. i really hope that
there is a solution for this.

thanks very much!



> > I have a Sun Fire 280R (2 * 950MHz) with 4GB memory and 73GB disks.

> > [...]
> > krtld: load_exec: fail to expand cpu/$CPU
> > krtld: error during initial load/link phase

> The problem is that the CPU's you've got require at least Solaris 8 10/01.

> The error message (which isn't very clear) is basically the kernel's
> runtime linker telling you it can't resolve the CPU type...because there
> is no support for those modules in your boot image.

> Sorry that isn't what you wanted to hear but you'll have to move to 10/01
> at least.

> Cheers
> Jimmo

 
 
 

1. UniPack and 2.5 booting: cannot find misc/krtld

This is a good one. I've just installed Solaris 2.5 on a SPARCStation 2,
with 64MB RAM, and only one disk - an external 2.1GB Sun UniPack,
connected to the SS2's normal SCSI connector via the cable supplied
with the UniPack. Installation was fine, but when attempting to boot,
I get:

boot: cannot find misc/krtld

I've repeated the installation (Developer's package, with some additions
but nothing removed) several times, with the same result. The disk
produces the same effect on other SS2's, which have had the same
installation done onto their own (non-UniPack) external disks without
problem.

Naturally, I've mounted the disk after booting from CD-ROM;
/kernel/misc/krtld is there, and looks just like the one on the other
SS2s. The SS2 in question has a *newer* PROM rev. than the others,
but since they fail to boot from this disk anyway, I'm assuming it's
either the UniPack or the cable that's making the difference. However,
if anyone's got any other suggestions, I'd be grateful.

steve
--

ISPs are responsible for maintaining the Information Superhighway. They
are not responsible for how you drive.      #include <std_disclaimer.h>

2. CERN httpd w/ cache: How to tell it works ?

3. alpha (alcor) failing during boot: NCR53c810/NCR53c875 give error "Cache test failed"

4. what's wrong?

5. krtld error msg using DLT8000, need help

6. VGA work for Xfree and KDE

7. help pls - fsck fail on boot; fixed, fsck still fails on boot

8. If MS were, should Linux too?

9. Sun Fire 280R boot problems

10. Sun Fire 280R - keeps crashing with "Error ECC corrected"

11. 280R crash with AFT1 errors

12. 43P-260 firmware errors - boot fails

13. RAID1 Boot fails with LILO Error L40