Determining disk device and kicking GEOM when doing automatic
mounting of umass devices
Dag-Erling Smørgrav
des at des.no
Fri Jun 10 07:16:06 GMT 2005
"Darren Pilgrim" <dmp at bitfreak.org> writes:
> Attached as named above. The logs show the da0 DISK class 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.
Here's what I get in a similar scenario:
Jun 10 09:14:02 xps des: START
Jun 10 09:14:06 xps kernel: umass0: vendor 0x0d7d USB DISK, rev 1.10/1.00, addr 5
Jun 10 09:14:06 xps kernel: umass0:0:0:-1: Attached to scbus0
Jun 10 09:14:07 xps kernel: pass0 at umass-sim0 bus 0 target 0 lun 0
Jun 10 09:14:07 xps kernel: pass0: < USB DISK 1.20> Removable Direct Access SCSI-0 device
Jun 10 09:14:07 xps kernel: pass0: Serial Number
Jun 10 09:14:07 xps kernel: pass0: 1.000MB/s transfers
Jun 10 09:14:07 xps kernel: GEOM: new disk da0
Jun 10 09:14:07 xps kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Jun 10 09:14:07 xps kernel: da0: < USB DISK 1.20> Removable Direct Access SCSI-0 device
Jun 10 09:14:07 xps kernel: da0: Serial Number
Jun 10 09:14:07 xps kernel: da0: 1.000MB/s transfers
Jun 10 09:14:07 xps kernel: da0: 31MB (64000 512 byte sectors: 64H 32S/T 31C)
Jun 10 09:14:13 xps des: STOP
except my fob is unpartitioned (like a floppy), which is why I only
get da0.
DES
--
Dag-Erling Smørgrav - des at des.no
More information about the freebsd-hackers
mailing list