Error sending ATA command IDENTIFY DEVICE

[Thaddaeus Tintenfisch]

I'm not able to mount my external HDD using Xubuntu 13.04 (udisks2), not even while booting into a live medium. However, Windows 7 and Ubuntu 12.04.2 (udisks) are able to mount the device without problem.

Syslog is showing following entries:
Mar 29 19:19:41 local kernel: [ 46.012101] usb 2-2: new high-speed USB device number 5 using ehci-pci
Mar 29 19:19:41 local kernel: [ 46.145401] usb 2-2: New USB device found, idVendor=14cd, idProduct=6116
Mar 29 19:19:41 local kernel: [ 46.145409] usb 2-2: New USB device strings: Mfr=1, Product=3, SerialNumber=2
Mar 29 19:19:41 local kernel: [ 46.145412] usb 2-2: Product: USB 2.0 SATA BRIDGE
Mar 29 19:19:41 local kernel: [ 46.145416] usb 2-2: Manufacturer: Super Top
Mar 29 19:19:41 local kernel: [ 46.145419] usb 2-2: SerialNumber: M6116018VE15
Mar 29 19:19:41 local kernel: [ 46.153488] Initializing USB Mass Storage driver...
Mar 29 19:19:41 local kernel: [ 46.153614] usbcore: registered new interface driver usb-storage
Mar 29 19:19:41 local kernel: [ 46.153617] USB Mass Storage support registered.
Mar 29 19:19:41 local kernel: [ 46.157283] scsi6 : usb-storage 2-2:1.0
Mar 29 19:19:41 local kernel: [ 46.157457] usbcore: registered new interface driver ums-cypress
Mar 29 19:19:42 local kernel: [ 47.156812] scsi 6:0:0:0: Direct-Access WDC WD32 00BEVT-22ZCT0 PQ: 0 ANSI: 0
Mar 29 19:19:42 local kernel: [ 47.157700] sd 6:0:0:0: Attached scsi generic sg2 type 0
Mar 29 19:19:42 local kernel: [ 47.159898] sd 6:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
Mar 29 19:19:42 local kernel: [ 47.160903] sd 6:0:0:0: [sdb] Write Protect is off
Mar 29 19:19:42 local kernel: [ 47.160909] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
Mar 29 19:19:42 local kernel: [ 47.161741] sd 6:0:0:0: [sdb] No Caching mode page present
Mar 29 19:19:42 local kernel: [ 47.161748] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:19:42 local kernel: [ 47.165016] sd 6:0:0:0: [sdb] No Caching mode page present
Mar 29 19:19:42 local kernel: [ 47.165023] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:19:42 local kernel: [ 47.206914] sdb: sdb1 sdb2
Mar 29 19:19:42 local kernel: [ 47.209109] sd 6:0:0:0: [sdb] No Caching mode page present
Mar 29 19:19:42 local kernel: [ 47.209115] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Mar 29 19:19:42 local kernel: [ 47.209120] sd 6:0:0:0: [sdb] Attached SCSI disk
Mar 29 19:19:50 local kernel: [ 54.928067] usb 2-2: reset high-speed USB device number 5 using ehci-pci
Mar 29 19:19:50 local udisksd[1881]: Error probing device: Error sending ATA command IDENTIFY DEVICE to /dev/sdb: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0)

thad@local:~$ apt-cache policy udisks2
udisks2:
  Installed: 2.1.0-2
  Candidate: 2.1.0-2
  Version table:
 *** 2.1.0-2 0
        500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Andrey (abelt)]

My logs are the same.

[Andrey (abelt)]

lsusb -vd 14cd:6116
...
  idVendor 0x14cd Super Top
  idProduct 0x6116 M6116 SATA Bridge
  bcdDevice 1.60
...

[mikes-rus (mikes001-p)]

too affect this bug
here is my log

