Date: Fri, 9 Aug 2002 17:12:00 +0200 From: Bernd Walter <ticso@cicely5.cicely.de> To: Marcin Gryszkalis <mgryszkalis@cerint.pl> Cc: freebsd-scsi@FreeBSD.ORG, freebsd-alpha <freebsd-alpha@FreeBSD.ORG> Subject: Re: da driver problem? Message-ID: <20020809151159.GV52932@cicely5.cicely.de> In-Reply-To: <3D53C01A.1050702@cerint.pl> References: <3D5280F4.8030706@cerint.pl> <20020808152922.A18763@panzer.kdm.org> <3D53BD58.1060600@cerint.pl> <20020809130749.GJ52932@cicely5.cicely.de> <3D53C01A.1050702@cerint.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 09, 2002 at 03:14:02PM +0200, Marcin Gryszkalis wrote: > Bernd Walter wrote: > >>camcontrol devlist: > >><DEC RZ29B (C) DEC 0016> at scbus0 target 1 lun 0 (pass0,da0) > .... > >><DEC RZ29B (C) DEC 0016> at scbus0 target 15 lun 0 (pass14,da14) > > >If this is all the same drive you should check for an SCSI-ID > >collision - most likely with the host adapter. > > Sure - it is the same drive - I can't access the other one. > but - how do I check - I don't know much about scsi internals. I would say selecting IDs is scsi fundamentals. Each scsi device usualy has 3 to 4 id jumpers which are binary coded to an id. The hostadapter typicaly use id 7. But after reviewing your mail before I noticed that there is no id 0, which could mean that your drive as well the hostadapter is on id 0. As you said it's a new problem I would guess the controller driver failed to use the right ID for itself. Do you have bootlogs in /var/log/messages* from the old OS version? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020809151159.GV52932>