RobJ Posted December 21, 2013 Share Posted December 21, 2013 Hi All, Done a big batch of preclearing - can anyone please look at the 3 reports below? The first two are from brand new Seagate NAS drives - have I got lemons? Drive 1 (new Seagate NAS) Drive 2 (new Seagate NAS) Drive 3 (old Seagate) In addition, I still have 2 WDC_WD30EZRX preclearing after 46 hours (one 89% of copying zeros and the other at 3% of the post-read) (sdd and sdf). I have previously had issues trying to preclear these a few days ago where they got stuck late in the post-read process. A third drive I have of exactly the same type successfully precleared after 37 hours with no issues. Attached is a link to the errors and minor issues in the syslog. These drives look like they are in a world of pain. Should I write them off? Sorry for the long post... Any help is very much appreciated The 3 SMART reports look fine, except that the 2 new NAS drives got rather hot. Their temps rose from 25 to 41 which is quite a jump. I suspect they were installed somewhere without any airflow. Nothing wrong with the drives though. That's only a small fragment of the syslog, so hard to draw any conclusions. Whatever drive is sdf has a lot of bad sectors, and the drive sdd has found a single bad sector. I can't tell which drives those are without the earlier part of the syslog, but you can identify them from the UnRAID webgui. Quote Link to comment
RobJ Posted December 21, 2013 Share Posted December 21, 2013 Just want someone to confirm what I see, everything look good to me. 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. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: 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 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2 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 - 81 10 Spin_Retry_Count 0x0032 100 253 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 - 2 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 126 118 000 Old_age Always - 24 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 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged Like someone showing us their report card with all A+'s and all test scores equal to 100, you showed us your perfect SMART report indicating zero problems found and all VALUE's of 100 or better, and then you ask if anyone sees anything wrong??? I think most of us didn't know how to respond. Quote Link to comment
Thermo Posted December 21, 2013 Share Posted December 21, 2013 The 3 SMART reports look fine, except that the 2 new NAS drives got rather hot. Their temps rose from 25 to 41 which is quite a jump. I suspect they were installed somewhere without any airflow. Nothing wrong with the drives though. That's only a small fragment of the syslog, so hard to draw any conclusions. Whatever drive is sdf has a lot of bad sectors, and the drive sdd has found a single bad sector. I can't tell which drives those are without the earlier part of the syslog, but you can identify them from the UnRAID webgui. Thanks for taking a look, it is very much appreciated. I will move the NAS drives around to get them in front of a fan. sdf and sdd are the 2 WDC_WD30EZRX drives... Might be best to give up on them... Quote Link to comment
nanoman06 Posted December 22, 2013 Share Posted December 22, 2013 Can anyone give me an opinion on these resultes? Are the drives bad?no, they look great. are they reliable? Probably... only time will tell. So I should not be worried about the raw read error rate or spin retry count? I have another 3tb that came out with this: == ST3000DM001-1CH166 W1F2YATC == 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_V LUE Raw_Read_Error_Rate = 118 102 6 ok 17262 704 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 77 45 ok 26 Temperature_Celsius = 26 23 0 ok 26 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. root@Storage:/boot# Quote Link to comment
CyberMew Posted December 23, 2013 Share Posted December 23, 2013 Only know how to take some pictures... here is my preclear results from 2 old drives, not sure what they mean...is this the correct results? I don't know how to scroll up to display more information http://i.imgur.com/Br7T9AL.jpg and http://i.imgur.com/nDe1zBo.jpg Quote Link to comment
RobJ Posted December 23, 2013 Share Posted December 23, 2013 Can anyone give me an opinion on these resultes? Are the drives bad?no, they look great. are they reliable? Probably... only time will tell. So I should not be worried about the raw read error rate or spin retry count? Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 I could not improve on Joe's response, as he was absolutely correct. Just a tip, if you are going to question the experts, it would be good to understand the subject matter first? As you can see above, the VALUE's for Spin_Retry_Count and End-to-End_Error are 100, could not be more perfect. The VALUE's for Raw_Read_Error_Rate for 2 of the drives at THIS moment are a little below 100, but are not a problem, they are still a long way from 44. Quote Link to comment
nanoman06 Posted December 23, 2013 Share Posted December 23, 2013 Can anyone give me an opinion on these resultes? Are the drives bad?no, they look great. are they reliable? Probably... only time will tell. So I should not be worried about the raw read error rate or spin retry count? Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 I could not improve on Joe's response, as he was absolutely correct. Just a tip, if you are going to question the experts, it would be good to understand the subject matter first? As you can see above, the VALUE's for Spin_Retry_Count and End-to-End_Error are 100, could not be more perfect. The VALUE's for Raw_Read_Error_Rate for 2 of the drives at THIS moment are a little below 100, but are not a problem, they are still a long way from 44. I believe you misinterpreted the text.. I am unfamiliar with most of the test results. I know that I have had some drives that return with no additional notes above the 0 SMART failures list before. I wasn't sure if he perhaps had missed the notes above the smart tests. These drives were different, they listed a few seemingly not great things. Thank you both for shedding some light on the result from the preclear script. I feel comfortable with filling these drives now Quote Link to comment
CyberMew Posted December 24, 2013 Share Posted December 24, 2013 Only know how to take some pictures... here is my preclear results from 2 old drives, not sure what they mean...is this the correct results? I don't know how to scroll up to display more information http://i.imgur.com/Br7T9AL.jpg and http://i.imgur.com/nDe1zBo.jpg Anyone? Also, why did my 3tb/4tb drive shows MBR in the steps during preclearing? Shouldn't it be GPT? Quote Link to comment
RobJ Posted December 24, 2013 Share Posted December 24, 2013 Only know how to take some pictures... here is my preclear results from 2 old drives, not sure what they mean...is this the correct results? I don't know how to scroll up to display more information http://i.imgur.com/Br7T9AL.jpg and http://i.imgur.com/nDe1zBo.jpg The drive in first pic is troubling, shows 22 new bad sectors AFTER the Post-Read, not good. Preclear it again. Only if after another one or 2 Preclears it appears to be fine should it be considered safe to use. The drive in second pic looks older with some wear, but may be OK at the moment. We really need to check the SMART reports for both drives. All of the reports including the Preclear reports are in a folder on the flash drive. I don't remember the path, but it has 'Preclear' in the name. Quote Link to comment
CyberMew Posted December 25, 2013 Share Posted December 25, 2013 Only know how to take some pictures... here is my preclear results from 2 old drives, not sure what they mean...is this the correct results? I don't know how to scroll up to display more information http://i.imgur.com/Br7T9AL.jpg and http://i.imgur.com/nDe1zBo.jpg The drive in first pic is troubling, shows 22 new bad sectors AFTER the Post-Read, not good. Preclear it again. Only if after another one or 2 Preclears it appears to be fine should it be considered safe to use. The drive in second pic looks older with some wear, but may be OK at the moment. We really need to check the SMART reports for both drives. All of the reports including the Preclear reports are in a folder on the flash drive. I don't remember the path, but it has 'Preclear' in the name. Thanks for the interpretation! I just did 2 preclear on the drive in the first pic, seems ok right? (first) http://i.imgur.com/l6gtXaC.jpg and (second) http://i.imgur.com/RrBr3TU.jpg Also finished a preclear on a brand new 3tb drive: http://i.imgur.com/qjK4g8N.jpg and it also seems ok! Once my fourth drive is done (4tb is taking almost 70 hours now for 2 preclears) I will try to get the text files from the usb drive Quote Link to comment
CyberMew Posted December 25, 2013 Share Posted December 25, 2013 https://dl-web.dropbox.com/get/Public/preclear.zip?w=AAD9Xjb0Ep7PbvIwOO-eKOqV_C5g5NA19z8liLPHpxw78g&dl=1 my results for the 4 drives. 2 preclears of 4TB took almost 73 hours! Let me know if you can't download from the above. Quote Link to comment
Joe L. Posted December 25, 2013 Share Posted December 25, 2013 https://dl-web.dropbox.com/get/Public/preclear.zip?w=AAD9Xjb0Ep7PbvIwOO-eKOqV_C5g5NA19z8liLPHpxw78g&dl=1 my results for the 4 drives. 2 preclears of 4TB took almost 73 hours! Let me know if you can't download from the above. I get Error (403) It seems you don't belong here! Hint: if you make it difficult for us to get to the preclear reports, we are not as likely to perform an analysis. Just zip them up and attach them to your next post. They are in your /boot/preclear_reports directory. Quote Link to comment
CyberMew Posted December 25, 2013 Share Posted December 25, 2013 Didn't think of uploading it as an attachment, sorry! preclear.zip Quote Link to comment
Drider Posted December 27, 2013 Share Posted December 27, 2013 Greetings! I purchased two 3TB drives last week, as the deal was WAY too good to pass up, ($30.00/TB). I'v been running them both through 3 cycles of preclear in which one has finished, (I'll post the (3) resulting files below), but the other is still running. I'm a bit concerned about the second drive as I'll explain below my results of drive one. preclear_rpt_SEGS: ========================================================================1.14 == invoked as: ./preclear_disk.sh -M4 -A -c3 /dev/sdg == TOSHIBADT01ACA300 X3S97SEGS == Disk /dev/sdg has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 6:28:20 (128 MB/s) == Last Cycle's Zeroing time : 5:37:51 (148 MB/s) == Last Cycle's Post Read Time : 12:20:30 (67 MB/s) == Last Cycle's Total Time : 17:59:25 == == Total Elapsed Time 60:29:20 == == Disk Start Temperature: 27C == == Current Disk Temperature: 28C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 214 222 0 ok 28 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. ============================================================================ preclear_start_SEGS: Disk: /dev/sdg smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 3.5" HDD DT01ACA... Device Model: TOSHIBA DT01ACA300 Serial Number: X3S97SEGS LU WWN Device Id: 5 000039 ff4d24bf5 Firmware Version: MX6OABB0 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Tue Dec 24 18:34:07 2013 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (22365) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 373) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 054 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 134 134 024 Pre-fail Always - 425 (Average 427) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 12 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 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 1 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 12 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 12 194 Temperature_Celsius 0x0002 222 222 000 Old_age Always - 27 (Min/Max 20/27) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. preclear_finish_SEGS Disk: /dev/sdg smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 3.5" HDD DT01ACA... Device Model: TOSHIBA DT01ACA300 Serial Number: X3S97SEGS LU WWN Device Id: 5 000039 ff4d24bf5 Firmware Version: MX6OABB0 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Fri Dec 27 07:03:28 2013 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (22365) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 373) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 054 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 134 134 024 Pre-fail Always - 425 (Average 427) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 12 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 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 61 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 12 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 12 194 Temperature_Celsius 0x0002 214 214 000 Old_age Always - 28 (Min/Max 20/30) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Looking at my report(card)s for this drive, am I safe to assume this drive is good for placement in the array? On that note, I really don't know what I'm looking at/for in these reports. Is there an outline of how exactly read these reports? If its already been detailed in this thread, please just say so, and I'll hunt it down, I just didn't want to go through 44 pages of postings to find nothing. Really I'd like to eventually be able to judge the condition of these drives for myself. Now, about the second drive. It's still in the 3rd cycle of preclear in step 2 of 10. Everything was fine and dandy through cycle one of preclear on both drives, and they were both pretty much neck and neck the whole way through. it was in cycle 2 I became concerned as the second drive PLUMMETED in speed on step 2, (went from ~160MB/s to ~55MB/s), all other steps have ran at what appears to be nominal speeds. It again showed the same behavior in cycle 3 as it's currently in step 2 at 77% complete while running 49.3MB/s Again, I'm new to all of this, so maybe my concern is overreaction, but expert opinion/thought/advice on this is most welcome Thanks for all your assistance, -D Quote Link to comment
archedraft Posted December 27, 2013 Share Posted December 27, 2013 Am leaning towards the PSU being the issue. Is there anyway an older motherboard would be the cause of this because the hard drive is 3 TB? I was of the understanding that it shouldn't matter with unRAID but thought I would check anyways. If the disk controller was not compatible with 3TB drives, then it would not work at all, that is, you would not see 3TB available. Yours does appear to work fine. I can't see any connection with the motherboard, because we need a suspect that is able to cause corruption and trouble WITHIN the drive, and that is a very short list. The only possibilities I can think of are power issues, heat issues, or a defective drive (bad firmware). My friends server is running Plex, Sickbeard, and Transmission. Plex updates itself every hour, Sickbeard every 10 minuets, and I am sure Transmission updates it self as well... I guess I will turn off all the plugins and try again before I tell my friend to buy new stuff but the question is, will adding this drive to the array cause problems later on if I turn the plugins back on? Remember that if you discover a relation between a software running and the drive crashing, then that could only point to heavy power draw (perhaps pulling the voltage down too low), and that implicates the power supply (not the software or other hardware), as either too inadequate or too poorly designed. Aerocool makes interesting products (I like some of their cases), but I don't believe they are a good name in power supplies (I could be wrong, I haven't kept up with PSU's recently). I can't help being very suspicious of your PSU. Well my friend replaced his power supply but the preclear still give the same error (here is a link to my earlier post :http://lime-technology.com/forum/index.php?topic=4068.msg275829#msg275829). Thermo posted this a few weeks ago (http://lime-technology.com/forum/index.php?topic=30789.msg278242#msg278242) and had the same issue and indicated that buying a new PSU, motherboard, RAM, and CPU fixed the same error. I was able to successful run preclears on a 1 TB and 500 GB hard drive on his computer before. I am highly suspicious that his old motherboard does not like the fact that the 2 new hard drives are 3 TB... Any more thoughts before I tell him to nuke the computer and upgrade? Quote Link to comment
FreeMan Posted December 28, 2013 Share Posted December 28, 2013 I've just purchased my first 3TB drive and updated from unRAID 4.7 to 5.0.4. I've updated to preclear_disk.sh v 1.14, and when I run it on my 3TB drive, it's hanging. The first try, I kicked it off in 2 seperate putty sessions, one for the 3TB and one for the new 1TB. They got to 7% and 26% completion on the first step (EDIT: Disk Pre-Read) in about 30 minutes, then for the next 30 minutes, the sessions didn't update at all - the percentage didn't increase and the timer never changed. I killed both with a ctrl-c, and attempted to kick off the preclear again, and it told me it couldn't access /dev/sdx for either drive. After rebooting the server (it did properly shut down & restart - it was still very responsive), I tried the same thing again, and it got to the same place. After a 2nd reboot (via the web interface), I kicked off the preclear on only the 3TB, and went to bed. When I got up in the morning, it had made it to 9% of the first phase (don't remember how long it had taken), but it hung there with the clock not counting up as I checked in on it for about 15 min. What logs would someone need to see to get an idea of what's going on? It's not putting anything into the /boot/preclear_reports directory. It's a brand-new, fresh from the box WD30EZRX drive. I've not confirmed that the drive is OK by putting it in another machine, but the fact that it has gotten to 2 different levels of completion leads me to believe that it may not be the disk itself failing/DOA. I'm currently trying the 1TB drive by itself to see if that will run to completion. I'm chasing several niggling little issues as I try to reconfigure everything that was working in 4.7 to get it function in 5.0.4 (SAB, CP, Sick, unMenu, preclear, UPS integration, etc). TIA EDIT: The 1TB drive is now up to 34% complete of the Disk Pre-Read step, so it, at least, seems functional EDIT 2: The 1TB finished its pre-clear and is now a part of the array and is formatting. On to the 3TB... EDIT 3: The 3TB drive seems to preclearing now, it's at 17% and counting. Quote Link to comment
Drider Posted December 28, 2013 Share Posted December 28, 2013 Drive 2 (DBGS) finished sometime early this morning. Again results look ok to me, as they look pretty much identical to drive 1, but feedback is still appreciated. preclear_rpt_DBGS: ========================================================================1.14 == invoked as: ./preclear_disk.sh -M4 -A -c3 /dev/sdf == TOSHIBADT01ACA300 X3S99DBGS == Disk /dev/sdf has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 6:28:52 (128 MB/s) == Last Cycle's Zeroing time : 17:11:58 (48 MB/s) == Last Cycle's Post Read Time : 12:48:26 (65 MB/s) == Last Cycle's Total Time : 30:01:32 == == Total Elapsed Time 84:51:12 == == Disk Start Temperature: 29C == == Current Disk Temperature: 30C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 200 206 0 ok 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 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. ============================================================================ preclear_start_DBGS: Disk: /dev/sdf smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 3.5" HDD DT01ACA... Device Model: TOSHIBA DT01ACA300 Serial Number: X3S99DBGS LU WWN Device Id: 5 000039 ff4d25220 Firmware Version: MX6OABB0 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Tue Dec 24 18:34:07 2013 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (22222) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 371) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 054 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 131 131 024 Pre-fail Always - 438 (Average 439) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 12 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 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 1 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 12 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 12 194 Temperature_Celsius 0x0002 206 206 000 Old_age Always - 29 (Min/Max 21/29) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. preclear_finish_DBGS: Disk: /dev/sdf smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 3.5" HDD DT01ACA... Device Model: TOSHIBA DT01ACA300 Serial Number: X3S99DBGS LU WWN Device Id: 5 000039 ff4d25220 Firmware Version: MX6OABB0 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Dec 28 07:25:19 2013 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (22222) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 371) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 054 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 131 131 024 Pre-fail Always - 438 (Average 439) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 12 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 100 100 020 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 86 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 12 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 12 194 Temperature_Celsius 0x0002 200 200 000 Old_age Always - 30 (Min/Max 21/32) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Thanks! -D Quote Link to comment
Superorb Posted December 29, 2013 Share Posted December 29, 2013 I've never used a Seagate drive in the server, do these results from a 4TB NAS drive look Ok? Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ========================================================================1.14 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == invoked as: ./preclear_disk.sh -c 3 /dev/sdb (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == ST4000VN000-1H4168 Z300W13C (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Disk /dev/sdb has been successfully precleared (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == with a starting sector of 1 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Ran 3 cycles (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Using :Read block size = 8388608 Bytes (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Last Cycle's Pre Read Time : 9:44:21 (114 MB/s) (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Last Cycle's Zeroing time : 8:48:58 (126 MB/s) (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Last Cycle's Post Read Time : 22:17:29 (49 MB/s) (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Last Cycle's Total Time : 31:07:28 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Total Elapsed Time 102:37:54 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Disk Start Temperature: 24C (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == Current Disk Temperature: 25C, (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ============================================================================ (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Raw_Read_Error_Rate = 110 100 6 ok 26758944 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Spin_Retry_Count = 100 100 97 near_thresh 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: End-to-End_Error = 100 100 99 near_thresh 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: High_Fly_Writes = 49 100 0 ok 51 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Temperature_Celsius = 24 24 0 near_thresh 24 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: No SMART attributes are FAILING_NOW (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors were pending re-allocation before the start of the preclear. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors were pending re-allocation after post-read in cycle 1 of 3. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors were pending re-allocation after post-read in cycle 2 of 3. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors are pending re-allocation at the end of the preclear, (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: the number of sectors pending re-allocation did not change. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors had been re-allocated before the start of the preclear. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 0 sectors are re-allocated at the end of the preclear, (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: the number of sectors re-allocated did not change. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ============================================================================ (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ============================================================================ (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == S.M.A.R.T Initial Report for /dev/sdb (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Disk: /dev/sdb (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: === START OF INFORMATION SECTION === (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Device Model: ST4000VN000-1H4168 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Serial Number: Z300W13C (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Firmware Version: SC43 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: User Capacity: 4,000,787,030,016 bytes (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Device is: Not in smartctl database [for details use: -P showall] (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ATA Version is: 9 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ATA Standard is: Not recognized. Minor revision code: 0x001f (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Local Time is: Tue Dec 24 21:29:09 2013 MST (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SMART support is: Available - device has SMART capability. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SMART support is: Enabled (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: === START OF READ SMART DATA SECTION === (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SMART overall-health self-assessment test result: PASSED (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: General SMART Values: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Offline data collection status: (0x00)^IOffline data collection activity (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^Iwas never started. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Self-test execution status: ( 0)^IThe previous self-test routine completed (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^Iwithout error or no self-test has ever (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^Ibeen run. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Total time to complete Offline (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: data collection: ^I^I ( 107) seconds. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Offline data collection (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: capabilities: ^I^I^I (0x73) SMART execute Offline immediate. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^IAuto Offline data collection on/off support. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^ISuspend Offline collection upon new (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^Icommand. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^INo Offline surface scan supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^ISelf-test supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^IConveyance Self-test supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^ISelective Self-test supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SMART capabilities: (0x0003)^ISaves SMART data before entering (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^Ipower-saving mode. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^ISupports SMART auto save timer. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Error logging capability: (0x01)^IError logging supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^IGeneral Purpose Logging supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Short self-test routine (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: recommended polling time: ^I ( 1) minutes. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Extended self-test routine (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: recommended polling time: ^I ( 255) minutes. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Conveyance self-test routine (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: recommended polling time: ^I ( 2) minutes. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SCT capabilities: ^I (0x10bd)^ISCT Status supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^ISCT Error Recovery Control supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^ISCT Feature Control supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ^I^I^I^I^ISCT Data Table supported. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SMART Attributes Data Structure revision number: 10 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Vendor Specific SMART Attributes with Thresholds: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 31360 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 1 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 126 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 1 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 188 Command_Timeout 0x0032 100 253 000 Old_age Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 190 Airflow_Temperature_Cel 0x0022 076 050 045 Old_age Always - 24 (Min/Max 22/24) (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 1 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 194 Temperature_Celsius 0x0022 024 050 000 Old_age Always - 24 (0 22 0 0) (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SMART Error Log Version: 1 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: No Errors Logged (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SMART Self-test log structure revision number 1 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: # 1 Short offline Completed without error 00% 0 - (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SMART Selective self-test log data structure revision number 1 (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 1 0 0 Not_testing (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 2 0 0 Not_testing (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 3 0 0 Not_testing (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 4 0 0 Not_testing (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: 5 0 0 Not_testing (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: Selective self-test flags (0x0): (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: After scanning selected spans, do NOT read-scan remainder of disk. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: If Selective self-test is pending on power-up, resume after 0 minute delay. (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: == (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: ============================================================================ (Misc) Dec 29 04:07:06 unRAID preclear_disk-diff[3847]: (Misc) Quote Link to comment
FreeMan Posted December 29, 2013 Share Posted December 29, 2013 The pre-read hung at 99%. I rummaged through the end of the syslog, and this is what I found: Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 There were a lot of lines like that, and the ones I checked were all the same. Can anyone interpret that for me? I'm not sure what it means beyond, 'not good'. Quote Link to comment
Joe L. Posted December 29, 2013 Share Posted December 29, 2013 It indicates that many disk errors are occurring, and that the linux kernel does not know how to handle them, so it is probably resetting the disk controller each time and trying again. Other than a possible loose cable, I've no idea... but there are lots of other users with similar errors if you search on google for "disk cdb unhandled error" Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Unhandled error code Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] Dec 29 10:36:28 NAS kernel: Result: hostbyte=0x04 driverbyte=0x00 Dec 29 10:36:28 NAS kernel: sd 7:0:0:0: [sdg] CDB: Dec 29 10:36:28 NAS kernel: cdb[0]=0x88: 88 00 00 00 00 01 5d 50 78 00 00 00 00 08 00 00 There were a lot of lines like that, and the ones I checked were all the same. Can anyone interpret that for me? I'm not sure what it means beyond, 'not good'. Yes, not good. Joe L. Quote Link to comment
FreeMan Posted December 30, 2013 Share Posted December 30, 2013 I've been having other issues with the box since upgrading from 4.7 to 5.0.4 and adding 2 drives, so I'll see if I can get those sorted before totally giving up on this drive. On the bright side, I picked up the drive locally at Fry's, so it shouldn't be an issue walking back in to return it as DOA. The drive was on sale for $100 - if it hadn't been just before Christmas, with lots o' cash already spent on presents, I'd have picked up several. EDIT: Seems that it was an issue with the SATA controller card I also purchased. The drive's fine, preclear has finished and parity is now syncing. Quote Link to comment
aspik Posted January 8, 2014 Share Posted January 8, 2014 Hello everybody! I'm about to build my first unraid server based on Lian Li Q25 and SP X7SPA-HF-D525. Currently I have 4 HDDs preclear and wanted to share the results, so that the experts can tell me, if the disks are suitable for unRAID. Below the results for 2 old WD RE4-GP 2TB and 2 refurbished WD RED 3TB Drive1 WD RE4-GP 2TB ========================================================================1.14 == invoked as: ./preclear_disk.sh -c 3 -r 65536 -w 65536 -b 2000 -A /dev/sde == WDCWD2002FYPS-01U1B1 == Disk /dev/sde has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 7:59:46 (69 MB/s) == Last Cycle's Zeroing time : 6:17:28 (88 MB/s) == Last Cycle's Post Read Time : 16:52:26 (32 MB/s) == Last Cycle's Total Time : 23:10:57 == == Total Elapsed Time 78:04:25 == == Disk Start Temperature: 30C == == Current Disk Temperature: 33C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 119 122 0 ok 33 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. Drive2 WD RE4-GP 2TB ========================================================================1.14 == invoked as: ./preclear_disk.sh -c 3 -r 65536 -w 65536 -b 2000 -A /dev/sdd == WDCWD2002FYPS-01U1B1 == Disk /dev/sdd has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 8:01:11 (69 MB/s) == Last Cycle's Zeroing time : 6:21:07 (87 MB/s) == Last Cycle's Post Read Time : 16:55:36 (32 MB/s) == Last Cycle's Total Time : 23:17:46 == == Total Elapsed Time 78:12:19 == == Disk Start Temperature: 32C == == Current Disk Temperature: 36C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 116 120 0 ok 36 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. Drive3 WD RED 3TB ========================================================================1.14 == invoked as: ./preclear_disk.sh -c 3 -r 65536 -w 65536 -b 2000 /dev/sdb == WDCWD30EFRX-68EUZN0 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 9:44:50 (85 MB/s) == Last Cycle's Zeroing time : 7:07:01 (117 MB/s) == Last Cycle's Post Read Time : 19:00:28 (43 MB/s) == Last Cycle's Total Time : 26:08:31 == == Total Elapsed Time 94:20:29 == == Disk Start Temperature: 24C == == Current Disk Temperature: 26C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 124 126 0 ok 26 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. Drive4 WD RED 3TB ========================================================================1.14 == invoked as: ./preclear_disk.sh -c 3 -r 65536 -w 65536 -b 2000 /dev/sdc == WDCWD30EFRX-68EUZN0 == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 9:51:34 (84 MB/s) == Last Cycle's Zeroing time : 7:17:55 (114 MB/s) == Last Cycle's Post Read Time : 19:01:48 (43 MB/s) == Last Cycle's Total Time : 26:20:47 == == Total Elapsed Time 95:24:51 == == Disk Start Temperature: 25C == == Current Disk Temperature: 28C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 122 125 0 ok 28 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. Attached are also the start/finish reports. Are the OK for unRAID? Thanks for your help! preclear_reports.zip Quote Link to comment
Joe L. Posted January 8, 2014 Share Posted January 8, 2014 Hello everybody! I'm about to build my first unraid server based on Lian Li Q25 and SP X7SPA-HF-D525. Currently I have 4 HDDs preclear and wanted to share the results, so that the experts can tell me, if the disks are suitable for unRAID. Below the results for 2 old WD RE4-GP 2TB and 2 refurbished WD RED 3TB They all look great. Enjoy your server. Quote Link to comment
Superorb Posted January 8, 2014 Share Posted January 8, 2014 They all look great. Enjoy your server. Is it normal for the Post Read on all his drives to be nearly half the Preread and Zeroing speeds? Quote Link to comment
BobPhoenix Posted January 8, 2014 Share Posted January 8, 2014 They all look great. Enjoy your server. Is it normal for the Post Read on all his drives to be nearly half the Preread and Zeroing speeds? Yes. Always has been for me anyway. 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.