itimpi Posted August 20, 2014 Share Posted August 20, 2014 ...I started such a wiki tool, found at Understanding SMART Reports. ... RobJ - great job! Great info so far, and once complete this will be an outstanding resource!!! I will be adding a link from myMain. I agree. I am hoping that the descriptions for reallocated sectors and pending sectors get added ASAP as these are the ones that are probably of most importance to unRAID users. I would think that some sort of colour coding to indicate ones that are of particular interest would help. Quote Link to comment
squirrellydw Posted August 23, 2014 Share Posted August 23, 2014 So looking at this I know it passed and looks good to me. My question is the first part. Do i have to worry about any of that? Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 108 117 6 ok 19015016 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 83 87 0 ok 17 Airflow_Temperature_Cel = 68 70 45 near_thresh 32 Temperature_Celsius = 32 30 0 ok 32 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 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. 0 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. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. Quote Link to comment
StevenD Posted August 27, 2014 Share Posted August 27, 2014 I received some new HGST "NAS" drives this week. Model # H3IKNAS40003272SN (0S03664). This the fastest pre-clear I have seen on a spinner. Quote Link to comment
iveo83 Posted September 6, 2014 Share Posted September 6, 2014 I was told to post this here with my smart reports. I put all 3 in the same file separated by a line. I'm thinking about doing another 2 passes though. Pre-Clear_Smart_Report.txt Quote Link to comment
RobJ Posted September 7, 2014 Share Posted September 7, 2014 I was told to post this here with my smart reports. I put all 3 in the same file separated by a line. I'm thinking about doing another 2 passes though. All 3 drives look great. Quote Link to comment
Lt-Chewie Posted September 8, 2014 Share Posted September 8, 2014 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? Quote Link to comment
RobJ Posted September 9, 2014 Share Posted September 9, 2014 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. [images snipped] Looking at this image and the report, it seems the drive is okay right? Or am I missing something? The first Preclear forced the drive to deal with all of the marginal sectors, and when it tested them the drive found that ALL of the sectors were physically good, so put them back online. The drive is fine. Quote Link to comment
Lt-Chewie Posted September 9, 2014 Share Posted September 9, 2014 Thanks RobJ, much appreciated. Saves myself from RMA'ing it and getting a refurbished one back. Quote Link to comment
JHTom Posted September 9, 2014 Share Posted September 9, 2014 Question on preclearing a Seagate 6TB drive. The pre read time and post read time, and thus the cycle total time seem high to me. In addition, the read rate versus the zeroing rate seems out of whack when compared with smaller drives I have done. Anything to be concerned about here (results attached)? Seagate_6TB.txt Quote Link to comment
RobJ Posted September 9, 2014 Share Posted September 9, 2014 Question on preclearing a Seagate 6TB drive. The pre read time and post read time, and thus the cycle total time seem high to me. In addition, the read rate versus the zeroing rate seems out of whack when compared with smaller drives I have done. Anything to be concerned about here (results attached)? SMART report looks fine. It's hard to say what the times should be for a 6tb drive, until other reports come in. Doesn't look wildly wrong though. You used Preclear 1.9, which is very old, probably too old for very large drives. I'm not sure you can trust the result on drives over 2TB using any Preclear less than 1.13, and perhaps Preclear 1.15 (the latest). You should definitely upgrade Preclear, and you may want to try it again. At least, try a Preclear -t test on it, with the latest Preclear. Quote Link to comment
JHTom Posted September 9, 2014 Share Posted September 9, 2014 Question on preclearing a Seagate 6TB drive. The pre read time and post read time, and thus the cycle total time seem high to me. In addition, the read rate versus the zeroing rate seems out of whack when compared with smaller drives I have done. Anything to be concerned about here (results attached)? SMART report looks fine. It's hard to say what the times should be for a 6tb drive, until other reports come in. Doesn't look wildly wrong though. You used Preclear 1.9, which is very old, probably too old for very large drives. I'm not sure you can trust the result on drives over 2TB using any Preclear less than 1.13, and perhaps Preclear 1.15 (the latest). You should definitely upgrade Preclear, and you may want to try it again. At least, try a Preclear -t test on it, with the latest Preclear. Thanks Quote Link to comment
Joe L. Posted September 10, 2014 Share Posted September 10, 2014 Question on preclearing a Seagate 6TB drive. The pre read time and post read time, and thus the cycle total time seem high to me. In addition, the read rate versus the zeroing rate seems out of whack when compared with smaller drives I have done. Anything to be concerned about here (results attached)? SMART report looks fine. It's hard to say what the times should be for a 6tb drive, until other reports come in. Doesn't look wildly wrong though. You used Preclear 1.9, which is very old, probably too old for very large drives. I'm not sure you can trust the result on drives over 2TB using any Preclear less than 1.13, and perhaps Preclear 1.15 (the latest). You should definitely upgrade Preclear, and you may want to try it again. At least, try a Preclear -t test on it, with the latest Preclear. unRAID will NOT consider the disk pre-cleared. (the older version of the preclear script did not know how to properly create the preclear signature for disks over 2.2TB. ) A clue is that it says the partition starts on sector 64. That is completely WRONG for any disk over 2.2TB. Now, the disk did get zeroed, and does look good, but it does not contain a valid "protective" MBR starting on sector 1, nor a valid unRAID precleared signature. If you attempted to assign it to an array already protected by parity, unRAID will clear it again. (while the array is kept off-line) Joe l. Quote Link to comment
nanoman06 Posted September 16, 2014 Share Posted September 16, 2014 Thank you all who have helped in the past! I have two more drives I'd like to ask about ========================================================================1.14 == ST3000DM001- XXXXXXWA == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 112 100 6 ok 48827176 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 71 70 45 ok 29 Temperature_Celsius = 29 30 0 ok 29 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. ========================================================================1.14 == ST3000DM001-1CH166 XXXXXX44 == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 100 6 ok 74792176 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 70 70 45 near_thresh 30 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. These came out of the box and were ran through 5 cycles as I normally do. Are these drives worthy of joining my array or do they need to go back into the box? Do these issues mean something when they are presented at the same time? (dropped during shipping?) Quote Link to comment
Joe L. Posted September 16, 2014 Share Posted September 16, 2014 Thank you all who have helped in the past! I have two more drives I'd like to ask about ========================================================================1.14 == ST3000DM001- XXXXXXWA == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 112 100 6 ok 48827176 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 71 70 45 ok 29 Temperature_Celsius = 29 30 0 ok 29 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. ========================================================================1.14 == ST3000DM001-1CH166 XXXXXX44 == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 100 6 ok 74792176 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 70 70 45 near_thresh 30 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. These came out of the box and were ran through 5 cycles as I normally do. Are these drives worthy of joining my array or do they need to go back into the box? Do these issues mean something when they are presented at the same time? (dropped during shipping?) What issues are you seeing in those reports? They look just fine to me, in fact, the raw-read-error rate IMPROVED on both drives from starting values of 100 to 112 and 114. Joe L. Quote Link to comment
nanoman06 Posted September 16, 2014 Share Posted September 16, 2014 OH, cool. I incorrectly assumed that was a bad direction..lol. Some day I should really learn to read these reports.. Quote Link to comment
JHTom Posted September 16, 2014 Share Posted September 16, 2014 I wanted to post updated results of Seagate 6TB Preclear using Preclear 1.15 for reference (I think drive looks good). Seagate_6TB.txt Quote Link to comment
RobJ Posted September 17, 2014 Share Posted September 17, 2014 I wanted to post updated results of Seagate 6TB Preclear using Preclear 1.15 for reference (I think drive looks good). It does look good, Precleared correctly too, ready to go on line. Quote Link to comment
Moussa Posted September 19, 2014 Share Posted September 19, 2014 ========================================================================1.15 == invoked as: ./preclear_disk.sh -A -c 3 /dev/sdd == ST3000DM001-1CH166 Z1F51MFZ == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 6:42:28 (124 MB/s) == Last Cycle's Zeroing time : 5:00:57 (166 MB/s) == Last Cycle's Post Read Time : 12:06:13 (68 MB/s) == Last Cycle's Total Time : 17:08:10 == == Total Elapsed Time 58:23:11 == == Disk Start Temperature: 31C == == Current Disk Temperature: 38C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 100 6 ok 161579360 Seek_Error_Rate = 60 100 30 ok 1116436 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 98 100 0 ok 2 Airflow_Temperature_Cel = 62 69 45 near_thresh 38 Temperature_Celsius = 38 31 0 ok 38 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. ============================================================================ Just to confirm, these results look good right? Quote Link to comment
JustinChase Posted September 23, 2014 Share Posted September 23, 2014 I'm trying to preclear a drive that had red-balled on my, but I suspect it was just due to a cabling issue. I've since replaced that drive with a larger one, and am now trying to preclear the drive that 'failed' to confirm I can add it back to the array. I've put a stock version of unraid 6beta9 on a newly formatted USB, and put it and the drive into a different computer for this process. I've booted and started the process, and it seems to have started fine, but the onscreen info is showing it to be going VERY slow. Current stats are Disk Pre-Read in progress: 0% complete ( 4,201,881,600 bytes of 2,000,398,934,016 read ) 3.7 MB/s Disk Temperature: 36C, Elapsed Time 1:02:50 by my calculations, it's only .2% done, and will take about 500 hours to finish just the pre-read. Obviously something is wrong (3.7MB/s is not good). So, is this an indication that the drive is just bad after all, or is there possibly something else at play here? Ideas on how to proceed? Quote Link to comment
archedraft Posted September 23, 2014 Share Posted September 23, 2014 Just throwing out wild $#@ guesses but I wonder if it could be a beta 9 issue. You could try install unRAID 5 to rule that out. Quote Link to comment
JustinChase Posted September 23, 2014 Share Posted September 23, 2014 That's a good idea. It can't hurt, right Quote Link to comment
JustinChase Posted September 23, 2014 Share Posted September 23, 2014 initial signs are that this was not the problem. it started out at 27.7 MB/s, quickly dropped to 8.6, and now I'm waiting to see the next update. This seems to be the same as the last time I ran it. I wonder if this might do any better if I formatted it in windows, then tried pre-clearing it. I may need to see how to run a smart report on it, so see if it's 'okay' per SMART. Quote Link to comment
RobJ Posted September 23, 2014 Share Posted September 23, 2014 ========================================================================1.15 == invoked as: ./preclear_disk.sh -A -c 3 /dev/sdd == ST3000DM001-1CH166 Z1F51MFZ == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 1000448 Bytes == Last Cycle's Pre Read Time : 6:42:28 (124 MB/s) == Last Cycle's Zeroing time : 5:00:57 (166 MB/s) == Last Cycle's Post Read Time : 12:06:13 (68 MB/s) == Last Cycle's Total Time : 17:08:10 == == Total Elapsed Time 58:23:11 == == Disk Start Temperature: 31C == == Current Disk Temperature: 38C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 100 6 ok 161579360 Seek_Error_Rate = 60 100 30 ok 1116436 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 98 100 0 ok 2 Airflow_Temperature_Cel = 62 69 45 near_thresh 38 Temperature_Celsius = 38 31 0 ok 38 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 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. ============================================================================ Just to confirm, these results look good right? Looks good. Quote Link to comment
RobJ Posted September 23, 2014 Share Posted September 23, 2014 I'm trying to preclear a drive that had red-balled on my, but I suspect it was just due to a cabling issue. I've since replaced that drive with a larger one, and am now trying to preclear the drive that 'failed' to confirm I can add it back to the array. I've put a stock version of unraid 6beta9 on a newly formatted USB, and put it and the drive into a different computer for this process. I've booted and started the process, and it seems to have started fine, but the onscreen info is showing it to be going VERY slow. Current stats are Disk Pre-Read in progress: 0% complete ( 4,201,881,600 bytes of 2,000,398,934,016 read ) 3.7 MB/s Disk Temperature: 36C, Elapsed Time 1:02:50 by my calculations, it's only .2% done, and will take about 500 hours to finish just the pre-read. Obviously something is wrong (3.7MB/s is not good). So, is this an indication that the drive is just bad after all, or is there possibly something else at play here? Ideas on how to proceed? Edit: I apologize, I've just noticed elsewhere that you have included a syslog. [respectful chide mode on] It was hard to know how to respond. You have a drive that had been red-balled, and was now running extremely slowly, and yet it does not appear that you thought to check or include a SMART report and the syslog, which would normally be stuffed with reasons for the problem. I do understand this may be your first drive issue, but it still was very disappointing. I'm not blaming you, those of us who are veteran UnRAID users, including LimeTech staff, have to take some responsibility for not doing a very good educational job. We need to do a much better job making sure ALL users, both new and experienced, know what a syslog is, why it's so useful, and how to capture it, and the same with SMART reports. They are admittedly hard to interpret, but there are many here ready and willing to help with that. If we had done a good job, and a problem like this arose, every users first thought would be "something is wrong, let's see what the syslog says". Perhaps we need more stickied troubleshooting help posts. Perhaps the initial ReadMe needs an 'UnRAID Troubleshooting 101' section... There have been a number of cases like this lately, where the syslog was needed yet the user never thought of it. Just throwing out wild $#@ guesses but I wonder if it could be a beta 9 issue. You could try install unRAID 5 to rule that out. This too was disappointing. It's like someone has a shed on fire, and someone else says "I wonder if that strange foreign family down the street did this", leading to rumors and distrust. Please don't cast aspersions on something without a single shred of evidence. Beta 9 is working fine for most, and I don't know of any reports of slow drives with it, and slow drives are a relatively common issue. I'd venture to say that at this very moment, around the entire world, there are hundreds of thousands of very slow drives occurring, using many different operating system versions. Many of them are problems with the drives, and the others are problems with the interface to those drives. A syslog or comparable diagnostic will clarify the issue. [chide mode off] Quote Link to comment
JustinChase Posted September 23, 2014 Share Posted September 23, 2014 I'm trying to preclear a drive that had red-balled on my, but I suspect it was just due to a cabling issue. I've since replaced that drive with a larger one, and am now trying to preclear the drive that 'failed' to confirm I can add it back to the array. I've put a stock version of unraid 6beta9 on a newly formatted USB, and put it and the drive into a different computer for this process. I've booted and started the process, and it seems to have started fine, but the onscreen info is showing it to be going VERY slow. Current stats are Disk Pre-Read in progress: 0% complete ( 4,201,881,600 bytes of 2,000,398,934,016 read ) 3.7 MB/s Disk Temperature: 36C, Elapsed Time 1:02:50 by my calculations, it's only .2% done, and will take about 500 hours to finish just the pre-read. Obviously something is wrong (3.7MB/s is not good). So, is this an indication that the drive is just bad after all, or is there possibly something else at play here? Ideas on how to proceed? Edit: I apologize, I've just noticed elsewhere that you have included a syslog. [respectful chide mode on] It was hard to know how to respond. You have a drive that had been red-balled, and was now running extremely slowly, and yet it does not appear that you thought to check or include a SMART report and the syslog... [chide mode off] I understand your frustration, but since this is a fresh install, only being used to pre-clear, and the pre-clear was/is still running, I don't know of any way to get a syslog at this time. i suppose I could stop the pre-clear, and get a syslog, and considering how slowly it's moving, I don't suppose I really lose much by doing this. Currently, the pre-read is only 2% complete after 4 hours. If that's all the faster this drive is now able to function, it's useless to me, so I could just trash it. I posted in the hopes that the thorough information/history that I included might provide enough clues to be useful. I also mentioned in my follow up post that I may need to learn how to do a smart report, because I don't know how to do that right now. I cancelled the preclear. syslog and short smart test log attached. to my uneducated eye, it doesn't look good... Thanks for your help. syslog.txt smartshort.txt Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.