Sponsored Content
Full Discussion: SCSI boot errors
Operating Systems Solaris SCSI boot errors Post 302338668 by Sun Fire on Tuesday 28th of July 2009 03:08:05 PM
Old 07-28-2009
check /var/adm/messages for more detailed messages...to confirm if you have a disk failure or not.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Boot loop errors caused by RC.CONF

Hello all! I am praying someone can help me. I have been trying to install dual nics on my FreeBSD box. In my attempts I edited my RC.CONF file. I must have editing something wrong, because during the boot sequence, my machine gets through bringing up most of the services then it stops and gets... (5 Replies)
Discussion started by: ezekiel61
5 Replies

2. AIX

Adapter Errors and Link Errors

$ errpt | more IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION 3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR B8113DD1 0802050205 T H fcs1 LINK ERROR 3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR B8113DD1 ... (2 Replies)
Discussion started by: mcastill66
2 Replies

3. UNIX for Dummies Questions & Answers

Major OS errors/Bash errors help!!!!

Hi all, dummy here.... I have major errors on entering the shell. On login I get: -bash: dircolors: command not found -bash: tr: command not found -bash: fgrep: command not found -bash: grep: command not found -bash: grep: command not found -bash: id: command not found -bash: [: =: unary... (12 Replies)
Discussion started by: wcmmlynn
12 Replies

4. UNIX for Dummies Questions & Answers

Custom kernel compiling, won't boot, and errors.

First of all, I'd like to preface this post by relaying that I have considerable experience with FreeBSD but I'm a Linux newb. I've been attempting to compile linux-2.6.29.3 from source and I'm having some problems and have a few newb questions... a) First of all, my kernel won't boot, it fails... (0 Replies)
Discussion started by: urbanriot
0 Replies

5. AIX

AIX 5.3 Boot Errors

IBM P Series #7026 Error Codes #E47E212E - init #1BA70F4E - SRC #BA431EB7 - SRC #C69F5C9B- SYSPROC #369DO49B - SYSPFS This happens on reboot the core dump fills up the root file system so I don't think it completes the dump. I can't read the core file with dbx. Thanks (6 Replies)
Discussion started by: tholmes
6 Replies

6. Hardware

How to boot from scsi id1

I'm running sco 5.0.6 on two independent hard drives. I have one hard drive set at scsi id 0 and can boot from it with no problems. I have another hard drive set at scsi id 1 but cannot boot from it. I'm using an adaptec 29160 controller card. I have set the boot scsi id to 1 in SCSI select but... (3 Replies)
Discussion started by: powwm
3 Replies

7. Solaris

Sun Sparc Ultra 4 won't boot - disk errors

Hi all. I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'. I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies

8. Filesystems, Disks and Memory

What do these SCSI errors mean?

Linux / Kernel experts, Please help. I'm getting errors with various return codes, similar to: kernel: SCSI error : <0 0 5 165> return code = 0x8000002 I would like to know how / where to lookup the definition of the numbers between the angle brackets, and the return code itself. I... (3 Replies)
Discussion started by: bumblebee
3 Replies

9. Hardware

Cannot boot from scsi cdrom

I have a server with a scsi raid controller (for hard drives) and a scsi controller (for tape drive and cd-rom). I am trying to boot from the cd-rom but can't. During boot up, bootable media is detected in the cd-rom but the system will not boot from it. BIOS for the raid controller installs but... (1 Reply)
Discussion started by: powwm
1 Replies
syslog.conf(4)						     Kernel Interfaces Manual						    syslog.conf(4)

NAME
syslog.conf - syslogd configuration file SYNOPSIS
facility.severity destination Where: Is part of the system generating the message, specified in /usr/include/sys/syslog_pri.h. See also the syslogd(8) reference page. The severity level, which can be emerg, alert, crit, err, warning, notice, info, or debug. See /usr/include/sys/syslog_pri.h. The syslogd daemon logs all messages of the specified severity level plus all messages of greater severity. For example, if you specify level err, all messages of levels err, crit, alert, and emerg or panic are logged. A local file pathname to a log file, a host name for remote logging or a list of users. In the latter case the users will receive messages when they are logged in. An asterisk (*) causes a message to be sent to all users who are currently logged in. DESCRIPTION
The /etc/syslog.conf file is a system file that enables you to configure or filter events that are to be logged by syslogd. You can specify more than one facility and its severity level by separating them with semicolons. You can specify more than one facility logs to the same file by separating the facilities with commas, as shown in the EXAMPLES section. The syslogd daemon ignores blank lines and lines that begin with an octothorpe (#). You can specify # as the first character in a line to include comments in the file or to disable an entry. The facility and severity level are separated from the destination by one or more tab characters. If you want the syslogd daemon to use a configuration file other than the default, you must specify the file name with the following com- mand: # syslogd -f config_file Daily Log Files You can specify in the /etc/syslog.conf file that the syslogd daemon create daily log files. To create daily log files, use the following syntax to specify the path name of the message destination: /var/adm/syslog.dated/ { file} The file variable specifies the name of the log file, for example, mail.log or kern.log. If you specify a /var/adm/syslog.dated/file path name destination, each day the syslogd daemon creates a sub-directory under the /var/adm/syslog.dated directory and a log file in the sub-directory, using the following syntax: /var/adm/syslog.dated/ date / file Where: The date variable specifies the day, month, and time that the log file was created. The file variable specifies the name of the log file you previously specified in the /etc/syslog.conf file. The syslogd daemon automatically cre- ates a new date directory every 24 hours and also when you boot the system. The current directory is a link to the latest date directory. To get the latest logs, you only need to reference the /var/adm/syslog.dated/current directory. EXAMPLES
The following is a sample /etc/syslog.conf file: # # syslogd config file # # facilities: kern user mail daemon auth syslog lpr binary # priorities: emerg alert crit err warning notice info debug # kern.debug /var/adm/syslog.dated/kern.log user.debug /var/adm/sys- log.dated/user.log daemon.debug /var/adm/syslog.dated/daemon.log auth.crit;syslog.debug /var/adm/syslog.dated/syslog.log mail,lpr.debug /var/adm/syslog.dated/misc.log msgbuf.err /var/adm/crash.dated/msgbuf.savecore kern.debug /var/adm/messages kern.debug /dev/console *.emerg * FILES
/etc/syslog.conf /etc/syslog.auth - Authorization file for remote logging. /usr/include/sys/syslog_pri.h - Common components of a syslog event log record. RELATED INFORMATION
Commands: /usr/sbin/syslogd(8), /usr/sbin/binlogd(8) System Administration delim off syslog.conf(4)
All times are GMT -4. The time now is 11:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy