craneium.net

brain matters . . .

  • Increase font size
  • Default font size
  • Decrease font size
Home Other Life SuperTalent Hard Drives on Ubuntu

SuperTalent Hard Drives on Ubuntu

E-mail Print PDF

So the third party SuperTalent SSD's that are marketed for net-book replacements are pretty poorly supported in Ubuntu.  People have had problems from Intrepid, through Jaunty, Karmic and now Lucid!

It exhibits roughly the following symptoms:

Bootup is slow, some gnome application fail to load properly, and there are large pauses now and then when the drive is being soft-reset.

The associated dmesg output looks like:

[ 2962.988208] ata2: lost interrupt (Status 0x58)
[ 2962.988297] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 2962.988306] ata2.00: BMDMA stat 0x4
[ 2962.988323] ata2.00: cmd ca/00:08:40:e9:7d/00:00:00:00:00/e0 tag 0 dma 4096 out
[ 2962.988326] res 58/00:08:40:e9:7d/00:00:00:00:00/e0 Emask 0x2 (HSM violation)
[ 2962.988333] ata2.00: status: { DRDY DRQ }
[ 2962.988376] ata2: soft resetting link
[ 2963.196543] ata2.00: configured for UDMA/66
[ 2963.196581] ata2: EH complete

The error is a "HSM Violation" which I have no idea the deep seated nature of . . . but there is a quick and dirty work around:

Depending on your version of linux the file that needs alteration has a different name.  You can find it by running:

$cd /lib/udev/rules.d/

$grep smart *

This turned up some rules about photosmart printers, but we are looking for a line about libata.

Open the file of interest, typically named one of these two:

80-udisks.rules

95-devkit-disks.rules

There are three instances of the following line:

KERNEL=="sd*[!0-9]", ATTR{removable}=="0", ENV{ID_BUS}=="ata", ENV{DEVTYPE}=="disk", IMPORT{program}="udisks-probe-ata-smart $tempnode"

Comment out (add a # before) the one associated with libata (as described in the comments above the line in question)  Reboot, and everything should work fine!

Here are the associated launchpad link, it sounds like a inline fix is in the pipes, but this can cause hard-drive damage!  So fix it yourself ASAP!

Last Updated on Monday, 14 June 2010 16:51