[lkml]   [2000]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: BIG problem with BusLogic SCSI and/or something else
On Wed, Oct 11, 2000 at 05:11:39PM -0400, Richard B. Johnson wrote:

> Linux version 2.2.17
> I tried to add a new Hard disk. It's s Seagate ST39102LW 8.1 Gb.

Hmm. Your C/H/S multiplies out to 9.1 GB.
On the other hand, Seagate ST39102LW has 9105018880 bytes,
so probably the 8 was a typo (and you are wasting 7859200 bytes).

> In the BIOS setup of the BusLogic adapter, I was able to format
> and verify the disk with no problems whatsoever.
> fdisk seemed to work okay. I made partitions.
> mke2fs would fail (hang the system) while writing inodes.
> The BusLogic driver would complain about "Aborting SCSI host 0 channel 0,
> pid 84446".
> This can't be a pid --anyway.

A SCSI one, not a Unix one.

But you omit the interesting part.
SCSI drivers tend to give a reason, say timeout, or medium error, whatever.
What was the precise error message?

In such cases what fdisk or fsck or so say is hardly of any interest.
One wants the kernel messages. Literally.

> When the BusLogic driver was going through its hour-long fits of
> resetting the bus,

Yes, Linux SCSI error recovery behaviour is not a pleasure to behold.
Some aspects of it are better in 2.4, however.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:39    [W:0.087 / U:0.360 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site