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

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
"Darren Pilgrim" <> writes:
> 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?

It's a direct-access storage device.  It *can't* not support the READ
CAPACITY command.

> Why would the CAM errors prevent GEOM from creating the MBR geom during
> attach but not when trying to mount /dev/da0?

My guess is that the fob is marginal and takes a while to stabilize
after being plugged in.  GEOM first tastes it when it is plugged in,
it is still funky, and GEOM fails to read the partition table.  Then
you try to mount /dev/da0, it is opened r/w, which causes GEOM to
retaste it once it is closed; by that time, it has settled and the
second tasting succeeds.

Dag-Erling Sm=F8rgrav -

Want to link to this message? Use this URL: <>