May 7 22:50:49 homeusr-desktop kernel: [ 9067.432515] usb 1-1.1: new high-speed USB device number 4 using ehci-pci
May 7 22:50:50 homeusr-desktop kernel: [ 9067.525960] usb 1-1.1: New USB device found, idVendor=14cd, idProduct=6116
May 7 22:50:50 homeusr-desktop kernel: [ 9067.525965] usb 1-1.1: New USB device strings: Mfr=1, Product=3, SerialNumber=2
May 7 22:50:50 homeusr-desktop kernel: [ 9067.525968] usb 1-1.1: Product: USB 2.0 SATA BRIDGE
May 7 22:50:50 homeusr-desktop kernel: [ 9067.525970] usb 1-1.1: Manufacturer: Super Top
May 7 22:50:50 homeusr-desktop kernel: [ 9067.525972] usb 1-1.1: SerialNumber: M6116018VF16
May 7 22:50:50 homeusr-desktop kernel: [ 9067.526610] scsi7 : usb-storage 1-1.1:1.0
May 7 22:50:50 homeusr-desktop mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1"
May 7 22:50:50 homeusr-desktop mtp-probe: bus: 1, device: 4 was not an MTP device
May 7 22:50:51 homeusr-desktop kernel: [ 9068.524551] scsi 7:0:0:0: Direct-Access WDC WD10 JPVT-55A1YT0 PQ: 0 ANSI: 0
May 7 22:50:51 homeusr-desktop kernel: [ 9068.525326] sd 7:0:0:0: Attached scsi generic sg2 type 0
May 7 22:50:51 homeusr-desktop kernel: [ 9068.525991] sd 7:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
May 7 22:50:51 homeusr-desktop kernel: [ 9068.526873] sd 7:0:0:0: [sdb] Write Protect is off
May 7 22:50:51 homeusr-desktop kernel: [ 9068.526878] sd 7:0:0:0: [sdb] Mode Sense: 03 00 00 00
May 7 22:50:51 homeusr-desktop kernel: [ 9068.529089] sd 7:0:0:0: [sdb] No Caching mode page present
May 7 22:50:51 homeusr-desktop kernel: [ 9068.529094] sd 7:0:0:0: [sdb] Assuming drive cache: write through
May 7 22:50:51 homeusr-desktop kernel: [ 9068.531080] sd 7:0:0:0: [sdb] No Caching mode page present
May 7 22:50:51 homeusr-desktop kernel: [ 9068.531085] sd 7:0:0:0: [sdb] Assuming drive cache: write through
May 7 22:50:51 homeusr-desktop kernel: [ 9068.586118] sdb: sdb1
May 7 22:50:51 homeusr-desktop kernel: [ 9068.589203] sd 7:0:0:0: [sdb] No Caching mode page present
May 7 22:50:51 homeusr-desktop kernel: [ 9068.589208] sd 7:0:0:0: [sdb] Assuming drive cache: write through
May 7 22:50:51 homeusr-desktop kernel: [ 9068.589212] sd 7:0:0:0: [sdb] Attached SCSI disk
May 7 22:50:59 homeusr-desktop kernel: [ 9076.599154] usb 1-1.1: reset high-speed USB device number 4 using ehci-pci
May 7 22:50:59 homeusr-desktop udisksd[2115]: Error probing device: Error sending ATA command IDENTIFY DEVICE to /dev/sdb: Unexpected sense data returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................#012 (g-io-error-quark, 0)
May 7 22:51:52 homeusr-desktop udevd[13523]: timeout '/sbin/blkid -o udev -p /dev/sdb1'
May 7 22:51:53 homeusr-desktop udevd[13523]: timeout: killing '/sbin/blkid -o udev -p /dev/sdb1' [13679]
May 7 22:51:55 udevd[13523]: last message repeated 2 times
May 7 22:51:55 homeusr-desktop dbus[903]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out
May 7 22:51:56 homeusr-desktop udevd[13523]: timeout: killi...

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

Only a very small range of hard drivers seems to be affected by this bug. Using udisks instead of udisks2 is one possible workaround.

[mikes-rus (mikes001-p)]

how to do it? that we are losing in this case?

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

I simply removed the udisks2 package. However, some packages depend on udisks2 and you might lose gvfs-support.

[mikes-rus (mikes001-p)]

Unfortunately, for me it is not a solution, too many dependencies are removed, such as:
brasero
gnome-disk-utility
ia32-crossover
ia32-libs
ia32-libs-multiarch: i386
nautilus
nautilus-sendto
nautilus-share
software-center
teamviewer
ubuntu-desktop
udisks2

[Huan Zhang (victzhang)]

