Disk wakes up every 30 minutes and produces errors on dmesg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libatasmart |
Fix Released
|
Medium
|
|||
libatasmart (Fedora) |
Fix Released
|
Medium
|
|||
libatasmart (Ubuntu) |
Fix Released
|
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:
[189046.000077] res 40/00:00:
[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:
[190844.988597] res 40/00:00:
[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.
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.
Changed in devicekit-disks (Ubuntu): | |
importance: | Undecided → Low |
Changed in libatasmart (Fedora): | |
status: | Unknown → In Progress |
Changed in libatasmart: | |
status: | Unknown → Confirmed |
Changed in libatasmart (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in libatasmart (Fedora): | |
status: | In Progress → Fix Released |
Changed in libatasmart: | |
status: | Confirmed → Fix Released |
Changed in libatasmart (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in libatasmart (Ubuntu): | |
status: | Fix Released → Confirmed |
status: | Confirmed → Fix Released |
Changed in libatasmart: | |
importance: | Unknown → Medium |
Changed in libatasmart: | |
importance: | Medium → Unknown |
Changed in libatasmart: | |
importance: | Unknown → Medium |
Changed in libatasmart (Fedora): | |
importance: | Unknown → Medium |
Created attachment 336227
"sysctl -w vm.block_dump=1" activity for sdb
Description of problem:
I have an internal SATA drive (sdb) that I only use for backups; it is otherwise unmounted. I have it set to spin down when idle.
Recently, I noticed taht the drive is not spinning down. I checked to see what was accessing it using "sysctl -w vm.block_dump=1" (see the attached who-io.log). It appeared to be devkit- disks-part- id.
I ran "devkit-disks --monitor-detail" (see attached devkit.log), and it appears that deviceKit is polling smart data, which keeps the drive from spinning down.
The device is not removable, and it's not in the list of polled drives:
# ps -Afl | grep devkit-disks-daemon | grep -v grep devkit- disks-daemon disks-daemon: polling /dev/sdg /dev/sdf /dev/sr0 /dev/sde /dev/sr1 /dev/sdd
4 S root 4326 1 0 80 0 - 0 poll_s 17:23 ? 00:00:02 /usr/libexec/
1 S root 4382 4326 0 80 0 - 0 poll_s 17:23 ? 00:00:03 devkit-
Version-Release number of selected component (if applicable):
DeviceKit- disks-003- 7.fc11. x86_64 003-1.x86_ 64 power-006- 3.fc11. x86_64
DeviceKit-
DeviceKit-
How reproducible:
Always
Steps to Reproduce:
1.Unmount a drive
2.Set the spin down time
3.Watch nothing happen
Actual results:
Drives stay spun up, even when unmounted
Expected results:
Drives should spin down
Additional info: