Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 14 Feb 2008 11:28:44 +0100
From:      Ben Stuyts <ben@altesco.nl>
To:        freebsd-usb@freebsd.org
Subject:   LaCie hd SYNCHRONIZE CACHE errors
Message-ID:  <A8832964-7178-4803-B702-7931EBE7F65A@altesco.nl>

next in thread | raw e-mail | index | archive | help
Hello,

Now that these drives no longer immediately panic the system (see  
other thread), I see another problem. The drive is a mini LaCie 250 GB  
2.5". On connecting the drive I see:

Feb 13 20:44:25 mars root: Unknown USB device: vendor 0x059f product  
0x0c41 bus uhub3
Feb 13 20:44:25 mars kernel: umass1: <LaCie LaCie Hard Drive USB,  
class 0/0, rev 2.00/0.00, addr 3> on uhub3
Feb 13 20:44:26 mars kernel: da1 at umass-sim1 bus 1 target 0 lun 0
Feb 13 20:44:26 mars kernel: da1: <SAMSUNG HM250JI > Fixed Direct  
Access SCSI-2 device
Feb 13 20:44:26 mars kernel: da1: 40.000MB/s transfers
Feb 13 20:44:26 mars kernel: da1: 238475MB (488397168 512 byte  
sectors: 255H 63S/T 30401C)
Feb 13 20:44:26 mars kernel: GEOM_LABEL: Label for provider da1s1 is  
msdosfs/LACIE.

uname -a:
FreeBSD mars.altus-escon.com 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE  
#20: Wed Feb 13 20:22:18 CET 2008     root@mars.altus-escon.com:/usr/ 
obj/usr/src/sys/MARS  amd64

When accessing the drive I get lots of these errors:

Feb 13 22:27:30 mars kernel: (da1:umass-sim1:1:0:0): SYNCHRONIZE  
CACHE. CDB: 35 0 0 0 0 0 0 0 0 0
Feb 13 22:27:30 mars kernel: (da1:umass-sim1:1:0:0): CAM Status: SCSI  
Status Error
Feb 13 22:27:30 mars kernel: (da1:umass-sim1:1:0:0): SCSI Status:  
Check Condition
Feb 13 22:27:30 mars kernel: (da1:umass-sim1:1:0:0): ILLEGAL REQUEST  
asc:20,0
Feb 13 22:27:30 mars kernel: (da1:umass-sim1:1:0:0): Invalid command  
operation code
Feb 13 22:27:30 mars kernel: (da1:umass-sim1:1:0:0): Unretryable error

After each message it takes a moment for I/O to start again, so I/O  
performance is terrible. From reading sys/cam/README.quirks, I see  
there is a DA_Q_NO_SYNC_CACHE quirk that can be added, but  this  
should only be done on a device or system hang. Is this enough cause?  
Or is there something else I can try?

Thanks,
Ben




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A8832964-7178-4803-B702-7931EBE7F65A>