Ubuntu
linux package

04e8:60a6 External USB3 disk problems: Sense Key : Recovered Error

Bug #704900 reported by UWP
60
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I bought a Samsung S2 Portable 3 disk with 1 TB diskspace. It's an USB3 disk, but right now I don't have a USB3 controller. Because it's USB2 compatible it should also work without usind USB3 hardware. The disk itself can be found from the system:

[88630.509045] usb 1-4: new high speed USB device using ehci_hcd and address 5
[88630.649996] scsi7 : usb-storage 1-4:1.0
[88635.424345] scsi 7:0:0:0: Direct-Access Samsung S2 Portable 3 2AM1 PQ: 0 ANSI: 0
[88635.424941] sd 7:0:0:0: Attached scsi generic sg2 type 0
[88635.427174] sd 7:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[88635.427912] sd 7:0:0:0: [sdb] Write Protect is off
[88635.427916] sd 7:0:0:0: [sdb] Mode Sense: 23 00 00 00
[88635.427919] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[88635.429429] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[88635.429434] sdb: sdb1 sdb2
[88635.464287] sd 7:0:0:0: [sdb] Assuming drive cache: write through
[88635.464289] sd 7:0:0:0: [sdb] Attached SCSI disk

This might look fine but after one or two seconds the log says this:

[88635.534292] sd 7:0:0:0: [sdb] Sense Key : Recovered Error [current] [descriptor]
[88635.534298] Descriptor sense data with sense descriptors (in hex):
[88635.534300] 72 01 04 1d 00 00 00 0a 09 0c 00 00 00 00 00 07
[88635.534311] 00 00
[88635.534315] sd 7:0:0:0: [sdb] ASC=0x4 ASCQ=0x1d
[88640.878326] sd 7:0:0:0: [sdb] Sense Key : Recovered Error [current] [descriptor]

This goes on and on until I mount some partitions with it. Yes, fdisk and other stuff is working.
But: when I remove all filesystems and partitions the disk itself seems to "hop on hop off":

Jan 18 11:53:03 borgcube kernel: [4146611.121046] usb 1-3: new high speed USB de
vice using ehci_hcd and address 17
Jan 18 11:53:03 borgcube kernel: [4146611.258042] scsi15 : usb-storage 1-3:1.0
Jan 18 11:53:07 borgcube kernel: [4146614.864273] scsi 15:0:0:0: Direct-Access
   Samsung S2 Portable 3 2AM1 PQ: 0 ANSI: 0
