[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2014-12-29 Thread Bug Watch Updater
** Changed in: libatasmart
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2014-12-15 Thread Thaddäus Tintenfisch
It looks like the error has been been fixed at some point. Works fine in
14.10.

** Changed in: libatasmart (Ubuntu)
   Status: Confirmed = Incomplete

** Changed in: udisks2 (Ubuntu)
   Status: Confirmed = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2014-12-15 Thread Phillip Susi
** Changed in: libatasmart (Ubuntu)
   Status: Incomplete = Fix Committed

** Changed in: libatasmart (Ubuntu)
   Status: Fix Committed = Fix Released

** Changed in: udisks2 (Ubuntu)
   Status: Incomplete = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2014-04-22 Thread Danny Keary
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?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2014-04-19 Thread Papamatti
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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2014-01-03 Thread Phillip Susi
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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2014-01-02 Thread 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: [sdb] Assuming drive cache: write through
[33899.247723] sd 5:0:0:0: [sdb] No Caching mode page present
[33899.247728] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[33899.297542] sdb: sdb1
[33929.979207] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd

lsusb -v:

Bus 001 Device 004: ID 0011:7788
Couldn't open device, some information will be missing
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x0011
  idProduct 0x7788
  bcdDevice 1.03
  iManufacturer 1
  iProduct 2
  iSerial 3
  bNumConfigurations 1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 32
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
  (Bus Powered)
MaxPower 100mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber 0
  bAlternateSetting 0
  bNumEndpoints 2
  bInterfaceClass 8 Mass Storage
  bInterfaceSubClass 6 SCSI
  bInterfaceProtocol 80 Bulk-Only
  iInterface 0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
  Transfer Type Bulk
  Synch Type None
  Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
  Transfer Type Bulk
  Synch Type None
  Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0

sudo fdisk -l: (this hangs for quite a while on sdb - I've posted the
dmesg output below as 

[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-12-20 Thread Tor Sjowall
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
  bcdDevice1.50
...
bmAttributes 0xc0
  Self Powered
MaxPower2mA
...


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:~

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-11-16 Thread 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 disk back into a failure mode, as seen below. I checked
and observed that there was again a udisks process running,
/usr/lib/udisks2/udisksd --no-debug if I remember right.

[22885.448597] sd 15:0:0:0: [sdb] Unhandled sense code
[22885.448605] sd 15:0:0:0: [sdb]  
[22885.448608] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[22885.448612] sd 15:0:0:0: [sdb]  
[22885.448615] Sense Key : Medium Error [current] 
[22885.448621] sd 15:0:0:0: [sdb]  
[22885.448625] Add. Sense: Unrecovered read error
[22885.448634] sd 15:0:0:0: [sdb] CDB: 
[22885.448636] Read(10): 28 00 09 68 e5 7f 00 00 f0 00
[22885.448650] blk_update_request: 407 callbacks suppressed
[22885.448652] end_request: critical target error, dev sdb, sector 157869439
[22885.448657] quiet_error: 548 callbacks suppressed
[22885.448660] Buffer I/O error on device sdb1, logical block 19733672
[22885.448669] Buffer I/O error on device sdb1, logical block 19733673
[22885.448673] Buffer I/O error on device sdb1, logical block 19733674
[22885.448676] Buffer I/O error on device sdb1, logical block 19733675
[22885.448679] Buffer I/O error on device sdb1, logical block 19733676
[22885.448683] Buffer I/O error on device sdb1, logical block 19733677
[22885.448686] Buffer I/O error on device sdb1, logical block 19733678
[22885.448689] Buffer I/O error on device sdb1, logical block 19733679
[22885.448692] Buffer I/O error on device sdb1, logical block 19733680
[22885.448696] Buffer I/O error on device sdb1, logical block 19733681
[22885.460127] sd 15:0:0:0: [sdb] Unhandled sense code
[22885.460133] sd 15:0:0:0: [sdb]  
[22885.460137] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[22885.460141] sd 15:0:0:0: [sdb]  
[22885.460144] Sense Key : Medium Error [current] 
[22885.460149] sd 15:0:0:0: [sdb]  
[22885.460153] Add. Sense: Unrecovered 

[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-11-16 Thread Papamatti
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)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-10-23 Thread Aram Yegenian
Hello Thomas,

Thank you a lot, I confirm your workaround works.

Hope this gets fixed soon.

Regards.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-09-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: udisks2 (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-08-06 Thread 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,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-08-05 Thread Robert
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 +, 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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-08-02 Thread 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!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-08-02 Thread Thaddäus Tintenfisch
** Also affects: udisks2 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-06-19 Thread Huan Zhang
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 :00:1d.0: setting latency timer to 64
[17620.985227] ehci-pci :00:1a.0: setting latency timer to 64

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-05-13 Thread Thaddäus Tintenfisch
I simply removed the udisks2 package. However, some packages depend on
udisks2 and you might lose gvfs-support.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-05-13 Thread mikes-rus
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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-05-12 Thread Thaddäus Tintenfisch
Only a very small range of hard drivers seems to be affected by this
bug. Using udisks instead of udisks2 is one possible workaround.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-05-12 Thread mikes-rus
how to do it? that we are losing in this case?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-05-07 Thread mikes-rus
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/pci:00/: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:#012: 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: killing '/sbin/blkid -o 
udev -p /dev/sdb1' [13679]
May  7 22:52:06  udevd[13523]: last message repeated 10 times
May  7 22:52:06 homeusr-desktop udevd[13523]: '/sbin/blkid -o udev -p 
/dev/sdb1' [13679] terminated by signal 9 (Killed)
May  7 22:52:06 homeusr-desktop udevd[13523]: timeout 'udisks-part-id /dev/sdb1'
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795256] sd 7:0:0:0: [sdb] 
Unhandled sense code
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795262] sd 7:0:0:0: [sdb]  
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795264] Result: 
hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795266] sd 7:0:0:0: [sdb]  
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795268] Sense Key : Hardware 
Error [current] 
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795272] sd 7:0:0:0: [sdb]  
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795274] Add. Sense: No 
additional sense information
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795276] sd 7:0:0:0: [sdb] CDB: 
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795278] Read(10): 28 00 74 70 67 
f0 00 00 08 00
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795286] end_request: I/O error, 
dev sdb, sector 1953523696
May  7 22:52:06 homeusr-desktop kernel: [ 9143.795291] Buffer I/O error on 
device sdb1, logical block 244190206
May  7 22:52:07 homeusr-desktop udevd[13523]: timeout: killing 'udisks-part-id 
/dev/sdb1' [13729]
May  7 22:52:20  udevd[13523]: last message repeated 13 times
May  7 22:52:20 homeusr-desktop dbus[903]: [system] Failed to activate service 
'org.freedesktop.Avahi': timed out
May  7 22:52:21 homeusr-desktop udevd[13523]: timeout: killing 'udisks-part-id 
/dev/sdb1' [13729]
May  7 22:52:45  udevd[13523]: last message repeated 24 times
May  7 

