Date: Thu, 29 Dec 2011 06:47:40 -0800 From: Matthew Jacob <mj@feral.com> To: freebsd-scsi@freebsd.org Subject: Re: Fwd: ISP driver and FreeBSD Message-ID: <4EFC7D8C.1000904@feral.com> In-Reply-To: <CAG%2Br6L-e6NAA=jOQQ8V13%2Bp-3fBMV0aEsWybScs5e7uE4AbbfA@mail.gmail.com> References: <CAG%2Br6L8qNvgVQ8cb1Hd%2Bekrnifmqvnh5ztmDqDZqQcG75rPw4A@mail.gmail.com> <CAG%2Br6L-e6NAA=jOQQ8V13%2Bp-3fBMV0aEsWybScs5e7uE4AbbfA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/29/2011 12:16 AM, Omer Faruk SEN wrote: > Sorry for cross posting but i thinkt this is the right place not > freebsd-questions. Generally speaking these kinds of issues have to do with what LUNs your EMC is exporting and how FreeBSD configures drives. FreeBSD isn't all that smart about using REPORT LUNS to find the correct luns to attach, so this likely means that the EMC is exporting, say, LUN 10 as a real volume and LUN 0 as a stub, bogus lun. FreeBsD hits lun0, it fails to attach, so FreeBSD stops looking. You either need to reconfigure the EMC to export something at lun0, or you can do this: + Find out what LUN the EMC is exporting for the data volume + Explicitly scan for it You do the latter by finding the bus number for whichever isp you want to scan (using 'camcontrol devlist -v'), and then explicitly scan for it: camcontrol rescan N:0:M (where N == scbus number and M is the lun).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EFC7D8C.1000904>