search for: reallocated_sector_ct

...> >> >> Folks >> >> I've encountered situations where I want to reuse a hard-drive. I do If it is a Seagate, don't bother. They have the highest failure rate in the industry. Look at the SMART statistics before deciding to re-use a disk, especially "Reallocated_Sector_Ct," "Power_On_Hours," and run the "extended SMART test." Todd Merriman Software Toolz, Inc.

...HEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 115 075 006 Pre-fail Always - 94384069 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 15 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 084 060 030 Pre-fail Always - 263091894 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 4050 10 Spin_Retry_Count 0x0013 100 100...

...N_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 067 063 044 Pre-fail Always - 6218970 3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 14 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 21 7 Seek_Error_Rate 0x000f 091 060 030 Pre-fail Always - 1433294073 9 Power_On_Hours 0x0032 090 090 000 Old_age Always - 8825 10 Spin_Retry_Count 0x0013 100...

...;>>Folks >>>I've encountered situations where I want to reuse a hard-drive. I do > >If it is a Seagate, don't bother. They have the highest failure >rate in the industry. > >Look at the SMART statistics before deciding to re-use a disk, >especially "Reallocated_Sector_Ct," >"Power_On_Hours," and run the "extended SMART test." > >Todd Merriman >Software Toolz, Inc. Todd The reason I'm reusing a disk is not because of hardware failures, but rather because I've abandoned a particular use for that disk, maybe changed ope...

...D WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 185 183 021 Pre-fail Always - 7750 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 075 075 000 Old_age Always - 18868 10 Spin_Retry_Count 0x0012 100 253 000...

...think) the important bits of the smartctl output for $(smartctl -a /dev/sdb) (the full results are attached): ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 253 006 Pre-fail Always - 0 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 086 060 030 Pre-fail Always - 440801014 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 0...

...- 0 2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 115 115 024 Pre-fail Always - 188 (Average 194) 4 Start_Stop_Count 0x0012 099 099 000 Old_age Always - 4026 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 9 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 097 097 000 Ol...

...- 0 2 Throughput_Performance 0x0005 133 133 054 Pre-fail Offline - 138 3 Spin_Up_Time 0x0007 142 142 024 Pre-fail Always - 178 (Average 109) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 120 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 139 139 020 Pre-fail Offline - 26 9 Power_On_Hours 0x0012 100 100 000 Old_...

...to and from it just to see if it was OK. I left it there, waiting for an opportunity to configure it to do real work. Now I have looked at it with smartctl -a and it gives me the following info: 1 Raw_Read_Error_Rate 0x0033 104 104 050 Pre-fail Always - 9127078 5 Reallocated_Sector_Ct 0x0033 100 100 003 Pre-fail Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 55 (241 12 0) 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 7 13 Read_Soft_Error_Rate 0x0032 104 10...

Hi List, What this means? md: syncing RAID array md0 md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc. md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction. md: using 128k window, over a total of 2096384 blocks. md: md0: sync done. RAID1 conf printout: --- wd:2 rd:2 disk 0, wo:0, o:1, dev:sda2 disk 1, wo:0, o:1, dev:sdb2 sd 0:0:0:0:

...D WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1091 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 15 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 523 10 Spin_Retry_Count 0x0032 100 253 000...

...WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 114 107 021 Pre-fail Always - 7283 4 Start_Stop_Count 0x0032 091 091 000 Old_age Always - 9764 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 080 080 000 Old_age Always - 14907 10 Spin_Retry_Count 0x0032 100 100 000...

...HEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 191 189 021 Pre-fail Always - 7425 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 184 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 9 Power_On_Hours 0x0032 062 062 000 Old_age Always - 28012 10 Spin_Retry_Count 0x0012 100 100 051...

...EN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 181943016 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 17 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 39599363 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 821 10 Spin_Retry_Count 0x0013 100 100...

...W_VALUE > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always > - 0 > 3 Spin_Up_Time 0x0027 114 107 021 Pre-fail Always > - 7283 > 4 Start_Stop_Count 0x0032 091 091 000 Old_age Always > - 9764 > 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 080 080 000 Old_age Always > - 14907 > 10 Spin_Retry_Count 0x0032 100 1...

...N_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 185 170 021 Pre-fail Always - 1716 4 Start_Stop_Count 0x0032 067 067 000 Old_age Always - 33362 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 098 098 000 Old_age Always - 2129 10 Spin_Retry_Count 0x0032 100 100 051...

Folks I've encountered situations where I want to reuse a hard-drive. I do not want to preserve anything on the drive, and I'm not concerned about 'securely erasing' old content. I just want to be able to define it as an Physical Volume (in a logical volume set), or make it a ZFS disk, or sometimes make it a simple EXT3, ExFAT or NTFS disk. However, old

...EN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 062 061 044 Pre-fail Always - 173060773 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 17 5 Reallocated_Sector_Ct 0x0033 089 089 036 Pre-fail Always - 243 7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail Always - 27793554 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 5695 10 Spin_Retry_Count 0x0013 100 100...

Hello list I've been running the following command, first in fc20 and then now (since the beginning of March) in fc26: now=$(date +"%Y%m%d-%H%M"); sudo rsync -ahuAESX -vi /home/ /run/media/readlegal/Backup/home > /run/media/readlegal/Backup/rsync-changes_$now Since the move to fc26, this command has caused the complete freeze/crash of the system. I tried it under multi-user

On Sun, Jan 17, 2016 at 10:05 AM, Matt Garman <matthew.garman at gmail.com> wrote: > I'm not sure what's going on with your drive. But if it were mine, I'd want > to replace it. If there are issues, that long smart check ought to turn up > something, and in my experience, that's enough for a manufacturer to do a > warranty replacement. I agree with Matt. Go