Superorb Posted April 22, 2011 Share Posted April 22, 2011 ^^ How much RAM do you have, and are you running more than 1 preclear at the same time? Quote Link to comment
victurbo Posted April 22, 2011 Share Posted April 22, 2011 ^^ How much RAM do you have, and are you running more than 1 preclear at the same time? 2 - 1 gig sticks. My first few attempts were trying to preclear all 3 drives simultaneously via Screen. After those failed I began attempting each drive individually via Screen, then individual drives locally while swapping SATA ports and cables. All results ended with the same lockups eventually. Quote Link to comment
Superorb Posted April 22, 2011 Share Posted April 22, 2011 2 - 1 gig sticks. My first few attempts were trying to preclear all 3 drives simultaneously via Screen. After those failed I began attempting each drive individually via Screen, then individual drives locally while swapping SATA ports and cables. All results ended with the same lockups eventually. Did you change any of the settings in the BIOS, anything to do with the SATA controller? Quote Link to comment
victurbo Posted April 22, 2011 Share Posted April 22, 2011 2 - 1 gig sticks. My first few attempts were trying to preclear all 3 drives simultaneously via Screen. After those failed I began attempting each drive individually via Screen, then individual drives locally while swapping SATA ports and cables. All results ended with the same lockups eventually. Did you change any of the settings in the BIOS, anything to do with the SATA controller? My first attempts were with default settings, then I found the board BIOS recommendations from unRAID wiki: Set the OnChip SATA Type to AHCI Disable SATA IDE Combined Mode Same results either way. Quote Link to comment
Superorb Posted April 22, 2011 Share Posted April 22, 2011 That's really weird then. Hopefully Joe or Raj can help you out as I've never used that board or drives before. Quote Link to comment
RockDawg Posted April 23, 2011 Share Posted April 23, 2011 I just ran a preclear cycle on a drive that's been in my array for ~18 months. I did this because it showed disabled in my array after a power outage. Here are the results: =========================================================================== = unRAID server Pre-Clear disk /dev/sdi = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Elapsed Time: 14:46:22 ============================================================================ == == Disk /dev/sdi has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 50c50 < 1 Raw_Read_Error_Rate 0x000f 103 093 006 Pre-fail Always - 55633165 --- > 1 Raw_Read_Error_Rate 0x000f 103 093 006 Pre-fail Always - 0 54c54 < 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 136059092 --- > 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 140644518 58,60c58,60 < 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 15391 < 190 Airflow_Temperature_Cel 0x0022 076 051 045 Old_age Always - 24 (Lifetime Min/Max 21/24) < 195 Hardware_ECC_Recovered 0x001a 056 052 000 Old_age Always --- > 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 22207 > 190 Airflow_Temperature_Cel 0x0022 070 051 045 Old_age Always - 30 (Lifetime Min/Max 21/31) > 195 Hardware_ECC_Recovered 0x001a 070 052 000 Old_age Always ============================================================================ Anything to be worried about there? Quote Link to comment
Joe L. Posted April 24, 2011 Share Posted April 24, 2011 I just ran a preclear cycle on a drive that's been in my array for ~18 months. I did this because it showed disabled in my array after a power outage. Here are the results: =========================================================================== = unRAID server Pre-Clear disk /dev/sdi = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Elapsed Time: 14:46:22 ============================================================================ == == Disk /dev/sdi has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 50c50 < 1 Raw_Read_Error_Rate 0x000f 103 093 006 Pre-fail Always - 55633165 --- > 1 Raw_Read_Error_Rate 0x000f 103 093 006 Pre-fail Always - 0 54c54 < 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 136059092 --- > 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 140644518 58,60c58,60 < 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 15391 < 190 Airflow_Temperature_Cel 0x0022 076 051 045 Old_age Always - 24 (Lifetime Min/Max 21/24) < 195 Hardware_ECC_Recovered 0x001a 056 052 000 Old_age Always --- > 189 High_Fly_Writes 0x003a 001 001 000 Old_age Always - 22207 > 190 Airflow_Temperature_Cel 0x0022 070 051 045 Old_age Always - 30 (Lifetime Min/Max 21/31) > 195 Hardware_ECC_Recovered 0x001a 070 052 000 Old_age Always ============================================================================ Anything to be worried about there? Nothing to worry about. Looks fine, but you used a very old version of the preclear script. You should get the newest one. Joe L. Quote Link to comment
RockDawg Posted April 24, 2011 Share Posted April 24, 2011 Thanks. Yah, I need updated it and unmenu. Which reminds me, thanks for your great contributions to unraid! Quote Link to comment
Wild_Pony Posted April 24, 2011 Share Posted April 24, 2011 Hello, I just precleared a drive before I add it to may array. I got errors and I don't know if it is bad or not : 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 100 100 051 Pre-fail Always - 1 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 068 067 025 Pre-fail Always - 9830 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 63 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 73 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 59 181 Program_Fail_Cnt_Total 0x0022 100 100 000 Old_age Always - 1860 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 6 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 29 (Lifetime Min/Max 19/33) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 1 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 78 The Raw_Read_Error_Rate and the UDMA_CRC_Error_Count kind of worry me but I'm not an expert at all and I want to be sure, so if someone can enlighten me it would me much appreciated. (I ran another preclear on this disk to see if ther is any more errors) Thank you! Quote Link to comment
Wild_Pony Posted April 24, 2011 Share Posted April 24, 2011 Damn the other disk seems to have errors too : 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 100 100 051 Pre-fail Always - 0 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 067 025 Pre-fail Always - 10007 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 124 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 138 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 90 181 Program_Fail_Cnt_Total 0x0022 100 100 000 Old_age Always - 1273 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 2 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 059 000 Old_age Always - 30 (Lifetime Min/Max 19/41) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 7 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 143 I find nowhere the explanations for this kind of errors, is this bad or can I add it anyway in my array? Quote Link to comment
prostuff1 Posted April 24, 2011 Share Posted April 24, 2011 Your drives are fine, and if you search back through this thread you would find and lot of posts like yours. It appears you are using an older version of the preclear script also, I suggest updating it. Quote Link to comment
Wild_Pony Posted April 24, 2011 Share Posted April 24, 2011 Your drives are fine, and if you search back through this thread you would find and lot of posts like yours. It appears you are using an older version of the preclear script also, I suggest updating it. I read most of this subject but I probably missed useful things, sorry. This is very hard for newbies to have a clear view about all that happens in preclear, maybe if someone nice enough would do some kind of FAQ/WIKI/recap post about it, it would avoid seemingly stupid and redundant questions like mine (if anything clear and reachable had been written about it, I would undoubtly had read it). Something like : ... G-Sense_Error_Rate : Not to be taken care of Power-Off_Retract_Count : Check PSU if to many errors ... and so on I don't know anything about it but I guess it would not take hours to do and it would be an interesting knowledge database for very new users like me. The thing a bout the outdated preclear script is much more annoying to me cause I downloaded it not a week ago from what seemed to me the official preclear thread (this one : http://lime-technology.com/forum/index.php?topic=2817.0). Quote Link to comment
prostuff1 Posted April 24, 2011 Share Posted April 24, 2011 Your drives are fine, and if you search back through this thread you would find and lot of posts like yours. It appears you are using an older version of the preclear script also, I suggest updating it. I read most of this subject but I probably missed useful things, sorry. This is very hard for newbies to have a clear view about all that happens in preclear, maybe if someone nice enough would do some kind of FAQ/WIKI/recap post about it, it would avoid seemingly stupid and redundant questions like mine (if anything clear and reachable had been written about it, I would undoubtly had read it). Something like : ... G-Sense_Error_Rate : Not to be taken care of Power-Off_Retract_Count : Check PSU if to many errors ... and so on I don't know anything about it but I guess it would not take hours to do and it would be an interesting knowledge database for very new users like me. The thing a bout the outdated preclear script is much more annoying to me cause I downloaded it not a week ago from what seemed to me the official preclear thread (this one : http://lime-technology.com/forum/index.php?topic=2817.0). If my post came across harsh or anything of the sort I apologize. I did not mean it that way. The FAQ, wiki thing is a good idea but it takes time to put together and I know I do not have the time to do it right now. The newest version of preclear has a nice "report" that is printed at the end of the clear process that points out anything that might be of concern. Quote Link to comment
Wild_Pony Posted April 24, 2011 Share Posted April 24, 2011 If my post came across harsh or anything of the sort I apologize. I did not mean it that way. The FAQ, wiki thing is a good idea but it takes time to put together and I know I do not have the time to do it right now. The newest version of preclear has a nice "report" that is printed at the end of the clear process that points out anything that might be of concern. It's not coming harsh, I also apologize if mine sounded like I was complaining. Like I said, every answer is truly appreciated. The problem is that it is very difficult for a newbie not to drown as there is so many parameters to take care of while installing and running unRAID. Lots of them are greatly documented and as I said in my presentation post, even an average PC user can do it without much trouble providing he follows the steps and read as much as he can the main subjects. Preclear is one of the most important script and that's why I think it should be better documented, to avoid having every newbie coming her and asking for million-times-answered questions. As far as I read, it doesn't seem to be a lot of truly important lines to worry about in the preclear log, but it is very hard to find what's relevant in a 58 pages and very technical thread. For the "report" is this something like this ? : ============================================================================ 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. ============================================================================ Quote Link to comment
Joe L. Posted April 24, 2011 Share Posted April 24, 2011 That report is generated because the raw smart report is very difficult to interpert. The raw numbers are meaningless to anybody but the manufacturer. I know the thread is long, but it is because the disks are so important to us. Quote Link to comment
Wild_Pony Posted April 25, 2011 Share Posted April 25, 2011 I know the thread is long, but it is because the disks are so important to us. Of course. This is why we use unRAID at the first place : secure datas. That report is generated because the raw smart report is very difficult to interpert. The raw numbers are meaningless to anybody but the manufacturer. So if nothing appears suspicious in this report, we can say that everything is fine with the disk an doesn't worry about the other values? Thank you Quote Link to comment
arcane Posted April 25, 2011 Share Posted April 25, 2011 Just pre-cleared three drives and was wondering if everything is OK? Or should I run some additional cycles on the Seagate drives? Thanks! ========================================================================1.9 == invoked as: ./preclear_disk.sh -M 4 /dev/sdb == SAMSUNG HE103UJ S13VJ1NQ700004 == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:26:40 (80 MB/s) == Last Cycle's Zeroing time : 3:05:45 (89 MB/s) == Last Cycle's Post Read Time : 6:43:34 (41 MB/s) == Last Cycle's Total Time : 13:17:02 == == Total Elapsed Time 13:17:02 == == Disk Start Temperature: 21C == == 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 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 79 0 ok 26 Temperature_Celsius = 75 73 0 ok 25 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. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sdb == Disk: /dev/sdb smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net ========================================================================1.9 == invoked as: ./preclear_disk.sh -M 4 /dev/sdc == ST31500341AS 9VS070GD == Disk /dev/sdc has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 4:28:47 (93 MB/s) == Last Cycle's Zeroing time : 4:10:28 (99 MB/s) == Last Cycle's Post Read Time : 9:32:32 (43 MB/s) == Last Cycle's Total Time : 18:12:55 == == Total Elapsed Time 18:12:55 == == Disk Start Temperature: 35C == == Current Disk Temperature: 30C, == ============================================================================ ** 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 = 110 114 6 ok 27804642 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 59 86 0 ok 41 Airflow_Temperature_Cel = 70 65 45 near_thresh 30 Temperature_Celsius = 30 35 0 ok 30 Hardware_ECC_Recovered = 54 40 0 ok 27804642 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. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sdc == Disk: /dev/sdc smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net ========================================================================1.9 == invoked as: ./preclear_disk.sh -M 4 /dev/sdd == ST31500341AS 9VS0AK9C == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 4:23:55 (94 MB/s) == Last Cycle's Zeroing time : 4:25:01 (94 MB/s) == Last Cycle's Post Read Time : 9:24:00 (44 MB/s) == Last Cycle's Total Time : 18:14:03 == == Total Elapsed Time 18:14:03 == == Disk Start Temperature: 36C == == Current Disk Temperature: 32C, == ============================================================================ ** 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 = 105 113 6 ok 8274288 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 93 95 0 ok 7 Airflow_Temperature_Cel = 68 64 45 near_thresh 32 Temperature_Celsius = 32 36 0 ok 32 Hardware_ECC_Recovered = 54 33 0 ok 8274288 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. 3 sectors had been re-allocated before the start of the preclear. 3 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sdd == Disk: /dev/sdd smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Quote Link to comment
madburg Posted April 25, 2011 Share Posted April 25, 2011 Some disk controllers do not like the default "-d ata" argumant passed to the smartctl command. The preclear_disk.sh program was unable to read the smart information therefor, that part of its output report is meaningless. You might be able to type: smartctl -a /dev/sdb and see if it will respond. If that works then you can use the "-D" option to the preclear_disk.sh script. preclear_disk.sh -D -M 4 /dev/sdb if not, you might be able to supply an alternate device type using the "-d" option: -D = disable "-d ata" used as argument to smartctl -d device_type = supply "-d device_type" to smartctl used to get device status This is not really an issue with the preclear script, but one with the smartctl program and your disk controller. Joe L. How are you JoeL, sort of a question/request based on a previous post quoted above. I have been working with many LSI chipset controllers and will be posting to contribute as soon as I am finished. The usage of the –D option with these SAS/SATA controllers allows the preclear_disk script to run exactly (right? It seems it’s the same to me SMART before and after reports are inculded) as it does without the –D on regular SATA controllers. Would there be a way to see what controller the drive is tied too OR detect the SMART failure and then proceed to attempt to run via –D on its own? There by automating it to the next level for members. Quote Link to comment
Joe L. Posted April 25, 2011 Share Posted April 25, 2011 Would there be a way to see what controller the drive is tied too OR detect the SMART failure and then proceed to attempt to run via –D on its own? There by automating it to the next level for members. Probably can detect the failure and try without the "-d ata" Not a bad idea for the next version. Thanks for the feedback. Quote Link to comment
madburg Posted April 25, 2011 Share Posted April 25, 2011 Would there be a way to see what controller the drive is tied too OR detect the SMART failure and then proceed to attempt to run via –D on its own? There by automating it to the next level for members. Probably can detect the failure and try without the "-d ata" Not a bad idea for the next version. Thanks for the feedback. Thank you Quote Link to comment
BRiT Posted April 25, 2011 Share Posted April 25, 2011 At this point on unRAID 5.0 I'd go the other way ... try running smartctl without any "-d" options at all and detect errors to try it with "-d ata". Quote Link to comment
Whaler_99 Posted April 26, 2011 Share Posted April 26, 2011 I just tried to preclear a disk on one of my HighPoint RocketRaid cards, which have worked fine before, but now getting some weird issues. Command I used was: preclear_disk.sh -D -M 4 /dev/sdb And got the following back: Pre-Clear unRAID Disk /dev/sdb ################################################################## 1.9 smartctl may not be able to run on /dev/sdb. however this should not affect the clearing of a disk. smartctl exit status = 4 smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green family Device Model: WDC WD5000AAVS-00G9B1 Serial Number: WD-WCAUF2042515 Firmware Version: 05.04C05 User Capacity: 500,107,862,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Apr 26 00:14:01 2011 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Error SMART Status command failed Please get assistance from http://smartmontools.sourceforge.net/ A mandatory SMART command failed: exiting. To continue, add one or more '-T perm issive' options.$ Do you wish to continue? (Answer Yes to continue. Capital 'Y', lower case 'es'): But, if I go into unMenu -> Disk Management and run the Smart Status, works fine. (attached) I "assume" this drive is fine and just an issue with the preclear script and the smartctl command. Shawn smart.txt Quote Link to comment
arcane Posted April 27, 2011 Share Posted April 27, 2011 Just pre-cleared a new, unused WD Caviar Black drive. Although it looks fine, the temperature has me a bit concerned. Am I interpreting it correctly... that the temperature went over 100C at some point? The interim reports I received all averaged about 35C. Maybe it has something to do with me preclearing 20 disks at once? Will post results of other drives when finished. Thanks for looking. ========================================================================1.9 == invoked as: ./preclear_disk.sh -M 4 /dev/sdi == WDC WD2001FASS-00W2B0 WD-WMAY00412287 == Disk /dev/sdi has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 5:37:34 (98 MB/s) == Last Cycle's Zeroing time : 4:59:27 (111 MB/s) == Last Cycle's Post Read Time : 12:23:18 (44 MB/s) == Last Cycle's Total Time : 23:01:26 == == Total Elapsed Time 23:01:26 == == Disk Start Temperature: 35C == == Current Disk Temperature: -->46<--C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 106 117 0 ok 46 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. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sdi == Disk: /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD2001FASS-00W2B0 Serial Number: WD-WMAY00412287 Firmware Version: 05.01D05 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon Apr 25 17:27:53 2011 PDT 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: (29280) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) SCT Status 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 0x002f 100 253 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 - 6 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 - 0 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 - 5 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 13 194 Temperature_Celsius 0x0022 117 114 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 253 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 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. == ============================================================================ ============================================================================ == == S.M.A.R.T Final Report for /dev/sdi == Disk: /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD2001FASS-00W2B0 Serial Number: WD-WMAY00412287 Firmware Version: 05.01D05 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Tue Apr 26 16:29:18 2011 PDT 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: (29280) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) SCT Status 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 0x002f 200 199 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 - 6 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 - 18 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 - 5 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 15 194 Temperature_Celsius 0x0022 106 104 000 Old_age Always - 46 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 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. == ============================================================================ Quote Link to comment
Superorb Posted April 27, 2011 Share Posted April 27, 2011 ^^ I believe those values over 100 are just the cryptic values that manufacturers use. I doubt your drive was above 100C, that's over 212F. Quote Link to comment
arcane Posted April 27, 2011 Share Posted April 27, 2011 ^^ I believe those values over 100 are just the cryptic values that manufacturers use. I doubt your drive was above 100C, that's over 212F. Just wanted some confirmation that I wasn't crazy. Didn't think it could reach those temps no matter how brief... 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.