My hard disk does not work on Ubuntu 13.04 probably due to this bug. It worked fine on Ubuntu 12.10, and also works fine on a Windows 7 machine. I really need a workaround for this issue because I use Ubuntu everyday.

Here is dmesg log:

[17570.344528] usb 1-1.2: new high-speed USB device number 10 using ehci-pci
[17570.437866] usb 1-1.2: New USB device found, idVendor=14cd, idProduct=6116
[17570.437873] usb 1-1.2: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[17570.437877] usb 1-1.2: Product: USB 2.0 SATA BRIDGE
[17570.437880] usb 1-1.2: Manufacturer: Super Top
[17570.437882] usb 1-1.2: SerialNumber: M6116018VF16
[17570.438452] scsi13 : usb-storage 1-1.2:1.0
[17571.435109] scsi 13:0:0:0: Direct-Access SAMSUNG HM321HI PQ: 0 ANSI: 0
[17571.436009] sd 13:0:0:0: Attached scsi generic sg2 type 0
[17571.436556] sd 13:0:0:0: [sdb] 625142448 512-byte logical blocks: (320 GB/298 GiB)
[17571.437191] sd 13:0:0:0: [sdb] Write Protect is off
[17571.437200] sd 13:0:0:0: [sdb] Mode Sense: 03 00 00 00
[17571.438563] sd 13:0:0:0: [sdb] No Caching mode page present
[17571.438572] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[17571.441056] sd 13:0:0:0: [sdb] No Caching mode page present
[17571.441061] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[17571.811215] sdb: sdb1
[17571.813636] sd 13:0:0:0: [sdb] No Caching mode page present
[17571.813640] sd 13:0:0:0: [sdb] Assuming drive cache: write through
[17571.813643] sd 13:0:0:0: [sdb] Attached SCSI disk
[17579.587207] usb 1-1.2: reset high-speed USB device number 10 using ehci-pci
-----------------------------------------------------(after disconnecting)-----------------------------------------------------------------------
[17606.644883] usb 1-1.2: USB disconnect, device number 10
[17606.648136] scsi 13:0:0:0: rejecting I/O to offline device
[17606.648140] scsi 13:0:0:0: [sdb] killing request
[17606.648148] scsi 13:0:0:0: [sdb] Unhandled error code
[17606.648162] scsi 13:0:0:0: [sdb]
[17606.648167] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[17606.648171] scsi 13:0:0:0: [sdb] CDB:
[17606.648175] Read(10): 28 00 25 42 d6 af 00 00 08 00
[17606.648190] end_request: I/O error, dev sdb, sector 625137327
[17606.648194] quiet_error: 531 callbacks suppressed
[17606.648197] Buffer I/O error on device sdb1, logical block 312568632
[17606.648201] Buffer I/O error on device sdb1, logical block 312568633
[17606.648204] Buffer I/O error on device sdb1, logical block 312568634
[17606.648207] Buffer I/O error on device sdb1, logical block 312568635
[17606.648258] Buffer I/O error on device sdb1, logical block 312568632
[17606.648266] Buffer I/O error on device sdb1, logical block 312568633
[17606.648270] Buffer I/O error on device sdb1, logical block 312568634
[17606.648273] Buffer I/O error on device sdb1, logical block 312568635
[17606.648305] Buffer I/O error on device sdb1, logical block 0
[17606.648306] Buffer I/O error on device sdb1, logical block 1
[17620.969267] ehci-pci 0000:00:1d.0: setting latency timer to 64
[17620.985227] ehci-pci 0000:00:1a.0: setting latency timer to 64

[Thomas Forgber (thomas-forgber)]

Sry for the late repley - just found this!
One simple workaround is to manually downgrade the udisks2 package:

HOW TO:

Download an older version of the package eg here:
www.ubuntuupdates.org/package/core/quantal/main/base/udisks2

go to folder which includes the package an type:

sudo dpkg -i package.deb

Now check the Version again with:

sudo apt-cache showpkg udisks2

It should show you the downloaded version number now + some dependences (like this)
Provides:
2.1.0-2 - udisks2:i386
2.0.0-1 - udisks2:i386
Reverse Provides:
udisks2:i386 2.1.0-2

