Krtld Error During Initial Load Link Phase Solaris 10

CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions in Kernel All PlacesServer & Storage SystemsOracle SolarisKernel This discussion is archived 9 Replies Latest reply on Apr 23, 2009 8:23 PM by 807761 Booting fails 807567 Jun 22, 2008 4:18 PM I am having Sun v240 server. When I am booting gets the following error message. Sun Fire V240, No Keyboard Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.13.2, 1536 MB memory installed, Serial #63971475. Ethernet address 0:3:ba:d0:20:93, Host ID: 83d02093. Rebooting with command: boot Boot device: /pci@1c,600000/scsi@2/disk@0,0:a File and args: boot: cannot open kernel/unix Enter filename [kernel/unix]: /platform/sun4u/kernel/unix Enter default directory for modules [platform/sun4u/kernel /kernel /usr/kernel]: krtld: load_exec: fail to expand cpu/$CPU krtld: error during initial load/link phase panic - boot: exitto returned from client program Program terminated ok Please suggest. 1353Views Tags: none (add) This content has been marked as final. Show 9 replies 1. Re: Booting fails 807567 Jun 22, 2008 8:50 PM (in response to 807567) need some more info... did this ever work? was a kernel patch installed recently? anything else critical change? Like Show 0 Likes(0) Actions 2. Re: Booting fails 807567 Jun 23, 2008 2:49 PM (in response to 807567) sc> console -f Enter #. to return to ALOM. boot: cannot open Enter filename [kernel/sparcv9/unix]: boot: cannot open kernel/sparcv9/unix Enter filename [kernel/sparcv9/unix]: /platform/sun4u/kernel/sparcv9/unix Alloc of 0x400000 bytes at 0x1000000 refused. Elf64 read error. boot failed Enter filename [platform/sun4u/

Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries Inside-ERP VoIP_News MacProTX I_am_the_dragon Inside-CRM maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate https://community.oracle.com/thread/1950187 JoeTorre Locutus Craig Borysowich Dennis Stevenson DukeGanote Richard mircea_luca iudithm Clinton Jones bracke Nikki Klein AbhaiTripathi Iqbalyk blrvenkat jakarman Adrian_Grigoriu COMPANIES Sophos EdgeWave Skybot Software Epicor Software ... View All Topics View All Members View All Companies Toolbox for IT Topics UNIX Groups Ask a New Question Solaris The Solaris group is a http://unix.ittoolbox.com/groups/technical-functional/solaris-l/sun-fire-v280r-boot-problem-panic-boot-exitto64-returned-from-client-program-2222619 forum where peers share technical expertise, solve problems, and discuss issues related to the Solaris operating system, including OS-related malfunctions, security issues, and network performance. Home | Invite Peers | More UNIX Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Sun Fire V280R boot problem "panic - boot: exitto64 returned from client program" ushassymon asked Jul 7, 2008 | Replies (11) Hi Everybody, I am facing a problem with my Sun Fir

patch I saw some error msgs concerning /lib/ld.so.1, and I inadvertently did Ctrl-C, so the patch modifications could not be reverted. Now the server does http://www.adras.com/Cannot-boot-after-interrupting-kernel-patch.t9576-76.html not boot anymore. It hangs with the following error messages: Loading: /platform/SUNW,Sun-Fire-T200/ufsboot Loading: https://wiki.smartos.org/display/DOC/PXE+Booting+SmartOS /platform/sun4v/ufsboot not found: get_cpu_pagesizes do_relocations: /platform/sun4v/kernel/cpu/sparcv9/SUNW,UltraSPARC-T1 do_relocate failed krtld: error during initial load/link phase panic - boot: exitto64 returned from client program Program terminated {0} ok Is there any way to recover from this or I am fu*** and I have to reinstall Solaris from scratch? Thanks for your help! From: Colin B. on 9 krtld error Feb 2007 10:56 GS wrote:> Hi, > I have a Sun T2000 with Solaris 10, and I have a big big problem. > > While installing a kernel patch I saw some error msgs concerning > /lib/ld.so.1, and I inadvertently did Ctrl-C, so the patch modifications > could not be reverted. > > Now the server does not boot anymore. It hangs with the following error > messages: krtld error during > > Loading: /platform/SUNW,Sun-Fire-T200/ufsboot > Loading: /platform/sun4v/ufsboot > not found: get_cpu_pagesizes > do_relocations: /platform/sun4v/kernel/cpu/sparcv9/SUNW,UltraSPARC-T1 > do_relocate failed > krtld: error during initial load/link phase > panic - boot: exitto64 returned from client program > Program terminated > > {0} ok > > > Is there any way to recover from this or I am fu*** and I have to > reinstall Solaris from scratch? Ugly! You might be able to boot from media, and either reapply that patch to a mounted partition, or backout on the patch. However, my instinct is that it's a fairly low probability of working. Good luck. Let us know how it works. Colin From: Richard B. gilbert on 9 Feb 2007 10:56 GS wrote:> Hi, > I have a Sun T2000 with Solaris 10, and I have a big big problem. > > While installing a kernel patch I saw some error msgs concerning > /lib/ld.so.1, and I inadvertently did Ctrl-C, so the patch modifications > could not be reverted. > > Now the server does not boot anymore. It hangs with the following error > messages: > > Loading: /platform/SUNW,Sun-Fire-T200/ufsboot > Loading: /platform/sun4v/ufsboot > not found: get_cpu_pagesizes > do_relocations: /platform/sun4v/kernel/cpu/sparcv9/SUNW,UltraSPARC-T1 > do_relocate failed > krtld: error during initial load

Getting Started with SmartOS PXE Booting SmartOS Tools Attachments (0) Page History Restrictions Info Link to this Page… View in Hierarchy View Wiki Markup PXE Booting SmartOS Skip to end of metadata Page restrictions apply Added by benr@joyent.com, last edited by Sébastien Taylor on Dec 30, 2014 (view change) Comment: Go to start of metadata The NetBoot Environment Adding SmartOS Images to an Existing PXE Environment Building an iPXE Boot Infrastructure ISC DHCP TFTP iPXE PXEGRUB & OpenSolaris Legacy Kernel Boot Options Alternatives Stripped down dnsmasq, tftp-hpa, pxegrub Motivation Zone Configuration Setting up TFTP Setting up DHCP (using Dnsmasq) Setting up the tftpboot directory Integrating SmartOS into an existing PXELINUX environment While USB and DVD installation are useful for small or non-production deployments, SmartOS is fundamentally designed as a netboot operating system. Advantages of netbooting include: Scalability: Media (USB or CD/DVD) is not required for each node Speed: Boot times on a 1Gb/s network (100MB/s) are much faster than USB 2.0 (10-30MB/s depending on USB key) or optical media Versatility & Safety: Clients can be upgraded easily by simply changing the boot target to the new image and rebooting at your leasure into the new image, rather than re-flashing a USB key in place which could leave you stranded on a bad upgrade. This applies equally to upgrades and downgrades. The NetBoot Environment Adding SmartOS Images to an Existing PXE Environment If you already have a DHCP/TFTP environment in place for netbooting, you can simply download the latest platform release and unpack it into your TFTP directory. There are 2 files of importance, the kernel ("unix") and the boot archive ("boot_archive"). The paths to these files are significant and should not be omitted. They should be: (prefix)/platform/i86pc/kernel/amd64/unix (prefix)/platform/i86pc/amd64/boot_archive The prefix may be anything you wish (a common prefix would be "/tftpboot/smartos/20121004T212912Z/") but the path after the prefix must be in the form above. If you do not the OS will fail to boot with an error saying "krtld: error during initial load/link phase"; in this case the image make sure your path is in the proper form. The important point being, don't just untar the latest platform image into your TFTP directory and boot it, you'll have problems unless you change the typical "platform_20121004T