| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||||||
Solution Type Technical Instruction Sure Solution 1905981.1 : Solaris may fail to boot after replacing system battery on a SPARC T4-x/T5-x servers
In this Document
Created from <SR 3-9288185162> Applies to:SPARC T4-2 - Version All Versions to All Versions [Release All Releases]SPARC T5-2 - Version All Versions to All Versions [Release All Releases] Information in this document applies to any platform. GoalThe system battery on motherboard may fail with the following message. -> show faulty
Target | Property | Value -------------------+-----------------------+----------------------------------- /SP/faultmgmt/0 | fru | /SYS/MB/BAT /SP/faultmgmt/0/ | class | fault.chassis.battery.fail faults/0 | | /SP/faultmgmt/0/ | sunw-msg-id | SPT-8000-G3 faults/0 | | /SP/faultmgmt/0/ | component | /SYS faults/0 | | /SP/faultmgmt/0/ | uuid | a7fca6b2-10fa-67f4-86a3-df7d8ed8b2 faults/0 | | d8 /SP/faultmgmt/0/ | timestamp | 2014-07-01/05:40:32 faults/0 | | /SP/faultmgmt/0/ | detector | /SYS/MB/V_BAT faults/0 | | /SP/faultmgmt/0/ | system_manufacturer | Oracle Corporation faults/0 | | /SP/faultmgmt/0/ | system_name | SPARC T4-2 faults/0 | | /SP/faultmgmt/0/ | system_part_number | 32343684+1+1 faults/0 | | /SP/faultmgmt/0/ | system_serial_number | xxxxxxxxxx
After replacing the system battery with a new one, Solaris may fail to boot up. When booting Solaris from disk, the system console may display the following error messages: {0} ok boot -F fail -s
: Boot device: /pci@400/pci@2/pci@0/pci@e/scsi@0/disk@p0 File and args: -s | SunOS Release 5.11 Version 11.1 64-bit Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved. INIT: Cannot stat /etc/inittab, errno: 79 INIT: Cannot stat /etc/inittab, errno: 79 INIT: Cannot stat /etc/inittab, errno: 79 : : WARNING: init(1M) exited on fatal signal 9: restarting automatically WARNING: init(1M) exited on fatal signal 9: restarting automatically : (messages repeat forever) When trying to boot cdrom, the system console will display the following messages: {0} ok boot dvd -s ... When trying to boot from network device, the system console will display the following messages: {0} ok boot net:dhcp - install
Boot device: /pci@400/pci@2/pci@0/pci@6/network@0:dhcp File and args: - install 100 Mbps full duplex Link up Timed out waiting for BOOTP/DHCP reply 100 Mbps full duplex Link up SunOS Release 5.10 Version Generic_147440-01 64-bit Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved. - svc.configd: smf(5) database integrity check of: /etc/svc/repository.db failed. The database might be damaged or a media error might have prevented it from being verified. Additional information useful to your service provider is in: /etc/svc/volatile/db_errors The system will not be able to boot until you have restored a working database. svc.startd(1M) will provide a sulogin(1M) prompt for recovery purposes. The command: /lib/svc/bin/restore_repository can be run to restore a backup version of your repository. See http://sun.com/msg/SMF-8000-MY for more information. Requesting System Maintenance Mode (See /lib/svc/share/README for more information.) svc.configd exited with status 102 (database initialization failure)
SolutionIf the system TOD [ time of day] becomes incorrect, by design Solaris will not boot successfully. Because the TOD clock can only be set from Solaris and when the system gets into this state, there is no way from OS's pont of view to fix the problem. In such kind of circumstances, please re-seat the battery so that the server will get a chance to re-initialize the TOD clock. This is supposed to set the TOD to correct value. If re-seating the battery does not resolve the boot failure, please proceed to contact Oracle support engineer (with an existing Service Request) or raise a new Service Request for further investigation.
Other than re-seating the battery to re-initialize the TOD clock, Oracle service engineer can login into the ILOM using Escalation mode, then run the following command to manually set the TOD to the correct time. Note that the timezone here is default in GMT. hw call /SYS/MB/TOD settime MMDDhhmmYYYY
For more information please see [Bug 16410029 - Services framework prevents Solaris from booting if OBP date is incorrect].
References<NOTE:1568668.1> - How to Diagnose and Troubleshoot a System Battery failure on SPARC T3/T4/T5 Systems<NOTE:1567869.1> - SPARC T5-2 : After multiple coin battery replacement the server still reports SPT-8000-G3 (fault.chassis.battery.fail) <NOTE:1327763.1> - Boot returns errors: WARNING: init(1M) exited on fatal signal 9: restarting automatically Attachments This solution has no attachment |
||||||||||||||||
|
||||||||||||||||