标题: M5000 solaris 10启动问题 [打印本页] 作者: zhouwei4479 时间: 2011-11-02 16:12 标题: M5000 solaris 10启动问题 以前机器连了存储，现在存储拿走了。正常模式下，solaris启动停在了显示主机名那
LOG:
XSCF> console -d 0
Connect to DomainID 0?[y|n] :y
POST Sequence 07 Memory Initialize
POST Sequence 08 Memory
POST Sequence 09 Raw UE In Cache
POST Sequence 0A Floating Point Unit
POST Sequence 0B SC
POST Sequence 0C Cacheable Instruction
POST Sequence 0D Softint
POST Sequence 0E CPU Cross Call
POST Sequence 0F CMU-CH
POST Sequence 10 PCI-CH
POST Sequence 11 Master Device
POST Sequence 12 DSCP
POST Sequence 13 SC Check Before STICK Diag
POST Sequence 14 STICK Stop
POST Sequence 15 STICK Start
POST Sequence 16 Error CPU Check
POST Sequence 17 System Configuration
POST Sequence 18 System Status Check
POST Sequence 19 System Status Check After Sync
POST Sequence 1A OpenBoot Start...
POST Sequence Complete.
Sun SPARC Enterprise M5000 Server, using Domain console
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Copyright 2009 Sun Microsystems, Inc. and Fujitsu Limited. All rights reserved.
OpenBoot 4.24.11, 65536 MB memory installed, Serial #88431494.
Ethernet address 0:21:28:45:5b:86, Host ID: 85455b86.
Nov 2 12:23:05 TJANAOLAP dscpd[759]: Failed to start DSCP for domain0 (error=2)
Boot device: /pci@0,600000/pci@0/pci@8/pci@0/scsi@1/disk@0,0:a File and args:
|
/
-
\
|/-\|/-\|/-\|/-\|/
SunOS Release 5.10 Version Generic_137137-09 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-
The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
"svcadm clear system/boot-archive"
Nov 2 10:58:45 svc.startd[7]: svc:/system/boot-archive:default: Method "/lib/svc/method/boot-
archive" failed with exit status 95.
Nov 2 10:58:45 svc.startd[7]: system/boot-archive:default failed fatally: transitioned to
maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
Root password for system maintenance (control-d to bypass):
Login incorrect
Root password for system maintenance (control-d to bypass):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode
Nov 2 10:59:51 su: 'su root' succeeded for root on /dev/console
Sun Microsystems Inc. SunOS 5.10 Generic January 2005
-sh: /opt/EMCpower/scripts/emcp_setup.sh: not found
Sourcing //.profile-EIS.....
root@tjanaolap # who -r
. run-level S Nov 2 10:23 S 0 0
root@tjanaolap # more /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/md/dsk/d20 - - swap - no -
/dev/md/dsk/d10 /dev/md/rdsk/d10 / ufs 1 no -
/dev/md/dsk/d60 /dev/md/rdsk/d60 /export/home ufs 2 yes -
/dev/md/dsk/d50 /dev/md/rdsk/d50 /opt ufs 2 yes -
/devices - /devices devfs - no -
sharefs - /etc/dfs/sharetab sharefs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes -
root@tjanaolap # more /etc/system
*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*
* moddir:
*
* Set the search path for modules. This has a format similar to the
* csh path variable. If the module isn't found in the first directory
* it tries the second and so on. The default is /kernel /usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules
* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
[7m--More--(27%)[m
*[K
* (Swap device configuration should be specified in /etc/vfstab.)
* exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys
* forceload:
*
* Cause these modules to be loaded at boot time, (just before mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it will
* be installed.
*
* Example:
* forceload: drv/foo
* set:
*
[7m--More--(48%)[m
[K* Set an integer variable in the kernel or a module to a new value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named 'test_module'
*
* set test_module:debug = 0x13
* Begin MDD root info (do not edit)
rootdev:/pseudo/md@0:0,10,blk
* End MDD root info (do not edit)
set md:mirrored_root_flag=1
*EMCpower forceload sd added following:
forceload: drv/sd
*EMCpower forceload ssd added following:
forceload: drv/ssd
forceload: drv/emcp
forceload: misc/emcpmp
forceload: misc/emcpmpc
forceload: misc/emcpmpaa
forceload: misc/emcpmpap
forceload: misc/emcpsapi
forceload: misc/emcpcg
forceload: misc/emcphr
forceload: misc/emcpioc
*EMCpower added the following line:
[7m--More--(74%)[m
set emcp:bPxEnableInit=1
*EMCpower added the following line:
set default_stksize=0x6000
*EMCpower added the following line:
set lwp_default_stksize=0x6000
*EMCpower added the following line:
set rpcmod:svc_default_stksize=0x6000
* vxvm_START (do not remove)
forceload: drv/vxdmp
forceload: drv/vxio
forceload: drv/vxspec
* vxvm_END (do not remove)
* vxfs_START -- do not remove the following lines:
* VxFS requires a stack size greater than the default 8K.
* The following value allows the kernel stack size to be
* increased to 24K.
set lwp_default_stksize=0x6000
* vxfs_END
* vxfs_START -- do not remove the following lines:
* VxFS requires a stack size greater than the default 8K.
* The following value allows the kernel stack size to be
* increased to 24K.
set rpcmod:svc_default_stksize=0x6000
* vxfs_END
root@tjanaolap # vi /etc/system
[34;1H"/var/tmp/Ex.vaWsa" [7mRead-only file system[m
root@tjanaolap # ^[:q
^[:q: not found
root@tjanaolap #
root@tjanaolap #
The recommended action is to reboot to the failsafe archive to correct
the above inconsistency. To accomplish this, on a GRUB-based platform,
reboot and select the "Solaris failsafe" option from the boot menu.
On an OBP-based platform, reboot then type "boot -F failsafe". Then
follow the prompts to update the boot archive. Alternately, to continue
booting at your own risk, you may clear the service by running:
"svcadm clear system/boot-archive" 作者: zhouwei4479 时间: 2011-11-02 18:12
来点给力的意见。作者: cwnlinux 时间: 2011-11-03 11:31
3L的还不给力？ 作者: 财版 时间: 2011-11-04 15:05
先按3L的做 作者: doni 时间: 2011-11-04 16:45
svcadm clear system/boot-archive
基本上就是这个 作者: campoeagle 时间: 2011-11-05 17:51
以前好像遇到过是powerpath的问题
