Andreas Fink (afink@pingnet.ch)
Thu, 18 Feb 1999 07:34:57 +0100
>On Wed, Feb 17, 1999, Dave Beck <dave@arginine.umdnj.edu> wrote:
>
>>Simply having the drive connected causes the boot process to fail?
>>That is really bizzare. Do you have a log of the boot and any
>>errors related to the failure? I'm going to assume the failure
>>occurs during the kernel init of the internal SCSI driver? Or is
>>it a quik thing?
>
>Basically, the kernel runs the SCSI initialization scripts, and they keep
>timing out and re-running over and over. The only way to boot
>successfully is to disconnect the drive until after boot-time.
>
>I'll ask our sysadmin if he can log the errors, or at least write them
>down. It's a long, ten-line-plus piece of information that repeats, so
>that might take a little while to get.
>
Watch out. This problem couldbe drive specific. I recently had such a case
with a very dumb NCR53c810 controller and some older Quantum 500M drives.
SCSI timeouts and getting stuck at boot. This was by using Kernel 2.2.1. It
was on the Alpha Platform though. However, I assume this can happen on any
platform. Since I got 5 IBM 4.5GB drives connected to it, everything works
fine, even the RAID5.
Andreas Fink
Chief Technical Manager
-----------------------------------------------------------------------
Ping Net GmbH, Hohlstrasse 608, 8048 Zürich, Switzerland
afink@pingnet.ch http://www.pingnet.ch/ Tel: 01 4391313 Fax: 01 4391310
Administration: admin@pingnet.ch Tech Support: support@pingnet.ch
-----------------------------------------------------------------------
Ping Net Sarl, World Trade Center, Av. Gratta Paille 2,
1000 Lausanne 30, Switzerland. Tel: 021-6411339 Fax: 021-6411310
-----------------------------------------------------------------------
This archive was generated by hypermail 2.0b3 on Wed Feb 17 1999 - 22:42:52 PST