Error /pci@400/pci@2/pci@0/pci@4/scsi@0 Boot-read Fail
Contents |
Preinstalled Software Supported Versions of Oracle Solaris OS, Firmware, and Software OS Package and Patch Updates Determining Oracle Solaris 11 OS Package Update Version Determining Oracle Solaris 10 Patch Revision Minimum Required Patchset for Oracle Solaris 10 8/11 OS eeprom auto-boot Minimum Required Patchsets and SPARC Bundle for Oracle Solaris 10 9/10 OS
Eeprom Boot-device
Minimum Required Patchsets and SPARC Bundle for Oracle Solaris 10 10/09 OS Installing and Booting Oracle Solaris 11 From solaris 10 eeprom boot device Devices Connected to a USB Port Support for new 16 Gbyte and 32 Gbyte DIMMs Rules for I/O Slot Use by Certain Cards 2. Known Product Issues Hardware Issues Maximizing Memory ok boot prompt commands in solaris Bandwidth Direct I/O Support Use Links Labeled SPARC T3 to Download sas2ircu Firmware and Documentation for SPARC T4 Servers Sun Type 6 Keyboards Are Not Supported By SPARC T4 Series Servers Caution Needed When Removing a SATA Data Cable From a Backplane Connector Caution Needed When Handling the Connector Board Server Panics When Booting From a USB Thumbdrive Attached to the Front
Eeprom Devalias
USB Ports (Bug ID 15667682) PSH Might Not Clear a Retired Cache Line on a Replaced Motherboard (Bug ID 15705327, Bug ID 15713018) PCIe Correctable Errors Might Be Reported (Bug ID 15720000, Bug ID 15722832) SPARC T3 and T4 Platforms Might See Dropped or Doubled Character Input From USB Keyboards (Bug ID 15700526, Bug ID 15728507) Supplementary Notes L2 Cache UEs Are Sometimes Reported as Core Faults Without Any Cache Line Retirements (Bug ID 15731176) Upon a Reboot After an Unrecoverable Hardware Error, CPUs Might Not Start (Bug ID 15733431) reset /SYS Operations Can Cause the SAS Controller to Disappear (Bug ID 15737475) SAS Command Might Fail to Complete When Certain SAS Devices Are Put Under Heavy Load (Bug ID 15802084) Rebooting an SDIO-SAS HBA Guest Domain Might Generate ereport.io.pciex.pl.re (Bug ID 15718101) Characters Are Occasionally Dropped at the Oracle OpenBoot Prompt (Bug ID15813690) Oracle Solaris OS Issues When a Start Address Is Not Aligned With the Largest Page Size, the OS Should Use the Next Available Page Size (Bug ID 15718159) Cannot Boot Oracle Solaris 10 10/09 OS (U8) From the Internal DV
a SPARC Based System (Overview) 2.Booting a SPARC Based System to a Specified State (Tasks) 3.Shutting Down a System (Tasks) 4.Rebooting a SPARC Based System (Tasks) 5.Booting a SPARC Based System From the Network (Tasks) 6.Modifying Boot Parameters on a SPARC Based System (Tasks) Modifying Boot nvalias commands solaris Parameters on a SPARC Based System (Task Map) Modifying Boot Parameters on a SPARC Based devalias boot-device System How to Identify the PROM Revision Number for a System How to Identify Devices on a System How to Determine the Default Boot
Solaris "boot -r"
Device How to Change the Default Boot Device by Using the Boot PROM How to Change the Default Boot Device by Using the eeprom Utility How to Change the Default Boot File by Using the Boot PROM How https://docs.oracle.com/cd/E22985_01/html/E22987/z400000b1036986.html to Change the Default Boot File by Using the eeprom Utility 7.Creating, Administering, and Booting From ZFS Boot Environments on SPARC Platforms (Tasks) 8.Keeping a SPARC Based System Bootable (Tasks) 9.Troubleshooting Booting a SPARC Based System (Tasks) Index Modifying Boot Parameters on a SPARC Based System The boot PROM is used to boot a SPARC based system and to modify boot parameters. For example, you might want to reset the device from which to boot, change the default https://docs.oracle.com/cd/E23824_01/html/821-2731/gkkvd.html boot file or kernel, or run hardware diagnostics before bringing the system to a multiuser state. If you need to perform any of the following tasks, you need to change the default boot device: Add a new drive to the system either permanently or temporarily Change the network boot strategy Temporarily boot a stand-alone system from the network For a complete list of PROM commands, see the monitor(1M) and eeprom(1M) man pages. How to Identify the PROM Revision Number for a System Bring the system to the ok PROM prompt.For more information, see How to Shut Down a System by Using the init Command. Display a system's PROM revision number by using the banner command.ok banner How to Identify Devices on a System You might need to identify the devices on a system to determine the appropriate devices from which to boot.Before You Begin Before you can safely use the probe commands to determine what devices are attached to the system, you need to do the following: Change the PROM auto-boot? parameter to false.ok setenv auto-boot? false Issue the reset-all command to clear system registers.ok reset-all You can view the probe commands that are available on your system by using the sifting probe command:ok sifting probe If you run the probe commands without clearing the system registers, the following message is displayed:ok probe-scsi This command may hang the system if a
Server and Site Specifications Installation Task Overview Server Overview Front Panel Components Rear Panel Components Confirming Specifications Preparing for Installation Shipping Kit Inventory List Handling Precautions ESD Precautions Tools Needed for Installation Installing the Server Install Optional Components https://docs.oracle.com/cd/E23075_01/html/E23076/z40002af1505679.html Rack Compatibility Rack Cautions Stabilize the Rack Disassemble Slide Rails Install Mounting Brackets https://www.veritas.com/support/en_US/article.000064711 on Server Attach Slide Rail Assemblies to Rack Install the Server Installing the CMA (Optional) Connecting Cables Cabling Requirements Identifying Ports Connecting Data and Management Cables Secure Cables to CMA (Optional) Powering On the Server for the First Time Prepare the Power Cords Connect a Terminal or Emulator to the SER MGT Port Power eeprom boot on the System for the First Time Oracle ILOM System Console Installing the OS Oracle Solaris OS Configuration Parameters Assigning a Static IP Address to the SP Assign a Static IP Address to the NET MGT Port Administration Understanding System Administration Resources Oracle ILOM Overview Platform-Specific Oracle ILOM Features Oracle Solaris OS Overview OpenBoot Overview Oracle VM Server for SPARC Overview Multipathing Software Hardware Management Pack Overview Source error /pci@400/pci@2/pci@0/pci@4/scsi@0 boot-read for Downloading Hardware Management Pack Software Hardware Management Pack Documentation Accessing the Server Log In to Oracle ILOM Log In to the System Console Display the ok Prompt Display the Oracle ILOM -> Prompt Use a Local Graphics Monitor Oracle ILOM Remote Console Controlling the Server Power On the Server (Oracle ILOM) Power Off the Server (Oracle ILOM) Reset the Server (Oracle Solaris OS) Reset the Server (Oracle ILOM) Reset the SP to Default Values Configuring Hardware RAID Hardware RAID Support Important Hardware RAID Guidelines Prepare to Use the FCode Utility FCode Utility Commands Create a Hardware RAID Volume Hot Spare Drives in RAID Volumes (LSI) Determining If a Drive Has Failed RAID Drive Replacement Strategies Locate Device Paths Changing Server Identification Information Change Customer Data on FRU PROMs Change System Identifier Information Configuring Policy Settings Specify Cooldown Mode Restore the Host Power State at Restart Specify the Host Power State at Restart Disable or Re-Enable the Host Power-On Delay Specify Parallel Boot of the SP and Host Configure Host Behavior (Keyswitch State) Configuring Network Addresses SP Network Address Options Disable or Re-Enable Network Access to the SP Display the DHCP Server IP Address Display the IP Address of the SP Di
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet How to replace a faulty Solaris boot disk (boot device) Article:000064711 Publish: Article URL:http://www.veritas.com/docs/000064711 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Description The following article attempts to explain the steps required to replace a faulty boot disk (boot device) on Solaris. Figure 1.0 In the above example, disk media (dm) name "rootdg01" has failed and needs to be replaced.Configuration details # modinfo | grep vx 35 1347360 37f28 308 1 vxdmp (VxVM 5.0-2006-05-11a: DMP Drive) 37 7c002000 337840 309 1 vxio (VxVM 5.0-2006-05-11a I/O driver) 39 137b4e0 d48 310 1 vxspec (VxVM 5.0-2006-05-11a control/st) 188 7b7ff338 c30 311 1 vxportal (VxFS 5.0_REV-5.0A55_sol portal ) 189 7ae00000 1ba6d0 21 1 vxfs (VxFS 5.0_REV-5.0A55_sol SunOS 5) # uname -a SunOS dopey 5.10 Generic_138888-01 sun4v sparc SUNW,T5140 # cat /etc/release Solaris 10 10/08 s10s_u6wos_07b SPARC Copyright 2008 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 27 October 2008 Veritas Volume Manager (VxVM) disk content# vxdisk -eo alldgs list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME c1t0d0s2 auto - - error c1t0d0s2 <<<<<<<<<<< disk to replace c1t1d0s2 auto -