dgaschk Posted September 16, 2010 Share Posted September 16, 2010 Power-Off_Retract_Count is usually the count of how many times the disk heads were retracted in a power loss. Load_Cycle_Count is how many times the disk heads are loaded from their parked position. Both counts incremented by 1. (as if the disk lost power, it retracted the disk heads, then power was restored, and it re-loaded them) I'd look for a loose power connection to the drive. Or, it could be your power supply is not up to the task, or you have a bad splitter, back-plane, card-rack, etc... It is not normal to see those counts increment in a pre-clear cycle. I will check the cables. I'm running a new US budget box build. Is there any reason the 400W power supply is not enough? We have no idea... How many disks do you have attached, how many are "green"? What specific 400 Watt supply? Is it a single 12 Volt rail supply? Joe L. CORSAIR CMPSU-400CX 400W Power supply This has a single 12v rail. The spec for the US budget box build said that this will support up to 12 green drives. I have only 5 drives in the box. 2 of which are green. I expect that by the time I have 12 drives they will all be green. I noticed that the budget build now specifies a 430W power supply. Can anyone advise on how many green drives total this can support in addition to 3 non-green drives? What procedure can I use to isolate this problem? I plan to reseat the power cables and rerun the test. Quote Link to comment
dgaschk Posted September 16, 2010 Share Posted September 16, 2010 Maxtor 6L250R0 =========================================================================== = unRAID server Pre-Clear disk /dev/hdd = 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 Disk Temperature: 33C, Elapsed Time: 5:53:32 ============================================================================ == == Disk /dev/hdd 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 58c58 < 8 Seek_Time_Performance 0x0027 249 243 187 Pre-fail Always - 64056 --- > 8 Seek_Time_Performance 0x0027 252 243 187 Pre-fail Always - 43285 70c70 < 201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 2 --- > 201 Soft_Read_Error_Rate 0x000a 253 252 000 Old_age Always - 0 ============================================================================ root@192:/boot# Are these SMART changes meaningful? Quote Link to comment
Joe L. Posted September 16, 2010 Share Posted September 16, 2010 Are these SMART changes meaningful? No, they are perfectly normal. In neither parameter is the "Current Normalized value" anywhere near the failure threshold. Quote Link to comment
Blofeld Posted September 16, 2010 Share Posted September 16, 2010 Hello there, here's the result of my 3 drives after one cycle pre-clear (all Samsung F2 2TB green). I hope it looks alright, as I wanna get going with copying my stuff over to my unRaid box Anyone wanna take a glimpse at the log? And another question, is it necessary to keep the Telnet window on my main computer open, or can I kick off a pre-clear, and log out (and later back in)? Or is it enough to just monitor it off the syslog? (Probably a stupid questions, but bear with me, I'm a newbie) Thanks for the great script, Joe L.! sdb Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Disk /dev/sdb has been successfully precleared Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Ran 1 preclear-disk cycle Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Using :Read block size = 8225280 Bytes Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Last Cycle's Pre Read Time : 7:40:08 (72 MB/s) Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Last Cycle's Zeroing time : 7:22:08 (75 MB/s) Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Last Cycle's Post Read Time : 16:36:40 (33 MB/s) Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Last Cycle's Total Time : 31:40:21 Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Total Elapsed Time 31:40:21 Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Disk Start Temperature: 30C Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Current Disk Temperature: 32C, Sep 16 03:55:29 Tower preclear_disk-diff[26249]: == Sep 16 03:55:29 Tower preclear_disk-diff[26249]: ============================================================================ Sep 16 03:55:29 Tower preclear_disk-diff[26249]: S.M.A.R.T. error count differences detected after pre-clear Sep 16 03:55:29 Tower preclear_disk-diff[26249]: note, some 'raw' values may change, but not be an indication of a problem Sep 16 03:55:29 Tower preclear_disk-diff[26249]: 55c55 Sep 16 03:55:29 Tower preclear_disk-diff[26249]: < 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 Sep 16 03:55:29 Tower preclear_disk-diff[26249]: --- Sep 16 03:55:29 Tower preclear_disk-diff[26249]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 68 Sep 16 03:55:29 Tower preclear_disk-diff[26249]: 67c67 Sep 16 03:55:29 Tower preclear_disk-diff[26249]: < 195 Hardware_ECC_Recovered 0x003a 252 252 000 Old_age Always Sep 16 03:55:29 Tower preclear_disk-diff[26249]: --- Sep 16 03:55:29 Tower preclear_disk-diff[26249]: > 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always Sep 16 03:55:29 Tower preclear_disk-diff[26249]: 72c72 Sep 16 03:55:29 Tower preclear_disk-diff[26249]: < 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 Sep 16 03:55:29 Tower preclear_disk-diff[26249]: --- Sep 16 03:55:29 Tower preclear_disk-diff[26249]: > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 1 Sep 16 03:55:29 Tower preclear_disk-diff[26249]: ============================================================================ Sep 16 03:55:29 Tower preclear_disk-diff[26249]: sdc Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Disk /dev/sdc has been successfully precleared Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Ran 1 preclear-disk cycle Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Using :Read block size = 8225280 Bytes Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Last Cycle's Pre Read Time : 11:00:36 (50 MB/s) Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Last Cycle's Zeroing time : 7:30:56 (73 MB/s) Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Last Cycle's Post Read Time : 16:44:40 (33 MB/s) Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Last Cycle's Total Time : 35:17:38 Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Total Elapsed Time 35:17:38 Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Disk Start Temperature: 29C Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Current Disk Temperature: 31C, Sep 16 07:37:45 Tower preclear_disk-diff[11816]: == Sep 16 07:37:45 Tower preclear_disk-diff[11816]: ============================================================================ Sep 16 07:37:45 Tower preclear_disk-diff[11816]: S.M.A.R.T. error count differences detected after pre-clear Sep 16 07:37:45 Tower preclear_disk-diff[11816]: note, some 'raw' values may change, but not be an indication of a problem Sep 16 07:37:45 Tower preclear_disk-diff[11816]: 55c55 Sep 16 07:37:45 Tower preclear_disk-diff[11816]: < 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0 Sep 16 07:37:45 Tower preclear_disk-diff[11816]: --- Sep 16 07:37:45 Tower preclear_disk-diff[11816]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 64 Sep 16 07:37:45 Tower preclear_disk-diff[11816]: ============================================================================ Sep 16 07:37:45 Tower preclear_disk-diff[11816]: sda Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Disk /dev/sda has been successfully precleared Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Ran 1 preclear-disk cycle Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Using :Read block size = 8225280 Bytes Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Last Cycle's Pre Read Time : 11:07:59 (49 MB/s) Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Last Cycle's Zeroing time : 7:42:48 (72 MB/s) Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Last Cycle's Post Read Time : 16:57:28 (32 MB/s) Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Last Cycle's Total Time : 35:49:40 Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Total Elapsed Time 35:49:40 Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Disk Start Temperature: 29C Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Current Disk Temperature: 30C, Sep 16 08:02:18 Tower preclear_disk-diff[12872]: == Sep 16 08:02:18 Tower preclear_disk-diff[12872]: ============================================================================ Sep 16 08:02:18 Tower preclear_disk-diff[12872]: S.M.A.R.T. error count differences detected after pre-clear Sep 16 08:02:18 Tower preclear_disk-diff[12872]: note, some 'raw' values may change, but not be an indication of a problem Sep 16 08:02:18 Tower preclear_disk-diff[12872]: 55c55 Sep 16 08:02:18 Tower preclear_disk-diff[12872]: < 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 0 Sep 16 08:02:18 Tower preclear_disk-diff[12872]: --- Sep 16 08:02:18 Tower preclear_disk-diff[12872]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 47 Quote Link to comment
Blofeld Posted September 16, 2010 Share Posted September 16, 2010 I found this in another thread, I guess it answers that one part of my question.. You can log in via telnet multiple times from your PC or MAC, and in each session invoke one preclear script. Or, if you log in at the system console, (assuming you have a monitor and keyboard attached) you can switch between 6 different "system consoles" using "Alt-F1" through "Alt-F6". You can log in on each in turn, cd to /boot, and invoke one clear operation on each, each on a different disk. Quote Link to comment
Joe L. Posted September 16, 2010 Share Posted September 16, 2010 Hello there, here's the result of my 3 drives after one cycle pre-clear (all Samsung F2 2TB green). I hope it looks alright, as I wanna get going with copying my stuff over to my unRaid box Anyone wanna take a glimpse at the log? All the disks look fine. You can also install "screen" It allows you to connect and disconnect from terminal sessions without terminating the processes running on them. Quote Link to comment
Blofeld Posted September 16, 2010 Share Posted September 16, 2010 Thanks for your input, Joe L.! Quote Link to comment
Blofeld Posted September 16, 2010 Share Posted September 16, 2010 I just realized one thing: after pre-clearing, and before assigning the disks, can I swap the SATA cables for host 1 and host 2? i.e., as of now, I have sata 1 connected to disk 2 and vice versa, and I wanna get that in order before I start, just for organization's sake. Or will it mess with something if I do that? Quote Link to comment
Joe L. Posted September 16, 2010 Share Posted September 16, 2010 I just realized one thing: after pre-clearing, and before assigning the disks, can I swap the SATA cables for host 1 and host 2? i.e., as of now, I have sata 1 connected to disk 2 and vice versa, and I wanna get that in order before I start, just for organization's sake. Or will it mess with something if I do that? Do not swap cables and add drives at the same time. Do it as two steps. Stop array Power down Swap Cables Power Up Re-assign drives on devices page as needed Start Array Then Stop Array Assign new drives Start Array Make certain ONLY the new drives show as un-formatted. If any others show as un-formatted DO NOT PROCEED. Press "Format" button on management console button to Format the new drives. Joe L. Quote Link to comment
Blofeld Posted September 16, 2010 Share Posted September 16, 2010 OK, thanks, that seems to have worked. However, I screwed up on something earlier (at least I think so): I've put two disks (-60 and -62) in without pre-clearing them, used them for some testing, realized my error, unassigned them, and ran the pre-clear on those two and another third added disk. Of course, it now gives me this error (see attached screenshot): Stopped. Invalid configuration.Too many wrong and/or missing disks! I thought I could just format them and start from scratch, but I guess that's not the case. There's nothing on them save for the pre-clear check, so is there a reasonable way to proceed from here? Thanks again for your patience, Joe L. .... Quote Link to comment
dgaschk Posted September 16, 2010 Share Posted September 16, 2010 Power-Off_Retract_Count is usually the count of how many times the disk heads were retracted in a power loss. Load_Cycle_Count is how many times the disk heads are loaded from their parked position. Both counts incremented by 1. (as if the disk lost power, it retracted the disk heads, then power was restored, and it re-loaded them) I'd look for a loose power connection to the drive. Or, it could be your power supply is not up to the task, or you have a bad splitter, back-plane, card-rack, etc... It is not normal to see those counts increment in a pre-clear cycle. I will check the cables. I'm running a new US budget box build. Is there any reason the 400W power supply is not enough? We have no idea... How many disks do you have attached, how many are "green"? What specific 400 Watt supply? Is it a single 12 Volt rail supply? Joe L. CORSAIR CMPSU-400CX 400W Power supply This has a single 12v rail. The spec for the US budget box build said that this will support up to 12 green drives. I have only 5 drives in the box. 2 of which are green. I expect that by the time I have 12 drives they will all be green. I noticed that the budget build now specifies a 430W power supply. Can anyone advise on how many green drives total this can support in addition to 3 non-green drives? What procedure can I use to isolate this problem? I plan to reseat the power cables and rerun the test. Joe, I read that Power-Off_Retract does not actually require that the power goes off. This counter will increment if the head is parked after long enough idle period. Does the script contain any idle periods that might allow the head to park? Thanks, David Quote Link to comment
Joe L. Posted September 16, 2010 Share Posted September 16, 2010 No, it does not have any idle periods. It is a mystery. It is either reading, or writing the disk... and doing a lot of it at that. Quote Link to comment
barbapapa Posted September 17, 2010 Share Posted September 17, 2010 Well that depends. Any sectors pending reallocation is not good. But it's ok as long as there not thausands of them and they do not increase over time. So what you should do it to run a few more times the preclear script and check if there will be an increase in "5 Reallocated_Sector_Ct " and the pending sectors. After you run the next preclear, the 17 pending sectors should have been reallocated and appear in "5 Reallocated_Sector_Ct ". If there is no increase in pending sectors, you'll probably be fine. Just keep an eye on it from time to time by running some SMART tests while it's in use in your array. Still in the 2nd of 3 more cycles of pre-clear, but I'm seeing one heck of a lot of errors in my syslog now, here's a sample: Sep 17 04:57:23 Tower kernel: ata4.00: failed command: READ DMA EXT Sep 17 04:57:23 Tower kernel: ata4.00: cmd 25/00:08:c0:cf:14/00:00:94:00:00/e0 tag 0 dma 4096 in Sep 17 04:57:23 Tower kernel: res 51/40:00:c7:cf:14/40:00:94:00:00/e0 Emask 0x9 (media error) Sep 17 04:57:23 Tower kernel: ata4.00: status: { DRDY ERR } Sep 17 04:57:23 Tower kernel: ata4.00: error: { UNC } Sep 17 04:57:23 Tower kernel: ata4: hard resetting link Sep 17 04:57:24 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 17 04:57:24 Tower kernel: ata4.00: configured for UDMA/133 Sep 17 04:57:24 Tower kernel: ata4: EH complete Sep 17 04:57:27 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Sep 17 04:57:27 Tower kernel: ata4.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable Sep 17 04:57:27 Tower kernel: ata4.00: failed command: READ DMA EXT Sep 17 04:57:27 Tower kernel: ata4.00: cmd 25/00:08:c0:cf:14/00:00:94:00:00/e0 tag 0 dma 4096 in Sep 17 04:57:27 Tower kernel: res 51/40:00:c7:cf:14/40:00:94:00:00/e0 Emask 0x9 (media error) Sep 17 04:57:27 Tower kernel: ata4.00: status: { DRDY ERR } Sep 17 04:57:27 Tower kernel: ata4.00: error: { UNC } Sep 17 04:57:27 Tower kernel: ata4: hard resetting link Sep 17 04:57:27 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 17 04:57:27 Tower kernel: ata4.00: configured for UDMA/133 Sep 17 04:57:27 Tower kernel: ata4: EH complete Sep 17 04:57:30 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Sep 17 04:57:30 Tower kernel: ata4.00: edma_err_cause=00000084 pp_flags=00000001, dev error, EDMA self-disable Sep 17 04:57:30 Tower kernel: ata4.00: failed command: READ DMA EXT Sep 17 04:57:30 Tower kernel: ata4.00: cmd 25/00:08:c0:cf:14/00:00:94:00:00/e0 tag 0 dma 4096 in Sep 17 04:57:30 Tower kernel: res 51/40:00:c7:cf:14/40:00:94:00:00/e0 Emask 0x9 (media error) Sep 17 04:57:30 Tower kernel: ata4.00: status: { DRDY ERR } Sep 17 04:57:30 Tower kernel: ata4.00: error: { UNC } Sep 17 04:57:30 Tower kernel: ata4: hard resetting link Sep 17 04:57:30 Tower kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Sep 17 04:57:30 Tower kernel: ata4.00: configured for UDMA/133 Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] Unhandled sense code Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] Result: hostbyte=0x00 driverbyte=0x08 Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] Sense Key : 0x3 [current] [descriptor] Sep 17 04:57:30 Tower kernel: Descriptor sense data with sense descriptors (in hex): Sep 17 04:57:30 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Sep 17 04:57:30 Tower kernel: 94 14 cf c7 Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] ASC=0x11 ASCQ=0x4 Sep 17 04:57:30 Tower kernel: sd 4:0:0:0: [sdd] CDB: cdb[0]=0x28: 28 00 94 14 cf c0 00 00 08 00 Sep 17 04:57:30 Tower kernel: end_request: I/O error, dev sdd, sector 2484391879 Sep 17 04:57:30 Tower kernel: Buffer I/O error on device sdd, logical block 310548984 sdd is the disk I'm preclearing. I don't recall seeing all those errors during a preclear before. Bad sign? Quote Link to comment
Joe L. Posted September 17, 2010 Share Posted September 17, 2010 UNC errors are UNCorrectable read errors. (unreadable sectors) Basically, you'll see them in the SMART report as sectors to be re-allocated unless the process of writing zeros to the drive in the next phase is able to re-write them in their original locations and have them readable. Joe L. Quote Link to comment
dgaschk Posted September 17, 2010 Share Posted September 17, 2010 ============================================================================ == == Disk /dev/sdc has been successfully precleared == == Ran 1 preclear-disk cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:28:35 (85 MB/s) == Last Cycle's Zeroing time : 6:05:03 (91 MB/s) == Last Cycle's Post Read Time : 12:57:36 (42 MB/s) == Last Cycle's Total Time : 25:32:30 == == Total Elapsed Time 25:32:30 == == Disk Start Temperature: 29C == == Current Disk Temperature: 33C, == ============================================================================ 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 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activity < was never started. --- Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. 61,62c61,62 < 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 489 < 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 489 --- 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 492 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 492 ============================================================================ This is the disk with the power problem. I'm checking 2 other 2 TB drives and if they don't have this problem I will move the power cable around to see if it follows a cable connection. Why is the post read so much slower than the pre read? Is this normal? It cleared about 2 hours faster this time. Is it normal for clear time to vary so much? Quote Link to comment
Joe L. Posted September 17, 2010 Share Posted September 17, 2010 Why is the post read so much slower than the pre read?Pre-read we just ignore what we've read and send it to /dev/null Post-read we sum all the bytes read and verify all zeros are being read back where expected. Is this normal? Yes It cleared about 2 hours faster this time. Is it normal for clear time to vary so much? Depends on what else is going on at the same time. Since the clearing process sets the geometry, and read-block-size is based on the existing geometry, I suppose it could vary some. Quote Link to comment
barbapapa Posted September 19, 2010 Share Posted September 19, 2010 First off, thanks again to Joe for a great script! I just precleared 2 WD20EARS drives (with pins 7 and 8 jumpered). I precleared them simultaneously using separate screen sessions. They both successfully precleared, but gave me the "Offline data collection activity was suspended by an interrupting command from host" warning. I gather from reading posts in the forum about it, I shouldn't need to worry about this. I am a little worried about the Raw_Read_Error_Rate and Current_Pending_Sector values for one of the drives though: Sep 12 14:26:23 Tower preclear_disk-finish[30093]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 1 Raw_Read_Error_Rate 0x002f 197 195 051 Pre-fail Always - 291 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 32 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 19 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 17 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Sep 12 14:26:23 Tower preclear_disk-finish[30093]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Are my worries about this drive warranted? OK I pre-cleared this drive for 3 more cycles, here are the results: Sep 18 19:08:45 Tower preclear_disk-finish[937]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Sep 18 19:08:45 Tower preclear_disk-finish[937]: 1 Raw_Read_Error_Rate 0x002f 197 195 051 Pre-fail Always - 1536 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 180 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 111 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 10 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 21 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Sep 18 19:08:45 Tower preclear_disk-finish[937]: 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 49 Sep 18 19:08:45 Tower preclear_disk-diff[950]: < 1 Raw_Read_Error_Rate 0x002f 199 195 051 Pre-fail Always - 291 Sep 18 19:08:45 Tower preclear_disk-diff[950]: --- Sep 18 19:08:45 Tower preclear_disk-diff[950]: > 1 Raw_Read_Error_Rate 0x002f 197 195 051 Pre-fail Always - 1536 Sep 18 19:08:45 Tower preclear_disk-diff[950]: 63c62 Sep 18 19:08:45 Tower preclear_disk-diff[950]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 106 Sep 18 19:08:45 Tower preclear_disk-diff[950]: --- Sep 18 19:08:45 Tower preclear_disk-diff[950]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 111 Sep 18 19:08:45 Tower preclear_disk-diff[950]: 65c64 Sep 18 19:08:45 Tower preclear_disk-diff[950]: < 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 28 Sep 18 19:08:45 Tower preclear_disk-diff[950]: --- Sep 18 19:08:45 Tower preclear_disk-diff[950]: > 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 10 Sep 18 19:08:45 Tower preclear_disk-diff[950]: 74,75c73,74 What happened to the 17 Current Pending Sectors from my first pre-clear? I was expecting to see them under Reallocated Event Count this time around. What's the verdict, is this drive too flakey to go into the array? Quote Link to comment
Joe L. Posted September 19, 2010 Share Posted September 19, 2010 I think something is flaky. Each time there are sectors pending re-allocation in the result, but no re-allocated sectors. The only way I know that can happen is if the sectors are able to be written to their original locations on the disk (the disk tries that first) So, to me, it indicates the ability to read what was written on that disk is not reliable. (constantly different sectors pending re-allocation) The raw-read-error rate is a number that has no meaning to anyone but the manufacturer. The normalized value is continually dropping (towards the failure threshold of 51, but nowhere near close to it YET) That is not a good sign, but seems to go hand in hand with the pending re-allocation errors you are seeing. My vote... RMA the drive. Joe L. Quote Link to comment
Tight_wad Posted September 19, 2010 Share Posted September 19, 2010 Here are my preclear results. What exactly do they mean? It says it was successfully precleared, but it has error? ep 18 20:42:59 Tower preclear_disk-diff[31210]: ============================================================================ Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Disk /dev/sdf has been successfully precleared Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Ran 1 preclear-disk cycle Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Using :Read block size = 8225280 Bytes Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Last Cycle's Pre Read Time : 3:21:56 (82 MB/s) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Last Cycle's Zeroing time : 3:22:20 (82 MB/s) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Last Cycle's Post Read Time : 7:28:46 (37 MB/s) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Last Cycle's Total Time : 14:14:09 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Total Elapsed Time 14:14:09 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Disk Start Temperature: 35C Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Current Disk Temperature: 35C, Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: ============================================================================ Sep 18 20:42:59 Tower preclear_disk-diff[31210]: S.M.A.R.T. error count differences detected after pre-clear Sep 18 20:42:59 Tower preclear_disk-diff[31210]: note, some 'raw' values may change, but not be an indication of a problem Sep 18 20:42:59 Tower preclear_disk-diff[31210]: 55c55 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: < 1 Raw_Read_Error_Rate 0x000f 114 100 006 Pre-fail Always - 64402186 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: --- Sep 18 20:42:59 Tower preclear_disk-diff[31210]: > 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 174564160 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: 59c59 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: < 7 Seek_Error_Rate 0x000f 064 060 030 Pre-fail Always - 3018274 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: --- Sep 18 20:42:59 Tower preclear_disk-diff[31210]: > 7 Seek_Error_Rate 0x000f 064 060 030 Pre-fail Always - 3095398 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: 66,67c66,67 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: < 190 Airflow_Temperature_Cel 0x0022 065 053 045 Old_age Always - 35 (Lifetime Min/Max 31/37) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: < 195 Hardware_ECC_Recovered 0x001a 036 025 000 Old_age Always Sep 18 20:42:59 Tower preclear_disk-diff[31210]: --- Sep 18 20:42:59 Tower preclear_disk-diff[31210]: > 190 Airflow_Temperature_Cel 0x0022 065 053 045 Old_age Always - 35 (Lifetime Min/Max 31/39) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: > 195 Hardware_ECC_Recovered 0x001a 052 025 000 Old_age Always Sep 18 20:42:59 Tower preclear_disk-diff[31210]: ============================================================================ Quote Link to comment
Joe L. Posted September 19, 2010 Share Posted September 19, 2010 Here are my preclear results. What exactly do they mean? It says it was successfully precleared, but it has error? ep 18 20:42:59 Tower preclear_disk-diff[31210]: ============================================================================ Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Disk /dev/sdf has been successfully precleared Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Ran 1 preclear-disk cycle Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Using :Read block size = 8225280 Bytes Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Last Cycle's Pre Read Time : 3:21:56 (82 MB/s) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Last Cycle's Zeroing time : 3:22:20 (82 MB/s) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Last Cycle's Post Read Time : 7:28:46 (37 MB/s) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Last Cycle's Total Time : 14:14:09 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Total Elapsed Time 14:14:09 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Disk Start Temperature: 35C Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Current Disk Temperature: 35C, Sep 18 20:42:59 Tower preclear_disk-diff[31210]: == Sep 18 20:42:59 Tower preclear_disk-diff[31210]: ============================================================================ Sep 18 20:42:59 Tower preclear_disk-diff[31210]: S.M.A.R.T. error count differences detected after pre-clear Sep 18 20:42:59 Tower preclear_disk-diff[31210]: note, some 'raw' values may change, but not be an indication of a problem Sep 18 20:42:59 Tower preclear_disk-diff[31210]: 55c55 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: < 1 Raw_Read_Error_Rate 0x000f 114 100 006 Pre-fail Always - 64402186 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: --- Sep 18 20:42:59 Tower preclear_disk-diff[31210]: > 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 174564160 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: 59c59 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: < 7 Seek_Error_Rate 0x000f 064 060 030 Pre-fail Always - 3018274 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: --- Sep 18 20:42:59 Tower preclear_disk-diff[31210]: > 7 Seek_Error_Rate 0x000f 064 060 030 Pre-fail Always - 3095398 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: 66,67c66,67 Sep 18 20:42:59 Tower preclear_disk-diff[31210]: < 190 Airflow_Temperature_Cel 0x0022 065 053 045 Old_age Always - 35 (Lifetime Min/Max 31/37) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: < 195 Hardware_ECC_Recovered 0x001a 036 025 000 Old_age Always Sep 18 20:42:59 Tower preclear_disk-diff[31210]: --- Sep 18 20:42:59 Tower preclear_disk-diff[31210]: > 190 Airflow_Temperature_Cel 0x0022 065 053 045 Old_age Always - 35 (Lifetime Min/Max 31/39) Sep 18 20:42:59 Tower preclear_disk-diff[31210]: > 195 Hardware_ECC_Recovered 0x001a 052 025 000 Old_age Always Sep 18 20:42:59 Tower preclear_disk-diff[31210]: ============================================================================ There were no errors. In fact most of the "normalized" values IMPROVED. Prior to the pre-clear, the normalized value for Raw Read Error Rate was 114, After it was 118. Higher numbers are better. If the error rate goes BELOW the error threshold (006) the drive will be considered as failing. Prior to the pre-clear, the "normalized" Seek-Error-Rate was 064, after it was 064, It was unchanged. Prior to the pre-clear the highest temperature recorded by the drive was 37, after it was 39. The "normalized" value of 65 is not below the "failure threshold" of 45 for that parameter. Prior to the pre-clear, the "normalized" Hardware ECC Recovered value was 36, after it was 52. It also improved. Its failure threshold is 0. All drives internally handle error correction. All drives have internal errors and re-read and perform error correction. some drive models report "raw" numbers in the "raw" column, but they are meaningful to the manufacturer only. (with few exceptions. The re-allocated sectors, pending re-allocated sectors, and temperature being the exceptions) Enjoy your new drive. It looks great. Joe L. Quote Link to comment
Blofeld Posted September 22, 2010 Share Posted September 22, 2010 I started a pre-clear routine yesterday, it was chugging along, and then I turned off my desktop from which I telnet-induced it. I thought I could see the results in the syslog, but apparently that isn't so. Is there a way to find out the results of the pre-clear after the fact? Here's the last messages it gave me before I logged out (and for some reason, a monitor connected to the server is not giving me a signal): Sep 21 12:33:55 Tower preclear_disk-start[4750]: === START OF INFORMATION SECTION === Sep 21 12:33:55 Tower preclear_disk-start[4750]: Device Model: ST31500341AS Sep 21 12:33:55 Tower preclear_disk-start[4750]: Serial Number: 9VS141QF Sep 21 12:33:55 Tower preclear_disk-start[4750]: Firmware Version: CC1H Sep 21 12:33:55 Tower preclear_disk-start[4750]: User Capacity: 1,500,301,910,016 bytes Sep 21 12:33:55 Tower preclear_disk-start[4750]: Device is: Not in smartctl database [for details use: -P showall] Sep 21 12:33:55 Tower preclear_disk-start[4750]: ATA Version is: 8 Sep 21 12:33:55 Tower preclear_disk-start[4750]: ATA Standard is: ATA-8-ACS revision 4 Sep 21 12:33:55 Tower preclear_disk-start[4750]: Local Time is: Tue Sep 21 12:33:55 2010 CEST Sep 21 12:33:55 Tower preclear_disk-start[4750]: SMART support is: Available - device has SMART capability. Sep 21 12:33:55 Tower preclear_disk-start[4750]: SMART support is: Enabled Sep 21 12:33:55 Tower preclear_disk-start[4750]: Sep 21 12:33:55 Tower preclear_disk-start[4750]: === START OF READ SMART DATA SECTION === Sep 21 12:33:55 Tower preclear_disk-start[4750]: SMART overall-health self-assessment test result: PASSED Sep 21 12:33:55 Tower preclear_disk-start[4750]: Sep 21 12:33:55 Tower preclear_disk-start[4750]: General SMART Values: Sep 21 12:33:55 Tower preclear_disk-start[4750]: Offline data collection status: (0x82)^IOffline data collection activity Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^Iwas completed without error. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Sep 21 12:33:55 Tower preclear_disk-start[4750]: Self-test execution status: ( 0)^IThe previous self-test routine completed Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^Iwithout error or no self-test has ever Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^Ibeen run. Sep 21 12:33:55 Tower preclear_disk-start[4750]: Total time to complete Offline Sep 21 12:33:55 Tower preclear_disk-start[4750]: data collection: ^I^I ( 617) seconds. Sep 21 12:33:55 Tower preclear_disk-start[4750]: Offline data collection Sep 21 12:33:55 Tower preclear_disk-start[4750]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^IAuto Offline data collection on/off support. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^ISuspend Offline collection upon new Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^Icommand. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^IOffline surface scan supported. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^ISelf-test supported. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^IConveyance Self-test supported. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^ISelective Self-test supported. Sep 21 12:33:55 Tower preclear_disk-start[4750]: SMART capabilities: (0x0003)^ISaves SMART data before entering Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^Ipower-saving mode. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^ISupports SMART auto save timer. Sep 21 12:33:55 Tower preclear_disk-start[4750]: Error logging capability: (0x01)^IError logging supported. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^IGeneral Purpose Logging supported. Sep 21 12:33:55 Tower preclear_disk-start[4750]: Short self-test routine Sep 21 12:33:55 Tower preclear_disk-start[4750]: recommended polling time: ^I ( 1) minutes. Sep 21 12:33:55 Tower preclear_disk-start[4750]: Extended self-test routine Sep 21 12:33:55 Tower preclear_disk-start[4750]: recommended polling time: ^I ( 255) minutes. Sep 21 12:33:55 Tower preclear_disk-start[4750]: Conveyance self-test routine Sep 21 12:33:55 Tower preclear_disk-start[4750]: recommended polling time: ^I ( 2) minutes. Sep 21 12:33:55 Tower preclear_disk-start[4750]: SCT capabilities: ^I (0x103f)^ISCT Status supported. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^ISCT Feature Control supported. Sep 21 12:33:55 Tower preclear_disk-start[4750]: ^I^I^I^I^ISCT Data Table supported. Sep 21 12:33:55 Tower preclear_disk-start[4750]: Sep 21 12:33:55 Tower preclear_disk-start[4750]: SMART Attributes Data Structure revision number: 10 Sep 21 12:33:55 Tower preclear_disk-start[4750]: Vendor Specific SMART Attributes with Thresholds: Sep 21 12:33:55 Tower preclear_disk-start[4750]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Sep 21 12:33:55 Tower preclear_disk-start[4750]: 1 Raw_Read_Error_Rate 0x000f 115 099 006 Pre-fail Always - 89889091 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 3 Spin_Up_Time 0x0003 095 092 000 Pre-fail Always - 0 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 325 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 7 Seek_Error_Rate 0x000f 064 060 030 Pre-fail Always - 2876303 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 424 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 4 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 77 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 189 High_Fly_Writes 0x003a 086 086 000 Old_age Always - 14 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 190 Airflow_Temperature_Cel 0x0022 066 052 045 Old_age Always - 34 (Lifetime Min/Max 21/34) Sep 21 12:33:55 Tower preclear_disk-start[4750]: 195 Hardware_ECC_Recovered 0x001a 055 040 000 Old_age Always - 89889091 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 108456514158987 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1090825743 Sep 21 12:33:55 Tower preclear_disk-start[4750]: 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3122341491 Sep 21 12:33:55 Tower preclear_disk-start[4750]: Sep 21 12:33:55 Tower preclear_disk-start[4750]: SMART Error Log Version: 1 Sep 21 12:33:55 Tower preclear_disk-start[4750]: No Errors Logged Sep 21 12:33:55 Tower preclear_disk-start[4750]: Sep 21 12:33:55 Tower preclear_disk-start[4750]: SMART Self-test log structure revision number 1 Sep 21 12:33:55 Tower preclear_disk-start[4750]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Sep 21 12:33:55 Tower preclear_disk-start[4750]: Sep 21 12:33:55 Tower preclear_disk-start[4750]: Sep 21 12:33:55 Tower preclear_disk-start[4750]: SMART Selective self-test log data structure revision number 1 Sep 21 12:33:55 Tower preclear_disk-start[4750]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Sep 21 12:33:55 Tower preclear_disk-start[4750]: 1 0 0 Not_testing Sep 21 12:33:55 Tower preclear_disk-start[4750]: 2 0 0 Not_testing Sep 21 12:33:55 Tower preclear_disk-start[4750]: 3 0 0 Not_testing Sep 21 12:33:55 Tower preclear_disk-start[4750]: 4 0 0 Not_testing Sep 21 12:33:55 Tower preclear_disk-start[4750]: 5 0 0 Not_testing Sep 21 12:33:55 Tower preclear_disk-start[4750]: Selective self-test flags (0x0): Sep 21 12:33:55 Tower preclear_disk-start[4750]: After scanning selected spans, do NOT read-scan remainder of disk. Sep 21 12:33:55 Tower preclear_disk-start[4750]: If Selective self-test is pending on power-up, resume after 0 minute delay. Sep 21 12:33:55 Tower preclear_disk-start[4750]: Quote Link to comment
Joe L. Posted September 22, 2010 Share Posted September 22, 2010 Yes, it is actually quite easy in this case. Your pre-clear terminated as soon as you terminated the telnet session when you turned off your desktop. Only the smart report from before the pre-cleat is in your log. Joe L. Quote Link to comment
Blofeld Posted September 22, 2010 Share Posted September 22, 2010 oh ...so I've got to run it again, right? I was trying to take the array offline to look if I could "see" the drive, and the server crashed on me, forcing me to do a hard reset. It's booted up again, and doing a parity check - should I cancel that, and wait until the new drive is cleared and added, or should I let it do its thing? Quote Link to comment
slarco Posted September 22, 2010 Share Posted September 22, 2010 Hi. I Just finished running the preclear script in 2 of my drives and i was wondering if anyone can give me some help in interpretate the syslogs. I read in this post about similar Syslogs and the Raw & UDMA errors and seems to e normal, but i just rather double check before start moving data. Syslogs attached Thanks in advance! syslog_21-9-2010-1000.txt syslog_22-9-2010-0940.txt Quote Link to comment
Joe L. Posted September 22, 2010 Share Posted September 22, 2010 Hi. I Just finished running the preclear script in 2 of my drives and i was wondering if anyone can give me some help in interpretate the syslogs. I read in this post about similar Syslogs and the Raw & UDMA errors and seems to e normal, but i just rather double check before start moving data. Syslogs attached Thanks in advance! Everything looks normal. Enjoy your new drives. 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.