My device with Rockchip vid 071b pid 3203 is disconnecting again, just like it did back in the days of https://bugzilla.kernel.org/show_bug.cgi?id=11423 I'll attach a log which shows the DRIVE_CAPACITY command being issued. Then a MODE_SENSE command goes in and the device starts disconnecting, and then the scsi routines claim DRIVE_CAPACITY failed. Very similar to bug 11423 in fact. Now I can see that US_FL_NO_WP_DETECT is set in the quirks, but in this version of the kernel it doesn't seem to be blocking the MODE_SENSE page=0x3f for some reason.
Created attachment 57742 [details] dmesg with CONFIG_USB_DEBUG enabled
Friends I strongly suspect the problem is in scsi/sd.c, function sd_read_cache_type() which under certain circumstances will do a MODE_SENSE page=0x3f
The problem has been fixed by this commit: https://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git;a=commit;h=3dea642afd9187728d119fce5c82a7ed9faa9b6a which will appear in the upcoming 2.6.39 release. Alternatively, you could apply this patch: http://marc.info/?l=linux-scsi&m=130089710431684&w=2 which has not yet been merged.
Many thanks for quick reply. Yes the commit quoted above fixes it. It would be good if that (or similar) appeared in a 2.6.38.stable release.
Just for the record, I also tried the other patch mentioned, i.e. http://marc.info/?l=linux-scsi&m=130089710431684&w=2 and that worked fine too with my device.
Hi, I have been struggling with the same problem for the last 6 hours. I feel lucky to encounter this kernel patch. After failed attempts to apply this patch I updated my kernel from 2.6.38 to 2.6.39, because it is mentioned above that this patch will be in 2.6.39. Do I still need to patch? because my external hdd is still not mounted after the kernel upgrade. It has precious data in it and I am in panic. If I have to then can you please tell me how I am going to patch 2.6.39 kernel?
You don't have to patch anything, the change is indeed present in 2.6.39. You must be suffering from a different problem. To help track it down, you can collect a usbmon trace showing what happens when the drive is plugged in. See the instructions in the kernel source file Documentation/usb/usbmon.txt.
Actually I am now afraid to plug the hdd back in. Because it started to make occasional clicking sounds which might tell that the hard drive is about to die. Actually when I do lsusb the drive is listed but not when sudo fdisk -l. dmesg | tail suggests that hard drive resets itself continuously. I tried to plug into a windows environment and on the tray drivers was installed but system could not read file system. Other usb devices work normally on my ubuntu 11.04 gnome 3. The possibility of a hardware problem scares me. I have read ddrescue is very helpful but it requires the device to be recognized. How can I find out that my laptop's BIOS recognizes the Western Digital My Passport essential usb 3.0/2.0 drive? What else I can do to recover my data without further damage and eventual death of the hard drive? Your help is greatly appreciated.
This could be a power issue. Is the drive getting enough current? If there's no other choice, you can try opening up the device's case and removing the hard disk unit. The disk drive could then be hooked up to a desktop computer using a normal SATA connection.
I opened up the case as you said but the usb ınterface ıs not removable. there is a micro b connector. and I do not think I might be able to find an mıcro b to sata connector? what else can you suggest?
You can try plugging the drive into a different computer. But if that doesn't work, you're probably out of options. It looks like the only way to communicate with the drive is through the USB connector, and if that has failed then you can't communicate the drive at all.