Thanks for your analysis. On Fri, 27 Jun 2014 11:15:41 +0100 "Bryn M. Reeves" <[email protected]> wrote:
> On Thu, Jun 26, 2014 at 08:55:19PM +0200, Michael Büsch wrote: > > Jun 26 20:47:14 wiggum kernel: [156019.870310] sd 22:0:0:0: [sdb] 976773168 > > 512-byte logical blocks: (500 GB/465 GiB) > > Jun 26 20:47:14 wiggum kernel: [156019.870653] sd 22:0:0:0: [sdb] Write > > Protect is off > > Jun 26 20:47:14 wiggum kernel: [156019.870659] sd 22:0:0:0: [sdb] Mode > > Sense: 47 00 10 08 > > The disk says it supports FUA: Is this the disk reporting that, or the USB->SATA controller? The disk works perfectly fine, if connected via on board SATA controller. > Looks like a WRITE(10) with the FUA bit set: > > > Jun 26 20:47:27 wiggum kernel: [156032.938239] sd 22:0:0:0: [sdb] CDB: > > Jun 26 20:47:27 wiggum kernel: [156032.938241] Write(10): 2a 08 1d 04 00 3f > > 00 00 08 00 > > > > Does somebody have a hint to debug this? > > I'd guess the device lies about supporting FUA. There seems to be > another report on the Debian lists of the same problem with a similar > JMicron enclosure: Is there a workaround for this problem, or even a quirk-patch that I could test? -- Michael.
signature.asc
Description: PGP signature
