Sponsored Content
Full Discussion: boot messages
Operating Systems Solaris boot messages Post 40819 by Perderabo on Tuesday 23rd of September 2003 09:08:56 PM
Old 09-23-2003
cpu 0 is displaying those messages.

psrinfo -v

will confirm that all is cool.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot messages - how to eliminate them

Anyone would know how to get rid off a message that comes up during a boot-up on Solaris? It says that the clusters for this software are not installed. I deleted the software because it was crashing some other stuff but it did not get rid off all the stuff. Yes, I am coming from windows and... (2 Replies)
Discussion started by: softarch
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. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

4. Linux

boot messages

Where do all those messages at boot time get stored / logged? like: starting eth0 : OK starting mysql : OK etc... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies

5. Solaris

Solaris Boot Problems, random messages [/etc/rcS: /etc/dfs/sharetab: cannot create]

Hello All, I have all of a sudden developed issues with booting up one of my Solaris Servers. Upon a routine reboot, I was faced with the following errors: Feb 1 07:56:44 sco1-au-tci scsi: WARNING: /pci@1c,600000/scsi@2/sd@0,0 (sd0): Feb 1 07:56:44 sco1-au-tci Error for Command: read(10)... (9 Replies)
Discussion started by: ranjtech
9 Replies

6. Red Hat

Boot Messages changed after mondorestore

Hello All, I backed up my RHEL 4 as an image. Then I restored the image (by mondorestore) on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4. The messages that are shown when the system boots are something like- "... (13 Replies)
Discussion started by: shamik
13 Replies

7. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies

8. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

9. Red Hat

Grub.conf kernel field boot messages verbosity configuration

I am trying to understand what are the differences of boot messages verbosity levels for the kernel field in grub.conf From my research, there appear to be three levels: quiet verbose debug I have also found documents that specify removing quiet from the kernel field. If this is done, is... (1 Reply)
Discussion started by: thaebich
1 Replies

10. Red Hat

Customized boot log messages

Hi all Many years ago, I found online this script that was incredibly funny and I had blogged it Unfortunately because of my poor record-keeping, I seem to have lost the shell script Would somebody be kind enough to tell me how to replicate this? Thank you! (0 Replies)
Discussion started by: hedkandi
0 Replies
dmesg(1M)																 dmesg(1M)

NAME
dmesg - collect system diagnostic messages to form error log SYNOPSIS
DESCRIPTION
looks in a system buffer for recently printed diagnostic messages and prints them on the standard output. The messages are those printed by the system when unusual events occur (such as when system tables overflow or the system crashes). If the argument is specified, com- putes (incrementally) the new messages since the last time it was run and places these on the standard output. This is typically used with (see cron(1)) to produce the error log by running the command: every 10 minutes. The arguments and allow substitution for the defaults and where should be a file containing the image of the kernel virtual memory saved by the savecrash(1M) command and should be the corresponding kernel. If the system is booted with a kernel other than /stand/vmunix say /stand/vmunix_new, must be passed this name, the command must be, WARNINGS
The system error message buffer is of small, finite size. is run only every few minutes, so there is no guarantee that all error messages will be logged. AUTHOR
was developed by the University of California, Berkeley. FILES
error log (conventional location) memory scratch file for option special file containing the image of kernel virtual memory the kernel, system name list SEE ALSO
savecrash(1M). dmesg(1M)
All times are GMT -4. The time now is 01:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy