> 
>    From: blymn@awadi.com.au (Brett Lymn)
>    Date: Mon, 5 Feb 1996 14:05:34 +1030 (CST)
> 
>    According to kpneal@unity.ncsu.edu:
>    >
>    >BTW, I already have one pr open for this drive:
>    >ahsc0 targ 0 lun 0: <MAXTOR, LXT-200S, 4.18> SCSI1 0/direct fixed
>    >scsi_inqmatch: 2/0/0 <, , >
>    >sd0 at scsibus0: 191MB, 1314 cyl, 7 head, 42 sec, 512 bytes/sec
>    >ahsc0 targ 0 lun 1: <MAXTOR, LXT-200S, 4.18> SCSI1 0/direct fixed
>    >ahsc0 targ 0 lun 2: <MAXTOR, LXT-200S, 4.18> SCSI1 0/direct fixed
>    >ahsc0 targ 0 lun 3: <MAXTOR, LXT-200S, 4.18> SCSI1 0/direct fixed
>    >ahsc0 targ 0 lun 4: <MAXTOR, LXT-200S, 4.18> SCSI1 0/direct fixed
>    >ahsc0 targ 0 lun 5: <MAXTOR, LXT-200S, 4.18> SCSI1 0/direct fixed
>    >ahsc0 targ 0 lun 6: <MAXTOR, LXT-200S, 4.18> SCSI1 0/direct fixed
>    >ahsc0 targ 0 lun 7: <MAXTOR, LXT-200S, 4.18> SCSI1 0/direct fixed
> 
>    Annoying but, unfortunately for you, not an OS problem.  I have seen
>    quite a few maxtors with exactly this problem on our Suns at work.  It
>    seems to be a fairly common fault with these disks, I have resurrected
>    one or two by swapping the drive electronics with a drive that had a
>    head crash.
> 
> Wouldn't it help to add them to the NOLUN list in scsi_conf.c? I mean,
> the particular model wouldn't have real LUNs, anyway?
> 

Did I mention that I already have a pr open for this, *with* a patch
to apply to the kernel included?

Unless I screwed up my send-pr, which I might have, but I did see
my pr come back across the list.

Anyway, Briggs sent me a patch for the not ready error, which I will
try as soon as I can.

I only have 5 homework assignments and two more tests this week.

Sigh.
XCOMM --------------------------------------------------------
XCOMM Kevin P. Neal, Sophomore CSC/CPE     kpneal@eos.ncsu.edu 
XCOMM North Carolina State University      kevinneal@bix.com
XCOMM --------------------------------------------------------