Date: Thu, 08 May 2008 09:01:37 -0600 From: Scott Long <scottl@samsco.org> To: Sean Bruno <sbruno@miralink.com> Cc: freebsd-scsi@freebsd.org Subject: Re: USB drive serial numbers Message-ID: <482315D1.4040401@samsco.org> In-Reply-To: <4823150F.30909@miralink.com> References: <48222930.2010808@miralink.com> <48223940.5090109@samsco.org> <482240FF.4030704@miralink.com> <48224361.10809@samsco.org> <48224E01.4030907@miralink.com> <48229F7F.6040602@samsco.org> <4823150F.30909@miralink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sean Bruno wrote: > >> >> A thumb drive that I have lying around has the same problem, it ignores >> the EVPD bit and happily returns std inq data for all requests. An >> ATA->USB+Firewire enclosure works correctly; it doesn't support any >> VPD pages, but returns a sense error in response, as it should. Given >> that Firewire is more explicit in its implementation of SBP/SPC, I'm not >> too surprised that it worked correctly (I tested this over the USB port, >> though). I have another ATA->USB enclosure lying around, but I can't >> find the power cord for it right now. >> >> Scott >> > > Interesting. Is there some other method that could be used to > "identify" drives > in the system? > Sean I think the only option is to do a std inq followed by an EVPD inquiry and bcmp the results. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?482315D1.4040401>