mounting usb on fbsd6beta4...

[Adriaan de Groot]

[Some notes from a user perspective, on 5.4]

On Saturday 17 September 2005 01:39, Jeff D. Hamann wrote:
> Sep 17 16:24:46 bobby kernel: umass0: vendor 0x090a product 0x1001, rev
> 1.10/1.00, addr 2
> Sep 17 16:24:46 bobby kernel: da0 at umass-sim0 bus 0 target 0 lun 0
> Sep 17 16:24:46 bobby kernel: da0: <STORIX AXIS 1.00> Removable Direct
> Access SCSI-0 device
> Sep 17 16:24:46 bobby kernel: da0: 1.000MB/s transfers
> Sep 17 16:24:46 bobby kernel: da0: 250MB (512000 512 byte sectors: 64H
> 32S/T 250C)

This is largely to be expected -- there's a umass device being found, it's 
being mapped to a SCSI disk device, it has a lousy transfer rate because you 
plugged it into a USB1 port, and it's 250MB (a weird size, maybe). I get very 
similar output with either my USB1 key (64M) or my removeable HDD (12G 
leftover piece of junk in a generic USB HDD enclosure).


> Sep 17 16:24:46 bobby kernel: da1 at umass-sim0 bus 0 target 0 lun 1

That's odd. I don't particularly see why one device would show up as two SCSI 
disks (though it's not impossible).

> Sep 17 16:24:46 bobby kernel: (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, scsi status == 0x0

Typicaly missing quirk. There was a quirks table early on in 5.X's life which 
I believe has been removed by now. The quirks documented weird behavior that 
specific USB devices have. In fact, I have a 128M USB stick that -- once I 
had put in the right quirks -- worked fairly well, but now crashes the system 
hard on removal.

So it's not _just_ you, there's more USB devices out there that give trouble 
-- at least on 5-STABLE still. Whether any of my rambling applies to 
6-CURRENT, I don't know.

-- 
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot