Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 323
  • Last Modified:

LILO/SCSI bootup problem

Ok, I installed Red Hat 6.1 from a SCSI CD Rom on a AHA-3940 SCSI controller.  Everything went great until it went to bootup.  It runs LILO and gets alomst done when it craps out. after it detects the TEAC SCSI Cd_Rom the exact wording is as follows  Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 scsi : aborting command due to timeout : pid 0, scsi1, channel 0, id 0, lun 0 test unit ready 00 00 00 00 00 then it just sits there.
When i put in the bootable CD rom and then type vmlinuz root=/dev/hda1 it brings up a windows asking me if i want to remove the SCSI cd-rom i said keep the info and then it booted up.  But i had no access to my Cd-Rom.  So then i reboot the box,remove the bootable cd-rom and it goes back to the same problem.  Is there something I'm missing ??



tommyt
0
ttrogden
Asked:
ttrogden
  • 10
  • 9
  • 3
1 Solution
 
jlevieCommented:
What does your SCSI bus look like? What devices are connected, in what order and with what SCSI ID's. Are you certain that the termination is correct? Have you tried disconnecting the CD drive (and re-terminating if necessary) to see if the disk will boot then?
0
 
jlevieCommented:
Never mind the last about disconnecting the CD, I just re-read the question and realized it erroring on scsi 1,0.0, not the CD (0,3,0).
0
 
ttrogdenAuthor Commented:
so what should i try??

0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jlevieCommented:
The rest of my questions still apply. What's the SCSI config, etc...
0
 
ttrogdenAuthor Commented:
where do i get that info ??
0
 
ttrogdenAuthor Commented:
i hope this is what you need

SCSI ID #3 Teac - CD ROM CD-56 on Channel A on a AHA-3940  Card
0
 
jlevieCommented:
Whats on channel B, the way I read the error that's the device that has the error.
0
 
ttrogdenAuthor Commented:
there is nothing connected to B.  He has only one Scsi device and thats the CD-Rom, His HD is an IDE

0
 
jlevieCommented:
Oh, well that's why the error occurs. It's trying to probe devices on the B channel and gets a timeout error.

Lemme see what I can find on how to keep that from happening.
0
 
ttrogdenAuthor Commented:
thanks
0
 
jlevieCommented:
Which particular 3940 is it, 3940, 3940U, 3940U2? Is termination in the Adaptec bios set to "enabled"?
0
 
kiffneyCommented:
I had lots of timeout problems on Adaptec controllers connected to cd-roms with redhat 6.1 (which I think comes with kernel version 2.2.3).  When I upgraded the kernel to 2.2.14 those problems went away.  You might try that.
0
 
jlevieCommented:
kiffney... Which Adaptec, what version of firmware on it and what CD drive. I've got a number of RH 6.1 taking to quite a few Adaptec's and have never, ever seem any timeouts that weren't explained by bad hardware or old firmware.
0
 
ttrogdenAuthor Commented:
it's a 3940 Ultra/Ultra wide.  I went into the AHA config mode and couldn't find where i could disable the B channel -

I looked on the B channel again to make sure nothing was connected to it and all it showed was AHA-3940 on #7
0
 
kiffneyCommented:
An Adaptec 1740 (EISA) and a 1542B going to a NEC 7-slot changer and some old XM3014s.  I swapped out adapters, cables, machines, etc. until I upgraded the kernel, then timeouts disappeared.  That doesn't PROVE the kernel 'solved' the problem, but it may be that overly tight timing requirements in earlier code were relaxed in later versions.  There were sync_rate patches to the aic7xxx driver (which ttrogden is using) in the 2.2.10 kernel, and patches that fixed my Adapted 1542 problems in the 2.2.12 kernel.  We're trying to answer ttrogden's answer here, right?  I'm not saying he couldn't have a termination problem - I'm just saying I KNOW I didn't have termination problems, and my firmware was up-to-date, and I still got timeouts from my scsi cds under that kernel with the controllers mentioned above.  
0
 
kiffneyCommented:
An Adaptec 1740 (EISA) and a 1542B going to a NEC 7-slot changer and some old XM3014s.  I swapped out adapters, cables, machines, etc. until I upgraded the kernel, then timeouts disappeared.  That doesn't PROVE the kernel 'solved' the problem, but it may be that overly tight timing requirements in earlier code were relaxed in later versions.  There were sync_rate patches to the aic7xxx driver (which ttrogden is using) in the 2.2.10 kernel, and patches that fixed my Adapted 1542 problems in the 2.2.12 kernel.  We're trying to answer ttrogden's answer here, right?  I'm not saying he couldn't have a termination problem - I'm just saying I KNOW I didn't have termination problems, and my firmware was up-to-date, and I still got timeouts from my scsi cds under that kernel with the controllers mentioned above.  
0
 
jlevieCommented:
Leeme take another looks at the docs about the termination
0
 
ttrogdenAuthor Commented:
Don't worry about it.  I decided that this was just to mauch crap and I really need this to work ASAP, so I removed the Adaptec Card.  Anyway, I'm going to change this question.  I'm having problems with a 3c905-tx card.  It's not running correctly.  Linux RH 6.1 doesn't list this card in there linuxconf area.  should i use another driver for it.


Sorry about changing the question.  It was just frustrating the hell out of me.  I'm going to leave the points the same.


thanks


Ttrogden
0
 
jlevieCommented:
The 3c905 shouldn't be a problem, it's on the HCL and every RH6.1 system I've got except one has that card.

What problem have you got with the card?
0
 
ttrogdenAuthor Commented:
i didn't seea  choice for that card in the linuxconf area.  I saw the 3c509 but no 3c905 - so i set it up as a 3c509 and it's not working


0
 
jlevieCommented:
Well that's why it's not working. You normally don't have to manually select the "Kernel module", "I/O port", or "Irq" for most ethernet adapters as the kernel will figure it out on its own. But, if you do manually select one it has to be the right driver. In the case of 3c905, you'd select 3c59x, as that driver supports the 3c905.
0
 
ttrogdenAuthor Commented:
Thanks for the help jlevie !!


0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 10
  • 9
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now