1)to boot into single-user mile stone
{0} ok boot -m milestone=single-user
Boot device: /virtual-devices@100/channel-devices@200/disk@0:a File and args: -m milestone=single-user
SunOS Release 5.11 Version 11.1 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Booting to milestone "milestone/single-user:default".
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Enter user name for system maintenance (control-d to bypass): Hostname: guest1
Enter user name for system maintenance (control-d to bypass): root
Enter root password (control-d to bypass):
single-user privilege assigned to root on /dev/console.
Entering System Maintenance Mode
Sep 20 17:36:26 su: 'su root' succeeded for root on /dev/console
Oracle Corporation SunOS 5.11 11.1 September 2012
root@guest1:~# who -r
. run-level S Sep 20 17:36 S 0 0
root@guest1:~# df -kh
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris 49G 2.3G 41G 6% /
/devices 0K 0K 0K 0% /devices
/dev 0K 0K 0K 0% /dev
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 7.2G 2.1M 7.2G 1% /system/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
fd 0K 0K 0K 0% /dev/fd
rpool/ROOT/solaris/var
49G 93M 41G 1% /var
swap 7.2G 0K 7.2G 0% /tmp
rpool/VARSHARE 49G 44K 41G 1% /var/share
root@guest1:~# pwd
/root
2)) To boot init ot multi-user mile stone ?????????
{0} ok boot -m milestone=multi-user
Boot device: /virtual-devices@100/channel-devices@200/disk@0:a File and args: -m milestone=multi-user
SunOS Release 5.11 Version 11.1 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Booting to milestone "milestone/multi-user:default".
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Enter user name for system maintenance (control-d to bypass): Hostname: guest1
root
Enter root password (control-d to bypass):
single-user privilege assigned to root on /dev/console.
Entering System Maintenance Mode
Sep 20 17:47:37 su: 'su root' succeeded for root on /dev/console
Oracle Corporation SunOS 5.11 11.1 September 2012
root@guest1:~# pwd
/root
root@guest1:~# ls
iozone3_260
root@guest1:~# df -kh
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris 49G 2.3G 41G 6% /
/devices 0K 0K 0K 0% /devices
/dev 0K 0K 0K 0% /dev
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 7.2G 2.2M 7.2G 1% /system/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
fd 0K 0K 0K 0% /dev/fd
rpool/ROOT/solaris/var
49G 93M 41G 1% /var
swap 7.2G 0K 7.2G 0% /tmp
rpool/VARSHARE 49G 46K 41G 1% /var/share
rpool/export 49G 32K 41G 1% /export
rpool/export/home 49G 31K 41G 1% /export/home
rpool 49G 73K 41G 1% /rpool
root@guest1:~# who -r
. run-level 2 Sep 20 17:47 2 0 S
root@guest1:~# svcs -a|grep -i mile
disabled 17:47:00 svc:/milestone/multi-user-server:default
online 17:47:24 svc:/milestone/unconfig:default
online 17:47:25 svc:/milestone/config:default
online 17:47:25 svc:/milestone/devices:default
online 17:47:31 svc:/milestone/network:default
online 17:47:32 svc:/milestone/name-services:default
online 17:47:43 svc:/milestone/single-user:default
online 17:47:44 svc:/milestone/self-assembly-complete:default
online 17:47:45 svc:/milestone/multi-user:default
3)))) To boot in multi-user-server milestone
# reboot -- -m milestone=multi-user-server
[ or ]
{0} ok boot -m milestone=multi-user-server
SPARC Enterprise T5120, No Keyboard
Copyright (c) 1998, 2012, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.33.6.b, 7296 MB memory available, Serial #83437981.
Ethernet address 0:14:4f:f9:29:9d, Host ID: 84f9299d.
Boot device: /virtual-devices@100/channel-devices@200/disk@0:a File and args: -m milestone=multi-user-server
SunOS Release 5.11 Version 11.1 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Booting to milestone "milestone/multi-user-server:default".
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Enter user name for system maintenance (control-d to bypass): Hostname: guest1
root
Enter root password (control-d to bypass):
single-user privilege assigned to root on /dev/console.
Entering System Maintenance Mode
Sep 20 17:52:03 su: 'su root' succeeded for root on /dev/console
Oracle Corporation SunOS 5.11 11.1 September 2012
root@guest1:~# df -kh
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris 49G 2.3G 41G 6% /
/devices 0K 0K 0K 0% /devices
/dev 0K 0K 0K 0% /dev
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 7.2G 2.2M 7.2G 1% /system/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
fd 0K 0K 0K 0% /dev/fd
rpool/ROOT/solaris/var
49G 93M 41G 1% /var
swap 7.2G 0K 7.2G 0% /tmp
rpool/VARSHARE 49G 46K 41G 1% /var/share
rpool/export 49G 32K 41G 1% /export
rpool/export/home 49G 31K 41G 1% /export/home
rpool 49G 73K 41G 1% /rpool
root@guest1:~# svcs -a|grep -i mile
online 17:51:47 svc:/milestone/unconfig:default
online 17:51:48 svc:/milestone/config:default
online 17:51:48 svc:/milestone/devices:default
online 17:51:54 svc:/milestone/network:default
online 17:51:54 svc:/milestone/name-services:default
online 17:52:05 svc:/milestone/single-user:default
online 17:52:07 svc:/milestone/self-assembly-complete:default
online 17:52:08 svc:/milestone/multi-user:default
online 17:52:09 svc:/milestone/multi-user-server:default
root@guest1:~# who -r
. run-level 3 Sep 20 17:52 3 0 S
1. Boot archive failure
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, and potentially fsck, 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 command via
# /usr/sbin/mount -o rw,remount /
/system/volatile is a temporary filesystem generally reserved for Oracle
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 .
svc.configd will give detailed instructions for recovery if the
corruption is detected in the repository. If svc.configd 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.
If the inittab(4) line to invoke svc.startd 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 cannot be run because of missing or corrupt library
components, then the affected components will need to be replaced, as
for svc.configd above.
5. Activating basic networking configuration.
If svc.startd 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 can be
attempted.
In some scenarios, one may be able to use routeadm 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 command. On typical IPv4 networks, this invocation would be
# /usr/sbin/route add net default gateway_IP
{0} ok boot -m milestone=single-user
Boot device: /virtual-devices@100/channel-devices@200/disk@0:a File and args: -m milestone=single-user
SunOS Release 5.11 Version 11.1 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Booting to milestone "milestone/single-user:default".
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Enter user name for system maintenance (control-d to bypass): Hostname: guest1
Enter user name for system maintenance (control-d to bypass): root
Enter root password (control-d to bypass):
single-user privilege assigned to root on /dev/console.
Entering System Maintenance Mode
Sep 20 17:36:26 su: 'su root' succeeded for root on /dev/console
Oracle Corporation SunOS 5.11 11.1 September 2012
root@guest1:~# who -r
. run-level S Sep 20 17:36 S 0 0
root@guest1:~# df -kh
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris 49G 2.3G 41G 6% /
/devices 0K 0K 0K 0% /devices
/dev 0K 0K 0K 0% /dev
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 7.2G 2.1M 7.2G 1% /system/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
fd 0K 0K 0K 0% /dev/fd
rpool/ROOT/solaris/var
49G 93M 41G 1% /var
swap 7.2G 0K 7.2G 0% /tmp
rpool/VARSHARE 49G 44K 41G 1% /var/share
root@guest1:~# pwd
/root
2)) To boot init ot multi-user mile stone ?????????
{0} ok boot -m milestone=multi-user
Boot device: /virtual-devices@100/channel-devices@200/disk@0:a File and args: -m milestone=multi-user
SunOS Release 5.11 Version 11.1 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Booting to milestone "milestone/multi-user:default".
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Enter user name for system maintenance (control-d to bypass): Hostname: guest1
root
Enter root password (control-d to bypass):
single-user privilege assigned to root on /dev/console.
Entering System Maintenance Mode
Sep 20 17:47:37 su: 'su root' succeeded for root on /dev/console
Oracle Corporation SunOS 5.11 11.1 September 2012
root@guest1:~# pwd
/root
root@guest1:~# ls
iozone3_260
root@guest1:~# df -kh
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris 49G 2.3G 41G 6% /
/devices 0K 0K 0K 0% /devices
/dev 0K 0K 0K 0% /dev
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 7.2G 2.2M 7.2G 1% /system/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
fd 0K 0K 0K 0% /dev/fd
rpool/ROOT/solaris/var
49G 93M 41G 1% /var
swap 7.2G 0K 7.2G 0% /tmp
rpool/VARSHARE 49G 46K 41G 1% /var/share
rpool/export 49G 32K 41G 1% /export
rpool/export/home 49G 31K 41G 1% /export/home
rpool 49G 73K 41G 1% /rpool
root@guest1:~# who -r
. run-level 2 Sep 20 17:47 2 0 S
root@guest1:~# svcs -a|grep -i mile
disabled 17:47:00 svc:/milestone/multi-user-server:default
online 17:47:24 svc:/milestone/unconfig:default
online 17:47:25 svc:/milestone/config:default
online 17:47:25 svc:/milestone/devices:default
online 17:47:31 svc:/milestone/network:default
online 17:47:32 svc:/milestone/name-services:default
online 17:47:43 svc:/milestone/single-user:default
online 17:47:44 svc:/milestone/self-assembly-complete:default
online 17:47:45 svc:/milestone/multi-user:default
3)))) To boot in multi-user-server milestone
# reboot -- -m milestone=multi-user-server
[ or ]
{0} ok boot -m milestone=multi-user-server
SPARC Enterprise T5120, No Keyboard
Copyright (c) 1998, 2012, Oracle and/or its affiliates. All rights reserved.
OpenBoot 4.33.6.b, 7296 MB memory available, Serial #83437981.
Ethernet address 0:14:4f:f9:29:9d, Host ID: 84f9299d.
Boot device: /virtual-devices@100/channel-devices@200/disk@0:a File and args: -m milestone=multi-user-server
SunOS Release 5.11 Version 11.1 64-bit
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Booting to milestone "milestone/multi-user-server:default".
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Enter user name for system maintenance (control-d to bypass): Hostname: guest1
root
Enter root password (control-d to bypass):
single-user privilege assigned to root on /dev/console.
Entering System Maintenance Mode
Sep 20 17:52:03 su: 'su root' succeeded for root on /dev/console
Oracle Corporation SunOS 5.11 11.1 September 2012
root@guest1:~# df -kh
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris 49G 2.3G 41G 6% /
/devices 0K 0K 0K 0% /devices
/dev 0K 0K 0K 0% /dev
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 7.2G 2.2M 7.2G 1% /system/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
fd 0K 0K 0K 0% /dev/fd
rpool/ROOT/solaris/var
49G 93M 41G 1% /var
swap 7.2G 0K 7.2G 0% /tmp
rpool/VARSHARE 49G 46K 41G 1% /var/share
rpool/export 49G 32K 41G 1% /export
rpool/export/home 49G 31K 41G 1% /export/home
rpool 49G 73K 41G 1% /rpool
root@guest1:~# svcs -a|grep -i mile
online 17:51:47 svc:/milestone/unconfig:default
online 17:51:48 svc:/milestone/config:default
online 17:51:48 svc:/milestone/devices:default
online 17:51:54 svc:/milestone/network:default
online 17:51:54 svc:/milestone/name-services:default
online 17:52:05 svc:/milestone/single-user:default
online 17:52:07 svc:/milestone/self-assembly-complete:default
online 17:52:08 svc:/milestone/multi-user:default
online 17:52:09 svc:/milestone/multi-user-server:default
root@guest1:~# who -r
. run-level 3 Sep 20 17:52 3 0 S
1. Boot archive failure
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, and potentially fsck, 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 command via
# /usr/sbin/mount -o rw,remount /
/system/volatile is a temporary filesystem generally reserved for Oracle
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 .
svc.configd will give detailed instructions for recovery if the
corruption is detected in the repository. If svc.configd 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.
If the inittab(4) line to invoke svc.startd 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 cannot be run because of missing or corrupt library
components, then the affected components will need to be replaced, as
for svc.configd above.
5. Activating basic networking configuration.
If svc.startd 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 can be
attempted.
In some scenarios, one may be able to use routeadm 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 command. On typical IPv4 networks, this invocation would be
# /usr/sbin/route add net default gateway_IP
No comments:
Post a Comment