Now you have to lock the version in order to not update it automatically while apt-get update is running either with synaptic or console:

Synaptic:
search for udisks2 - it should show you again the downloaded version, mark it, and select lock version under package

console:
sudo echo “package hold” | sudo dpkg –set-selections

If all is done reboot, test it and run

sudo apt-get update

to check if it gets updated or not.

Hope that works for you guys!

[Robert (roseg)]

Hallo Thomas

Many thanks for the workaround. I can confirm it works.

Would you know if any plans exist to fix this in a future version of
udisks?

On Fre, 2013-08-02 at 07:35 +0000, Thomas Forgber wrote:
> Sry for the late repley - just found this!
> One simple workaround is to manually downgrade the udisks2 package:
>
> HOW TO:
>
> Download an older version of the package eg here:
> www.ubuntuupdates.org/package/core/quantal/main/base/udisks2
>
> go to folder which includes the package an type:
>
> sudo dpkg -i package.deb
>
> Now check the Version again with:
>
> sudo apt-cache showpkg udisks2
>
> It should show you the downloaded version number now + some dependences (like this)
> Provides:
> 2.1.0-2 - udisks2:i386
> 2.0.0-1 - udisks2:i386
> Reverse Provides:
> udisks2:i386 2.1.0-2
>
> Now you have to lock the version in order to not update it automatically
> while apt-get update is running either with synaptic or console:
>
> Synaptic:
> search for udisks2 - it should show you again the downloaded version, mark it, and select lock version under package
>
> console:
> sudo echo “package hold” | sudo dpkg –set-selections
>
> If all is done reboot, test it and run
>
> sudo apt-get update
>
> to check if it gets updated or not.
>
> Hope that works for you guys!
>

--
Robert

[Thomas Forgber (thomas-forgber)]

Glad that it works for you too!

Sorry but I have no idea wether it will be fixes or not - seems the error occures quite often.

I also tried my external harddrive with Kile Linux (Debian disstribution) and it runs...Dont exactly know what package they use through...

Regards,

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Aram Yegenian (aramyegenian)]

Hello Thomas,

Thank you a lot, I confirm your workaround works.

Hope this gets fixed soon.

Regards.

[Simon Braunschmidt (simon-braunschmidt)]

Hi all,

I seem to also be affected. I know that I used to have no problems with
the enclosure (lsusb details below), but nowadays in Ubuntu I get
the errors.

Searching google for 14cd:6116 gives several error reports from different
distributions etc., also it looks similar to
launchpad bug https://launchpad.net/bugs/1176355 and
maybe https://launchpad.net/bugs/1082215.

It seems to me that the USB device "14cd:6116" shows different
failure modes depending on the bcdDevice number (release number),
the number for my problematic device is "1.50", but others seem to
be also problematic.

Killing all "udisks" processes (all that show up from "ps fax|grep udisk")
helps to be able to mount the disk and use it, but I seems that when
a process "/usr/lib/udisks2/udisksd --no-debug" is running again
(started by some under the hood mechanism that I was not aware
of, when using KDE program gwenview to access the disk), then
the disk is again going into failure mode.
Downgrading the udisks2 package as described above leads to a
situation where even such a "/usr/lib/udisks2/udisksd --no-debug"
process running does not put the disk into failure mode.

I did not test with the regular udisks processes running though,
because I do not know how to restart them properly.

Regards
Simon

below:
* dmesg of the problem with comments
* lsusb -vvv -d 14cd:6116

dmesg, with comments:
Note that I run the module usb_storage with delay_use=5
(sudo modprobe usb_storage delay_use=5), from an earlier attempt to
fix the problem.

plugging, having killed all instances of "udisks" processes prior:

