Solaris10啟動不能進入圖形介面的一個bug
這是Solaris10的一個Bug,已經修正但目前沒有反映到Solaris10當前版本中(06/06版本)。 我安裝的sol-10-u6-ga1-x86-dvd.iso版本,沒查是否包含在內。
只能啟動到如下命令列
Root password for system maintenance (control-d to bypass):
輸入root密碼後進入#命令列
a. #svcadm clear system/boot-archive 然後執行#/lib/svc/method/boot-archive 啟動了圖形介面模式。
Root passord for system maintenance(control-d bypass):
see /lib/svc/share/README for information
console login service(s) cannot run
#svcadm clear system/boot-archive
#The / file system (/dev/rdsk/c0d0s0) is being checked.
/dev/rdsk/c0d0s7 is clean
Reading ZFS config:done.
到此圖形介面起來了!
b.每次重起機器後都發生,追加cronjob 定期執行 /usr/sbin/bootadm update-archive
對這個問題還是一知半解,等弄明白了再來補充!
[@more@]# pwd
/lib/svc/share
# cat README
Copyright 2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
ident "@(#)README.share 1.3 08/06/06 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
The 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 to rebuild the archive and correct the inconsistency.
To accomplish this, on a GRUB-based platform, 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. On an OBP-
based platform, type 'boot -F failsafe' and follow the instructions.
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
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
That version includes additional
document references.)
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/60144/viewspace-1023569/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Ubuntu 重啟無法進入圖形介面的解決辦法Ubuntu
- solaris10命令列模式和圖形介面的切換命令列模式
- Solaris10上啟動Oracle11g例項遇到的一個bugOracle
- Win8系統一啟動就進入傳統介面的技巧
- Redhat linux AS 4啟動後進入圖形介面還是命令列的選擇!RedhatLinux命令列
- phpStudy啟動介面的功能簡介PHP
- Ubuntu無法進入圖形介面Ubuntu
- 讓redhat9 自動進入圖形登陸介面(轉)Redhat
- ubuntu密碼正確,卻不能登入圖形介面Ubuntu密碼
- 啟動netbackup client for aix圖形介面,進行檔案恢復clientAI
- 寫一個點選圖片進入瀏覽圖片介面的第三方庫思路
- Oracle RAC 一個節點不能自動啟動 怪問題Oracle
- 用Python寫一個帶圖形介面的檔案壓縮軟體Python
- 解除Ubuntu18.04.1 root登入圖形介面的限制Ubuntu
- SVG XML 格式定義圖形入門介紹SVGXML
- linux5.5 x86_64 安裝完畢後不能啟動圖形化介面Linux
- 圖靈社群的一個BUG圖靈
- solaris取消或啟動圖形介面登陸
- Aseprite入門:第一個gif動圖
- redhat as 4.0系統啟動到一半不能啟動!Redhat
- GraphicsJS 入門,一個輕量級的前端圖形庫JS前端
- win10怎麼進修復介面_win10啟動時進入修復模式介面的方法Win10模式
- Linux7 圖形介面的切換Linux
- 圖形介面的TCP/IP簡單通訊TCP
- Kindd:一個圖形化 dd 命令前端前端
- docker 不能正常啟動Docker
- kali 安裝完不能使用 root 賬戶登入圖形化介面(一直報錯)
- ubuntu下圖形程式自啟動的幾種方法Ubuntu
- ubuntu如何關閉圖形介面,啟動文字模式Ubuntu模式
- rhel5_無法啟動圖形介面_X serverServer
- JBuilder Debug時不能進入源程式檔案視窗跟蹤除錯?UI除錯
- 網路圖形格式簡介
- fedora 17的root不能圖形介面登陸
- 如何登陸solaris10時進入字元模式(命令列)字元模式命令列
- 我的開發環境介紹及一個 Expression Bland 畫圖形的例子開發環境Express
- 無法啟動?教你進入安全模式模式
- RedHat 5.4啟動圖形介面出現Could not start the X ServerRedhatServer
- Win10系統如何進入高階啟動模式_win10進入高階啟動模式的圖文教程Win10模式