|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
Strange problem.Please Help !
Post 397 by Neo on Thursday 30th of November 2000 11:00:50 PM
12-01-2000
Administrator
If the UNIX kernal crashed (panics) you might not get any error messages because the kernal logging facility might only right to the console. However, you said it 'looks like a power outage when it dies'; so I assume you cannot read a console. Is that right? If you can make sure the console monitor is up and working, if the kernel panics you will see something on the monitor (normally).
I am going to guess that you are having a problem which shuts down the hardware, i.e. the motherboard; because this would kill the video output as well as the disks, etc. Without further information the best guess I can make is a motherboard problem because you say the 'entire system dies like a power outage'.
Motherboards can and do break. Bugs in the bios can cause strange behavior. The SCSI error you post would cause the system to lock-up, but the power, monitor, console would still work. So, if the system is just 'locking up' but the video card works; the next logical place would be the SCSI controller (and you have an error message to back this up.)
The most common cause of SCSI errors is not terminating the ends of the SCSI bus, or having an improper termination in the middle of the bus. So, the first thing to do is to insure that your SCSI bus is configured properly and terminated properly. This is not always easy if you are not a SCSI guru.
Hope this helps get up started. If you have any more clues, please post. We love puzzles here at UNIX.COM
I am going to guess that you are having a problem which shuts down the hardware, i.e. the motherboard; because this would kill the video output as well as the disks, etc. Without further information the best guess I can make is a motherboard problem because you say the 'entire system dies like a power outage'.
Motherboards can and do break. Bugs in the bios can cause strange behavior. The SCSI error you post would cause the system to lock-up, but the power, monitor, console would still work. So, if the system is just 'locking up' but the video card works; the next logical place would be the SCSI controller (and you have an error message to back this up.)
The most common cause of SCSI errors is not terminating the ends of the SCSI bus, or having an improper termination in the middle of the bus. So, the first thing to do is to insure that your SCSI bus is configured properly and terminated properly. This is not always easy if you are not a SCSI guru.
Hope this helps get up started. If you have any more clues, please post. We love puzzles here at UNIX.COM
|
|
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I did an installation of Redhat 7.1 and it seem to install smoothly. I go and reboot and I get the following message:
"INIT: Id "x" respawing too fast: disabled for 5 minutes"
The screen flashes 4 times every 10 seconds or so.
I can't seem to figure why this does this. It might be a simple... (2 Replies)
Discussion started by: forjohnny
2 Replies
2. UNIX for Dummies Questions & Answers
Hi..
Some of my application were not running properly due to lack of virtual memory.....so wht i did add one free harddisk as swap file system...and increased the swap memory..
But since than my root file system is showing 100% full thr is no space left...is thr any link between these two..... (1 Reply)
Discussion started by: Prafulla
1 Replies
3. Linux
I have installed Fedora Core on a Toshiba Satellite Pro4600 laptop recently I have experienced a rather mysterious problem if I touch anything specially the keyboard or mouse I see this stuff “67yujhnmyyy” straight away some time it won't stop for while like this... (5 Replies)
Discussion started by: kemobyte
5 Replies
4. Shell Programming and Scripting
I am using SunOS 5.9 and I don't know why all my commands are getting executed as if an extra 'enter' has been pressed.
What could be the reason and how to correct it?
Please help.
Asty (2 Replies)
Discussion started by: Asty
2 Replies
5. Shell Programming and Scripting
Well, my script started off to do what i wanted. Now, i think its not recognizing the pattern so its not moving anything.
What i have to do is execute my script command for the move to take effect. So i did that and yayy it worked.
Strange thing is that my DESTDIR was empty to begin with.... (2 Replies)
Discussion started by: oxoxo
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
in my environment we have several server with rlogin passwordless login enabled, now there is a problem to setup this with a hpux server. i have check the .rhosts file and kerberos key are all setup properly and permission is correct, even other user id on the server can login without... (3 Replies)
Discussion started by: robertngo
3 Replies
7. Shell Programming and Scripting
Hi All,
I am encountering an unexpected problem while running my process, using daemon placed in /etc/init.d/.
I have a process that is opening shared library using dlopen.
When I run my process on the command line, it is able to open the library. But when I used daemon to run my process, I... (0 Replies)
Discussion started by: qwerty-1
0 Replies
8. UNIX for Dummies Questions & Answers
windowsxp:192.168.0.11
fedora14:192.168.0.12, running smb server
I have disabled selinux.
user list of fedora14:
jone (wihch is created when install fedora14, with password 'jone')
jone2 (which is added by hand, with password 'jone2')
I added jone and jone2 as samba users using 'smbpasswd... (1 Reply)
Discussion started by: vistastar
1 Replies
9. Shell Programming and Scripting
hello all,
i am having problem in accessing a directory.I dont think its a permission issue.can anyone help me out. I am using korn sell
code:
$ ls -ltr sc*
lrwxrwxrwx 1 essbase essbase 21 Oct 8 2010 sc_ssp -> /work/nfs/nas2/sc_ssp
$ cd sc_ssp
ksh: sc_ssp: not found
$ (6 Replies)
Discussion started by: manid
6 Replies
LEARN ABOUT ULTRIX
scsi
SCSI(4) Kernel Interfaces Manual SCSI(4) Name SCSI - Small Computer System Interconnect Description The ULTRIX system interfaces to disk and tape devices through the Small Computer System Interconnect (SCSI). Initial ULTRIX SCSI support is limited to the Digital-supplied mass storage devices. The following devices are fully supported on the ULTRIX system: o Winchester disks: RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33 o Magnetic tapes: TZ30, TZK50, TLZ04, TSZ05, TKZ08, TZK10 o Optical disks: RRD40, RRD42 Under the ULTRIX operating system, a SCSI device is referred to by its logical name. Logical names take the following form: nn# The nn argument is the two-character name; the number sign (#) represents the unit number. The two character names for SCSI devices are: rz - RZ22, RZ23, RZ23L, RZ24, RZ55, RZ56, RZ57, RX23, RX26, RX33, RRD40, RRD42 disks tz - TZ30, TZK50, TLZ04, TSZ05, TKZ08, and TZK10 tapes The unit number is a combination of the SCSI bus number, either 0, 1, ... and the device's target ID number. The unit number is eight times the bus number plus the target ID. For example, an RZ23 disk at target ID 3 on bus 0 would be referred to as rz3; a TZK50 tape at target ID 5 on the second SCSI bus would be referred to as 13. The SCSI bus has eight possible target device IDs. By default, one is allocated to the system. This allows for a maximum of seven target devices connected to a SCSI bus. Restrictions The ULTRIX SCSI device driver does not operate with optical disks, other than the Digital-supplied devices. The SCSI driver attempts to support on a best effort basis, non-Digital-supplied winchester disks and magnetic tapes. The following notes apply to the driver's handling of non-Digital-supplied disks: o These disks are assigned a device type of RZxx, instead of RZ22, RZ23, RZ23L, RZ55, RZ56, RZ57, RX23, RX26, or RX33. The RZxx disks follow the same logical device naming scheme as the Digital-supplied disks. o During the autoconfigure phase of the system startup, the driver prints the contents of the SCSI vendor ID, product ID, and the revision level fields of the inquiry data return by the SCSI device. o RZxx disks are assigned a default partition table. The default table can be modified by editing the sz_rzxx_sizes[8] entry in the file The utility can also be used to modify the partition table on a RZxx disk. o The only logical unit number (LUN) supported for each target ID is 0. See Also rz(4), tz(4), chpt(8) SCSI(4)