Solaris10..Open boot diagnostic failed


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris10..Open boot diagnostic failed
Prev   Next
# 1  
Old 02-05-2009
Solaris10..Open boot diagnostic failed

Hi all,

when am rebooting the server (SF v890) we are facing
"open boot diagnostic failed".

Thanks in Adv.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Fresh Install - Boot Load Failed

I have M10-1. Installation OS 10 from cdrom external. Here message from OK Prompt {0} ok probe-scsi-all /pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4,1/cdrom@1 Unit 0 Removable Read Only device HL-DT-STDVDRAM GP65NB60 PF00 But.. {0} ok boot... (3 Replies)
Discussion started by: mbahjiman
3 Replies

2. Solaris

Solaris 10 boot failed init

Dear all, I have a solaris 10 in my environment (VMware virtual machine). recently I increased the harddisk size from the VMware and reboot my server. after reboot the os is unable to boot and gives the below error message. exec(/sbin/init) file not found press any key to restart ... (3 Replies)
Discussion started by: krishna001
3 Replies

3. HP-UX

HP-UX stops on boot; DIAGNOSTIC SYSTEM WARNING

Hi all, I have an HP-UX server that halts during boot. Below is CO output. Any ideas how to solve this? Any help would be appreciated. Thank you. HP-UX Boot Loader for IPF -- Revision 2.027 Press Any Key to interrupt Autoboot \EFI\HPUX\AUTO ==> boot vmunix -lq Seconds left till... (0 Replies)
Discussion started by: MazenH
0 Replies

4. Red Hat

rpmdb open failed

Hi, # yum --skip-broken -y update rpmdb: Thread/process 6657/3078387392 failed: Thread died in Berkeley DB library error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery error: cannot open Packages index using db3 - (-30974) error: cannot open... (3 Replies)
Discussion started by: sef alislam
3 Replies

5. Solaris

libucb.s0.1: open failed...

Hi all. I try to start an application, but libucb.so1 is missing. # appl23 # appl23ld.so.1: appl23: fatal: libucb.so1: open failed: No such file or directory killed # # ldd appl23 libXm.so.3 => /usr/lib/libXm.so.3 libMrm.so.3 => /usr/lib/libMrm.so.3 ... (14 Replies)
Discussion started by: wolfgang
14 Replies

6. Solaris

Solaris10 on vmware - Internet connection failed

Installed Sun Solaris 10 (5/09) on vmware 6.0 but system is not connecting to internet. when I check "ipconfig /all" I do not get any DNS Suffix name -- neither for vmnet1 and vmnet8 nor for local ethernet IP. Default gateways are 192.168.1.1 and 192.168.1.2 1. Created /etc/resolv.conf domain... (1 Reply)
Discussion started by: johnjerry
1 Replies

7. Solaris

V490 Failed To Boot After ALOM poweron

After issuing reboot command (and disconnected from PuTTY), server is not even rebooted because ping test is succesful. So I connect to ALOM and issue poweroff command. After a minute, I did poweron and get this message (only). rsc> poweron Are you sure you want to turn your system power on... (10 Replies)
Discussion started by: Olli.Lang
10 Replies

8. Solaris

How can i connect to win2k3 RDP from Solaris10 or Open Solaris

Hi all, O people of expert how can i connect to windows server 2003 remote desktop through Microsoft terminal server i don't want to install third parties products such VNC server or any web browser tools such as Remotely AnyWhere on the windows box what options and what procedures do i have to... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies

9. Solaris

libCstd.so.1: open failed

Morning all, I have a problem with a Sun workstation which is running Solaris 8. When I attempt to open an application, the executable fails with this message : "fatal: libcstd.so.1: open failed: No such file or directory" It was suggested to me that I need to add these patches to fix the... (4 Replies)
Discussion started by: AndyD
4 Replies

10. Solaris

boot load failed

I modified the partitions on my Solaris 10 disk using format command in "boot cdrom -s" mode and then tried rebooting with "reboot". It said "Boot load failed". Why does this happen? I have faced this error before:( and I went in for a fresh installation of the OS.Can anyone tell me the reason as... (1 Reply)
Discussion started by: lydiaEd
1 Replies
Login or Register to Ask a Question
prtdiag(1M)															       prtdiag(1M)

NAME
prtdiag - display system diagnostic information SYNOPSIS
/usr/sbin/prtdiag [-v] [-l] prtdiag displays system configuration and diagnostic information on sun4u and sun4v systems. The diagnostic information lists any failed field replaceable units (FRUs) in the system. The interface, output, and location in the directory hierarchy for prtdiag are uncommitted and subject to change in future releases. prtdiag does not display diagnostic information and environmental status when executed on the Sun Enterprise 10000 server. See the /var/opt/SUNWssp/adm/${SUNW_HOSTNAME}/messages file on the system service processor (SSP) to obtain such information for this server. The following options are supported: -l Log output. If failures or errors exist in the system, output this information to syslogd(1M) only. -v Verbose mode. Displays the time of the most recent AC Power failure, and the most recent hardware fatal error information, and (if applicable) environmental status. The hardware fatal error information is useful to repair and manufacturing for detailed diagnos- tics of FRUs. The following exit values are returned: 0 No failures or errors are detected in the system. 1 Failures or errors are detected in the system. 2 An internal prtdiag error occurred, for example, out of memory. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWkvm | +-----------------------------+-----------------------------+ |Interface Stability |Unstable* | +-----------------------------+-----------------------------+ *The output is unstable. modinfo(1M), prtconf(1M), psrinfo(1M), sysdef(1M), syslogd(1M), attributes(5), openprom(7D) NOTES
Not all diagnostic and system information is available on every Solaris platforn, and therefore cannot be displayed by prtdiag. On those platforms, further information can be obtained from the System Controller. 29 Aug 2005 prtdiag(1M)