Jan 18 11:53:07 borgcube kernel: [4146614.864839] sd 15:0:0:0: Attached scsi gen
eric sg2 type 0
Jan 18 11:53:07 borgcube kernel: [4146614.869054] sd 15:0:0:0: [sdb] 1953525168
512-byte logical blocks: (1.00 TB/931 GiB)
Jan 18 11:53:07 borgcube kernel: [4146614.869870] sd 15:0:0:0: [sdb] Write Prote
ct is off
Jan 18 11:53:07 borgcube kernel: [4146614.871374] sdb: sdb1
Jan 18 11:53:07 borgcube kernel: [4146614.904607] sd 15:0:0:0: [sdb] Attached SCSI disk
Jan 18 11:53:07 borgcube kernel: [4146615.219224] sd 15:0:0:0: [sdb] Sense Key : Recovered Error [current] [descriptor]
Jan 18 11:53:07 borgcube kernel: [4146615.219230] Descriptor sense data with sense descriptors (in hex):
Jan 18 11:53:07 borgcube kernel: [4146615.219233] 72 01 04 1d 00 00 00 0a 09 0c 00 00 00 00 00 07
Jan 18 11:53:07 borgcube kernel: [4146615.219248] 00 00
Jan 18 11:53:07 borgcube kernel: [4146615.219251] sd 15:0:0:0: [sdb] ASC=0x4 ASCQ=0x1d
Jan 18 11:53:07 borgcube usbmount[17389]: /dev/sdb does not contain a filesystem or disklabel
Jan 18 11:53:07 borgcube usbmount[17416]: /dev/sdb1 does not contain a filesystem or disklabel
Jan 18 11:53:10 borgcube kernel: [4146618.110387] usb 1-3: USB disconnect, address 17
Jan 18 11:53:10 borgcube kernel: [4146618.365031] usb 1-3: new high speed USB device using ehci_hcd and address 18
Jan 18 11:53:10 borgcube kernel: [4146618.502330] scsi16 : usb-storage 1-3:1.0
Jan 18 11:53:11 borgcube kernel: [4146619.500708] scsi 16:0:0:0: Direct-Access Samsung S2 Portable 3 2AM1 PQ: 0 ANSI: 0
Jan 18 11:53:11 borgcube kernel: [4146619.501482] sd 16:0:0:0: Attached scsi generic sg2 type 0
Jan 18 11:53:11 borgcube kernel: [4146619.508149] sd 16:0:0:0: [sdc] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
Jan 18 11:53:11 borgcube kernel: [4146619.509024] sd 16:0:0:0: [sdc] Write Protect is off
Jan 18 11:53:11 borgcube kernel: [4146619.510690] sdc: sdc1
Jan 18 11:53:11 borgcube kernel: [4146619.513177] sd 16:0:0:0: [sdc] Attached SCSI disk
Jan 18 11:53:11 borgcube kernel: [4146619.550430] sd 16:0:0:0: [sdc] Sense Key : Recovered Error [current] [descriptor]
Jan 18 11:53:11 borgcube kernel: [4146619.550437] Descriptor sense data with sense descriptors (in hex):
Jan 18 11:53:11 borgcube kernel: [4146619.550439] 72 01 04 1d 00 00 00 0a 09 0c 00 00 00 00 00 07
Jan 18 11:53:11 borgcube kernel: [4146619.550450] 00 00
Jan 18 11:53:11 borgcube kernel: [4146619.550453] sd 16:0:0:0: [sdc] ASC=0x4 ASCQ=0x1d
Jan 18 11:53:11 borgcube usbmount[17499]: /dev/sdc does not contain a filesystem or disklabel
Jan 18 11:53:12 borgcube usbmount[17527]: /dev/sdc1 does not contain a filesystem or disklabel
Jan 18 11:53:13 borgcube kernel: [4146621.134641] usb 1-3: USB disconnect, address 18
Jan 18 11:53:13 borgcube kernel: [4146621.388038] usb 1-3: new high speed USB device using ehci_hcd and address 19
Jan 18 11:53:13 borgcube kernel: [4146621.525989] scsi17 : usb-storage 1-3:1.0
Jan 18 11:53:14 borgcube kernel: [4146622.525709] scsi 17:0:0:0: Direct-Access Samsung S2 Portable 3 2AM1 PQ: 0 ANSI: 0
Jan 18 11:53:14 borgcube kernel: [4146622.526276] sd 17:0:0:0: Attached scsi generic sg2 type 0
[...]

This counting of scsi15,16,17 is while I am not unplugging or plugging in the cable, it's still plugged in the whole time. When I was fast enough to bring a FS onto the disk and to bring it up I could use the disk but I also had one time data-loss. This is something I cannot recreate. But the scsi-sense-problems are even coming sometimes when partitions of the disk are mounted. BTW, smartctl cannot find the disk:

/dev/sdb: Unknown USB bridge [0x04e8:0x60a6 (0x100)]

It might be that the disk simply is a bit new but hey, it's just a disk...

Can anyone help with such topics? Maybe it's something with the udev-system, where I only have to disable some automatisms to get a more reliable disk. I don't think the disk is damaged, it runs fine under XP systems without any errors.

Here comes more data about my system:

Linux borgcube 2.6.35-24-generic-pae #42-Ubuntu SMP Thu Dec 2 03:21:31 UTC 2010 i686 GNU/Linux
Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8
Description: Ubuntu 10.10
Release: 10.10

Extra informations come in the attached tar file.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-24-generic-pae 2.6.35-24.42
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8
Uname: Linux 2.6.35-24-generic-pae i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC663 Analog [ALC663 Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: uwp 3272 F.... jackd
 /dev/snd/pcmC0D0c: uwp 3272 F...m jackd
 /dev/snd/pcmC0D0p: uwp 3272 F...m jackd
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc220000 irq 46'
   Mixer name : 'Realtek ALC663'
   Components : 'HDA:10ec0663,17341157,00100001'
   Controls : 25
   Simple ctrls : 15
Date: Wed Jan 19 14:24:05 2011
HibernationDevice: RESUME=UUID=acb1c3db-1250-4d0b-8ce0-a72914b84e8e
MachineType: FUJITSU SIEMENS ESPRIMO E7935
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-24-generic-pae root=UUID=0b5298b8-476c-444f-8d9d-7667bbd855c7 ro quiet splash
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 PATH=(custom, user)
 LANG=de_DE.utf8
 SHELL=/bin/tcsh
RelatedPackageVersions: linux-firmware 1.38
RfKill:

SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 01/15/2009
dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
dmi.bios.version: 6.00 R1.11.2828.A1
dmi.board.name: D2828-A1
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: S26361-D2828-A1
dmi.chassis.type: 3
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.11.2828.A1:bd01/15/2009:svnFUJITSUSIEMENS:pnESPRIMOE7935:pvr:rvnFUJITSUSIEMENS:rnD2828-A1:rvrS26361-D2828-A1:cvnFUJITSUSIEMENS:ct3:cvr:
dmi.product.name: ESPRIMO E7935
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
UWP (uwp) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi UWP,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
In , Ralf (ralf-redhat-bugs) wrote :
Download full text (4.4 KiB)

Description of problem:

When powering on my external USB-HD I am observing this in /var/log/messages:

Feb 14 09:11:52 beck kernel: [ 412.689038] usb 1-1: new high speed USB device using ehci_hcd and address 2
Feb 14 09:11:52 beck kernel: [ 412.832306] usb 1-1: New USB device found, idVendor=174c, idProduct=55aa
Feb 14 09:11:52 beck kernel: [ 412.832311] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Feb 14 09:11:52 beck kernel: [ 412.832314] usb 1-1: Product: AS2105
Feb 14 09:11:52 beck kernel: [ 412.832317] usb 1-1: Manufacturer: ASMedia
Feb 14 09:11:52 beck kernel: [ 412.832319] usb 1-1: SerialNumber: 0123456789ABCDEF
Feb 14 09:11:52 beck kernel: [ 412.832883] scsi7 : usb-storage 1-1:1.0
Feb 14 09:12:02 beck kernel: [ 423.113020] scsi 7:0:0:0: Direct-Access SAMSUNG HD154UI 1AG0 PQ: 0 ANSI: 0
Feb 14 09:12:02 beck kernel: [ 423.113617] sd 7:0:0:0: Attached scsi generic sg8 type 0
Feb 14 09:12:02 beck kernel: [ 423.114377] sd 7:0:0:0: [sdg] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)
Feb 14 09:12:02 beck kernel: [ 423.116886] sd 7:0:0:0: [sdg] Write Protect is off
Feb 14 09:12:02 beck kernel: [ 423.116894] sd 7:0:0:0: [sdg] Assuming drive cache: write through
Feb 14 09:12:02 beck kernel: [ 423.118808] sd 7:0:0:0: [sdg] Assuming drive cache: write through
Feb 14 09:12:02 beck kernel: [ 423.118815] sdg: sdg1
Feb 14 09:12:02 beck kernel: [ 423.128136] sd 7:0:0:0: [sdg] Assuming drive cache: write through
Feb 14 09:12:02 beck kernel: [ 423.128140] sd 7:0:0:0: [sdg] Attached SCSI disk
Feb 14 09:12:03 beck kernel: [ 423.332057] sd 7:0:0:0: [sdg] Sense Key : Recovered Error [current] [descriptor]
Feb 14 09:12:03 beck kernel: [ 423.332063] Descriptor sense data with sense descriptors (in hex):
Feb 14 09:12:03 beck kernel: [ 423.332065] 72 01 04 1d 00 00 00 0a 09 0c 00 00 00 00 00 07
Feb 14 09:12:03 beck kernel: [ 423.332075] 00 00
Feb 14 09:12:03 beck kernel: [ 423.332078] sd 7:0:0:0: [sdg] ASC=0x4 ASCQ=0x1d
Feb 14 09:12:03 beck kernel: [ 423.350809] sd 7:0:0:0: [sdg] Sense Key : Recovered Error [current] [descriptor]
Feb 14 09:12:03 beck kernel: [ 423.350816] Descriptor sense data with sense descriptors (in hex):
Feb 14 09:12:03 beck kernel: [ 423.350818] 72 01 04 1d 00 00 00 0e 09 0c 00 00 00 00 ae 87
Feb 14 09:12:03 beck kernel: [ 423.350826] 00 7a 00 a8 40 50
Feb 14 09:12:03 beck kernel: [ 423.350830] sd 7:0:0:0: [sdg] ASC=0x4 ASCQ=0x1d
Feb 14 09:12:03 beck kernel: [ 423.354685] sd 7:0:0:0: [sdg] Sense Key : Recovered Error [current] [descriptor]
Feb 14 09:12:03 beck kernel: [ 423.354689] Descriptor sense data with sense descriptors (in hex):
Feb 14 09:12:03 beck kernel: [ 423.354691] 72 01 04 1d 00 00 00 0e 09 0c 00 00 00 00 00 07
Feb 14 09:12:03 beck kernel: [ 423.354699] 00 08 00 00 40 50
Feb 14 09:12:03 beck kernel: [ 423.354703] sd 7:0:0:0: [sdg] ASC=0x4 ASCQ=0x1d
Feb 14 09:12:03 beck kernel: [ 423.696909] sd 7:0:0:0: [sdg] Sense Key : Recovered Error [current] [descriptor]
Feb 14 09:12:03 beck kernel: [ 423.696913] Descriptor sense data with sense descriptors (in hex):
Feb 14 09:12:03 beck kernel: [ 423.69691...

Read more...

Revision history for this message
In , Ralf (ralf-redhat-bugs) wrote :

FWIW: This issue also is present with kernel-2.6.38-0.rc4.git0.1.fc15.x86_64

Revision history for this message
In , Christoph (christoph-redhat-bugs) wrote :

I'm seeing the same problem here:

sd 10:0:0:0: [sdb] Sense Key : Recovered Error [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 01 04 1d 00 00 00 0e 09 0c 00 00 00 00 5b 00
00 00 00 00 00 50
sd 10:0:0:0: [sdb] ASC=0x4 ASCQ=0x1d

Kernel:
2.6.34.8-67.fc13.x86_64

- This is a USB-3 enclosure attached to a USB-2 port.
(applies here too)

additionally I see the following lines in /var/log/messages
quiet_error: 32 callbacks suppressed
Buffer I/O error on device dm-3, logical block 0
Buffer I/O error on device dm-3, logical block 1
Buffer I/O error on device dm-3, logical block 2
Buffer I/O error on device dm-3, logical block 3
Buffer I/O error on device dm-3, logical block 4
Buffer I/O error on device dm-3, logical block 5
Buffer I/O error on device dm-3, logical block 6
Buffer I/O error on device dm-3, logical block 7
Buffer I/O error on device dm-3, logical block 8
Buffer I/O error on device dm-3, logical block 9

Could this also be a HW problem?

Revision history for this message
In , Christoph (christoph-redhat-bugs) wrote :

When unmounting the device (using the grafical interface: right click on icon...)

Error detaching: helper exited with exit code 1: Detaching device /dev/sdd
USB device: /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2)
SYNCHRONIZE CACHE: FAILED: No such file or directory
(Continuing despite SYNCHRONIZE CACHE failure.)
STOP UNIT: FAILED: No such file or directory

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Yann (lostec) wrote :

I experience the same problem (with up to date 10.04.1 running 2.6.32-31-generic-pae) with a brand new USB key (Super Talent Express Ram Cache 32GB, USB3 used in an USB2 port).

I noticed problems at umount (error messages concerning cache sync and device stop) so I checked dmesg after a automount and:

****

[ 843.688065] usb 1-3: new high speed USB device using ehci_hcd and address 4
[ 843.830750] usb 1-3: configuration #1 chosen from 1 choice
[ 843.831639] scsi3 : SCSI emulation for USB Mass Storage devices
[ 843.832036] usb-storage: device found at 4
[ 843.832041] usb-storage: waiting for device to settle before scanning
[ 848.832311] usb-storage: device scan complete
[ 850.893642] scsi 3:0:0:0: Direct-Access Express RAM Cache 1102 PQ: 0 ANSI: 0
[ 850.894860] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 850.896370] sd 3:0:0:0: [sdb] 57343999 512-byte logical blocks: (29.3 GB/27.3 GiB)
[ 850.897902] sd 3:0:0:0: [sdb] Write Protect is off
[ 850.897910] sd 3:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 850.897916] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 850.902414] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 850.902425] sdb: sdb1
[ 850.909458] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 850.909468] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 852.772700] sd 3:0:0:0: [sdb] Sense Key : Recovered Error [current] [descriptor]
[ 852.772713] Descriptor sense data with sense descriptors (in hex):
[ 852.772718] 72 01 04 1d 00 00 00 0a 09 0c 00 00 00 00 00 08
[ 852.772741] 00 00
[ 852.772748] sd 3:0:0:0: [sdb] ASC=0x4 ASCQ=0x1d

****

ASC 0x4 seems to be a hardware error reported by attached device, recovered because sense key 4 (offset 2 in descriptor)... could not find any explication for ASCQ 0x1d in charts availlable online and I'm not a SCSI emulation expert ;o)

So do not assume expired. Let me know asap if some more experiment is needed on my side...

Also, the device seems to be operating nicely (cache WT setup at plug may help for umount problem!) despite of these reported problems that do show up in other distros as well (google on it, you'll find it on Fedora and others).

Regards

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
TGL (tom-gl) wrote :
Download full text (4.4 KiB)

Similar issue here with an USB-3 disk on the USB-2 port of my EeePC 1000HE, with Jaunty and a 2.6.38-8-generic kernel (backport from kernel PPA).

Dmesg when I plug the disk
=================
[ 4224.716182] usb 1-4: new high speed USB device using ehci_hcd and address 5
[ 4227.425643] usbcore: registered new interface driver uas
[ 4227.475955] Initializing USB Mass Storage driver...
[ 4227.477114] scsi2 : usb-storage 1-4:1.0
[ 4227.477952] usbcore: registered new interface driver usb-storage
[ 4227.477961] USB Mass Storage support registered.
[ 4228.487008] scsi 2:0:0:0: Direct-Access StoreJet Transcend 2AC1 PQ: 0 ANSI: 2 CCS
[ 4228.490640] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 4228.494719] sd 2:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 4228.495572] sd 2:0:0:0: [sdb] Write Protect is off
[ 4228.495594] sd 2:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 4228.496834] sd 2:0:0:0: [sdb] No Caching mode page present
[ 4228.496857] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 4228.503295] sd 2:0:0:0: [sdb] No Caching mode page present
[ 4228.503310] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 4228.526348] sdb: sdb1
[ 4228.529783] sd 2:0:0:0: [sdb] No Caching mode page present
[ 4228.529798] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 4228.529811] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 4228.644685] sd 2:0:0:0: [sdb] Sense Key : Recovered Error [current] [descriptor]
[ 4228.644706] Descriptor sense data with sense descriptors (in hex):
[ 4228.644715] 72 01 04 1d 00 00 00 0a 09 0c 00 00 00 00 00 07
[ 4228.644749] 00 00
[ 4228.644760] sd 2:0:0:0: [sdb] ASC=0x4 ASCQ=0x1d

