Lt-Chewie
-
Posts
21 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Lt-Chewie
-
-
The full story is of my drive problem is here.
But the short of it is the drive had REISERFS errors, I used the Western Digital Diagnostic tool and it said too many errors.
So I precleared it twice (picture 1), ran the WD diagnostic tool again and it said the drive was fine.
Then I precleared it one more time (picture 2) so I could add it to the array if needed.
1)
2)
Start:
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 - 547 3 Spin_Up_Time 0x0027 176 174 021 Pre-fail Always - 4191 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 592 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 - 1812 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 93 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 582 194 Temperature_Celsius 0x0022 112 108 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 194 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 194 194 000 Old_age Offline - 2172 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 182 182 000 Old_age Offline - 7276 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 1812 - # 2 Conveyance offline Completed without error 00% 1806 - # 3 Conveyance offline Completed: read failure 90% 1760 1137246032 # 4 Short offline Completed without error 00% 1717 - # 5 Short offline Completed without error 00% 44 -
Finish:
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 - 547 3 Spin_Up_Time 0x0027 176 174 021 Pre-fail Always - 4191 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 592 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 098 098 000 Old_age Always - 1835 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 93 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 12 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 582 194 Temperature_Celsius 0x0022 111 108 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 194 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 194 194 000 Old_age Offline - 2172 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 182 182 000 Old_age Offline - 7276 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 1812 - # 2 Conveyance offline Completed without error 00% 1806 - # 3 Conveyance offline Completed: read failure 90% 1760 1137246032 # 4 Short offline Completed without error 00% 1717 - # 5 Short offline Completed without error 00% 44 -
Looking at this image and the report, it seems the drive is okay right? Or am I missing something?
-
Thank you itimpi and Joe, RMA won't happen since it's past warranty - purchased about 3 or so years ago.
I don't think it's the power-supply as I have precleared other drives with no issues.
I'll just stick this into something unimportant like the NAS for the CCTV at work.
Thanks again for taking the time to look at it
-
Just precleared one of my Samsungs that I had laying about, I think from the numbers in the start and finish files it looks okay but the "pending re-allocation" parts in the report is what concerns me.
I've also attached the start and finish files from the preclears if that is needed.
Any insight as to what I should do with this drive, and perhaps a little understanding of what the last paragraph means for future preclears would be appreciated, thanks.
First 2 cylcle preclear:
========================================================================1.15 == invoked as: ./preclear_disk.sh -A -c 2 /dev/sdb == SAMSUNGHD204UI S2HGJ1BZ828875 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 == Ran 2 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 6:34:59 (84 MB/s) == Last Cycle's Zeroing time : 5:33:53 (99 MB/s) == Last Cycle's Post Read Time : 12:17:30 (45 MB/s) == Last Cycle's Total Time : 17:52:27 == == Total Elapsed Time 42:21:33 == == Disk Start Temperature: 29C == == Current Disk Temperature: 32C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Current_Pending_Sector = 99 100 0 ok 149 No SMART attributes are FAILING_NOW 11 sectors were pending re-allocation before the start of the preclear. 160 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 151 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 149 sectors are pending re-allocation at the end of the preclear, a change of 138 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
Second 2 cycle preclear:
========================================================================1.15 == invoked as: ./preclear_disk.sh -A -c 2 /dev/sdb == SAMSUNGHD204UI S2HGJ1BZ828875 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 == Ran 2 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 6:29:41 (85 MB/s) == Last Cycle's Zeroing time : 5:34:01 (99 MB/s) == Last Cycle's Post Read Time : 12:07:12 (45 MB/s) == Last Cycle's Total Time : 17:42:18 == == Total Elapsed Time 42:05:16 == == Disk Start Temperature: 27C == == Current Disk Temperature: 32C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Current_Pending_Sector = 100 99 0 ok 100 No SMART attributes are FAILING_NOW 149 sectors were pending re-allocation before the start of the preclear. 150 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 149 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 100 sectors are pending re-allocation at the end of the preclear, a change of -49 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================
preclear_start_S2HGJ1BZ828875_2014-07-17.txt
preclear_finish_S2HGJ1BZ828875_2014-07-17.txt
Preclear.sh results - Questions about your results? Post them here.
in User Customizations
Posted
Thanks RobJ, much appreciated.
Saves myself from RMA'ing it and getting a refurbished one back.