- Jun 12, 2012
- 1
- 0
- 10,510
I had my computer ask me to manually run fsck today for the first time since I got it about 3.5 years ago. My setup is:
OS: Arch Linux (not that it's that relevant to the question)
Disk: WD WD10EARX (WD Green) 1TB hard drive
Partition type: ext4
I'm not entirely sure what caused the need for fsck, but it apparently was bad enough that I needed to tell it to fix about 50 items (bad inodes, incorrect bitmap things, etc). I then ran smart and got the following:
The two numbers that have me wondering are the Load_Cycle_Count and the Power_On_Hours. While 10,000 hours isn't a terrible number for a hard drive, the 200,000 load cycles has me nervous. Until about a year ago, the drive was having issues hanging up every 7-9 seconds and that number went up quite quickly (I believe linux touches the drive every couple of seconds, but the power saving "feature" of the wd drive is that it hangs up when nobody touches it after a couple seconds...so it would hang up, get touched, hang up, get touched, etc). I then used some dos wd tool that modified the timeout so that this wouldn't happen as often and it has stayed about the same.
I read somewhere that the designed number of head load cycles was 300,000 for WD Green drives. My question is: Is my drive near death right now?
I've only ever had hard drives fail from temperature and such and since this one has lasted this long, it's likely that any manufacturing defect will not cause it to fail.
OS: Arch Linux (not that it's that relevant to the question)
Disk: WD WD10EARX (WD Green) 1TB hard drive
Partition type: ext4
I'm not entirely sure what caused the need for fsck, but it apparently was bad enough that I needed to tell it to fix about 50 items (bad inodes, incorrect bitmap things, etc). I then ran smart and got the following:
Code:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 117 111 021 Pre-fail Always - 7125
4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2436
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 087 087 000 Old_age Always - 10137
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2421
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 233
193 Load_Cycle_Count 0x0032 134 134 000 Old_age Always - 200727
194 Temperature_Celsius 0x0022 112 104 000 Old_age Always - 35
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 198 000 Old_age Always - 20
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0The two numbers that have me wondering are the Load_Cycle_Count and the Power_On_Hours. While 10,000 hours isn't a terrible number for a hard drive, the 200,000 load cycles has me nervous. Until about a year ago, the drive was having issues hanging up every 7-9 seconds and that number went up quite quickly (I believe linux touches the drive every couple of seconds, but the power saving "feature" of the wd drive is that it hangs up when nobody touches it after a couple seconds...so it would hang up, get touched, hang up, get touched, etc). I then used some dos wd tool that modified the timeout so that this wouldn't happen as often and it has stayed about the same.
I read somewhere that the designed number of head load cycles was 300,000 for WD Green drives. My question is: Is my drive near death right now?
I've only ever had hard drives fail from temperature and such and since this one has lasted this long, it's likely that any manufacturing defect will not cause it to fail.
Facebook
Twitter
Instagram