Excerpt from "lsusb -v"
==============
Bus 001 Device 005: ID 174c:5106 ASMedia Technology Inc.
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x174c ASMedia Technology Inc.
  idProduct 0x5106
  bcdDevice 0.02
  iManufacturer 2 StoreJet Transcend
  iProduct 3 StoreJet Transcend
  iSerial 1 S1WFJDZB109753
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
      Self Powered
    MaxPower 0mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk (Zip)
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
      ...

Read more...

Revision history for this message
In , Christoph (christoph-redhat-bugs) wrote :

2.6.35.13-92.fc14.x86_64
Problem still persists, any news?

[436368.018260] ata6: exception Emask 0x50 SAct 0x0 SErr 0x4090800 action 0xe frozen
[436368.018269] ata6: irq_stat 0x00400040, connection status changed
[436368.018280] ata6: SError: { HostInt PHYRdyChg 10B8B DevExch }
[436368.018297] ata6: hard resetting link
[436368.744809] ata6: SATA link down (SStatus 0 SControl 300)
[436373.735368] ata6: hard resetting link
[436374.039828] ata6: SATA link down (SStatus 0 SControl 300)
[436374.039844] ata6: limiting SATA link speed to 1.5 Gbps
[436379.030554] ata6: hard resetting link
[436379.335008] ata6: SATA link down (SStatus 0 SControl 310)
[436379.335022] ata6.00: disabled
[436379.335046] ata6: EH complete
[436379.335055] ata6.00: detaching (SCSI 5:0:0:0)
[436379.339627] sd 5:0:0:0: [sdb] Synchronizing SCSI cache
[436379.340123] sd 5:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[436379.340129] sd 5:0:0:0: [sdb] Stopping disk
[436379.340140] sd 5:0:0:0: [sdb] START_STOP FAILED
[436379.340142] sd 5:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK

Revision history for this message
In , Chuck (chuck-redhat-bugs) wrote :

(In reply to comment #3)
> When unmounting the device (using the grafical interface: right click on
> icon...)
>
> Error detaching: helper exited with exit code 1: Detaching device /dev/sdd
> USB device: /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2)
> SYNCHRONIZE CACHE: FAILED: No such file or directory
> (Continuing despite SYNCHRONIZE CACHE failure.)
> STOP UNIT: FAILED: No such file or directory

That is a completely different error, and it's likely that the drive simply doesn't support those commands.

Revision history for this message
e-frog (e-frog) wrote :

Same problem here with oneirec. This upstream patch fixes this for me:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e16da02fcdf1c5e824432f88abf42623dafdf191;hp=73ddc2474bcc5234fa0a4e406e015ed16d16b6c8

Revision history for this message
e-frog (e-frog) wrote :

The above mentioned patch is included in Kernel 3.0.9 stable release and is now available for oneiric https://bugs.launchpad.net/ubuntu/+source/linux/+bug/890952

Revision history for this message
In , Andrew (andrew-redhat-bugs) wrote :

From what I've read,

ASC=0x4 ASCQ=0x1d
Sense Key : Recovered Error [current] [descriptor]

is a benign error and can be ignored.

See "SMART responses for SATA disks on SAS get interpreted as errors"
https://bugzilla.kernel.org/show_bug.cgi?id=13594

"This is a message the kernel prints out on all recovered error returns
(except those marked REQ_QUIET). It's purely informational and doesn't
affect return processing of the command at all, so the kernel is
actually treating this as a successful completion not an error."

There is also a patch provided there to quiet the message if you find it really annoying.

Revision history for this message
penalvch (penalvch) wrote :

UWP, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

summary: - External USB3 disk problems: Sense Key : Recovered Error
+ 04e8:60a6 External USB3 disk problems: Sense Key : Recovered Error
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

This message is a notice that Fedora 14 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 14. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 14 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Bug Watch Updater (bug-watch-updater)
Changed in fedora:
importance: Unknown → Undecided
status: Unknown → Won't Fix
Revision history for this message
penalvch (penalvch) wrote :

OR using EOL release, and no response for years.

no longer affects: linux (Ubuntu)
affects: fedora → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Won't Fix → New
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.