[1382] in linux-scsi channel archive
Re: Scsi changes in 2.0.28?
daemon@ATHENA.MIT.EDU (kagel@quasar.bloomberg.com)
Mon Feb 3 16:25:14 1997
Date: Mon, 3 Feb 1997 14:57:35 -0500
From: kagel@quasar.bloomberg.com
To: alan@news.manawatu.gen.nz
Cc: submit-linux-dev-scsi@ratatosk.yggdrasil.com
In-Reply-To: <5d1r8v$cm3@papaioea.manawatu.gen.nz> (alan@news.manawatu.gen.nz)
Reply-To: kagel@dg1.bloomberg.com
Errors-To: postmaster@ns1
Path: manawatu.planet.co.nz!manawatu.gen.nz!not-for-mail
From: alan@news.manawatu.gen.nz (Alan Brown)
Newsgroups: linux.dev.scsi
Date: 2 Feb 1997 23:45:51 +1300
Organization: PlaNet (NZ) Manawatu, +64 6 357-9245, +64 6 367-9944
Lines: 14
X-Submitted-Via: news@ratatosk.yggdrasil.com (linux.* gateway)
Sender: owner-linux-scsi@vger.rutgers.edu
Precedence: bulk
Content-Type: text
Content-Length: 576
Has anyone got any idea why I would get scsi devices sda->sdg
detected on 2.0.28 when only sda->sdc are physically present?
Previous kernel was 2.0.12, adaptor is Adaptec 2940B (early PCI release)
sdb and sdc have two partitions, sda has only one.
This can happen if a device has the same SCSI ID as the controller. Most SCSI
controllers configure themselves as ID 7 but I have seen a few which use ID 0.
Check the IDs on your two drives.
--
Art S. Kagel, kagel@quasar.bloomberg.com
A proverb is no proverb to you 'till life has illustrated it. -- John Keats
