USB and 6.1-RELEASE

[backyard1454-bsd at yahoo.com]

> >>
> >> Now I'm on to another issue.
> >>
> >> When I plug in the thumb drive, which is a 512MB
> USB 2.0 Mobile 
> >> Swingdrive, containing an MS-DOS filesystem, I
> get the following:
> >>    umass0: vendor 0x0930 USB Flash Memory, rev
> 2.00/1.00, addr 2
> >>    da0 at umass-sim0 bus 0 target 0 lun 0
> >>    da0: < USB Flash Memory 1.04> Removable Direct
> Access SCSI-0 device
> >>    da0: 40.000MB/s transfers
> >>    da0: 489MB (1001472 512 byte sectors: 64H
> 32S/T 489C)
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0
> >>    umass0: Phase Error, residue = 0
> >>    (da0:umass-sim0:0:0:0): Synchronize cache
> failed, status == 0x4, 
> >> scsi status == 0x0

> >
> > Looks like those messages are a quirk of some USB
> drives: 
> >
>
http://lists.freebsd.org/pipermail/freebsd-bugs/2006-April/018182.html
> 
> > According to that PR/patch, that particular drive
> still works despite 
> > the messages, so hopefully yours will too.
> 
> Yup.  It seems to be working.  Thanks for all the
> help.
> _______________________________________________
> 
=== message truncated ===

Yeah I've noticed similar errors with a USB floppy
device I have as well with Rel_6.1. I'm not entirely
sure that the errors occurred with 6.0, and am certain
I never saw those errors with Rel_5.4. Are there new
features added into the USB system that are still
being worked out? These really concerned me becuase I
was trying to build a Grub boot disk to ease boot
loader installations with my server builds at the
time, and I didn't need the trivial matter of grub
installation failing on top of learning how to build a
(G)VINUM (looks like a new man page to read from other
threads I've been seeing...) RAID.

On a related issue is fdformat supposed to work with
USB floppy devices? I thought it worked in the past
(Rel_5.4) for me but with Rel_6.1 it doesn't. It bails
with device not a floppy drive error. Can I tweak
devd.conf (devfs.conf maybe; I can ls the correct one
later, sorry about my sloppy documentation. Both might
be valid and need configuration I'm just thinking out
loud) to trick the system into thinking the USB floppy
device is a REAL floppy drive? 

On my servers this isn't an issue but on my floppyless
laptop this is a major issue. I know I can build a
filesystem at a RAW level on the disk, but I have no
way of validating the media with a format. I've tried
"low leveling" with a dd command but this takes
forever to do (even with bs=512 I think I even tried
bs=1024 but prolly not because I believe this is twice
the standard block size and no use loading the buffers
with extra I/O requests and pending interrupts
right???), and am certain this isn't the right route
to be taking, just a hackish verification all the
blocks are writable. Of course I guess thats how
formatting came into being in the first place...


-brian