Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1010038.1
Update Date:2011-02-04
Keywords:

Solution Type  Technical Instruction Sure

Solution  1010038.1 :   How to verify your boot media exists and is bootable on a Sun Fire[TM] V20z/40z Server  


Related Items
  • Sun Fire V20z Compute Grid Rack System
  •  
  • Sun Fire V20z Server
  •  
  • Sun Fire V40z Server
  •  
Related Categories
  • GCS>Sun Microsystems>Servers>x64 Servers
  •  

PreviouslyPublishedAs
213787


Description
This document provides some pointers on how to verify your boot media exists and is bootable on a Sun Fire V20z/V40z Server
Symptoms:

How to check boot media and what documents are available



Steps to Follow
After the BIOS phase and when the POST is finished without error, the system will try to boot from the boot media.


Boot devices are many and varying:
  • CD-/DVD-ROM,
  • An internal hard disk or a raid device on the the internal SCSI controller
  • A RAID device on an optional RAID controller card
  • A PXE boot configuration over the network.

As there are varying bootable choices, this Infodoc will only consider the basic steps to verify.

Booting from a single boot hard disk connected to the internal LSI SCSI controller

During the Systems start up phase, the BIOS shows information about the configuration of the internal SCSI controller:

LSI Logic Corp. MPT IME BIOS
Copyright 1995-2005 LSI Logic Corp.
MPTBIOS-IME-5.10.02.04
HBA ID LUN VENDOR   PRODUCT              REV  SYNC  WIDE   CAPACITY
--- -- --- -------- ---------------- -------- ----- ---- ------------
0   0  0  SEAGATE  ST336607LC           0007 320.0  16     36706 MB
0   7  0  LSILogic LSI1030[    402]  1032920 320.0  16

In this example, you see that the controller found an existing "SEAGATE" hard disk "ST336607LC" which is usable for the system.

If you do not see the hard disk in this screen, the initialization of the hard disk wasn't successful and it is not available as boot media. You need to follow one of the following the resolution path, depending on your operating system:

<Document: 1017472.1> : Analyzing Internal non-RAID Disk Failures for x64 Solaris
<Document: 1008407.1> : Analyzing Internal non-RAID Disk Failures for x64 Linux
<Document: 1004259.1> : Analyzing Internal non-RAID Disk Failures for Windows Installations

Booting from a RAID Configuration on the Internal SCSI controller

If you have configured a raid (mirror) on the internal LSI Controller of the V20z/V40z, you will see the following screen with information about mirror device:

LSI Logic Corp. MPT IME BIOS
Copyright 1995-2005 LSI Logic Corp.
MPTBIOS-IME-5.10.02.04
HBA ID LUN VENDOR   PRODUCT              REV  SYNC  WIDE   CAPACITY
--- -- --- -------- ---------------- -------- ----- ---- ------------
0   0  0  LSILOGIC 1030 IM       IM     1000        16     36703 MB
0   7  0  LSILogic LSI1030[    402]  1032920 320.0  16
LSI Logic Corp. MPT boot ROM successfully installed!

As you can see, the device ID 0 LUN 0 on the internal HBA 0 shows as product "1030 IM" which means this is an integrated mirror (IM) device.

After the MPT boot ROM is successfully installed, this device should be available as boot medium to the system.

A description of the internal RAID support can be found in the Sun Fire V20z and Sun Fire V40z Servers - User Guide, Part No: 817-5248, Appendix D

Available at: x86 Servers - Legacy Product Documentation

If you need to get information on configuring the internal Raid device, please refer to:

<Document: 1005041.1> : Setting up Integrated Mirror on Sun Fire [TM] V20/V40z

If you have any problems or errors on the internal RAID Disks, you need to follow the following document:

<Document: 1004259.1> : Analyzing Internal RAID Disk Failures for v20/v40z Server Installations

Booting from a MegaRAID PCI controller

When you are using a raid device on an external Mega Raid controller, you should see something like this during startup:

LSI MegaRAID BIOS     Version H420 (Build Jun 28, 2004)
Copyright(c) 2004 LSI Logic Corp.
HA-1 (Bus 3 Dev 0) MegaRAID SCSI 320-2X
Standard FW 413Y DRAM =128MB (SDRAM)
1 Logical Drive(s) found on the host adapter.
1 Logical Drive(s) handled by BIOS
Press <Ctrl><M> to Run MegaRAID Configuration Utility
Or press <Ctrl><H> for WebBIOS

In this sample, one Logical Drive was found which is handled by the BIOS of the system. This device is usable as boot media at the startup of the system.

Booting from a DVD-/CD-ROM media

Booting from DVD-/CD-ROM media is straight forward process. First, you need to determinate if the system has a DVD or CD-ROM drive and if this drive is recognized during the startup process. If you see the following message, a drive is recognized and should be available for booting the system:

ATAPI CD-ROM: MATSHITADVD-ROM SR-8178

If you insert a DVD-/CD-ROM media and the system do not use this to boot from, please check the following steps:

  • Make sure you setup the right boot media order in the BIOS of the system
  • When the drive is blinking all the time, it's indicating that the media isn't readable (e.g. brocken or empty media). In this case please check the media and try to boot from a different media. The media will be ignored and the boot process select the next boot media, e.g. hard disk or network.
  • The media isn't bootable, e.g. just contains data but no bootable block. In this case the DVD-/CD-ROM media will be ignored and the system try to start from a different media, e.g. hard disk or network.

Checking your PXE boot configuration

If you are trying to boot your system over the network, e.g. to install an Operating System on the server, you use PXE boot for this process.

If you select the network interface as boot device, you will see the following during the startup process:

Broadcom UNDI PXE-2.1 v7.6.6
Copyright (C) 2000-2004 Broadcom Corporation
Copyright (C) 1997-2000 Intel Corporation
All rights reserved.
CLIENT MAC ADDR: 00 09 3D 13 xx xx  GUID: C6B231EA 45C1 11DA B7E9 001083FB2573
DHCP.-

At this point, the PXE boot agent tries to get the TFTP server address and boot image information about the boot process from the DHCP server.

If you are installing the Linux Operating System over the network, please refer to:

  • Sun Fire V20z and Sun Fire V40z Servers--Linux Operating System Installation Guide, Part No: 817-5250

Available at:

x86 Servers - Legacy Product Documentation



Product
Sun Fire V40z Server
Sun Fire V20z Server
Sun Fire V20z Compute Grid Rack System

Internal Comments
If you are installing the Solaris OS over the network, please refer to:

<Document: 1018925.1> : PXE boot example with Solaris[TM] 10 01/06 Operating System on Sun Fire[TM] 40z Server.


This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this
document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the "Document Feedback" alias(es) listed below:
Normalization team alias: tsc-emea-x64@sun.com
Domain Lead: Anthony.McNamara@sun.com

x64, normalized, v20z, v40z, boot, PXE, DVD
Previously Published As
91616

Change History
Date: 2007-12-29
User Name: 31620
Action: Approved

Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback