Tom899 Posted December 9, 2010 Share Posted December 9, 2010 If you look back at a couple of other people's posts, you can see this is normal. Joe will have to explain why.... but it's in other's results as well.. Jim Ok, thanks Jim A master boot record has positions in it for 4 partitions. unRAID uses only 1. The bytes describing the other possible three must be cleared in case they once held old partitioning information. as described this message is informational and completely normal. Two of my disks have finished the preclear. I don't see much information though, only a few of lines? Here they are. Please, what do you think? Disk /dev/sdf 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 59c59 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Disk /dev/sdc 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 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 19 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 38 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Quote Link to comment
Joe L. Posted December 9, 2010 Share Posted December 9, 2010 I guess you did not read any of the prior posts in this thread describing how to interpret the results. Your disks are quite normal. Quote Link to comment
Tom899 Posted December 9, 2010 Share Posted December 9, 2010 I guess you did not read any of the prior posts in this thread describing how to interpret the results. Your disks are quite normal. Sorry Joe, yes I need to study the prior posts and will do that. I'm using putty to telnet and "screen". Somehow I can't seem to see any of my other disks anymore so I don't know when thy will be finished or the results. I login to tower, then root, then screen -r 2048 (the session thats preclearing my drives) which did work to cycle through my drives with Ctrl A then N, but it is not available now. Is there another way to see if my drives are still in the preclear stage? Thanks, Tom Quote Link to comment
Joe L. Posted December 9, 2010 Share Posted December 9, 2010 I guess you did not read any of the prior posts in this thread describing how to interpret the results. Your disks are quite normal. Sorry Joe, yes I need to study the prior posts and will do that. I'm using putty to telnet and "screen". Somehow I can't seem to see any of my other disks anymore so I don't know when thy will be finished or the results. I login to tower, then root, then screen -r 2048 (the session thats preclearing my drives) which did work to cycle through my drives with Ctrl A then N, but it is not available now. Is there another way to see if my drives are still in the preclear stage? Thanks, Tom look for them in the process list? top will show you active processes. Look for their entries in the syslog. Their completion is logged there. Quote Link to comment
Tom899 Posted December 9, 2010 Share Posted December 9, 2010 I guess you did not read any of the prior posts in this thread describing how to interpret the results. Your disks are quite normal. Sorry Joe, yes I need to study the prior posts and will do that. I'm using putty to telnet and "screen". Somehow I can't seem to see any of my other disks anymore so I don't know when thy will be finished or the results. I login to tower, then root, then screen -r 2048 (the session thats preclearing my drives) which did work to cycle through my drives with Ctrl A then N, but it is not available now. Is there another way to see if my drives are still in the preclear stage? Thanks, Tom look for them in the process list? top will show you active processes. Look for their entries in the syslog. Their completion is logged there. Thanks, I just assigned a parity drive, 4 data drives and a cache drive. It said the data and cache drives were not formatted so I started to format. Not sure why the parity drive did not request a format. It now says the parity drive is syncing with 700 minutes to go! Quote Link to comment
Joe L. Posted December 9, 2010 Share Posted December 9, 2010 I guess you did not read any of the prior posts in this thread describing how to interpret the results. Your disks are quite normal. Sorry Joe, yes I need to study the prior posts and will do that. I'm using putty to telnet and "screen". Somehow I can't seem to see any of my other disks anymore so I don't know when thy will be finished or the results. I login to tower, then root, then screen -r 2048 (the session thats preclearing my drives) which did work to cycle through my drives with Ctrl A then N, but it is not available now. Is there another way to see if my drives are still in the preclear stage? Thanks, Tom look for them in the process list? top will show you active processes. Look for their entries in the syslog. Their completion is logged there. Thanks, I just assigned a parity drive, 4 data drives and a cache drive. It said the data and cache drives were not formatted so I started to format. Not sure why the parity drive did not request a format. It now says the parity drive is syncing with 700 minutes to go! The parity drive is never formatted. It does not contain a file-system, it just contains parity calculations. It sounds like you are well on your way. Do not forget to perform a "Check" of the parity once the initial parity calculation is complete. Right now you are writing the parity disk you will not know if it is readable until you perform a subsequent "Check" by pressing the "Check" button on the user-interface. Joe L. Quote Link to comment
Tom899 Posted December 9, 2010 Share Posted December 9, 2010 I guess you did not read any of the prior posts in this thread describing how to interpret the results. Your disks are quite normal. Sorry Joe, yes I need to study the prior posts and will do that. I'm using putty to telnet and "screen". Somehow I can't seem to see any of my other disks anymore so I don't know when thy will be finished or the results. I login to tower, then root, then screen -r 2048 (the session thats preclearing my drives) which did work to cycle through my drives with Ctrl A then N, but it is not available now. Is there another way to see if my drives are still in the preclear stage? Thanks, Tom look for them in the process list? top will show you active processes. Look for their entries in the syslog. Their completion is logged there. Thanks, I just assigned a parity drive, 4 data drives and a cache drive. It said the data and cache drives were not formatted so I started to format. Not sure why the parity drive did not request a format. It now says the parity drive is syncing with 700 minutes to go! The parity drive is never formatted. It does not contain a file-system, it just contains parity calculations. It sounds like you are well on your way. Do not forget to perform a "Check" of the parity once the initial parity calculation is complete. Right now you are writing the parity disk you will not know if it is readable until you perform a subsequent "Check" by pressing the "Check" button on the user-interface. Joe L. Great! Thanks for that tip and all your help! Tom Quote Link to comment
BlackCat Posted December 9, 2010 Share Posted December 9, 2010 Ok so I ran my second pre-clear, I'll attach the log. So I had a couple of differences this time. 1) The time went from about 36 hrs the first time to around 45 hrs for the second. 2) The SMART Attributes table was nearly the same except in my 2nd preclear the Raw Value for the Load Cycle Count went up to 24 from 23 3) I got these errors. Based on the first few pages of this thread they might be a problem because the second column in the table went down instead of up and the third column increased? ============================================================================ Dec 9 13:20:15 Tower preclear_disk-diff[14034]: S.M.A.R.T. error count differences detected after pre-clear Dec 9 13:20:15 Tower preclear_disk-diff[14034]: note, some 'raw' values may change, but not be an indication of a problem Dec 9 13:20:15 Tower preclear_disk-diff[14034]: 58c58 Dec 9 13:20:15 Tower preclear_disk-diff[14034]: < 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Dec 9 13:20:15 Tower preclear_disk-diff[14034]: --- Dec 9 13:20:15 Tower preclear_disk-diff[14034]: > 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Dec 9 13:20:15 Tower preclear_disk-diff[14034]: ============================================================================ Syslog-Disk1_2nd_Preclear-12-09-2010.txt Quote Link to comment
dmgibney Posted December 10, 2010 Share Posted December 10, 2010 Hello All, I just picked up a Seagate 2TB drive and have run preclear on it twice now. I think the drive is ok, but I would like to make sure before adding it to my array. The first time around the Raw_Read_Error_Rate started at 100 and ended at 108 with threshold of 006. I wanted to be safe so I precleared it again. This time the started at 108 and ended at 112. It took about 29 hours to finish both times. If I understand the output correctly, that means the drive is good, since the value is moving away from the threshold. Is that right? Here are my output screens. Thanks for taking a look. I appreciate it! Quote Link to comment
Joe L. Posted December 10, 2010 Share Posted December 10, 2010 If I understand the output correctly, that means the drive is good, since the value is moving away from the threshold. Is that right? That's how I would interpret those results. Quote Link to comment
BlackCat Posted December 10, 2010 Share Posted December 10, 2010 If I understand the output correctly, that means the drive is good, since the value is moving away from the threshold. Is that right? That's how I would interpret those results. So then does that mean because mine went under the previous value that something is wrong or does it need to be run a third time to seem if it keeps going down? Quote Link to comment
Joe L. Posted December 10, 2010 Share Posted December 10, 2010 If I understand the output correctly, that means the drive is good, since the value is moving away from the threshold. Is that right? That's how I would interpret those results. So then does that mean because mine went under the previous value that something is wrong or does it need to be run a third time to seem if it keeps going down? If you find the time to do a little bit of reading in this thread you would see that the 100 200 and 253 values are those used by the manufacturers when a disk is initially manufactured and then set to either a 100 or 200 once the disk gets a bit of time on it. There is no "standard" and it is sometimes different by disk model even within a brand. The ONLY "failure" is if the normalized value goes below the threshold. Other than that, according to SMART, the disk has not failed. As long as the pre-clear said it was successful and no attribute is below its threshold your disk is working. The only attributes we really care about in pre-clearing (and where the "raw" value has some meaning to anyone other than the manufacturer) are re-allocated sectors or sectors pending re-allocation. Joe L. Quote Link to comment
BlackCat Posted December 10, 2010 Share Posted December 10, 2010 If I understand the output correctly, that means the drive is good, since the value is moving away from the threshold. Is that right? That's how I would interpret those results. So then does that mean because mine went under the previous value that something is wrong or does it need to be run a third time to seem if it keeps going down? If you find the time to do a little bit of reading in this thread you would see that the 100 200 and 253 values are those used by the manufacturers when a disk is initially manufactured and then set to either a 100 or 200 once the disk gets a bit of time on it. There is no "standard" and it is sometimes different by disk model even within a brand. The ONLY "failure" is if the normalized value goes below the threshold. Other than that, according to SMART, the disk has not failed. As long as the pre-clear said it was successful and no attribute is below its threshold your disk is working. The only attributes we really care about in pre-clearing (and where the "raw" value has some meaning to anyone other than the manufacturer) are re-allocated sectors or sectors pending re-allocation. Joe L. Thanks Joe, sorry I was trying to read it and figure what value is what. I had thought that earlier in the thread there was talk about if the numbers where going down it might not be good or the drive was just more susceptible to wear, I got confused. I will continue reading. Thanks again. Quote Link to comment
spinbot Posted December 10, 2010 Share Posted December 10, 2010 My Syslog, of the pre-clear results show: User Capacity: 1,500,301,910,016 bytes All my other formatted drives are 1,465,138,552 Is their any command I can run to verify the drive will format to the same size as my others ( I had to fix half my drives before as the MSI Motherboard wrote the BIOS backup to them ) Thanks Quote Link to comment
Joe L. Posted December 10, 2010 Share Posted December 10, 2010 fdisk -l or hdparm -I or hdparm -N or smartctl -d ata -a Quote Link to comment
spinbot Posted December 10, 2010 Share Posted December 10, 2010 hdparm -N Thanks... that's the one I was trying to recall from a while ago. For reference, the full command I used (in case others are wondering): /usr/sbin/hdparm -N /dev/sdb My new drive shows the exact same details as my older 1.5TB drives, so that's a good sign! root@Tower:/boot# /usr/sbin/hdparm -N /dev/sdb /dev/sdb: max sectors = 18446744072344861488/11041584, HPA setting seems invalid root@Tower:/boot# /usr/sbin/hdparm -N /dev/sdc /dev/sdc: max sectors = 18446744072344861488/11041584, HPA setting seems invalid root@Tower:/boot# /usr/sbin/hdparm -N /dev/sdd /dev/sdd: max sectors = 18446744072344861488/11041584, HPA setting seems invalid I'm am certain I dealt with the HPA a while ago, however on every drive I get "HPA setting seems invalid". Hmmmmm Quote Link to comment
Joe L. Posted December 10, 2010 Share Posted December 10, 2010 Trust me your drive does not have 18446744072344861488 sectors. 18446744072344861 sectors 18446744072344 M 18446744072 G 18446744 T 18446 P 18.446 Exabyte sectors... The HPA setting seems invalid message occurs because the HPA setting dies not equal the reported total number of sectors. If those 512 Byte sectors you would then have a 9146 Exabyte disk. Joe L. Quote Link to comment
Userpaul Posted December 12, 2010 Share Posted December 12, 2010 I'm trying to preclear a Seagate 500 gb hdd and it stuck at 70% for a while and then a "killed message came up on the screen. My syslog is to big to post but here is a flavour. Syslog is 1.6GB Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] Sense Key : 0xb [current] [descriptor] Dec 12 19:15:56 Tower kernel: Descriptor sense data with sense descriptors (in hex): Dec 12 19:15:56 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 12 19:15:56 Tower kernel: 00 00 00 0f Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] ASC=0x0 ASCQ=0x0 Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 37 3f e9 10 00 00 08 00 Dec 12 19:15:56 Tower kernel: end_request: I/O error, dev sdb, sector 926935312 Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] Sense Key : 0xb [current] [descriptor] Dec 12 19:15:56 Tower kernel: Descriptor sense data with sense descriptors (in hex): Dec 12 19:15:56 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 12 19:15:56 Tower kernel: 00 00 00 97 Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] ASC=0x0 ASCQ=0x0 Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 37 3f ea 98 00 00 08 00 Dec 12 19:15:56 Tower kernel: end_request: I/O error, dev sdb, sector 926935704 Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] Sense Key : 0xb [current] [descriptor] Dec 12 19:15:56 Tower kernel: Descriptor sense data with sense descriptors (in hex): Dec 12 19:15:56 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 12 19:15:56 Tower kernel: 00 00 00 1f Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] ASC=0x0 ASCQ=0x0 Dec 12 19:15:56 Tower kernel: sd 0:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 37 3f ec 20 00 00 08 00 Dec 12 19:15:56 Tower kernel: end_request: I/O error, dev sdb, sector 926936096 Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Dec 12 19:15:56 Tower kernel: ata1: status=0x41 { DriveReady Error } Dec 12 19:15:56 Tower kernel: ata1: error=0x04 { DriveStatusError } Dec 12 19:15:56 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 Is the hdd faulty? A few minutes later the system locked up. Will have to reboot Quote Link to comment
Rastaman Posted December 12, 2010 Share Posted December 12, 2010 Ive precleared 2 Samsung F3's and the first one looks fine i think. But the second one has some strange results. Does anyone know if there's any problem? == Disk /dev/sdf 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 55c55 < 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 136 67c67 < 195 Hardware_ECC_Recovered 0x003a 252 252 000 Old_age Always --- > 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always 72c72 < 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 --- > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 ============================================================================ == Disk /dev/sdc 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 18,28c18,95 < Error SMART Status command failed < Please get assistance from http://smartmontools.sourceforge.net/ < Register values returned from SMART Status command are: < ST =0x40 < ERR=0x00 < NS =0x0c < SC =0x00 < CL =0x88 < CH =0xe0 < SEL=0x40 < A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. --- > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED > > General SMART Values: > Offline data collection status: (0x00) Offline data collection activity > was never started. > Auto Offline Data Collection: Disabled. > 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: (25560) 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: ( 2) minutes. > Extended self-test routine > recommended polling time: ( 255) minutes. > SCT capabilities: (0x003f) 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 100 051 Pre-fail Always - 86 > 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 > 3 Spin_Up_Time 0x0023 060 060 025 Pre-fail Always - 12404 > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2 > 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 > 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 - 2 > 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 > 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 > 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always > 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 200 200 000 Old_age Always - 0 > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 9 > 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 > 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 > > 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 (0) should be 1 > SMART Selective self-test log data structure revision number 0 > Warning: ATA Specification requires selective self-test log data structure revision number = 1 > SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS > 1 0 0 Completed [00% left] (0-65535) > 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. > And a small update: im assuming the second disk is also correct, running preclear_disk.sh -t /dev/sdc gives the following results: Pre-Clear unRAID Disk ######################################################################## Device Model: SAMSUNG HD203WI Serial Number: S2ACJ1SZ901034 Firmware Version: 1AN10003 User Capacity: 2,000,398,934,016 bytes Disk /dev/sdc: 2000.3 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 63 3907029167 1953514552+ 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ============================================================================ == == DISK /dev/sdc IS PRECLEARED == ============================================================================ Quote Link to comment
BlackCat Posted December 12, 2010 Share Posted December 12, 2010 Disk 2: 1st PreClear > 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 42 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 43 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Every thing here looks good. Disk 2: 2nd Preclear < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 50 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 52 Looks good on the second pass Raw Read and UDMA Errors didn't show up. The Load Cycle Count is still good, because the raw value is only important to the Manufacture and the Start and current values are the same. Now here is my question. I committed the sin of buying two disks from newegg within a week from each other so both drives have same manufacturing date and site code. Both drives have been successfully precleared twice. The cycle times for 2 preclears on my first disk were 36 hrs and 44-45 hrs. Now my second disk took 24 and 25 hrs for two preclears. I have posted the cycle times below. From all the cycle times I have seen through this thread my disk1 zeroing time seems excessively slow. The only thing I saw earlier was that this could be affected by other activity on the server, but the only thing running was the preclear. I know each drive has its own characteristics, but is there something else that could be the cause like a SATA cable or the drive bay port on the backplane? Thanks for any insight. Disk1: Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA0324519 : Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Disk1 1st Pre-Clear Cycle time: I failed to copy all the system log info but the cycle time was about 36 hours Disk1 2nd Pre-Clear Cycle time: == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:20:16 (66 MB/s) == Last Cycle's Zeroing time : 21:47:41 (25 MB/s) == Last Cycle's Post Read Time : 14:39:26 (37 MB/s) == Last Cycle's Total Time : 44:48:31 Disk2: Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA0423649 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Disk2 1st Pre-Clear Cycle time: == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:00:00 (79 MB/s) == Last Cycle's Zeroing time : 5:52:08 (94 MB/s) == Last Cycle's Post Read Time : 12:15:08 (45 MB/s) == Last Cycle's Total Time : 25:08:27 == == Total Elapsed Time 25:08:27 Disk2 2nd Pre-Clear Cycle time: == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:07:27 (90 MB/s) == Last Cycle's Zeroing time : 5:43:43 (96 MB/s) == Last Cycle's Post Read Time : 12:14:26 (45 MB/s) == Last Cycle's Total Time : 24:06:45 == == Total Elapsed Time 24:06:45 Quote Link to comment
spinbot Posted December 12, 2010 Share Posted December 12, 2010 I don't have the answer, but just a few things to consider: If they are connected to your motherboard, two of my ports were set as "PATA" in the BIOS. I just pre-cleared 2 of the 1.5TB WD EARS drives and they took 21 hours each. Did you jump pins 7 and 8 ( picture on the top of the hard drive identifies which end pins 7 and 8 are on ) ? Quote Link to comment
BlackCat Posted December 13, 2010 Share Posted December 13, 2010 I don't have the answer, but just a few things to consider: If they are connected to your motherboard, two of my ports were set as "PATA" in the BIOS. I just pre-cleared 2 of the 1.5TB WD EARS drives and they took 21 hours each. Did you jump pins 7 and 8 ( picture on the top of the hard drive identifies which end pins 7 and 8 are on ) ? I jumpered both drives. I didn't see a spot for individual ports in the BIOs but I did change it over from IDE to SATA. I have the SUPERMICRO MBD-X8SIL-F-O motherboard, SuperMicro CSE-M35T-1B hot swap bay(s), and locking sata cables from monoprice I also attached an image(don't know where to host it) of when I added disk two to my pool after it has formatted. I haven't copied over any data but disk1 shows 49 reads and 38 writes, but disk 2 shows 33,298,778 reads and 3,830,610. Both show zero errors. Why such a big difference before even copying data over. Syslog_After_Preclear_Add_and_Format-12-12-2010.txt Quote Link to comment
spinbot Posted December 13, 2010 Share Posted December 13, 2010 Someone like Joe L. will chime in with some answers I'm sure For reference, my one drive, that hasn't had any data put on it yet, but is installed in my array shows: Reads: 29072288 Writes: 5734598 Although I do have one difference in that I am running my parity drive and I would have done a full parity check before I started using the two new drives. Quote Link to comment
BlackCat Posted December 13, 2010 Share Posted December 13, 2010 Someone like Joe L. will chime in with some answers I'm sure For reference, my one drive, that hasn't had any data put on it yet, but is installed in my array shows: Reads: 29072288 Writes: 5734598 Although I do have one difference in that I am running my parity drive and I would have done a full parity check before I started using the two new drives. This leads me to believe that disk 1 didn't format properly since the read/write of your fresh drive is similar to my disk 2, but my disk1 looks like it has no activity. I wonder if this could also be part of any possible problem causing the very slow pre-clear. I have a parity disk but it needs pre-clearing as well. I was going to wait until I had done some initial population of my data disks (original data still kept, since not protected by parity) before adding it. *Edit: hdparm -I report attached if it helps anything. Although I suspect no since not errors are being reported. HDparm_Disk1-12-12-2010.txt Quote Link to comment
BlackCat Posted December 14, 2010 Share Posted December 14, 2010 Spinbot thanks for the help. I realize this HDD issue is getting a bit off topic and probably should have gone in hardware, but can someone give me some idea of what is going on with my drive or at least where to look? I've been spending hours and hours and hours (I know like everyone else is), but I can't seem to find why this drive is so much slower and has much less read and writes after formatting compared to disk2. I just want to be able to understand my hardware before I get too deep into saturating the server with data. I was able to transfer a movie file(through shares in my network places) onto disk1 (the slow drive), that took about 2.5 hours for 8GB. I also transfer the same file to disk2 and that only took about a hour. Do I need the bwm-ng package to determine the actual disk performance for reading and writing data? Should I just change my sata cable and run preclear again and depending on the results switch Hot-Swap Bays? I don't have the full syslogs from my Disk 1 preclears because I only copied the SMART data, which was fine. Thanks for any help or pointers in the right direction. 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.