Ubuntu

Disk wakes up every 30 minutes and produces errors on dmesg

Reported by Ricardo Teixeira on 2009-09-23
106
This bug affects 16 people
Affects Status Importance Assigned to Milestone
libatasmart
Fix Released
Medium
libatasmart (Fedora)
Fix Released
Unknown
libatasmart (Ubuntu)
Medium
Martin Pitt

Bug Description

Hi.

I'm trying to make a hard disk drive that's only used for backups stay in standby but there is something that is spinning the drive up every 30 minutes (exactly) or whenever I login to Gnome.

The drive stays awake for a few seconds and then gets spun down again (even though I set hdparm -S 12 (1 minute)).
I can hear this perfectly because it's a pretty noisy drive: Maxtor 6L300R0

Further more, every time the drive is spun up I get the following messages in dmesg:

[189046.000060] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[189046.000075] ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
[189046.000077] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[189046.000082] ata1.00: status: { DRDY }
[189046.448025] ata1: soft resetting link
[189046.629893] ata1.00: configured for UDMA/100
[189046.629927] ata1: EH complete
[190844.988581] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[190844.988595] ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
[190844.988597] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[190844.988603] ata1.00: status: { DRDY }
[190846.444029] ata1: soft resetting link
[190846.625872] ata1.00: configured for UDMA/100
[190846.625904] ata1: EH complete

As you can see, this shows two occurrences of the problem, and they're ~ 1800 seconds (30 minutes) apart: 190844.988581-189046.000060 = 1798.988521
I thought it could be smartd but I disabled smartd and the problem persists.

System details:
Ubuntu karmic (development branch) 9.10 fully updated today.

Here is the dmesg output with echo 1 > /proc/sys/vm/block_dump.

Could it be kjournald2 that is causing the spin ups?

The disk in question is /dev/sda and apparently there is no write actions to the disk at the time of spin up.
I don't know how to check if there is any read actions.

I figure out what is spinning up the disks.
If I kill devkit-disks-daemon the spinning up stops.

I'm assigning this bug to devkit-disks.

affects: ubuntu → devicekit-disks (Ubuntu)

To furthermore pinpoint the problem it seems that the spinning up is happening because devkit is pooling the disk for smart data.
I did the following:

root@jupiter:~# hdparm -y /dev/sdc

/dev/sdc:
 issuing standby command
root@jupiter:~# hdparm -C /dev/sdc

/dev/sdc:
 drive state is: standby
root@jupiter:~# devkit-disks --ata-smart-refresh /dev/sdc >dump.txt
root@jupiter:~# hdparm -C /dev/sdc

/dev/sdc:
 drive state is: active/idle

but according to the devicekit man page it should only wakeup the disk if I issued devkit-disks --ata-smart-refresh /dev/sdc --ata-smart-wakeup

Martin Pitt (pitti) on 2009-10-01
Changed in devicekit-disks (Ubuntu):
importance: Undecided → Low
Martin Pitt (pitti) wrote :

This is pretty much wontfix, though. However, this could be made configurable.

Changed in devicekit-disks (Ubuntu):
importance: Low → Wishlist
status: New → Triaged

But is there a way (even if it is a hard one) to disable the spinning up?

Radu Cornea (raduc) wrote :

I noticed the same problem, any workarounds?

Thanks.

Antti Kaihola (akaihola) wrote :

Same problem here.

Strangely, when I tried monitoring disk access, I got no indication of any process accessing /dev/sdb* when the disk spun up or at any other time. I used this script to monitor:
    echo 1 >/proc/sys/vm/block_dump
    while ( ! dmesg -c|grep sdb ); do sleep 1; done
    echo 0 >/proc/sys/vm/block_dump

A work-around would be greatly appreciated. This pretty much prevents me from using Mythbuntu with my current hardware as a HTPC. My motherboard can't boot from the silent 1TB disk connected to my SATA PCI card, so I need an old noisy IDE disk just for booting up. Can't sleep if it's spinning up every 30 minutes in the next room.

Antti Kaihola (akaihola) wrote :

I peeked at the source code. The ATA smart collect script is called by the daemon like this:

    /usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect /dev/sdb 1

The "1" parameter is the "nowakeup" option. Executing the above call as root always spins up my disk (also when replacing "1" with "0"). The corresponding code is:

        nowakeup = atoi (argv[2]);

        if (sk_disk_open (device, &d) != 0) {
                g_printerr ("Failed to open disk %s: %m\n", device);
                goto out;
        }

        if (sk_disk_check_sleep_mode (d, &awake) != 0) {
                g_printerr ("Failed to check if disk %s is awake: %m\n", device);
                goto out;
        }

        /* don't wake up disk unless specically asked to */
        if (nowakeup && !awake) {
                g_printerr ("Disk %s is asleep and nowakeup option was passed\n", device);
                ret = 2;
                goto out;
        }

So either sk_disk_check_sleep_mode fails to detect that the disk is sleeping, or the nowakeup option is parsed incorrectly. I'll debug that later.

Hello.
I think I don't have the knowledge to help you in debugging this but I hope you succeed.
If you need any help please post.
Thanks.

Antti Kaihola (akaihola) wrote :

Ricardo,

You could check whether these commands spin up the disk on your system:

$ sudo /usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect /dev/sdX 1
$ sudo /usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect /dev/sdX 0

(replace sdX with your disk device)

Antti Kaihola (akaihola) wrote :

Here's a dirty work-around:

    ~$ cd /usr/lib/devicekit-disks
    /usr/lib/devicekit-disks$ sudo mv devkit-disks-helper-ata-smart-collect devkit-disks-helper-ata-smart-collect.real
    /usr/lib/devicekit-disks$ sudo sh -c "cat >devkit-disks-helper-ata-smart-collect <<EOF
    > #!/bin/sh
    > [ "$1" != "/dev/sdb" ] && /usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect.real "$@"
    > EOF"
    /usr/lib/devicekit-disks$ sudo chmod a+x devkit-disks-helper-ata-smart-collect
    $ ls -l devkit-disks-helper-ata-smart-collect*
    -rwxr-xr-x 1 root root 99 2009-10-16 09:30 devkit-disks-helper-ata-smart-collect
    -rwxr-xr-x 1 root root 5608 2009-09-19 18:30 devkit-disks-helper-ata-smart-collect.real

Replace /dev/sdb with the device you don't want to spin up.

All my disks that are inactive (spun down with hdparm -S12 /dev/sd*), are each 30 minutes woken up for a SMART check.

when i run Palimpsest Disk Utility and update now on a disk, I can see this with "ps auxf", and finally found out what is wakening my disks

root 1886 0.0 0.1 4944 2956 ? S 16:37 0:02 /usr/lib/DeviceKit/devkit-disks-daemon
root 1887 0.0 0.0 4608 684 ? S 16:37 0:03 \_ devkit-disks-daemon: polling /dev/sdb /dev/hdc /dev/sde /dev/sdc /dev/sdd
root 2570 0.0 0.0 2664 604 ? D 22:34 0:00 \_ /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/sda 0

running devicekit-disks 007 on Archlinux (gnome 2.28)

We don't. We specifically use libatasmart API to check if the disk is asleep before attempting retrieving SMART data from it. This works fine for most disks but some disks are broken insofar that checking if they are asleep wakes up the disk. Yes, priceless isn't it?

So this is either a hardware bug (most likely) or a libatatasmart bug (less likely). I'm saying the more is more likely because of the 8 external disks that I own, only one exhibits the behavior your bug is about.

Anyway, not a DeviceKit-disks bug.

Antti,

I've checked and both commands spin up the disk.

Just checked your workaround and it works for me.
Don't know if updates will break it...

Antti Kaihola (akaihola) wrote :

Ricardo,

Yes, any updates to devicekit-disks will break my work-around.

Antti Kaihola (akaihola) wrote :

I sprinkled some debug output into job-ata-smart-collect.c and it seems that the sk_disk_open() call spins up the disk even before the sleep mode gets checked.

sk_disk_open() is provided by libatasmart4, so should this bug be assigned there?

Strangely, hdparm -C manages to retrieve the sleep state correctly without spinning the disk up. Hdparm doesn't use libatasmart4, so it must use a more advanced method for getting smart data from a drive.

Antti Kaihola (akaihola) wrote :

I've traced the reason for the spin-up to the disk_smart_read_thresholds() call at the end of sk_disk_open() in atasmart.c.

Apparently the SMART "Read Thresholds" command implies spinning up the disk, at least on my and Ricardo's controllers. I wonder why libatasmart4 always executes that call already when opening the disk device.

Antti Kaihola (akaihola) wrote :

Adding libatasmart to the "Affects" list since that seems to be the root cause for the problem: libatasmart can't query the sleep state of a drive without opening it first, and opening a disk executes the "Read Thresholds" call which spins up the disk.

affects: devicekit-disks (Ubuntu) → libatasmart (Ubuntu)
Changed in libatasmart (Ubuntu):
status: Triaged → New
Rich Rauenzahn (rich-shroop) wrote :

FYI: The RedHat folks are also tracking this, but they claim it is a harddrive bug -- that the request shouldn't wake up most drives.

https://bugzilla.redhat.com/show_bug.cgi?id=491552

Regardless I'd like to see this fixed somehow... I'd rather not have to replace the 5 drives in my RAID5 setup!

This affects my 3 hdds...:

/dev/sda: Maxtor 6L300R0
/dev/sdb: SAMSUNG HD154UI
/dev/sdc: ST9120822AS

I only use sda and sdc once a day so I would also like to see this fixed.

Nico (nico-rdo) wrote :

wow wow wow !

Wishlist? Really?

Please help us!

The disk I am using for rsnapshot backups is perfectly fine, but it is noisy. Plus I have 2 disks in a small Shuttle enclosure, it gets hot in there, so spin-down is not part of a wishlist for me, it is a necessity!

Please help!

Radu Cornea (raduc) wrote :

Not to mention the wear in the hard drive's spindle motor from spin-up/spin-down every 30 minutes. This will result in bad drives and is not acceptable in a mature release!

Antti Kaihola (akaihola) wrote :

Rich,

Thanks for the Fedora bug link. That bug is assigned to the author of libatasmart, so I posted my findings there as well (see comment #15 above), with a link back to this Launchpad bug.

Antti Kaihola (akaihola) wrote :

The source file atasmart.c in current head of libatasmart Git repository [1] is identical Karmic's current 0.16 version. Just checked that to make sure a fix isn't already on its way.

  [1]: git://git.0pointer.de/libatasmart.git

Actually this seems to be a libatasmart bug, see these downstream bug reports

https://bugzilla.redhat.com/show_bug.cgi?id=491552
https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/435190

Unfortunately there's no bug tracker for libatasmart yet but I think Lenny wanted one on fd.o. I'll try to get that going, then I'll reassign this bug. Thanks.

Reassigning to libatasmart.

I understand that some drives are behaving differently, but I run hddtemp every 2 hours and have smartd polling every 2 hours, and neither utility wakes up my drives. They both know when they are asleep and they skip their check and log a message saying as much.

Hi Lenny,
I have one of these disks, too ;-)

Changed in libatasmart (Fedora):
status: Unknown → In Progress
Changed in libatasmart:
status: Unknown → Confirmed

Not sure who this "Lenny" guy is, I only know a distribution by that name...

But anyway, some guy called Lennart now prepped this patch:

http://git.0pointer.de/?p=libatasmart.git;a=commit;h=a223a4f6277a9f006b722b13671d5292dc6339bb

And I could use someone to test this before I roll a new release tarball for this. Anyone up for this?

I can test it --- what's the easiest way for me to get a build? Or build my own?

Fedora 11, 32bit

Rich

(In reply to comment #7)
> I can test it --- what's the easiest way for me to get a build? Or build my
> own?

If building your own would be OK're prefer that. It should be enough to build libatasmart from the git tree and run the dkdisks daemon with LD_LIBRARY_PATH=foobar/libatasmart/.libs/

> Fedora 11, 32bit

Uh, this should be tested with F12. We broke ABI and API of libatasmart between F11 and F12.

Hmph -- then that takes me out of the test pool!

Rich

Good work Lennart! now its working :)

/home/snorre# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/sda 1
Disk /dev/sda is asleep and nowakeup option was passed
/home/snorre# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/hda 1
Disk /dev/hda is asleep and nowakeup option was passed
/home/snorre# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/hdb 1
Disk /dev/hdb is asleep and nowakeup option was passed

(In reply to comment #10)
> Good work Lennart! now its working :)
>
> /home/snorre# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/sda
> 1
> Disk /dev/sda is asleep and nowakeup option was passed
> /home/snorre# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/hda
> 1
> Disk /dev/hda is asleep and nowakeup option was passed
> /home/snorre# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/hdb
> 1
> Disk /dev/hdb is asleep and nowakeup option was passed
>

Now we know that the wakeup situatin got fixed. But does reading the SMART data work as well, i.e. are there any regressions? Could you verify that please?

I run:
# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/sda 0
then the disk spins up and I get this error:
Failed to read smart data for /dev/sda: No such file or directory

On Fri, 23 Oct 2009 15:47:34 -0700 (PDT)
<email address hidden> wrote:

> http://bugs.freedesktop.org/show_bug.cgi?id=24579
>
>
>
>
>
> --- Comment #11 from Lennart Poettering <email address hidden>
> 2009-10-23 15:47:33 PST --- (In reply to comment #10)
> > Good work Lennart! now its working :)
> >
> > /home/snorre# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/sda
> > 1
> > Disk /dev/sda is asleep and nowakeup option was passed
> > /home/snorre# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/hda
> > 1
> > Disk /dev/hda is asleep and nowakeup option was passed
> > /home/snorre# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/hdb
> > 1
> > Disk /dev/hdb is asleep and nowakeup option was passed
> >
>
> Now we know that the wakeup situatin got fixed. But does reading the
> SMART data work as well, i.e. are there any regressions? Could you
> verify that please?
>
>
I run:
# /usr/lib/DeviceKit/devkit-disks-helper-ata-smart-collect /dev/sda 0
then the disk spins up and I get this error:
Failed to read smart data for /dev/sda: No such file or directory

Created an attachment (id=30689)
devkit-disks-helper-ata-smart-collect output with patched libatasmart

Lennart,

The patch fixed the spin-up problem on my Ubuntu 9.10 Alpha 6 box. Here's the output from devkit-disks-helper-ata-smart-collect when the drive is spun down, first with nowakeup=1, then nowakeup=0.

I installed the patched libatasmart from Martin Pitt's Ubuntu PPA: https://launchpad.net/~ubuntu-desktop/+archive/ppa

Created an attachment (id=30690)
skdump output with patched libatasmart

Here's skdump output for my disk with the patched libatasmart. I haven't compared it to the output before installing the patch, but all values seem valid.

Martin Pitt (pitti) wrote :

For easier testing, I prepared a package with Lennart's patch and uploaded it to

  https://launchpad.net/~ubuntu-desktop/+archive/ppa

There's nothing else in this PPA, so it's safe for upgrading.

Can folks affected by this please upgrade to this and verify that it fixes the problem? Thanks!

Changed in libatasmart (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
importance: Wishlist → Medium
status: New → In Progress
Nico (nico-rdo) wrote :

I'm soon leaving my home for a day at the office and I'd prefer not to have the 30mn wake ups for the whole day if it does not fix it.

But be assured that the PPA will be in as soon as I am back this evening!

I'll report back then.

Thanks!

Antti Kaihola (akaihola) wrote :

Martin,

Thanks for the PPA package! Works for me as expected:

$ sudo /usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect /dev/sdb 1
Disk /dev/sdb is asleep and nowakeup option was passed
$ sudo /usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect /dev/sdb 0
  [disk spins up and encoded SMART data is printed]
$ sudo /usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect /dev/sdb 1
  [encoded SMART data is printed]
  [wait for 31 s here, the spin-down timeout of my disk is 30 s]
$ sudo /usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect /dev/sdb 1
Disk /dev/sdb is asleep and nowakeup option was passed

Nico (nico-rdo) wrote :

Martin,

I have the same behaviour as Antti's.

So I'm guessing that we are good to go!

Many thanks!

Everything looks good then. I'll consider this bug fixed.

There was another positive testing response on the downstream lp bug. Thanks for fixing!

Martin Pitt (pitti) wrote :

Fixed in 0.17-1 in Debian.

Changed in libatasmart (Ubuntu):
status: In Progress → Fix Committed
Nico (nico-rdo) wrote :

Martin,

Thanks again.

After a night of practical use, the fix is sticking to the correct behaviour.

Nico (nico-rdo) wrote :

Hello Martin,

When ca we expect the fix to reach Karmic proper?

Changed in libatasmart (Fedora):
status: In Progress → Fix Released
Changed in libatasmart:
status: Confirmed → Fix Released
AmenophisIII (amenophisiii) wrote :

i was affected too.
after installing libatasmart from the ppa '/usr/lib/devicekit-disks/devkit-disks-helper-ata-smart-collect /dev/sdb 1' does not wake up my ST3250823AS (7200.8) drive anymore, thanks.
pls add this to karmic updates.

petrum (petru-marginean) wrote :

I have the same issue: one of the hdd i use for backups (Hitachi Deskstar T7K250 series, model HDT722525DLA380) wakes up every 30 minutes.

Please help,
Petru

Antti Kaihola (akaihola) wrote :

Petru,

Did you try with libatasmart from the PPA? See #24 above.

See also #11 with a non-elegant work-around.

Martin Pitt (pitti) wrote :

0.17-1 synced into lucid, which fixes this.

Changed in libatasmart (Ubuntu):
status: Fix Committed → Fix Released
AmenophisIII (amenophisiii) wrote :

thanks martin!
is there anything i/we can do, to get this fix backported to karmic?
imho its worth it and the regression potential is quite low, but it seems you think, its not important enough (i may be wrong in all points though :)

without a fix (the ppa is good enough for me personally), i would have to remove one backup harddrive from my pc, because its too noisy, which could lead to loss of data eventually. not exactly what the "user data loss" directive from https://wiki.ubuntu.com/StableReleaseUpdates#When means, i guess, but worth mentioning imo :)

Rich Rauenzahn (rich-shroop) wrote :

On fedora, since they aren't backporting to 11, I've done this in root's cron until I move to 12:

@hourly /usr/bin/killall devkit-disks-daemon > /dev/null 2>&1

Maybe it would work around it on ubuntu as well?

Nico (nico-rdo) wrote :

Rich,

your solution is a bit brutal and removes any service rendered by devkit-disk-daemon. And the smart alerting by default is one of my favorite new features of Karmic. Very elegant.

I want that service on all my disks, even on disks that are normally sleeping, but only when they are awake.

Rich Rauenzahn (rich-shroop) wrote :

I agree a backport is preferable, but until then, the killall is preferable to ruining my drive by having it cycle 100's of times a day (until I upgrade to a release that has the fix.)

If Ubuntu is on a similar roadmap as fedora, they can't backport easily because the ABI/API changed between releases.

Nico (nico-rdo) wrote :

Rich,

There is a PPA above, it has the fix for Karmic, it works. It prevents the wake-up cycles and it still allows for the SMART stuff. Best of both worlds.

Rich Rauenzahn (rich-shroop) wrote :

Ah! I didn't realize PPA == workaround/fix for karmic.

(Fedora User -- I'll be using killall! I also have smartd running in the background, though, which DOES do the right thing.)

Cr0n_J0b (cr0n-j0b) wrote :

I'm seeing the same issue here. with a new build of Karmic. I have drives, WD1000EADS, HDS, Maxtor, seagate. Drives are set to spindown every 20minutes. They are in RAID sets md0, md1 and md2. using mdadm software raid. I applied the updated package from the PPA above and so far (30 minutes) none of the drives have spun up. I'll give it another hour then reboot to see if all the changes are persistent. Thanks for the fast help on this one. I hate the idea of leaving 11 drives spinning in a system that's barely used.

Arlukin (daniel-cybercow) wrote :

Thanks for the PPM fix, it also worked for my Seagate disk.

It also spins up fine when doing the
devkit-disks --ata-smart-refresh /dev/sdb --ata-smart-wakeup

Mossroy (mossroy) wrote :

It looks like the patch works for me too.
My second hard disk (Western Digital WD2000JD of 200Gb) was constantly spinning up and down since the upgrade to karmic.
I had modified /etc/hdparm.conf so that this disk spins down automatically after a few minutes.
It worked great with jaunty, with the hard disk spinninp up only when I wanted to access it. After the upgrade, it was periodically spinning up, even if I did not access to the hard disk at all.
I found this bug and installed the PPA package.

Since then, the hard disk did not spin up periodically : it looks like it solved my problem.
Thanks to all of you who worked on it.

Will this patch be backported for karmic?

Changed in libatasmart (Ubuntu):
status: Fix Released → Confirmed
status: Confirmed → Fix Released
Ian! D. Allen (idallen) wrote :

This bug is three months old, and the fix is two months old, but I can't
find any mention of this bug (or the fix) in the Karmic release notes:

http://www.ubuntu.com/getubuntu/releasenotes/910

Please folks - when you find and fix a problem, be proud of your work and
update the release notes so that the rest of us have a clue what we're
getting into when we install the new release.

This power-up/power-down bug is a disk-killer (24 power-cycles per
day!) and people should know about it and the PPA fix if you aren't
going to push the fix into the regular Karmic update stream.

Thanks to Martin for the PPA.

boga (boga-inbox) wrote :

The PPA version fixed the main problem, however it seems that a smaller problem remains: if drive spin down timeout is 30minutes (or above I suppose) the drive never spins down. Drive is polled while being spinning and it resets the timeout and prevents it from spinning down.
I guess this should at least be documented somehow since it (smaller timeouts work, longer timeout dowsn't) appears like an extremely weird behaviour.

wind (pipilu8) wrote :

Running latest ubuntu 9.10 and this bug still happens. It caused 3000 load/unload counts on my a week old hard drive.

A work around is to comment out

# USB ATA enclosures with a SAT layer
#KERNEL=="sd*[!0-9]", ATTR{removable}=="0", ENV{ID_BUS}=="usb", ENV{DEVTYPE}=="disk", IMPORT{program}="devkit-disks-probe-ata-smart $tempnode"

# ATA disks driven by libata
#KERNEL=="sd*[!0-9]", ATTR{removable}=="0", ENV{ID_BUS}=="ata", ENV{DEVTYPE}=="disk", IMPORT{program}="devkit-disks-probe-ata-smart $tempnode"

in /lib/udev/rules.d/95-devkit-disks.rules

wind (pipilu8) wrote :

By the way, I use smartd once comment out the lines

Changed in libatasmart:
importance: Unknown → Medium
Changed in libatasmart:
importance: Medium → Unknown
Changed in libatasmart:
importance: Unknown → Medium

For those still affected by this issue please compile the attached test case and run
against the suspected disk. If it produces

[189046.000060] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[189046.000075] ata1.00: cmd b0/d1:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in
[189046.000077] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

On demand then let us know so we can duplicate this issue to

https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1092622

TEST CASE:

# sudo apt-get install -y libatasmart-dev
# gcc -o read_thresh_test skreadthreshold.c -latasmart
# sudo ./read_thresh_test /dev/sdX, where X is suspect device

As of 2013, Martin's package is no more in the "PPA" cited in message #38.
I tried to install libatasmart4 from packages.ubuntu.com/saucy/libatasmart4, but it doesn't fix the problem for me.

I'm on Debian 6.0, which doesn't have the updated package in repos (not in "unstable" repo, apparently).
Where can I get the package, preferably the individual "raw" .deb file so to not cause repo conflicts?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.