[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-04-24 Thread Thaddäus Tintenfisch
** Bug watch added: freedesktop.org Bugzilla #63883
   https://bugs.freedesktop.org/show_bug.cgi?id=63883

** Also affects: libatasmart via
   https://bugs.freedesktop.org/show_bug.cgi?id=63883
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-04-24 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=63883.

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 2013-04-24T11:01:40+00:00 Thaddäus Tintenfisch wrote:

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:#012: 
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

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

Reply at:
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1161985/comments/4


** Changed in: libatasmart
   Status: Unknown = Confirmed

** Changed in: libatasmart
   Importance: Unknown = Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1161985/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-04-22 Thread Andrey
lsusb -vd 14cd:6116
...
  idVendor   0x14cd Super Top
  idProduct  0x6116 M6116 SATA Bridge
  bcdDevice1.60
...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-04-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libatasmart (Ubuntu)
   Status: New = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-04-19 Thread Andrey
My logs are the same.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-04-03 Thread Martin Pitt
** Package changed: udisks2 (Ubuntu) = libatasmart (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1161985] Re: Error sending ATA command IDENTIFY DEVICE

2013-03-29 Thread Thaddäus Tintenfisch
** Also affects: libatasmart (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: libatasmart (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161985

Title:
  Error sending ATA command IDENTIFY DEVICE

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs