"Darren Pilgrim" <[EMAIL PROTECTED]> 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. DES -- Dag-Erling Sm�rgrav - [EMAIL PROTECTED] _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
