Date: Mon, 12 Aug 2002 14:24:28 +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: <20020812122428.GF55760@cicely5.cicely.de> In-Reply-To: <3D57A4BA.9060104@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> <20020809151159.GV52932@cicely5.cicely.de> <3D57A4BA.9060104@cerint.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 12, 2002 at 02:06:18PM +0200, Marcin Gryszkalis wrote: > Hi > Today I rebooted the box with ispfw.ko loaded but > it didn't help :( > Assignment is still the same (all da* to first hdd). > > I also booted 4.5-stable kernel (build from April 27) > and it went ok (reight assignment, second disc visible). > > Other thing - I saw this in messages: > > isp0: states=> GOT_BUS GOT_TGT > status=> > isp0: transport error for 0.1.0: > states=> GOT_BUS GOT_TGT > status=> Not surprising - I guess id 1 is your second disk, which failed, because the controller and the first hd share id 0. You should fix the isp nvram table. IIRC srm has support to edit these values. Another option would be to give disk id 0 a new id and leave the controller on 0. > but it may be becuse / was full (because > some directories from the other hdd were > not mounted and my scripts were writing > to /). No the filesystem has nothing to do with the scsi layer. -- 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-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020812122428.GF55760>