Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Jun 2005 01:08:10 -0700
From:      "Darren Pilgrim" <>
To:        =?iso-8859-1?Q?'=22Dag-Erling_Sm=F8rgrav=22'?= <>
Subject:   RE: Determining disk device and kicking GEOM when doing automatic mounting of umass devices
Message-ID:  <000001c56d93$8b65c590$0a2a15ac@SMILEY>
In-Reply-To: <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

> -----Original Message-----
> From: "Dag-Erling Sm=F8rgrav" []=20
> Sent: Friday, June 10, 2005 12:16 AM
> To: Darren Pilgrim
> Cc:
> Subject: Re: Determining disk device and kicking GEOM when=20
> doing automatic mounting of umass devices
> "Darren Pilgrim" <> writes:
> > Attached as named above.  The logs show the da0 DISK class=20
> in the GEOM
> > config, but no MBR class entry.
> 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".  =
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 =
the device attaches.  I also tested with a known-good USB zip drive =
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" =
drive saying there's no media present, so maybe the device doesn't =
the commands necessary to report disk capacity?  Is there a way to =
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?

Want to link to this message? Use this URL: <$8b65c590$0a2a15ac>