[16596.788460] usb 2-5: new high-speed USB device number 13 using ehci-pci
[16596.921661] usb 2-5: New USB device found, idVendor=14cd, idProduct=6116
[16596.921673] usb 2-5: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[16596.921681] usb 2-5: Product: USB 2.0 SATA BRIDGE
[16596.921687] usb 2-5: Manufacturer: Super Top
[16596.921693] usb 2-5: SerialNumber: M6116018VE15
[16596.922963] ums-cypress 2-5:1.0: USB Mass Storage device detected
[16596.924248] scsi15 : usb-storage 2-5:1.0
[16601.933622] scsi 15:0:0:0: Direct-Access FUJITSU MHV2100BH PL PQ: 0 ANSI: 0
[16601.934260] sd 15:0:0:0: Attached scsi generic sg2 type 0
[16601.942260] sd 15:0:0:0: [sdb] 195371568 512-byte logical blocks: (100 GB/93.1 GiB)
[16601.943869] sd 15:0:0:0: [sdb] Write Protect is off
[16601.943880] sd 15:0:0:0: [sdb] Mode Sense: 03 00 00 00
[16601.944466] sd 15:0:0:0: [sdb] No Caching mode page found
[16601.944470] sd 15:0:0:0: [sdb] Assuming drive cache: write through
[16601.946860] sd 15:0:0:0: [sdb] No Caching mode page found
[16601.946864] sd 15:0:0:0: [sdb] Assuming drive cache: write through
[16602.020545] sdb: sdb1
[16602.022864] sd 15:0:0:0: [sdb] No Caching mode page found
[16602.022869] sd 15:0:0:0: [sdb] Assuming drive cache: write through
[16602.022873] sd 15:0:0:0: [sdb] Attached SCSI disk

since I did kill the "udisks" processes/daemons before, I was now able to mount the
disk manually, an use it

[22828.940082] usb 2-5: reset high-speed USB device number 13 using ehci-pci

I decided to run the KDE program gwenview and have it access the disk.
This put the dis...

[CassieMoondust (cassie-lx)]

I can confirm this behavior with Ubuntu 13.10, also.

I have no problem in accesssing the usb drive using Kernel 3.8.0-33-generic #48~precise1-Ubuntu SMP Thu Oct 24 16:28:06 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux with Ubuntu 12.04.3 LTS (Raring HWE Stack)

[Tor Sjowall (u-cor-u)]

I too can confirm this problem on two different installations of Ubuntu 13.10.

lsusb -vd 14cd:6116
...
  idVendor 0x14cd Super Top
  idProduct 0x6116 M6116 SATA Bridge
  bcdDevice 1.50
...
    bmAttributes 0xc0
      Self Powered
    MaxPower 2mA
...

Note that the device reports 'self powered' and 2mA but it is in fact using power from the USB hub. The device works with Windows XP on a the same PC (dual boot).

I did make an unsuccessful attemp at downgrading udisks2 as described above. I didn't dare to force the downgrade considering the number of dependencies.

tor@maxlap:~/Downloads$ sudo dpkg -i udisks2_2.0.0-1_i386.deb
dpkg: warning: downgrading udisks2 from 2.1.0-4 to 2.0.0-1
(Reading database ... 244438 files and directories currently installed.)
Preparing to replace udisks2 2.1.0-4 (using udisks2_2.0.0-1_i386.deb) ...
Unpacking replacement udisks2 ...
dpkg: dependency problems prevent configuration of udisks2:
 udisks2 depends on libatasmart4 (>= 0.13).
 udisks2 depends on libgudev-1.0-0 (>= 165); however:
  Package libgudev-1.0-0:i386 is not installed.
 udisks2 depends on libpolkit-agent-1-0 (>= 0.99); however:
 udisks2 depends on libpolkit-gobject-1-0 (>= 0.101); however:
 udisks2 depends on libudisks2-0; however:

dpkg: error processing udisks2 (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db ...
Errors were encountered while processing:
 udisks2
tor@maxlap:~

[Rowan Potgieter (rowan-potgieter)]

Hi,

I can confirm I have the same issue on Ubuntu Ubuntu 12.04.3 LTS. I've posted a long comment on Bug #1176355 only to realise that it was a duplicate of this case.
However, I see a lot of people are complaining about this being an issue on 13.04 or 13.10 whereas I have this issue on 12.04 but only since an update sometime around the start of December.

Here is my comment from the other case - please excuse the length:

Hi, I have the same issue but it seems to affect ALL USB disks.

I unfortunately only have 1 on me right now but this disk does work on Windows and I'm fairly certain that I had no USB issues in November 2013, I suspect an update in December messed things up. I have also tried with 2 other USB disks which did work previously and they also are not working.

DMESG Ouptput:
[33712.381565] usb 1-1.2: new high-speed USB device number 4 using ehci_hcd
[33712.553269] usb 1-1.2: New USB device found, idVendor=0011, idProduct=7788
[33712.553273] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[33712.553276] usb 1-1.2: Product: Mass Storage
[33712.553278] usb 1-1.2: Manufacturer: Generic
[33712.553280] usb 1-1.2: SerialNumber: 29F9C21B
[33712.553948] scsi5 : usb-storage 1-1.2:1.0
[33713.552907] scsi 5:0:0:0: Direct-Access Generic Flash Disk 8.00 PQ: 0 ANSI: 2
[33713.553945] sd 5:0:0:0: Attached scsi generic sg2 type 0
[33713.555480] sd 5:0:0:0: [sdb] 16691200 512-byte logical blocks: (8.54 GB/7.95 GiB)
[33713.556071] sd 5:0:0:0: [sdb] Write Protect is off
[33713.556074] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[33713.556572] sd 5:0:0:0: [sdb] No Caching mode page present
[33713.556576] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[33713.559217] sd 5:0:0:0: [sdb] No Caching mode page present
[33713.559222] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[33713.609029] sdb: sdb1
[33713.611489] sd 5:0:0:0: [sdb] No Caching mode page present
[33713.611494] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[33713.611497] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[33744.352957] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33775.322639] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33806.228316] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33837.134160] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33868.167673] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33899.073388] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33899.241280] sd 5:0:0:0: [sdb] Media Changed
[33899.241285] sd 5:0:0:0: [sdb]
[33899.241287] Result: hostbyte=DID_ABORT driverbyte=DRIVER_SENSE
[33899.241289] sd 5:0:0:0: [sdb]
[33899.241290] Sense Key : Unit Attention [current]
[33899.241294] Info fld=0x0
[33899.241296] sd 5:0:0:0: [sdb]
[33899.241299] Add. Sense: Not ready to ready change, medium may have changed
[33899.241301] sd 5:0:0:0: [sdb] CDB:
[33899.241303] Read(10): 28 00 00 fe af f8 00 00 01 00
[33899.241311] end_request: I/O error, dev sdb, sector 16691192
[33899.241315] Buffer I/O error on device sdb, logical block 2086399
[33899.245484] sd 5:0:0:0: [sdb] No Caching mode page present
[33899.245489] sd 5:0:0:0: ...

[Phillip Susi (psusi)]

Rowan, I have no idea why you commented on this bug as your issue has absolutely nothing to do with it. This bug is just about an annoying error message in the system log that is benign.

[CassieMoondust (cassie-lx)]

I can confirm, this bug is solved in Ubuntu 14.04 LTS. I can use my external harddrive with no problems.

Bug is solved for me.

[Danny Keary (56kflyingtoaster)]

So i've been having this problem for a long time, with my OCZ Vertex 4 which i have since swapped for a 120GB Seagate Barracuda with an IDE to SATA converter. Still getting the same problem which causes my system to hang, and with the SSD to compleetly die reset, lose the disk, hang.

Here is some of my syslog if it helps

Apr 22 17:33:43 dan9550 kernel: [ 9186.674306] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Apr 22 17:33:43 dan9550 kernel: [ 9186.674316] ata2.00: failed command: SMART
Apr 22 17:33:43 dan9550 kernel: [ 9186.674326] ata2.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
Apr 22 17:33:43 dan9550 kernel: [ 9186.674326] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Apr 22 17:33:43 dan9550 kernel: [ 9186.674332] ata2.00: status: { DRDY }
Apr 22 17:33:43 dan9550 kernel: [ 9186.674339] ata2: hard resetting link
Apr 22 17:33:44 dan9550 kernel: [ 9187.670323] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Apr 22 17:33:44 dan9550 kernel: [ 9187.677119] ata2.00: configured for UDMA/100
Apr 22 17:33:44 dan9550 kernel: [ 9187.677160] ata2: EH complete

Is there a workaround i could use to stop the OS sending this SMART command to the drive?

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

It looks like the error has been been fixed at some point. Works fine in 14.10.

[Thaddaeus Tintenfisch (thad-fisch-deactivatedaccount)]

It looks like the error has been been fixed at some point. Works fine in Ubuntu 14.10.