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. -- Disk wakes up every 30 minutes and produces errors on dmesg https://bugs.launchpad.net/bugs/435190 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
