[ Keep me CCd on this, please. ]I have the same disks, only with more warranty and supposedly "enterprise" firmware (WD1000FYPS). The bug is the same, though, on all four of them (~ 9 cycles /hour): 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 917 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 8025 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 906 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 7908 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 907 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 8051 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 918 193 Load_Cycle_Count 0x0032 198 198 000 Old_age Always - 7869 Have they confirmed it's a bug? I have no idea how often the disks should do that. Why? Using a DOS boot disk once would not be that bad as a workaround, would it? Or is the setting not persistent? Either way I'd prefer to be able to leave the feature on (in usable form), eventually. The bigger question is - why the rapid loads / unloads? In my case the disks are idle hours at a time. No system files on there, just bulk data. Does / could the controller (sata_sil24 in my case) have any influence on this kind of power management? Thanks, C. --
| Andreas Gruenbacher | Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching |
| Alan Cox | Re: [patch 7/8] fdmap v2 - implement sys_socket2 |
| Jens Axboe | Re: regression: CD burning (k3b) went broke |
| Paul E. McKenney | Re: [PATCH 0/24] make atomic_read() behave consistently across all architectures |
git: | |
| KOSAKI Motohiro | [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| David Miller | [GIT]: Networking |
| Alexey Dobriyan | [PATCH 09/33] netns ct: per-netns /proc/net/nf_conntrack, /proc/net/stat/nf_conntr... |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
