GoChris Posted March 2, 2011 Share Posted March 2, 2011 == ST2000DL003-9VT166 5YD1KDT0 == Disk /dev/sda has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 100 6 ok 214322 368 Seek_Error_Rate = 61 100 30 ok 141365 7 Spin_Retry_Count = 100 100 97 near_thresh 0 Unknown_Attribute = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 75 45 ok 26 Temperature_Celsius = 26 25 0 ok 26 Hardware_ECC_Recovered = 37 100 0 ok 214322 368 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Looks good ya? Took a while Elapsed Time: 74:50:01 Quote Link to comment
papnikol Posted March 2, 2011 Share Posted March 2, 2011 == ST2000DL003-9VT166 5YD1KDT0 == Disk /dev/sda has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 100 6 ok 214322 368 Seek_Error_Rate = 61 100 30 ok 141365 7 Spin_Retry_Count = 100 100 97 near_thresh 0 Unknown_Attribute = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 75 45 ok 26 Temperature_Celsius = 26 25 0 ok 26 Hardware_ECC_Recovered = 37 100 0 ok 214322 368 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Looks good ya? Took a while Elapsed Time: 74:50:01 seems ok to me. but 3 days? it takes 25-30hrs for a 2TB WD EARS in my pc (and it is quite old, sata I - not that it makes any much difference) when nothing else is running Quote Link to comment
Joe L. Posted March 2, 2011 Share Posted March 2, 2011 Your three cycle preclear looks great to me. The Normalized raw-read-error-rate actually improved during the process from 100 to 119. There were a few seek errors, but still well above failure threshold. Joe L. Quote Link to comment
SSD Posted March 3, 2011 Share Posted March 3, 2011 I got some strange results running preclear (v 1.6, unRAID version 5.0b4). I was running three preclears at once in screen - 2 3T and 1 2T drive. Each of them got a single error on the verification step. Here are the results of each of the postread_errors files. skip=236000 count=200 bs=8225280 returned instead of 00000 (3T) skip=260800 count=200 bs=8225280 returned instead of 00000 (3T) skip=184400 count=200 bs=8225280 returned instead of 00000 (2T) This is the first time I have run a preclear on this (new) server. It is running a C2SEE-O motherboard (2 3T drives on this controller), and a BR10i controller (2T drive is on this controller). After a reboot I tried to double check that the values of these blocks was truly zero. Here are the results: root@Shark:/boot/unmenu# dd if=/dev/sda skip=236000 count=200 bs=8225280 conv=noerror 2>/dev/null|sum| awk '{print $1}' 00000 root@Shark:/boot/unmenu# dd if=/dev/sdb skip=260800 count=200 bs=8225280 conv=noerror 2>/dev/null|sum| awk '{print $1}' 00000 root@Shark:/boot/unmenu# dd if=/dev/sdd skip=184400 count=200 bs=8225280 conv=noerror 2>/dev/null|sum| awk '{print $1}' 00000 Whatever the problem, it is not memory. I ran the memory (4G) through a 2 night memtst - no errors. Have you ever seen this before? Any ideas what might have caused it? Quote Link to comment
Joe L. Posted March 3, 2011 Share Posted March 3, 2011 I got some strange results running preclear (v 1.6, unRAID version 5.0b4). I was running three preclears at once in screen - 2 3T and 1 2T drive. Each of them got a single error on the verification step. Here are the results of each of the postread_errors files. skip=236000 count=200 bs=8225280 returned instead of 00000 (3T) skip=260800 count=200 bs=8225280 returned instead of 00000 (3T) skip=184400 count=200 bs=8225280 returned instead of 00000 (2T) This is the first time I have run a preclear on this (new) server. It is running a C2SEE-O motherboard (2 3T drives on this controller), and a BR10i controller (2T drive is on this controller). After a reboot I tried to double check that the values of these blocks was truly zero. Here are the results: root@Shark:/boot/unmenu# dd if=/dev/sda skip=236000 count=200 bs=8225280 conv=noerror 2>/dev/null|sum| awk '{print $1}' 00000 root@Shark:/boot/unmenu# dd if=/dev/sdb skip=260800 count=200 bs=8225280 conv=noerror 2>/dev/null|sum| awk '{print $1}' 00000 root@Shark:/boot/unmenu# dd if=/dev/sdd skip=184400 count=200 bs=8225280 conv=noerror 2>/dev/null|sum| awk '{print $1}' 00000 Whatever the problem, it is not memory. I ran the memory (4G) through a 2 night memtst - no errors. Have you ever seen this before? Any ideas what might have caused it? "" instead of 00000 to me indicates nothing was returned, not an invalid value. (equally suspicious as a returned value though) Quote Link to comment
mrwebsmith Posted March 3, 2011 Share Posted March 3, 2011 HELP! I'm fairly new to unraid and this is only the 5th drive i've added/run the pre-clear script on... thats what i'm seeing.. the -D doesnt help (same exact error).. this drive is approx 6mos old, from a win7 htpc... never had any issues.. in fact the SMART status PASSES in unmenu for this hitachi, as well as the SHORT Smart Test... so it seems that the drive is OK?? but the preclear script isn't able to start on it.. any help for me or should i just re-use this drive in another machine somewhere and forget about ever adding it to the unraid box? I'd be greatful for guidance from the masters here -Matt Quote Link to comment
SSD Posted March 3, 2011 Share Posted March 3, 2011 "" instead of 00000 to me indicates nothing was returned, not an invalid value. (equally suspicious as a returned value though) Any theories of why this would happen? I'm wondering if these were aligned in time. Might be nice if preclear logged the date/time of a preclear post verification read error. And even do some retries to see if it is really a data issue, or a memory or other system issue. Quote Link to comment
heffneil Posted March 4, 2011 Share Posted March 4, 2011 Question / Concern: working on my second unraid box and I am preclearing three drives at the same time. SDA SDB and SDC. All the same brand of Seagate 2 TB drives. They have been running for about 20 hours now and two are on step 10 of 10 while the other is only 80% complete of Step 2. If I remember correctly steps 3 through 9 are pretty fast but I am curious if there could be a drive problem. They are all connected to the same supermicro controller card. Any insight would be appreciated. Thanks, Neil Quote Link to comment
prostuff1 Posted March 4, 2011 Share Posted March 4, 2011 Question / Concern: working on my second unraid box and I am preclearing three drives at the same time. SDA SDB and SDC. All the same brand of Seagate 2 TB drives. They have been running for about 20 hours now and two are on step 10 of 10 while the other is only 80% complete of Step 2. If I remember correctly steps 3 through 9 are pretty fast but I am curious if there could be a drive problem. They are all connected to the same supermicro controller card. Any insight would be appreciated. Thanks, Neil Let it complete and then figure it out. With three drives all going at the same time it might just be a fact that they are completing for resources. Quote Link to comment
heffneil Posted March 4, 2011 Share Posted March 4, 2011 All three started out pretty even so this morning when I checked it I was concerned. I was going to try the fourth drive but since I am still getting this server up and running I am using trial and don't have a registered license (yet). I just ordered a new key for this machine so we will see. Thanks! Neil Quote Link to comment
heffneil Posted March 5, 2011 Share Posted March 5, 2011 Here is the results of one of the faster drives. I think there might be problems: ================================================================== 1.7 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 64 = 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 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 29C, Elapsed Time: 30:44:05 ========================================================================1.7 == ST32000542AS 5XW11CLJ == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Raw_Read_Error_Rate = 111 100 6 ok 296390 39 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 95 100 0 ok 5 Airflow_Temperature_Cel = 71 74 45 ok 29 Temperature_Celsius = 29 26 0 ok 29 Hardware_ECC_Recovered = 54 100 0 ok 296390 39 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
heffneil Posted March 5, 2011 Share Posted March 5, 2011 Another disk with eh results: ================================================================== 1.7 = unRAID server Pre-Clear disk /dev/sda = cycle 1 of 1, partition start on sector 64 = 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 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 31C, Elapsed Time: 30:53:38 ========================================================================1.7 == ST32000542AS 5XW18HK7 == Disk /dev/sda has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Raw_Read_Error_Rate = 111 100 6 ok 370534 66 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 96 100 0 ok 4 Airflow_Temperature_Cel = 69 72 45 near_thresh 31 Temperature_Celsius = 31 28 0 ok 31 Hardware_ECC_Recovered = 51 100 0 ok 370534 66 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. root@Storage2:/boot# Quote Link to comment
heffneil Posted March 5, 2011 Share Posted March 5, 2011 Slow Drive. Anyone have any thoughts on these and the above results? ================================================================== 1.7 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 64 = 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 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 28C, Elapsed Time: 43:12:41 ========================================================================1.7 == ST32000542AS 5XW1LZJT == Disk /dev/sdc has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_V LUE Raw_Read_Error_Rate = 108 100 6 ok 16115 82 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 72 74 45 ok 28 Temperature_Celsius = 28 26 0 ok 28 Hardware_ECC_Recovered = 47 100 0 ok 16115 82 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. Thanks, Neil Quote Link to comment
prostuff1 Posted March 5, 2011 Share Posted March 5, 2011 I would run the slow drive through 2 more cycles. I run all my drives through 3 total cycles, but the slow one should be run again. Quote Link to comment
heffneil Posted March 5, 2011 Share Posted March 5, 2011 Yeah It just takes FOREVER! The slow one was more than 35 hours!!! I am not that patient Neil Quote Link to comment
betaman Posted March 5, 2011 Share Posted March 5, 2011 Just started a new pre_clear and noticed these errors related to the hdparm command. Should I be concerned? FYI, the drive is attached to an AOC-SASLP-MV8 card. Mar 5 14:21:08 Tower kernel: Pid: 7560, comm: hdparm Not tainted 2.6.32.9-unRAID #8 (Errors) Mar 5 14:21:08 Tower kernel: Call Trace: (Errors) Mar 5 14:21:08 Tower kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Mar 5 14:21:08 Tower kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors) Mar 5 14:21:08 Tower kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors) Mar 5 14:21:08 Tower kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors) Mar 5 14:21:08 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Mar 5 14:21:08 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Mar 5 14:21:08 Tower kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors) Mar 5 14:21:08 Tower kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors) Mar 5 14:21:08 Tower kernel: [<f844d69a>] sas_queuecommand+0x65/0x20d [libsas] (Errors) Mar 5 14:21:08 Tower kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Mar 5 14:21:08 Tower kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors) Mar 5 14:21:08 Tower kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors) Mar 5 14:21:08 Tower kernel: [<c1126798>] __blk_run_queue+0x78/0x10c (Errors) Mar 5 14:21:08 Tower kernel: [<c1124446>] elv_insert+0x67/0x153 (Errors) Mar 5 14:21:08 Tower kernel: [<c11245b8>] __elv_add_request+0x86/0x8b (Errors) Mar 5 14:21:08 Tower kernel: [<c1129343>] blk_execute_rq_nowait+0x4f/0x73 (Errors) Mar 5 14:21:08 Tower kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors) Mar 5 14:21:08 Tower kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors) Mar 5 14:21:08 Tower kernel: [<c112636f>] ? get_request+0x204/0x28d (Errors) Mar 5 14:21:08 Tower kernel: [<c11269d6>] ? get_request_wait+0x2b/0xd9 (Errors) Mar 5 14:21:08 Tower kernel: [<c112c2bf>] sg_io+0x22d/0x30a (Errors) Mar 5 14:21:08 Tower kernel: [<c112c5a8>] scsi_cmd_ioctl+0x20c/0x3bc (Errors) Mar 5 14:21:08 Tower kernel: [<c11b3257>] sd_ioctl+0x6a/0x8c (Errors) Mar 5 14:21:08 Tower kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors) Mar 5 14:21:08 Tower kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors) Mar 5 14:21:08 Tower kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors) Mar 5 14:21:08 Tower kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors) Mar 5 14:21:08 Tower kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors) Mar 5 14:21:08 Tower kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Mar 5 14:21:08 Tower kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors) Mar 5 14:21:08 Tower kernel: [<c1048c43>] ? unlock_page+0x18/0x1b (Errors) Mar 5 14:21:08 Tower kernel: [<c1057c63>] ? __do_fault+0x3a7/0x3da (Errors) Mar 5 14:21:08 Tower kernel: [<c105985f>] ? handle_mm_fault+0x42d/0x8f1 (Errors) Mar 5 14:21:08 Tower kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors) Mar 5 14:21:08 Tower kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors) Mar 5 14:21:08 Tower kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors) Mar 5 14:21:08 Tower kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors) Mar 5 14:21:08 Tower kernel: [<c105dcdd>] ? do_mmap_pgoff+0x232/0x294 (Errors) Mar 5 14:21:08 Tower kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors) Mar 5 14:21:08 Tower kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Quote Link to comment
jeff.lebowski Posted March 5, 2011 Share Posted March 5, 2011 Just started a new pre_clear and noticed these errors related to the hdparm command. Should I be concerned? FYI, the drive is attached to an AOC-SASLP-MV8 card. In one of the threads talking about this error, someone tried the pre_clear over and over until started. It was also mentioned that NO other processes were active when running pre_clear. Checking array, moving files, etc. Your issue and the other may not be related, but they seem to be at my (n00b) first glance. Quote Link to comment
betaman Posted March 5, 2011 Share Posted March 5, 2011 Thanks for the response. I probably should've noted that the script is running and advancing like normal. I just thought I should report the errors just in case they were more serious than I suspected. Just saw this thread: http://lime-technology.com/forum/index.php?topic=11501.0 Quote Link to comment
larson Posted March 8, 2011 Share Posted March 8, 2011 Ran a preclear on sdb yesterday, it probably finished sometime last evening. The session was idle overnight until I checked it now. Results made me want to run it again. I just went back to previous command by using up arrow and ran it again. Now I got something I never noticed before. Should I continue my preclear? root@Tower:/boot# preclear_disk.sh /dev/sdb ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/"e"/block: No such file or directory ls: cannot access /sys/devices/"public"/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/"-"/block: No such file or directory ls: cannot access /sys/devices/"public"/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/"-"/block: No such file or directory ls: cannot access /sys/devices/"public"/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory Pre-Clear unRAID Disk /dev/sdb ################################################################## 1.7 Model Family: Seagate Barracuda 7200.11 family Device Model: ST31000333AS Serial Number: 9TE1MZ4Q Firmware Version: CC1H User Capacity: 1,000,204,886,016 bytes Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 63 1953525167 976762552+ 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## invoked as ./preclear_disk.sh /dev/sdb ######################################################################## (partition starting on sector 63) (it will not be 4k-aligned) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): /Lars Olof Quote Link to comment
Joe L. Posted March 8, 2011 Share Posted March 8, 2011 Ran a preclear on sdb yesterday, it probably finished sometime last evening. The session was idle overnight until I checked it now. Results made me want to run it again. I just went back to previous command by using up arrow and ran it again. Now I got something I never noticed before. Should I continue my preclear? root@Tower:/boot# preclear_disk.sh /dev/sdb ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/"e"/block: No such file or directory ls: cannot access /sys/devices/"public"/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/"-"/block: No such file or directory ls: cannot access /sys/devices/"public"/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/"-"/block: No such file or directory ls: cannot access /sys/devices/"public"/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory ls: cannot access /sys/devices/""/block: No such file or directory Pre-Clear unRAID Disk /dev/sdb ################################################################## 1.7 Model Family: Seagate Barracuda 7200.11 family Device Model: ST31000333AS Serial Number: 9TE1MZ4Q Firmware Version: CC1H User Capacity: 1,000,204,886,016 bytes Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 63 1953525167 976762552+ 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## invoked as ./preclear_disk.sh /dev/sdb ######################################################################## (partition starting on sector 63) (it will not be 4k-aligned) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): /Lars Olof Yes, you can continue. I just need to not let those warning messages end up in the output. They are a result of me testing for drives already assigned to the array. The messages are harmless. The files they are testing for only exist in some versions of unRAID. Joe L. Quote Link to comment
larson Posted March 8, 2011 Share Posted March 8, 2011 Yes, you can continue. I just need to not let those warning messages end up in the output. They are a result of me testing for drives already assigned to the array. The messages are harmless. The files they are testing for only exist in some versions of unRAID. Joe L. Thanks for letting me know, Joe. /Lars Olof Quote Link to comment
jonlai9 Posted March 10, 2011 Share Posted March 10, 2011 Just wondering, what merit does the 'threshold' and 'type' have? I see a lot of people have values higher than the threshold where the types are saying pre-fail or old_age... are these of any concern or just the RAW_VALUE is what we care about? I'm curious as to why my Seagate is reporting some interesting numbers... Aren't these really big numbers? SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 116 100 006 Pre-fail Always - 115761536 <<<<<<<<<<< 3 Spin_Up_Time 0x0003 094 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 18 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 734918 <<<<<<<<<<< 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 87 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 9 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 066 066 045 Old_age Always - 34 (Lifetime Min/Max 28/34) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 3 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 18 194 Temperature_Celsius 0x0022 034 040 000 Old_age Always - 34 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 026 017 000 Old_age Always - 115761536 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 234552459001957 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1401882945 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1452924888 These two WD's look alright to me, right? SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 151 150 021 Pre-fail Always - 9416 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1076 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 096 096 000 Old_age Always - 3113 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 248 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 10 193 Load_Cycle_Count 0x0032 142 142 000 Old_age Always - 175274 194 Temperature_Celsius 0x0022 117 112 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 149 149 021 Pre-fail Always - 9516 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1001 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3415 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 254 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 149 149 000 Old_age Always - 155865 194 Temperature_Celsius 0x0022 117 111 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 However, I just tried to preclear another WD today, an EARS, and preclear hung (I think?). I look at the SMART and I see the following... does this mean I should RMA it? 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 110 110 051 Pre-fail Always - 17898 <<<<<<<<<<< 3 Spin_Up_Time 0x0027 162 161 021 Pre-fail Always - 8900 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 199 5 Reallocated_Sector_Ct 0x0033 149 149 140 Pre-fail Always - 403 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 607 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 61 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8 193 Load_Cycle_Count 0x0032 181 181 000 Old_age Always - 57559 194 Temperature_Celsius 0x0022 119 118 000 Old_age Always - 33 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 240 197 Current_Pending_Sector 0x0032 198 197 000 Old_age Always - 939 198 Offline_Uncorrectable 0x0030 198 197 000 Old_age Offline - 857 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 188 188 000 Old_age Offline - 2480 SMART Error Log Version: 1 ATA Error Count: 17860 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Thanks. Quote Link to comment
Joe L. Posted March 10, 2011 Share Posted March 10, 2011 The RAW values have meaning ONLY to the manufacturer. Only a few represent actual counts we can interpret. As an example, the "head flying hours" on your first disk has a raw value of 234552459001957 Now, even if not "hours" but seconds, it would indicate the drive was 446,246,575 years old. Now, it might be... but it is very unlikely. There is NO standard for the raw values. You can only compare the NORMALIZED "VALUE" to its affiliated failure "THRESHOLD" If higher than the threshold, the parameter is NOT failing. All your disks are perfectly fine. The "big" numbers are meaningless. Quote Link to comment
jonlai9 Posted March 10, 2011 Share Posted March 10, 2011 The RAW values have meaning ONLY to the manufacturer. Only a few represent actual counts we can interpret. As an example, the "head flying hours" on your first disk has a raw value of 234552459001957 Now, even if not "hours" but seconds, it would indicate the drive was 446,246,575 years old. Now, it might be... but it is very unlikely. There is NO standard for the raw values. You can only compare the NORMALIZED "VALUE" to its affiliated failure "THRESHOLD" If higher than the threshold, the parameter is NOT failing. All your disks are perfectly fine. The "big" numbers are meaningless. Thanks Joe, that's definitely great to hear. What do all the old_age and pre-fail mean then? When I first saw them, they were displeasing, until I saw others who had good drives also had those. Why would they have such statuses if they are fine? I'm concerned about my WD EARS then - my last drive posted. When I was migrating data from the disk in Windows, some files would not get copied, and I was reported I/O Error, 0x8007045d. They weren't important files, and I thought, maybe preclear will fix it, it's probably a corrupted sector or something. But when I tried to preclear it, it just hung. It even brought down unMENU with it, but it was probably just a coincidence. After a few minutes when I got back into unMENU, it reported: kernel: end_request: I/O error, dev sdd, sector 1495592 (Errors) kernel: Buffer I/O error on device sdd, logical block 186949 (Errors) That can't be good, right? Should I run a long SMART on this drive? Thanks. 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.