kernel-packages team mailing list archive

[jmp <jmp@xxxxxxxxxx>]

jkampe: I tried your workaround of adding usb-storage quirks 'uw' with
my Maxtor OneTouch 250GB, same kernel as yours (3.16.0-31-generic
#43~14.04.1-Ubuntu  - x86_64). So far,

IT WORKS.

I'll have to test it further: I'm still running a (lengthy as in hours
long) fsck caused by the previous test _without_ the quirks parameter
("filesystem with errors," etc.). But it does look good, I attached and
detached the disk several times without the dreaded "end_request:
critical target error, dev sdc, sector 0" that spelled trouble every
time.

(In this case, 
$ cat /etc/modprobe.d/maxtor-quirks.conf 
options usb-storage quirks=0d49:7010:uw
)


I confirm the difference in dmesg, the line

(...) Write cache: enabled, read cache: enabled, doesn't support DPO or
FUA

changes to

(...) Assuming drive cache: write through

-- As it should, I think, since this disk does not expose any
caches/cache control to the kernel. But what do I know?

Relevant messages:

[ 1301.964044] usb 1-2: new high-speed USB device number 5 using ehci-pci
[ 1302.096937] usb 1-2: New USB device found, idVendor=0d49, idProduct=7010
[ 1302.096940] usb 1-2: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 1302.096943] usb 1-2: Product: OneTouch
[ 1302.096945] usb 1-2: Manufacturer: Maxtor
[ 1302.096948] usb 1-2: SerialNumber: Y61JF0XE    
[ 1302.117520] usbcore: registered new interface driver usb-storage
[ 1302.119336] usbcore: registered new interface driver uas
[ 1302.120923] ums-onetouch 1-2:1.0: USB Mass Storage device detected
[ 1302.121003] ums-onetouch 1-2:1.0: Quirks match for vid 0d49 pid 7010: 800200
[ 1302.121070] input: Maxtor OneTouch as /devices/pci0000:00/0000:00:1a.7/usb1/1-2/input/input13
[ 1302.121215] scsi9 : usb-storage 1-2:1.0
[ 1302.121303] usbcore: registered new interface driver ums-onetouch
[ 1303.326245] scsi 9:0:0:0: Direct-Access     Maxtor   OneTouch         0200 PQ: 0 ANSI: 0 CCS
[ 1303.326528] sd 9:0:0:0: Attached scsi generic sg3 type 0
[ 1303.327979] sd 9:0:0:0: [sdc] 490232832 512-byte logical blocks: (250 GB/233 GiB)
[ 1303.327984] sd 9:0:0:0: [sdc] Assuming Write Enabled
[ 1303.327987] sd 9:0:0:0: [sdc] Assuming drive cache: write through
[ 1303.362025]  sdc: sdc1
[ 1303.363363] sd 9:0:0:0: [sdc] Attached SCSI disk


Thank you three times. This is some wizard level advice. :-) I never had heard about that "quirks" parameter... Let alone what might the value "uw" do.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1366538

Title:
  Synchronisation/close /dev/sdX: i/o error on target host

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged
Status in linux source package in Vivid:
  Triaged

Bug description:
  Ubuntu 14.04.1 x86-64
  wanting to unmout a pata drive (usb attached), I get this (title) "Warning from libparted" when gparted launches.
  Same issue with another pc x86-64
  Errors retries then ignore, shred /dev/sdi fails:

  shred: /dev/sdi : pass 1/2 (random)…
  shred: /dev/sdi : pass 1/2 (random)…231MiB/94GiB 0 %
  shred: /dev/sdi : failure of fdatasync: i/o error on target host

  I reached to shred the drive from a 12.04.4 i386 pc with no error.

  Sep  7 15:07:08 nux kernel: [261448.072475] usb 5-1: new high-speed USB device number 10 using xhci_hcd
  Sep  7 15:07:09 nux kernel: [261448.202999] usb 5-1: New USB device found, idVendor=04cf, idProduct=8818
  Sep  7 15:07:09 nux kernel: [261448.203008] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
  Sep  7 15:07:09 nux kernel: [261448.203013] usb 5-1: Product: USB Mass Storage Device
  Sep  7 15:07:09 nux kernel: [261448.203018] usb 5-1: Manufacturer: Myson Century, Inc.
  Sep  7 15:07:09 nux kernel: [261448.205463] usb-storage 5-1:1.0: USB Mass Storage device detected
  Sep  7 15:07:09 nux kernel: [261448.205673] scsi20 : usb-storage 5-1:1.0
  Sep  7 15:07:10 nux kernel: [261449.206849] scsi 20:0:0:0: Direct-Access     HTS72101 0G9AT00          MCZO PQ: 0 ANSI: 0 CCS
  Sep  7 15:07:10 nux kernel: [261449.207763] sd 20:0:0:0: Attached scsi generic sg7 type 0
  Sep  7 15:07:10 nux kernel: [261449.207901] sd 20:0:0:0: [sdi] 195371568 512-byte logical blocks: (100 GB/93.1 GiB)
  Sep  7 15:07:10 nux kernel: [261449.208068] sd 20:0:0:0: [sdi] Write Protect is off
  Sep  7 15:07:10 nux kernel: [261449.208074] sd 20:0:0:0: [sdi] Mode Sense: 00 14 00 00
  Sep  7 15:07:10 nux kernel: [261449.208280] sd 20:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
  Sep  7 15:07:10 nux kernel: [261449.555232]  sdi: unknown partition table
  Sep  7 15:07:10 nux kernel: [261449.555926] sd 20:0:0:0: [sdi] Attached SCSI disk
  Sep  7 15:07:43 nux kernel: [261482.219026] end_request: critical target error, dev sdi, sector 0
  Sep  7 15:07:52 nux kernel: [261492.015180] end_request: critical target error, dev sdi, sector 0
  Sep  7 15:07:55 nux kernel: [261494.261159] end_request: critical target error, dev sdi, sector 0
  Sep  7 15:16:23 nux kernel: [262003.027005] end_request: critical target error, dev sdi, sector 0
  Sep  7 15:16:35 nux kernel: [262014.215352] end_request: critical target error, dev sdi, sector 0
  Sep  7 15:16:35 nux kernel: [262014.859651] end_request: critical target error, dev sdi, sector 0

  [EDIT:
  Once shreded, no error on the i386, but still same error on the 2 x86-64]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366538/+subscriptions