From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 10 08:08:29 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9DD316A41C for ; Fri, 10 Jun 2005 08:08:29 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ACD243D1F for ; Fri, 10 Jun 2005 08:08:29 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 036AA19F3B; Fri, 10 Jun 2005 01:09:48 -0700 (PDT) From: "Darren Pilgrim" To: =?iso-8859-1?Q?'=22Dag-Erling_Sm=F8rgrav=22'?= Date: Fri, 10 Jun 2005 01:08:10 -0700 Message-ID: <000001c56d93$8b65c590$0a2a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: <86k6l23cnj.fsf@xps.des.no> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Cc: freebsd-hackers@freebsd.org Subject: RE: Determining disk device and kicking GEOM when doing automatic mounting of umass devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2005 08:08:29 -0000 > -----Original Message----- > From: "Dag-Erling Sm=F8rgrav" [mailto:des@des.no]=20 > Sent: Friday, June 10, 2005 12:16 AM > To: Darren Pilgrim > Cc: freebsd-hackers@freebsd.org > Subject: Re: Determining disk device and kicking GEOM when=20 > doing automatic mounting of umass devices >=20 >=20 > "Darren Pilgrim" writes: > > Attached as named above. The logs show the da0 DISK class=20 > in the GEOM > > config, but no MBR class entry. >=20 > Take a closer look at geom-logs. It shows a slew of CAM errors. > There's something wrong with your fob, or possibly (but not likely) > with the USB stack. Except that after all those errors, it still mounts and "works fine". = Also, trying to mount /dev/da0 does produce the MBR entry in the GEOM config: 1 MBR da0s1 255849984 512 i 0 o 2048 ty 11 It also produces a single "READ CAPACITY" CAM error like those produced = when the device attaches. I also tested with a known-good USB zip drive = plugged into the same USB port. It attached flawlessly: the console showed the normal attach messages, GEOM config shows the appropriate MBR entry and /dev/da0s4 is created. So yeah I gueuss my fob is busted or funky. The CAM errors are "just" = the drive saying there's no media present, so maybe the device doesn't = support the commands necessary to report disk capacity? Is there a way to = educate CAM about this so the attach procedure doesn't break? Why would the CAM errors prevent GEOM from creating the MBR geom during attach but not when trying to mount /dev/da0?