(Please pardon the excessive logs)
Very good question, sorry I forget it to start out with...
On 1 chanel (the internal one, if it matters), I have just 1 UWSCSI2
drive. On the other channel I have 6 devices, the 3 other drives, a CD-RW
drive, a ZIP drive, and a Conner tape drive. So, your guess about
termination on the 2 drives isn't it. Note that I do successfully write
entire CDs to the CD-RW with no SCSI problems. Admittedly this is really
slow (2X speed only) so it is not pushing the performance anywhere.
As to the id's, etc, here's a bit more from my logs:
Feb 1 07:48:16 dual kernel: (scsi0) <Adaptec AIC-7895 Ultra SCSI host
adapter> found at PCI 14/0
Feb 1 07:48:16 dual kernel: (scsi0) Wide Channel A, SCSI ID=7, 32/255 SCBs
Feb 1 07:48:16 dual kernel: (scsi0) Downloading sequencer code... 374
instructions downloaded
Feb 1 07:48:16 dual kernel: (scsi1) <Adaptec AIC-7895 Ultra SCSI host
adapter> found at PCI 14/1
Feb 1 07:48:16 dual kernel: (scsi1) Wide Channel B, SCSI ID=7, 32/255 SCBs
Feb 1 07:48:16 dual kernel: (scsi1) Downloading sequencer code... 374
instructions downloaded
Feb 1 07:48:16 dual kernel: scsi0 : Adaptec AHA274x/284x/294x
(EISA/VLB/PCI-Fast SCSI) 5.1.22/3.2.4
Feb 1 07:48:16 dual kernel: <Adaptec AIC-7895 Ultra SCSI host
adapter>
Feb 1 07:48:16 dual kernel: scsi1 : Adaptec AHA274x/284x/294x
(EISA/VLB/PCI-Fast SCSI) 5.1.22/3.2.4
Feb 1 07:48:16 dual kernel: <Adaptec AIC-7895 Ultra SCSI host
adapter>
Feb 1 07:48:16 dual kernel: scsi : 2 hosts.
Feb 1 07:48:16 dual kernel: (scsi0:0:1:0) Synchronous at 32.0 Mbyte/sec,
offset 8.
Feb 1 07:48:16 dual kernel: Vendor: SEAGATE Model: ST34555W
Rev: 0930
Feb 1 07:48:16 dual kernel: Type: Direct-Access
ANSI SCSI revision: 02
Feb 1 07:48:16 dual kernel: (scsi1:0:0:0) Synchronous at 20.0 Mbyte/sec,
offset 15.
Feb 1 07:48:16 dual kernel: Vendor: QUANTUM Model: FIREBALL_TM3200S
Rev: 300N
Feb 1 07:48:16 dual kernel: Type: Direct-Access
ANSI SCSI revision: 02
Feb 1 07:48:16 dual kernel: (scsi1:0:1:0) Synchronous at 10.0 Mbyte/sec,
offset 15.
Feb 1 07:48:16 dual kernel: Vendor: MELCO Model: DSC-E8000
Rev: 1.02
Feb 1 07:48:16 dual kernel: Type: Direct-Access
ANSI SCSI revision: 02
Feb 1 07:48:16 dual kernel: scsi1 : channel 0 target 1 lun 1 request sense
failed, performing reset.
Feb 1 07:48:16 dual kernel: SCSI bus is being reset for host 1 channel 0.
Feb 1 07:48:16 dual kernel: (scsi1:0:1:0) Synchronous at 10.0 Mbyte/sec,
offset 15.
Feb 1 07:48:16 dual kernel: (scsi1:0:3:0) Synchronous at 10.0 Mbyte/sec,
offset 15.
Feb 1 07:48:16 dual kernel: Vendor: nEC Model: DSE2010S
Rev: 0314
Feb 1 07:48:16 dual kernel: Type: Direct-Access
ANSI SCSI revision: 02
Feb 1 07:48:16 dual kernel: (scsi1:0:4:0) Synchronous at 5.0 Mbyte/sec,
offset 15.
Feb 1 07:48:16 dual kernel: Vendor: CONNER Model: CTT8000-S
Rev: 1.17
Feb 1 07:48:16 dual kernel: Type: Sequential-Access
ANSI SCSI revision: 02
Feb 1 07:48:16 dual kernel: Vendor: IOMEGA Model: ZIP 100
Rev: D.13
Feb 1 07:48:16 dual kernel: Type: Direct-Access
ANSI SCSI revision: 02
Feb 1 07:48:16 dual kernel: Vendor: RICOH Model: MP6200S
Rev: 2.03
Feb 1 07:48:16 dual kernel: Type: CD-ROM
ANSI SCSI revision: 02
Feb 1 07:48:16 dual kernel: Detected scsi disk sda at scsi0, channel 0, id
1, lun 0
Feb 1 07:48:16 dual kernel: Detected scsi disk sdb at scsi1, channel 0, id
0, lun 0
Feb 1 07:48:16 dual kernel: Detected scsi disk sdc at scsi1, channel 0, id
1, lun 0
Feb 1 07:48:16 dual kernel: Detected scsi disk sdd at scsi1, channel 0, id
3, lun 0
Feb 1 07:48:16 dual kernel: Detected scsi removable disk sde at scsi1,
channel 0, id 5, lun 0
Feb 1 07:48:16 dual kernel: SCSI device sda: hdwr sector= 512 bytes.
Sectors= 8888924 [4340 MB] [4.3 GB]
Feb 1 07:48:16 dual kernel: sda: sda1 sda2 sda3
Feb 1 07:48:16 dual kernel: (scsi1:0:0:0) Synchronous at 20.0 Mbyte/sec,
offset 15.
Feb 1 07:48:16 dual kernel: SCSI device sdb: hdwr sector= 512 bytes.
Sectors= 6281856 [3067 MB] [3.1 GB]
Feb 1 07:48:16 dual kernel: sdb: sdb1 sdb2
Feb 1 07:48:16 dual kernel: SCSI device sdc: hdwr sector= 512 bytes.
Sectors= 16512768 [8062 MB] [8.1 GB]
Feb 1 07:48:16 dual kernel: sdc: sdc1 sdc2 sdc3
Feb 1 07:48:16 dual kernel: SCSI device sdd: hdwr sector= 512 bytes.
Sectors= 3931200 [1919 MB] [1.9 GB]
Feb 1 07:48:16 dual kernel: sdd: sdd1 sdd2
Feb 1 07:48:16 dual kernel: sde : READ CAPACITY failed.
Feb 1 07:48:16 dual kernel: sde : status = 1, message = 00, host = 0,
driver = 28
Feb 1 07:48:16 dual kernel: sde : extended sense code = 2
Feb 1 07:48:16 dual kernel: sde : block size assumed to be 512 bytes, disk
size 1GB.
Feb 1 07:48:16 dual kernel: sde:scsidisk I/O error: dev 08:40, sector 0
Feb 1 07:48:16 dual kernel: unable to read partition table
Looking at these logs I also remembered that I have swap partitions on
each of the 4 SCSI devices as well. Could the be related?
And, here's my RAID info:
Feb 1 07:48:16 dual kernel: autorun ...
Feb 1 07:48:16 dual kernel: considering sda2 ...
Feb 1 07:48:16 dual kernel: adding sda2 ...
Feb 1 07:48:16 dual kernel: adding sdd2 ...
Feb 1 07:48:16 dual kernel: created md0
Feb 1 07:48:16 dual kernel: bind<sdd2,1>
Feb 1 07:48:16 dual kernel: bind<sda2,2>
Feb 1 07:48:16 dual kernel: running: <sda2><sdd2>
Feb 1 07:48:16 dual kernel: now!
Feb 1 07:48:16 dual kernel: sda2's event counter: 00000005
Feb 1 07:48:16 dual kernel: sdd2's event counter: 00000005
Feb 1 07:48:16 dual kernel: raid0 personality registered
Feb 1 07:48:16 dual kernel: mask fffffffc
Feb 1 07:48:16 dual kernel: rdev->size: 1180672
Feb 1 07:48:16 dual kernel: masked rdev->size: 1180672
Feb 1 07:48:16 dual kernel: new md_size: 1180672
Feb 1 07:48:16 dual kernel: rdev->size: 1823296
Feb 1 07:48:16 dual kernel: masked rdev->size: 1823296
Feb 1 07:48:16 dual kernel: new md_size: 3003968
Feb 1 07:48:16 dual kernel: md0: max total readahead window set to 256k
Feb 1 07:48:16 dual kernel: md0: 2 data-disks, max readahead per data-disk:
128k
Feb 1 07:48:16 dual kernel: raid0: looking at sdd2
Feb 1 07:48:16 dual kernel: raid0: comparing sdd2(1823296) with
sdd2(1823296)
Feb 1 07:48:16 dual kernel: raid0: END
Feb 1 07:48:16 dual kernel: raid0: ==> UNIQUE
Feb 1 07:48:16 dual kernel: raid0: 1 zones
Feb 1 07:48:16 dual kernel: raid0: looking at sda2
Feb 1 07:48:16 dual kernel: raid0: comparing sda2(1180672) with
sdd2(1823296)
Feb 1 07:48:16 dual kernel: raid0: NOT EQUAL
Feb 1 07:48:16 dual kernel: raid0: comparing sda2(1180672) with
sda2(1180672)
Feb 1 07:48:16 dual kernel: raid0: END
Feb 1 07:48:16 dual kernel: raid0: ==> UNIQUE
Feb 1 07:48:16 dual kernel: raid0: 2 zones
Feb 1 07:48:16 dual kernel: raid0: FINAL 2 zones
Feb 1 07:48:16 dual kernel: zone 0
Feb 1 07:48:16 dual kernel: checking sdd2 ... contained as device 0
Feb 1 07:48:16 dual kernel: (1823296) is smallest!.
Feb 1 07:48:16 dual kernel: checking sda2 ... contained as device 1
Feb 1 07:48:16 dual kernel: (1180672) is smallest!.
Feb 1 07:48:16 dual kernel: zone->nb_dev: 2, size: 2361344
Feb 1 07:48:16 dual kernel: current zone offset: 1180672
Feb 1 07:48:16 dual kernel: zone 1
Feb 1 07:48:16 dual kernel: checking sdd2 ... contained as device 0
Feb 1 07:48:16 dual kernel: (1823296) is smallest!.
Feb 1 07:48:16 dual kernel: checking sda2 ... nope.
Feb 1 07:48:16 dual kernel: zone->nb_dev: 1, size: 642624
Feb 1 07:48:16 dual kernel: current zone offset: 1823296
Feb 1 07:48:16 dual kernel: done.
Feb 1 07:48:16 dual kernel: raid0 : md_size is 3003968 blocks.
Feb 1 07:48:16 dual kernel: raid0 : conf->smallest->size is 642624 blocks.
Feb 1 07:48:16 dual kernel: raid0 : nb_zone is 5.
Feb 1 07:48:16 dual kernel: raid0 : Allocating 40 bytes for hash.
Feb 1 07:48:16 dual kernel: md: updating md0 RAID superblock on device
Feb 1 07:48:16 dual kernel: sda2 [events: 00000006](write) sda2's sb
offset: 1180672
Feb 1 07:48:16 dual kernel: sdd2 [events: 00000006](write) sdd2's sb
offset: 1823296
Feb 1 07:48:16 dual kernel: .
Feb 1 07:48:16 dual kernel: ... autorun DONE.
Feb 1 07:48:16 dual kernel: (read) sda3's sb offset: 3004032 [events:
00000006]
Feb 1 07:48:16 dual kernel: (read) sdc3's sb offset: 3004032 [events:
00000006]
Feb 1 07:48:16 dual kernel: (read) sdc2's sb offset: 3004032 [events:
00000006]
Feb 1 07:48:16 dual kernel: autorun ...
Feb 1 07:48:16 dual kernel: considering sdc2 ...
Feb 1 07:48:16 dual kernel: adding sdc2 ...
Feb 1 07:48:16 dual kernel: adding sdc3 ...
Feb 1 07:48:16 dual kernel: adding sda3 ...
Feb 1 07:48:16 dual kernel: created md1
Feb 1 07:48:16 dual kernel: bind<sda3,1>
Feb 1 07:48:16 dual kernel: bind<sdc3,2>
Feb 1 07:48:16 dual kernel: md1: WARNING: sdc2 appears to be on the same
physical disk as sdc3. True
Feb 1 07:48:16 dual kernel: protection against single-disk failure
might be compromised.
Feb 1 07:48:16 dual kernel: bind<sdc2,3>
Feb 1 07:48:16 dual kernel: running: <sdc2><sdc3><sda3>
Feb 1 07:48:16 dual kernel: now!
Feb 1 07:48:16 dual kernel: sdc2's event counter: 00000006
Feb 1 07:48:16 dual kernel: sdc3's event counter: 00000006
Feb 1 07:48:16 dual kernel: sda3's event counter: 00000006
Feb 1 07:48:16 dual kernel: md: md1: raid array is not clean -- starting
background reconstruction
Feb 1 07:48:16 dual kernel: raid5 personality registered
Feb 1 07:48:16 dual kernel: md1: max total readahead window set to 1024k
Feb 1 07:48:16 dual kernel: md1: 2 data-disks, max readahead per data-disk:
512k
Feb 1 07:48:16 dual kernel: raid5: device sdc2 operational as raid disk 2
Feb 1 07:48:16 dual kernel: raid5: device sdc3 operational as raid disk 1
Feb 1 07:48:16 dual kernel: raid5: device sda3 operational as raid disk 0
Feb 1 07:48:16 dual kernel: raid5: allocated 3197kB for md1
Feb 1 07:48:16 dual kernel: raid5: raid level 5 set md1 active with 3 out
of 3 devices, algorithm 2
Feb 1 07:48:16 dual kernel: raid5: raid set md1 not clean; reconstructing
parity
Feb 1 07:48:16 dual kernel: RAID5 conf printout:
Feb 1 07:48:16 dual kernel: --- rd:3 wd:3 fd:0
Feb 1 07:48:16 dual kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:sda3
Feb 1 07:48:16 dual kernel: disk 1, s:0, o:1, n:1 rd:1 us:1 dev:sdc3
Feb 1 07:48:16 dual kernel: disk 2, s:0, o:1, n:2 rd:2 us:1 dev:sdc2
Feb 1 07:48:16 dual kernel: disk 3, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 4, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 5, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 6, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual smb: smbd startup succeeded
Feb 1 07:48:16 dual kernel: disk 7, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 8, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 9, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 10, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 11, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: RAID5 conf printout:
Feb 1 07:48:16 dual kernel: --- rd:3 wd:3 fd:0
Feb 1 07:48:16 dual kernel: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:sda3
Feb 1 07:48:16 dual kernel: disk 1, s:0, o:1, n:1 rd:1 us:1 dev:sdc3
Feb 1 07:48:16 dual kernel: disk 2, s:0, o:1, n:2 rd:2 us:1 dev:sdc2
Feb 1 07:48:16 dual kernel: disk 3, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 4, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 5, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 6, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 7, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 8, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 9, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 10, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: disk 11, s:0, o:0, n:0 rd:0 us:0 dev:[dev
00:00]
Feb 1 07:48:16 dual kernel: md: updating md1 RAID superblock on device
Feb 1 07:48:16 dual kernel: sdc2 [events: 00000007](write) sdc2's sb
offset: 3004032
Feb 1 07:48:16 dual kernel: md: syncing RAID array md1
Feb 1 07:48:16 dual kernel: md: minimum _guaranteed_ reconstruction speed:
100 KB/sec.
Feb 1 07:48:16 dual kernel: md: using maximum available idle IO bandwith
for reconstruction.
Feb 1 07:48:16 dual kernel: md: using 1024k window.
Feb 1 07:48:16 dual kernel: sdc3 [events: 00000007](write) sdc3's sb
offset: 3004032
Feb 1 07:48:16 dual kernel: sda3 [events: 00000007](write) sda3's sb
offset: 3004032
Feb 1 07:48:16 dual kernel: .
Feb 1 07:48:16 dual kernel: ... autorun DONE.
Also from previously:
Feb 1 00:36:30 dual kernel: running: <sdb2><sdc2><sdc3><sda3>
Feb 1 00:36:30 dual kernel: now!
Feb 1 00:36:30 dual kernel: sdb2's event counter: 00000001
Feb 1 00:36:30 dual kernel: sdc2's event counter: 00000005
Feb 1 00:36:30 dual kernel: sdc3's event counter: 00000005
Feb 1 00:36:30 dual kernel: sda3's event counter: 00000005
Feb 1 00:36:30 dual kernel: md: superblock update time inconsistency --
using the most recent one
Feb 1 00:36:30 dual kernel: freshest: sdc2
Feb 1 00:36:30 dual kernel: md: kicking non-fresh sdb2 from array!
Feb 1 00:36:30 dual kernel: unbind<sdb2,3>
Feb 1 00:36:30 dual kernel: export_rdev(sdb2)
Feb 1 00:36:30 dual kernel: md1: removing former faulty sdb2!
Feb 1 00:36:30 dual kernel: raid5 personality registered
What might have caused sdb2 to get kicked?
Also a question into the mysteries of SCSI termination. I mentioned that
1 drive died and I removed it. When I removed it from its external case I
left the other drive in the case (it is a case for 2 drives). This means
that the ribbon cable in that case now only has one thing connected to it,
not 2. Should this make a difference? My understanding is no.
Also, regarding figuring out the general SCSI stuff before playing with
RAID. I heartily agree. Ugh, now my head hurts.
--Rainer
----- Original Message -----
From: James Manning <[EMAIL PROTECTED]>
To: Rainer Mager <[EMAIL PROTECTED]>
Cc: Linux-RAID <[EMAIL PROTECTED]>
Sent: Tuesday, February 01, 2000 12:00 PM
Subject: Re: Argh, more problems with SCSI and RAID
| Tell us how the 4 (5?) drives are scattered among the 2 controllers (2
| channels of one controller?), which id's, etc. The above looks like my
| 3960D problem that went away when I added "noapic" on my BP6 board.
|
| Perhaps it's a termination issue since it looks limited to 2 drives on
| one controller? Just a guess.
|
| In any case, I wouldn't bother with the md layer until you can get all
| the scsi drives acting happy for extended periods of time :)
|
| James
| --
| Miscellaneous Engineer --- IBM Netfinity Performance Development
|
