Forum OpenACS Q&A: Offtopic: SCSI problems on Redhat 7.2

Collapse
Posted by Jade Rubick on
Hi all,

I'm trying to get my new server up and running for one of my new OpenACS sites, and I'm getting stuck. I'll paypal some thank you bucks to someone who can help me figure this out. Or, I might just try and install an earlier version of Redhat (I know that 6.2 was supposed to be installed on this server previously).

Motherboard - Intel L440GX+ w/On Board Adaptec AIC-7896N SCSI Controller

After I install Red Hat 7.2, I boot up and get these messages:

scsi : aborting command due to time out : pid 0, scsi0, channel 
0, id0, lun 0, Inquiry 00 00 00 ff 00 

scsi : aborting command due to time out : pid 0, scsi0, channel 
0, id0, lun 0, Inquiry 00 00 00 ff 00 
It says that for id numbers 0-6 and then for id numbers 8-15. Then it says:
Attached scsi disk sda at scsi0, channel 0, id1, lun 0 

Attached scsi disk sdb at scsi0, channel 0, id2, lun 0 

scsi : aborting command due to time out : pid 0, scsi0, channel 
0, id0, lun 0, Test Unit Ready 00 00 00 00 00 

SCSI host 0 abort (pid 0) timed out - resetting 

SCSI bus is being reset for host 0 channel 0 

SCSI Host 0 abort (pid 0) timed out - resetting 

SCSI bus is being reset for host 0 channel 0 

(scsi0:0:1:0)Device reset, Message buffer in use 

SCSI host 0 channel 0 reset (pid 0) timed out - trying harder 

SCSI Host 0 abort (pid 0) timed out - resetting 

SCSI bus is being reset for host 0 channel 0 
...and on and on and on...

It also has a message about IRQ 11 being shared, but this might be because the Adaptec SCSI controller is a dual controller?

The only advice I've found online is to type:

linux apic
into lilo. This doesn't seem to do anything. Any other ideas?
Collapse
Posted by Petru Paler on

I've had the same problem with the same hardware, see bug #57408 in RedHat's bug database for the solution. You basically need to install the SMP kernel.

PS: I also had a somewhat similar problem with RedHat 7.1, but that one wouldn't install at all. The solution was to create custom boot disks and use

linux noapic
at install time, then also make sure that the custom kernel from the boot disks got installed (since the stock one didn't know about noapic). I guess that since then they've enabled the proper workaround for this chipset in the installation kernel.
Collapse
Posted by Jade Rubick on
Petru, thank you. Thank worked like a charm! It's up and running. Now, as soon as the new docs come out, I'll install OACS 4, and away we go!