Launchpad has imported 8 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=677239.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-02-14T08:21:37+00:00 Ralf wrote: 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.696915] 72 01 04 1d 00 00 00 0e 09 0c 00 00 00 00 00 0f Feb 14 09:12:03 beck kernel: [ 423.696923] 00 08 00 00 40 50 Feb 14 09:12:03 beck kernel: [ 423.696927] sd 7:0:0:0: [sdg] ASC=0x4 ASCQ=0x1d Feb 14 09:12:03 beck kernel: [ 423.702284] sd 7:0:0:0: [sdg] Sense Key : Recovered Error [current] [descriptor] Feb 14 09:12:03 beck kernel: [ 423.702288] Descriptor sense data with sense descriptors (in hex): Feb 14 09:12:03 beck kernel: [ 423.702290] 72 01 04 1d 00 00 00 0e 09 0c 00 00 00 00 ae 00 Feb 14 09:12:03 beck kernel: [ 423.702298] 00 4f 00 c2 00 50 Feb 14 09:12:03 beck kernel: [ 423.702302] sd 7:0:0:0: [sdg] ASC=0x4 ASCQ=0x1d Feb 14 09:12:04 beck kernel: [ 424.775236] EXT4-fs (sdg1): mounted filesystem with ordered data mode. Opts: (null) Version-Release number of selected component (if applicable): kernel-2.6.35.11-83.fc14.x86_64 How reproducible: Always Steps to Reproduce: 1. boot with external HD powered down. 2. login 3. power up external HD, watch /var/log/messages Actual results: c.f. above Additional info: - This is a USB-3 enclosure attached to a USB-2 port. - The drive appears (Brand new enclosed, no longer term experience, yet) to be working after having issued these warnings, except upon shutdown, where it occasionally seems to hangs. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/704900/comments/3 ------------------------------------------------------------------------ On 2011-02-14T17:37:59+00:00 Ralf wrote: FWIW: This issue also is present with kernel-2.6.38-0.rc4.git0.1.fc15.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/704900/comments/4 ------------------------------------------------------------------------ On 2011-02-15T21:59:27+00:00 Christoph 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? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/704900/comments/5 ------------------------------------------------------------------------ On 2011-02-15T22:07:51+00:00 Christoph 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/704900/comments/6 ------------------------------------------------------------------------ On 2011-06-21T13:27:36+00:00 Christoph 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/704900/comments/10 ------------------------------------------------------------------------ On 2011-08-29T20:57:15+00:00 Chuck 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/704900/comments/11 ------------------------------------------------------------------------ On 2012-02-09T19:22:22+00:00 Andrew 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/704900/comments/14 ------------------------------------------------------------------------ On 2012-08-16T13:45:18+00:00 Fedora 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/704900/comments/16 ** Changed in: fedora Status: Unknown => Won't Fix ** Changed in: fedora Importance: Unknown => Undecided ** Bug watch added: Linux Kernel Bug Tracker #13594 https://bugzilla.kernel.org/show_bug.cgi?id=13594 -- 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/704900 Title: 04e8:60a6 External USB3 disk problems: Sense Key : Recovered Error Status in linux package in Ubuntu: Incomplete Status in Fedora: Won't Fix 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/704900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
