请教solaris10 11/06 安装错误
在OK状态下输入BOOT CDROM后出现以下信息:
************************************
Sun Fire 480R, Keyboard Present
Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.10.8, 4096 MB memory installed, Serial #58406184.
Ethernet address 0:3:ba:7b:35:28, Host ID: 837b3528.
Rebooting with command: boot cdrom
Boot device: /pci@8,700000/ide@6/cdrom@0,0:f File and args:
SunOS Release 5.10 Version Generic_118833-33 64-bit
Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
*******
错误信息
*******
Feb 12 00:46:18 svc.startd[11]: restarting after interruption
Feb 12 00:46:19 svc.startd[14]: restarting after interruption
Requesting maintenance mode
(See /lib/svc/share/README for additional information.)
******************************
/lib/svc/share/README 文件的内容
******************************
Copyright 2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
ident "@(#)README.share 1.2 05/09/01 SMI"
/lib/svc/share/README
smf(5): Notes on maintenance mode and recovery
Failures that bring the system to maintenance mode may include hardware
or critical software failures. The procedures below are given so that
some software repairs can be made; the recommended exit approach once a
repair has been made is to reboot the system. The system can be brought
to maintenance mode deliberately via the '-s' option to boot(1M), or via
the 's' option to init(1M).
In failure scenarios, smf(5) may or may not be running, depending on
which component has failed. If smf(5) is running, and the /usr
filesystem is reachable, then the usual svcadm(1M) invocations to clear
maintenance state and restart services instances can be used.
Otherwise, the following instructions describe the direct execution of
service methods, so that capabilities that svc.startd(1M) would normally
start automatically can be started manually. In the case that the
document recommends an invocation like
# /lib/svc/method/example-method start
you may also consider running these scripts with the shell displaying
the commands from the service method as they are executed. For sh(1)
based scripts, this would mean running the method as
# /sbin/sh -x /lib/svc/method/example-method start
Some methods may be written to instead use ksh(1), with invocation
# /usr/bin/ksh -x /lib/svc/method/example-method start
The first line of the service method script will generally specify its
required interpreter using the standard #! notation. Method scripts may
potentially require interpreters other than sh(1) or ksh(1).
1. Boot archive failure
Boot archive may become out of sync with the root filesystem in
a reboot following an abnormal system shutdown. The recommended
action is to reboot immediately, choose "Solaris failsafe" when
the boot menu is displayed. Type 'i' to get an interactive recovery
shell and follow instructions to update the boot archive.
If the list of stale files are not yet loaded by the kernel
or are compatible, you may continue booting by clearing the
boot-archive service state
# svcadm clear system/boot-archive
2. Failure to mount filesystems.
In cases where the system was unable to bring a combination of the
system/filesystem/{root,usr,minimal} services online, it may be possible
to directly execute the corresponding service methods
# /lib/svc/method/fs-root
# /lib/svc/method/fs-usr
# /lib/svc/method/fs-minimal
to mount the various filesystems. In the case that these methods fail,
a direct invocation of mount(1M), and potentially fsck(1M), should be
attempted for file systems required for recovery purposes.
/lib/svc/method/fs-usr attempts to remount the root file system
read-write, such that persistent changes can be made to the system's
configuration. If this method is failing, one can directly remount
using the mount(1M) command via
# /sbin/mount -o rw,remount /
/etc/svc/volatile is a temporary filesystem generally reserved for Sun
private use. It may prove a useful location to create mount points if
the root file system cannot be remounted read-write.
3. Failure to run svc.configd(1M).
svc.configd(1M) will give detailed instructions for recovery if the
corruption is detected in the repository. If svc.configd(1M) cannot be
run because of missing or corrupt library components, then the affected
components will need to be replaced. Components could be copied from a
CD-ROM or DVD-ROM, or from another system.
4. Failure to run svc.startd(1M).
If the inittab(4) line to invoke svc.startd(1M) is missing or incorrect,
it will need to be restored. A valid entry is
smf::sysinit:/lib/svc/bin/svc.startd >/dev/msglog 2<>/dev/msglog </dev/console
If svc.startd(1M) cannot be run because of missing or corrupt library
components, then the affected components will need to be replaced, as
for svc.configd(1M) above.
5. Activating basic networking configuration.
If svc.startd(1M) did not execute successfully, it may also be necessary
to activate network interfaces manually, such that other hosts can be
contacted. The service methods can be invoked directly as
# /lib/svc/method/net-loopback
# /lib/svc/method/net-physical
If these methods fail, a direct invocation of ifconfig(1M) can be
attempted.
In some scenarios, one may be able to use routeadm(1M) to activate more
dynamic route management functionality; restoring the default dynamic
routing behaviour can be done using the '-u' option. (Invoking routeadm
with no arguments will display which commands must be accessible for the
current routing configuration to be invoked.) Otherwise, once
interfaces are up, a default route can be manually added using the
route(1M) command. On typical IPv4 networks, this invocation would be
# /sbin/route add net default _gateway_IP_
--
(An extended version of this document is available at
http://sun.com/msg/SMF-8000-QD. That version includes additional
document references.)>
请问这是什么问题?如何解决?
...全文
相关推荐
Oracle 10g R2 for Solaris x86在Solaris 11上的安装
### Oracle 10g R2 for Solaris x86 在 Solaris 11 上的安装指南#### 一、概述本文将详细介绍如何在 Solaris 11 操作系统上安装 Oracle 10g
Solaris 10上为Oracle 11G安装设置内核参数
Solaris 10上为Oracle 11G安装设置内核参数 如果使用Solaris系统缺省的内核参数,会导致创建数据库时出现Out of memory错误。 Solaris 10以前的版本是在/etc/system中设置系统参数,这种方式在Solaris 10/OpenSolaris中已经不用。 取而代之的是基于project的配置方式。 a. 修改 /etc/system,在其中添加
solaris10下安装oracle11gr2详解
### Solaris 10 下安装 Oracle 11g R2 数据库详解#### 一、环境准备在开始安装之前,需要确保环境已经准备好。
solaris10U11+Oracle RAC 11g安装文档
"Solaris 10 U11 + Oracle RAC 11g 安装文档"本文档详细介绍了 Solaris 10 U11 操作系统安装和 Oracle RAC 11g 的安装实施管理过程。
安装补丁solaris11
安装补丁 Solaris 11 的 troubleshoot:1. 如果在更新软件包时出现错误,可能是因为 Repository 库没有正确地更新。2.


其他技术讨论专区
