dcellis1950
asked on
SCSI timeout rebooting Linux OS
I have a server in a remote plant running RedHat 8.0. We have to use this version because 9.0 did not have a useable driver for the RAID controler we were using.
This server seems to have crashed with only the following messages int the /var/log/messages:
Kernel: SCSI: aborting command due to time out : pid 123456789 SCSI 1, Channel 0, id 0, lun 0 Read (10) 00 0a 51 95 97 00 00 80 00
Kernel: Abort Request: in the TOP
The boot drive is a IDE drive. The drives are set to RAID 0.
After the crash, the RAID file system required a manual fsck before we could bring the system back up.
Description of the RAID controler within /etc/sysconfig/hwconfig is
"CMD Technologies Inc | Silicon Image SiI 3112 SATARaid Controller"
vendor Id: 1095
deviceID:3112
subVenderId: 15d9
subDeviceId: 6112
pciType: 1
modules.conf showes
alias scsi hostadapter sii6512
Any idea's as to why the OS crashed instead of recovering gracefully?
Is this a software or hardware problem?
This server seems to have crashed with only the following messages int the /var/log/messages:
Kernel: SCSI: aborting command due to time out : pid 123456789 SCSI 1, Channel 0, id 0, lun 0 Read (10) 00 0a 51 95 97 00 00 80 00
Kernel: Abort Request: in the TOP
The boot drive is a IDE drive. The drives are set to RAID 0.
After the crash, the RAID file system required a manual fsck before we could bring the system back up.
Description of the RAID controler within /etc/sysconfig/hwconfig is
"CMD Technologies Inc | Silicon Image SiI 3112 SATARaid Controller"
vendor Id: 1095
deviceID:3112
subVenderId: 15d9
subDeviceId: 6112
pciType: 1
modules.conf showes
alias scsi hostadapter sii6512
Any idea's as to why the OS crashed instead of recovering gracefully?
Is this a software or hardware problem?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.