Oracle Solaris 11: Booting and Shutting Down on SPARC Platforms

4星 · 超过85%的资源需积分: 50 99 浏览量更新于2024-07-30 1 收藏 898KB PDF 举报

"Oracle Solaris 11 操作系统的启动与关闭指南" Oracle Solaris 11 是一个先进的操作系统，主要用于企业级服务器和数据中心环境。它以其稳定性和安全性著称，尤其在SPARC平台上表现优秀。SPARC（Scalable Processor Architecture）是Oracle公司设计的一种高性能的处理器架构，广泛应用于大型服务器和工作站。本指南《Booting and Shutting Down Oracle Solaris on SPARC Platforms》主要聚焦于在SPARC硬件上如何正确地启动和关闭Oracle Solaris 11操作系统。这包括了从基本的系统启动流程到更复杂的故障恢复操作，旨在确保系统的平稳运行和管理。启动过程： 1. **BIOS/EFI Boot**: SPARC系统通常使用开放标准的UEFI（统一可扩展固件接口）或传统的BIOS来加载引导加载程序。在启动时，系统会检测硬件、初始化系统设置，并寻找操作系统内核。 2. **Boot Loader**: Oracle Solaris 11 使用GRUB（GRand Unified Bootloader）或OpenBoot Prom（Open Firmware），它们负责加载内核和初始化进程。 3. **Kernel Initialization**: 内核加载后，开始初始化系统服务，如设备驱动、网络配置、文件系统等。 4. **System Services**: 系统服务如SMF（Service Management Facility）启动，这是Solaris 11中的服务管理框架，用于控制和管理系统的各个服务。 5. **Login Prompt**: 最终，用户界面或命令行提示符出现，允许用户登录并进行进一步的系统操作。关闭过程： 1. **Graceful Shutdown**: 用户或管理员通过`shutdown`命令安全地关闭系统，这会通知所有运行的服务和进程停止工作，确保数据的完整性和系统的正常关闭。 2. **Stopping Services**: SMF会按照预定的顺序停止服务，确保依赖关系得到妥善处理。 3. **Power Off/Reboot**: 系统完成所有必要的清理工作后，硬件电源会被安全关闭，或者系统重新启动。该文档可能还涵盖了故障排查和异常情况下的系统恢复方法，例如在启动过程中遇到问题时如何进入安全模式，或者如何通过NVRAM（非易失性随机存取存储器）设置来修复启动问题。 Oracle Solaris 11 提供了丰富的管理工具和技术，如DTrace（动态跟踪工具）用于系统性能分析，ZFS（Zettabyte File System）作为先进的文件系统提供高可靠性，以及 zones 和 containers 技术实现高效的资源隔离和虚拟化。请注意，Oracle对软件及其相关文档拥有知识产权，并受到严格的使用和披露限制。在使用或分发Oracle Solaris 11时，必须遵守许可协议的条款，未经授权的逆向工程、拆解或反编译是被禁止的。对于美国政府及其代理机构，系统和文档的使用也需遵循特定的政府权利规定。

Guidelines for Booting a System

Keep the following in mind when you boot a system:

■

After a SPARC based system is shut down, it is booted by using the boot command at the

PROM level.

■

A system can be rebooted by turning the power o and then back on.

Caution – This method is not considered a clean shutdown. Use this shutdown method only

as an alternative in emergency situations. Because system services and processes are

terminated abruptly, le system damage is likely to occur. The work required to repair this

type of damage could be substantial and might require the restoration of various user and

system les from backup copies.

Reasons to Boot a System

The following table lists system administration tasks and the corresponding boot option that is

used to complete the task.

TABLE 1–2 Reasons for Booting a System

Reason for a System Boot Appropriate Boot Option For More Information

Turn o system power due to anticipated

power outage.

Turn system power back on Chapter 3, “Shutting Down a System

(Tasks)”

Change kernel parameters in the

/etc/system le.

Reboot the system to a multiuser state (run

level 3 with SMB or NFS resources shared)

“How to Boot a System to a Multiuser State

(Run Level 3)” on page 23

Perform le system maintenance, such as

backing up or restoring system data.

Press Control-D from a single-user state

(run level S) to bring the system back to a

multiuser state (run level 3)

“How to Boot a System to a Single-User

State (Run Level S)” on page 24

Repair a system conguration le such as

/etc/system.

Interactive boot “How to Boot a System Interactively” on

page 25

Add or remove hardware from the system. Reconguration boot (turn on system

power after adding or removing devices, if

devices are not hot-pluggable)

“Setting up Disks for ZFS File Systems

(Task Map)” in Oracle Solaris

Administration: Devices and File Systems

Recover from a hung system and force a

crash dump.

Recovery boot “How to Force a Crash Dump and Reboot

of the System” on page 78

Boot the system by using the kernel

debugger (kmdb) to track down a system

problem.

Booting kmdb “How to Boot a System With the Kernel

Debugger (kmdb) Enabled” on page 79

Guidelines for Booting a System

Booting and Shutting Down Oracle Solaris on SPARC Platforms • November 201114

Service Management Facility and Booting

SMF provides an infrastructure that augments the traditional UNIX startup scripts, init run

levels, and conguration les. With the introduction of SMF, the boot process creates fewer

messages now. Services do not display a message by default when they are started. All of the

information that was provided by the boot messages can now be found in a log le for each

service that is in /var/svc/log. You can use the svcs command to help diagnose boot

problems. To generate a message when each service is started during the boot process, use the

-v option with the boot command.

When a system is being booted you can select the milestone to boot to or select the level of error

messages to be recorded. For instance:

■

You can choose a specic milestone to boot to using this command:

ok boot -m milestone=milestone

The default milestone is all which starts all enabled services. Another useful milestone is

none which starts only init, svc.startd and svc.configd. This milestone provides a very

useful debugging environment where services can be started manually. See

“How to Boot a

System Without Starting Any Services” on page 81

for instructions on how to use the none

milestone.

The run-level equivalents single-user, multi-user, and multi-user-server are also

available, but are not commonly used. The multi-user-server milestone, in particular

does not start any services which are not a dependency of that milestone, so may not include

important services.

■

You can choose which level of logging for svc.startd using the following command:

ok boot -m logging_level

The logging levels that you can select are quiet, verbose and debug. See “SMF Service Error

Logging” in Oracle Solaris Administration: Common Tasks

for specic information about

the logging levels.

Changes in Behavior When Using SMF

Most of the features that are provided by SMF occur behind the scenes, so users are not typically

aware of these features. Other features are accessed by new commands.

Service Management Facility and Booting

Chapter 1 • Booting and Shutting Down a SPARC Based System (Overview) 15

Here is a list of the behavior changes that are most visible:

■

The boot process creates many fewer messages now. Services do not display a message by

default when they are started. All of the information that was provided by the boot messages

can now be found in a log le for each service that is in /var/svc/log. You can use the svcs

command to help diagnose boot problems. In addition, you can use the -v option to the

boot command, which generates a message when each service is started during the boot

process.

■

Because services are automatically restarted if possible, it might seem that a process fails to

terminate. If the service is defective, the service is placed in maintenance mode, but

normally a service is restarted if the process for the service is terminated. The svcadm

command should be used to stop the processes of any SMF service that should not be

running.

■

Many of the scripts in /etc/init.d and /etc/rc*.d have been removed. The scripts are no

longer needed to enable or disable a service. Entries from /etc/inittab have also been

removed so that the services can be administered by using SMF. Scripts and inittab entries

that are provided by an ISV or are locally developed will continue to run. The services might

not start at exactly the same point in the boot process, but they are not started before the

SMF services..

How Run Levels Work

A system's run level (also known as an init state) denes what services and resources are

available to users. A system can be in only one run level at a time.

Oracle Solaris has eight run levels, which are described in the following table. The default run

level is specied in the /etc/inittab le as run level 3.

TABLE 1–3 Oracle Solaris Run Levels

Run Level Init State Type Purpose

0 Power-down state Power-down To shut down the operating system so that it is

safe to turn o power to the system.

s or S Single-user state Single-user To run as a single user with some le systems

mounted and accessible.

1 Administrative state Single-user To access all available le systems. User logins are

disabled.

2 Multiuser state Multiuser For normal operations. Multiple users can access

the system and all le systems. All daemons are

running except for the NFS server daemons.

3 Multiuser level with NFS resources

shared

Multiuser For normal operations with NFS resources

shared. This is the default run level.

How Run Levels Work

Booting and Shutting Down Oracle Solaris on SPARC Platforms • November 201116

剩余83页未读，继续阅读

weiwei966736

粉丝: 0
资源: 2

Oracle Solaris 11: Booting and Shutting Down on SPARC Platforms

oracle11.2.0.4数据库安装包百度网盘下载.txt

sol-11_4-text-x86.iso

oracle 11.2.0.4 win64 linux solaris64下载地址

Solaris8，Solaris9，Solaris10，Solaris11

Oracle Solaris 11 Installing Oracle Solaris 11 Systems-204

Oracle Solaris 11 Introduction to Oracle Solaris11 Developer Env

Oracle Solaris 11 Adding and Updating Oracle Solaris11 Software

Oracle Solaris 11 Copying and Creating Oracle Solaris11 Package

Oracle Solaris 11 Creating and Administering Oracle Solaris 11 B

Oracle Solaris 11 Creating a Custom Oracle Solaris11 Installatio

最新资源