In message <Pine.OSF.4.33.0109061221420.32463-100000@grover.WPI.EDU>, Ian Coope
r writes:
>> >   * Is /dev/sd0d the correct device?
>> maybe, maybe not - what does 'disklabel sd0' say?
>
>  root:/usr/local/swiftmq/samples/sun_examples# disklabel sd0
>  disklabel: can't read master boot record: Input/output error
>
>> > I have had no problems mounting this on linux, using the 'vfat' filesystem
>> > type.  Thoughts and ideas would be appreciated.  Thanks.
>>
>> Ahhh, you probably want 'mount -t msdos' then. See 'man mount_msdos' for
>> details.
>
>OK.  It gives the same error:
>
>  root:~# mount -t msdos /dev/sd0d /mnt/camera
>  mount_msdos: /dev/sd0d on /mnt/camera: Input/output error
>

I wonder if there are underlying problems in the umass0 code, or maybe 
the SCSI/usb code.  In the past, I've mentioned problems with a USB 
floppy, but I had more error messages:

umass0: TEAC     TEAC FD-05PUB   , rev 1.00/0.00, addr 2
umass0: using UFI over CBI-I
scsibus0 at umass0: 2 targets, 1 luns per target
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 1 lun 0: <TEAC, FD-05PUB, 1026> SCSI0 0/direct removable

sd0(umass0:1:0):  Check Condition on CDB: 0x2a 00 00 00 00 04 00 00 04 00
    SENSE KEY:  Not Ready
     ASC/ASCQ:  ASC 0x04 ASCQ 0xff

sd0(umass0:1:0):  Check Condition on CDB: 0x1e 00 00 00 00 00
    SENSE KEY:  Aborted Command
     ASC/ASCQ:  Overlapped Commands Attempted


I can *usually* read, but never write.  (I should really file a PR on 
this, I suppose, but I'll wait until after the next snapshot of 
-current.)

		--Steve Bellovin, http://www.research.att.com/~smb