[opensuse] hdparm -B default (96) causes -> Load_Cycle count now 27X Manuf Recommended
All, Where is the default Advanced Power Management setting for 'hdparm -B' set? I've looked at yast sysconfig and picked through /etc, but cannot find the setting. The allowed hdparm apm are setting from 1-127 allow drive spindown, 128-254 does not allow spindown, 255 disables. $ sudo smartctl -a /dev/sda | grep Load_Cycle 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 1422966 I need to set this setting at a minimum of 128 to prevent further spindown. With the default of 96, since I installed 13.1 on a new 750G laptop drive, I have experienced more than 1.4 million cycles (which exceeds the manufacturer lifecycle estimate of 50,000 -- by a lot, see: https://en.wikipedia.org/wiki/Hard_disk_drive_failure#Landing_zones_and_load...) I didn't install 13.1 until 7/2014 or a bit less than 2 years ago. With the processes running on the laptop, that is one cycle a minute (approximately). Granted, I'm not sure all 1.4 million are complete spindowns or simply some other power-saving feature moving the RW-head to the landing zone, but the Load_Cycle_Count is way above what sounds remotely reasonable for 22 months of drive use. I would like to set apm at some value above 128 to prevent unnecessary spindown. Where can I find where this is set by default and set a new value?? Thanks. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On April 2, 2016 11:51:01 PM PDT, "David C. Rankin"
All,
Where is the default Advanced Power Management setting for 'hdparm -B' set? I've looked at yast sysconfig and picked through /etc, but cannot find the setting. The allowed hdparm apm are setting from 1-127 allow drive spindown, 128-254 does not allow spindown, 255 disables.
$ sudo smartctl -a /dev/sda | grep Load_Cycle 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 1422966
I need to set this setting at a minimum of 128 to prevent further spindown. With the default of 96, since I installed 13.1 on a new 750G laptop drive, I have experienced more than 1.4 million cycles (which exceeds the manufacturer lifecycle estimate of 50,000 -- by a lot, see: https://en.wikipedia.org/wiki/Hard_disk_drive_failure#Landing_zones_and_load...) I didn't install 13.1 until 7/2014 or a bit less than 2 years ago. With the processes running on the laptop, that is one cycle a minute (approximately).
Granted, I'm not sure all 1.4 million are complete spindowns or simply some other power-saving feature moving the RW-head to the landing zone, but the Load_Cycle_Count is way above what sounds remotely reasonable for 22 months of drive use.
I would like to set apm at some value above 128 to prevent unnecessary spindown. Where can I find where this is set by default and set a new value??
Thanks.
Are you certain this 50,000 number actually applies to this device? Who knows how Old the info on that web page is? It would seem that anything of recent manufacture, intended for use in power saving environment would be engineered to handle the number of parking expected in today's usage world. Also, I thought I read somewhere that heads don't actually land anymore. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/03/2016 02:43 AM, John Andersen wrote:
Are you certain this 50,000 number actually applies to this device?
Who knows how Old the info on that web page is?
It would seem that anything of recent manufacture, intended for use in power saving environment would be engineered to handle the number of parking expected in today's usage world.
Also, I thought I read somewhere that heads don't actually land anymore.
John, I've seen 2 numbers. The first number was 600,000 cycles (which I took to be from a recent drive, then found the wiki page and was not sure which was correct) I suspect the 600K number is more correct today. As for whether the heads actually land, I'm not certain either, but what I am certain about is the cycles logged on my drive and the continual spindown/spinup I hear on a regular basis. Obviously, I just let it do its thing for a long time, but I'm noticing longer spinup times now which prompted this search for a permanent solution. I've installed an /etc/hdparm.conf (which I haven't rebooted yet to see if it is read on start, but I'll report back if it is) It will be interesting to find out what the best solution for this is. It looks like an issue that has been languishing in need to some easier user control setting. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/05/2016 10:45 AM, David C. Rankin wrote:
On 04/03/2016 02:43 AM, John Andersen wrote:
Are you certain this 50,000 number actually applies to this device?
Who knows how Old the info on that web page is?
It would seem that anything of recent manufacture, intended for use in power saving environment would be engineered to handle the number of parking expected in today's usage world.
Also, I thought I read somewhere that heads don't actually land anymore.
John,
I've seen 2 numbers. The first number was 600,000 cycles (which I took to be from a recent drive, then found the wiki page and was not sure which was correct) I suspect the 600K number is more correct today. As for whether the heads actually land, I'm not certain either, but what I am certain about is the cycles logged on my drive and the continual spindown/spinup I hear on a regular basis. Obviously, I just let it do its thing for a long time, but I'm noticing longer spinup times now which prompted this search for a permanent solution.
I've installed an /etc/hdparm.conf (which I haven't rebooted yet to see if it is read on start, but I'll report back if it is)
It will be interesting to find out what the best solution for this is. It looks like an issue that has been languishing in need to some easier user control setting.
Are you in a habit of turning off atime on your laptops? As far as I know, atime even affects cached files, and keeps drives spinning up and down frequently. But this might be obsolete information from years past. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/05/2016 01:08 PM, John Andersen wrote:
Are you in a habit of turning off atime on your laptops?
As far as I know, atime even affects cached files, and keeps drives spinning up and down frequently. But this might be obsolete information from years past.
No, I've never done it. It may be worth looking into to see if that is still a valid defense. I'll report back if it is still a viable solution. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2016-04-05 21:18, David C. Rankin wrote:
On 04/05/2016 01:08 PM, John Andersen wrote:
Are you in a habit of turning off atime on your laptops?
As far as I know, atime even affects cached files, and keeps drives spinning up and down frequently. But this might be obsolete information from years past.
No,
I've never done it. It may be worth looking into to see if that is still a valid defense. I'll report back if it is still a viable solution.
No, that's a different thing. What atime causes is that every read operation of a file (which already powers up the drive) involves an extra write operation, to record the time you accessed the file. Of course, a read of a cached file causes a write on the directory listing, an operation which is cached for a limited time itself. This should have no effect on a normal hard disk with a sleep time which could be ten or twenty minutes. It is a problem on disks with aggressive sleep strategy of a few seconds - which is the case with yours. The default nowdays is to mount "relatime" instead. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Hi David! Am Sonntag, 3. April 2016, 01:51:01 CEST schrieb David C. Rankin:
Where is the default Advanced Power Management setting for 'hdparm -B' set? I've looked at yast sysconfig and picked through /etc, but cannot find the setting. The allowed hdparm apm are setting from 1-127 allow drive spindown, 128-254 does not allow spindown, 255 disables.
$ sudo smartctl -a /dev/sda | grep Load_Cycle 193 Load_Cycle_Count 0x0032 001 001 000 Old_age Always - 1422966
I need to set this setting at a minimum of 128 to prevent further spindown. With the default of 96, since I installed 13.1 on a new 750G laptop drive, I have experienced more than 1.4 million cycles (which exceeds the manufacturer lifecycle estimate of 50,000 -- by a lot, see: https://en.wikipedia.org/wiki/Hard_disk_drive_failure#Landing_zones_and_load .2Funload_technology) I didn't install 13.1 until 7/2014 or a bit less than 2 years ago. With the processes running on the laptop, that is one cycle a minute (approximately).
Granted, I'm not sure all 1.4 million are complete spindowns or simply some other power-saving feature moving the RW-head to the landing zone, but the Load_Cycle_Count is way above what sounds remotely reasonable for 22 months of drive use.
I would like to set apm at some value above 128 to prevent unnecessary spindown. Where can I find where this is set by default and set a new value??
Looks like you have one of many drives the have a broken firmware. openSUSE has a special package named storage-fixup, that reconfigures your drive so that this does not happen, presupposed it is contained in the list of known broken devices. With so many Load_Cycles you can consider your drive close before failure. Better you replace it soon. All this happened with one of my drives, too. It was part of a RAID1, so I was save as it failed. Two other drives showed the same symptoms, but storage- fixup saved them. Herbert
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 04/03/2016 04:17 AM, Herbert Graeber wrote:
Looks like you have one of many drives the have a broken firmware. openSUSE has a special package named storage-fixup, that reconfigures your drive so that this does not happen, presupposed it is contained in the list of known broken devices.
With so many Load_Cycles you can consider your drive close before failure. Better you replace it soon.
All this happened with one of my drives, too. It was part of a RAID1, so I was
save as it failed. Two other drives showed the same symptoms, but storage- fixup saved them.
Herbert
Thanks Herbert, But unbelievably my drive is not one contained in /etc/storage-fixup.conf e.g. $ sudo smartctl -a /dev/sda smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.11.10-29-desktop] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD7500BPVX-22JC3T0 Serial Number: WD-WX61EC3RSP88 <snip> $ grep WDC /etc/storage-fixup.conf # Reported drive model: WDC WD2500BEVS-75UST0 ata model WDC WD*BEVS* # Reported drive model: WDC WD2500BEVS-75UST0 ata model WDC WD*BEVS* # Reported drive model: WDC WD1600BEVT-75ZCT0 ata model WDC WD*BEVT* # Reported drive model: WDC WD1600BEVE-00UYT0 ata model WDC WD*BEVE* # Reported drive model: WDC WD1200BEVE-00WZT0 ata model WDC WD*BEVE* # Reported drive model: WDC WD3200BEVT-22ZCT0 ata model WDC WD*BEVT* # Reported drive model: WDC WD1600BEVT-22ZCT0 ata model WDC WD*BEVT* # Reported drive model: WDC WD3200BEVT-22ZCT0 ata model WDC WD*BEVE* I would need a 'WDC WD*BPVX*' and that's nowhere to be found :( I'm crossing my finger the /etc/hdparm.conf will work: $ cat /etc/hdparm.conf /dev/sda { apm = 161 } ( 161 is just a unique number to check after reboot, I'll probably stick with 160 or 192 if it works ) - -- David C. Rankin, J.D.,P.E. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlcD+9sACgkQZMpuZ8CyrcipFQCcDPM5oNGXk/a7xataOMhTgM8v lbwAoJGGmk5uSTdKyKxsga/xjOrrrg6+ =7yha -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Apr 5, 2016 at 1:54 PM, David C. Rankin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/03/2016 04:17 AM, Herbert Graeber wrote:
Looks like you have one of many drives the have a broken firmware. openSUSE has a special package named storage-fixup, that reconfigures your drive so that this does not happen, presupposed it is contained in the list of known broken devices.
With so many Load_Cycles you can consider your drive close before failure. Better you replace it soon.
All this happened with one of my drives, too. It was part of a RAID1, so I was
save as it failed. Two other drives showed the same symptoms, but storage- fixup saved them.
Herbert
Thanks Herbert,
But unbelievably my drive is not one contained in /etc/storage-fixup.conf
I don't think storage-fixup upstream has seen any updates in 5 years, so it isn't surprising your new drive isn't in there. I'd just add it. Or you can add it to this minimalistic patch openSUSE maintains for the config file: https://build.opensuse.org/package/view_file/Base:System/storage-fixup/stora... BTW: WD adds an extra zero in their model numbers 5 years ago, so the WDC WD3200BEVT-22ZCT0 is a 320 GB drive, not a a 3.2 TB drive. I don't know if they still do that or not. Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/05/2016 01:06 PM, Greg Freemyer wrote:
On Tue, Apr 5, 2016 at 1:54 PM, David C. Rankin
Thanks Herbert,
But unbelievably my drive is not one contained in /etc/storage-fixup.conf
I don't think storage-fixup upstream has seen any updates in 5 years, so it isn't surprising your new drive isn't in there.
I'd just add it. Or you can add it to this minimalistic patch openSUSE maintains for the config file:
https://build.opensuse.org/package/view_file/Base:System/storage-fixup/stora...
BTW: WD adds an extra zero in their model numbers 5 years ago, so the WDC WD3200BEVT-22ZCT0 is a 320 GB drive, not a a 3.2 TB drive.
I don't know if they still do that or not.
Greg -- Greg Freemyer www.IntelligentAvatar.net
Thanks Greg, I'll give this a try as well: # Reported drive model: WDC WD7500BPVX-22JC3T0 rule toshiba-p205d dmi system-manufacturer TOSHIBA dmi system-product-name Satellite p205d ata model WDC WD*BPVX* act hdparm -B 192 $DEV I hope the 'rule' ... is just a unique identifier taken from the config file -- as it was just invented... Any thought on that issue? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Apr 5, 2016 at 3:16 PM, David C. Rankin
On 04/05/2016 01:06 PM, Greg Freemyer wrote:
On Tue, Apr 5, 2016 at 1:54 PM, David C. Rankin
Thanks Herbert,
But unbelievably my drive is not one contained in /etc/storage-fixup.conf
I don't think storage-fixup upstream has seen any updates in 5 years, so it isn't surprising your new drive isn't in there.
I'd just add it. Or you can add it to this minimalistic patch openSUSE maintains for the config file:
https://build.opensuse.org/package/view_file/Base:System/storage-fixup/stora...
BTW: WD adds an extra zero in their model numbers 5 years ago, so the WDC WD3200BEVT-22ZCT0 is a 320 GB drive, not a a 3.2 TB drive.
I don't know if they still do that or not.
Greg -- Greg Freemyer www.IntelligentAvatar.net
Thanks Greg,
I'll give this a try as well:
# Reported drive model: WDC WD7500BPVX-22JC3T0 rule toshiba-p205d dmi system-manufacturer TOSHIBA dmi system-product-name Satellite p205d ata model WDC WD*BPVX* act hdparm -B 192 $DEV
I hope the 'rule' ... is just a unique identifier taken from the config file -- as it was just invented... Any thought on that issue?
My uneducated guess is that you're right. Not sure that helps any. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R. -
David C. Rankin -
Greg Freemyer -
Herbert Graeber -
John Andersen