Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!spool.mu.edu!agate!tfs.com!tfs.com!julian
From: julian@tfs.com (Julian Elischer)
Subject: Re: help with the scsi subsystem needed
Message-ID: <1992Oct23.033335.578@tfs.com>
Organization: TRW Financial Systems
References: <BwJ5qz.32r@da_vinci.it.uswc.uswest.com>
Date: Fri, 23 Oct 1992 03:33:35 GMT
Lines: 67
In article <BwJ5qz.32r@da_vinci.it.uswc.uswest.com> awade@lookout.it.uswc.uswest.com (Allen Wade) writes:
>I need some help to figure out what this machine is trying to tell me
>I have the OS patchkit from terry installed and the beta3 scsi subsystem.
>The machine still boots ok I can still read the label from the second disk,
>but I cannot newfs the second disk. I have sd0 and sd1 defined in my kernel
>config file so what does it mean "Too many scsi disks".
>allen
>awade@lookout.uswest.com
>
>A little bit of /var/log/messages:
>
>Oct 21 21:48:57 kestrel /386bsd: pc0<color> at 0x60 irq 1 on isa
>Oct 21 21:48:57 kestrel /386bsd: com1 at 0x3f8 irq 4 on isa
>Oct 21 21:48:57 kestrel /386bsd: com2 at 0x2f8 irq 3 on isa
>Oct 21 21:48:57 kestrel /386bsd: fd0 drives 0: 1.44M at 0x3f0 irq 6 drq 2 on isa
>Oct 21 21:48:57 kestrel /386bsd: aha0 reading board settings, 150 nSEC ok, use 200 nSEC
>Oct 21 21:48:57 kestrel /386bsd: **aha0 probing for scsi devices**
>Oct 21 21:48:58 kestrel /386bsd: dev0,lu0: type 0(direct),fixed 'IMPRIMIS94601-15 1250' scsi1
>Oct 21 21:48:58 kestrel /386bsd: sd0: 990MB, cyls 1931, heads 15, secs 70, bytes/sec 512
>Oct 21 21:48:58 kestrel /386bsd: dev1,lu0: type 0(direct),fixed 'MAXTOR LXT-200S 4.18' scsi1
>Oct 21 21:48:58 kestrel /386bsd: Too many scsi disks..(2 > 1) reconfigure kernel dev1,lu1: type 0(direct),fixed 'MAXTOR LXT-200S 4.18' scsi1
>Oct 21 21:48:58 kestrel /386bsd: Too many scsi disks..(3 > 1) reconfigure kernel dev1,lu2: type 0(direct),fixed 'MAXTOR LXT-200S 4.18' scsi1
>Oct 21 21:48:58 kestrel /386bsd: Too many scsi disks..(4 > 1) reconfigure kernel dev1,lu3: type 0(direct),fixed 'MAXTOR LXT-200S 4.18' scsi1
>Oct 21 21:48:58 kestrel /386bsd: Too many scsi disks..(5 > 1) reconfigure kernel dev1,lu4: type 0(direct),fixed 'MAXTOR LXT-200S 4.18' scsi1
>Oct 21 21:48:58 kestrel /386bsd: Too many scsi disks..(6 > 1) reconfigure kernel dev1,lu5: type 0(direct),fixed 'MAXTOR LXT-200S 4.18' scsi1
>Oct 21 21:48:58 kestrel /386bsd: Too many scsi disks..(7 > 1) reconfigure kernel dev1,lu6: type 0(direct),fixed 'MAXTOR LXT-200S 4.18' scsi1
>Oct 21 21:48:58 kestrel /386bsd: Too many scsi disks..(8 > 1) reconfigure kernel dev1,lu7: type 0(direct),fixed 'MAXTOR LXT-200S 4.18' scsi1
>Oct 21 21:48:59 kestrel /386bsd: Too many scsi disks..(9 > 1) reconfigure kernel dev3,lu0: type 0(direct),fixed 'unknownunknown????' scsi0
>Oct 21 21:48:59 kestrel /386bsd: Too many scsi disks..(10 > 1) reconfigure kernelaha0 at 0x330 irq 11 drq 5 on isa
>Oct 21 21:48:59 kestrel /386bsd: npx0 at 0xf0 irq 13 on isa
>Oct 21 21:48:59 kestrel /386bsd: changing root device to as0a
>
>
>--
>----------------------------------------------------------------
>Allen Wade Faster, faster until
>awade@uswest.com thrill of speed overcomes
> the fear of death.
> H.S. Thompson
>
>----------------------------------------------------------------
you have a 'badly behaved' drive.
it is responding positively even on LUs that are invalid
as a workaround, look in scsiconf.c for the two nested loops
each doing 8 loops:
make the inner loop only run once and it should only probe the
first LU of the drives.
as for the disklabel,
what newfs,
what partitions do you have, and what disklabel?
the output from fdisk (posted recently) and disklabel -r
would be useful in debugging this.
julian
+----------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / On assignment
| / \ julian@tfs.com +------>x USA \ in a very strange
| ( OZ ) 2118 Milvia st. Berkeley CA. \___ ___ | country !
+- X_.---._/ USA+(510) 704-3137(wk) \_/ \\
v