Sponsored Content
Full Discussion: System boot up log file
Operating Systems Solaris System boot up log file Post 302250465 by kumarmani on Thursday 23rd of October 2008 11:22:56 AM
Old 10-23-2008
demsg is not to find the devices attached to your system or not. Its more to do with the diagnostic message to form log .

If you want to find any detail related with device you can execute the command

Quote:
prtdiag -v
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

System boot configuration

On my PC I have two hard disks, the first with Windows 98 SE and the second with Linux Mandrake 8.0 (Traktopel). When I have installed Linux, it has modified the boot record of the 1st HD and it has added a graphic menu (LILO) for selecting the OS to use. By default, if I don't press a key, Linux... (2 Replies)
Discussion started by: robotronic
2 Replies

2. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies

3. UNIX for Dummies Questions & Answers

Boot from a remote system

I have a diskless work station. i want to boot from a remote linux machine. what changes i will have to do in configuration. Plz tell me thanks (1 Reply)
Discussion started by: hemant29
1 Replies

4. SCO

Can't boot system--help

I get a message saying Not enough space to dump xxxxx pages Press any key to reboot Safe to power off After rebooting it never gets to the "Press CTRL D to continue or enter password for single user" message before it goes back to "Not enough space..." message above. Vicious cycle. ... (0 Replies)
Discussion started by: deloev
0 Replies

5. UNIX for Dummies Questions & Answers

help boot system erro

being nosey on sons laptop and set a password and now need to undo this but its in the boot system :eek::eek::eek: (4 Replies)
Discussion started by: hempel
4 Replies

6. Solaris

System will not boot

We have a system that won't boot. It is Sun V245 that was patched yesterday with the latest Recommended 10 patch cluster. I will post what we get during the boot at the end of the email message. We have tried rebuilding the bootblk, booting from the cdrom, and running an fsck, booting into failsafe... (2 Replies)
Discussion started by: brownwrap
2 Replies

7. Solaris

dual boot solaris/solaris zfs file system

Hi, I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out. First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies

8. HP-UX

File system full, won't complete boot

Hello, I have a very old hp rp2450 running 11i2 that I had to power off. When turning it back on it hangs with the following message. Would booting into SUM get me any further? I've never used SUM, so I'm asking before I go down that rabbit hole. Thanks for the help. # ## extra content... (1 Reply)
Discussion started by: calabaria
1 Replies

9. Red Hat

System fail to boot

Hi im using centos 6.4 starting yesterday i have a strange issue that im unable to resolve. the system is booting to GRUB menu and the os is not starting. i tried to run a repair install and the message attached is what i get, what can cause this? thanks, (1 Reply)
Discussion started by: guy3145
1 Replies

10. UNIX for Advanced & Expert Users

System cannot boot up

Hi, I got stuck in a very messy situation yesterday after attempting to resolve a filesystem full issue. The user reported that their filesystem (/var/DWS) was 100% full even after moving few files of sizes 14G, 30G and 50G out of the directory. I checked the filesystem once more after this... (5 Replies)
Discussion started by: anaigini45
5 Replies
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)
All times are GMT -4. The time now is 03:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy