heffneil

This is the output I got recently on my suspect drive while preclearing: = Post-Read in progress: 3% complete. ( of 2,000,398,934,016 bytes read ) Elapsed Time: 29:55:11 ./preclear_disk.sh: line 1080: 0+()%(243201) : syntax error: operand expected (error token is ")%(243201) ") ========================================================================1.11 == ST32000542AS 5XW1CTY2 == Disk /dev/sdi has NOT been precleared successfully == skip=3800 count=200 bs=8225280 returned instead of 00000 skip=6000 count=200 bs=8225280 returned instead of 00000 ============================================================================ Any ideas what is broken here? I am running this: preclear_disk.sh -A -c 3 /dev/sdi Thanks! Neil

I am running preclear and I used screen. I reconnected and it looks frozen. Problem is I don't know if it truly is locked up or if this is a problem with the interface. When I run ps -al I see the following: 0 S 0 3150 2665 0 80 0 - 880 wait pts/1 00:00:26 preclear_disk.s 1 S 0 24628 3150 0 80 0 - 880 pipe_w pts/1 00:00:00 preclear_disk.s 1 S 0 24634 24628 0 80 0 - 880 wait pts/1 00:00:00 preclear_disk.s 0 D 0 24635 24634 50 80 0 - 2457 - pts/1 03:37:41 dd 0 R 0 24636 24634 24 80 0 - 434 pipe_w pts/1 01:44:07 sed 0 S 0 24637 24634 0 80 0 - 524 pipe_w pts/1 00:00:00 awk 4 S 0 24668 24654 0 80 0 - 627 pause pts/0 00:00:00 screen 4 R 0 24691 24670 0 80 0 - 519 - pts/2 00:00:00 ps Not sure if I screwed this up or if this drive is suspect. It was laying around and I thought in previous installs it was a problem so I wanted to run it through its paces before I considered using it again. Any suggestions would be greatly appreciated. Thanks, Neil

The server is totally rebuilt with that one drive and everything looks great! Thanks for all the help! Neil

The upgrade instructions are in the announcement thread, basically yes, but there is also a newer version of the memory test file to copy in place, so three files in total for you: Upgrading an existing Flash Device ---------------------------------- Note: after upgrading, some changes may require additional user intervention, please refer to the Change Log below. If you are currently running unRAID Server 4.6 or higher, please copy the following files from the new release to the root of your Flash device: bzimage bzroot If you are currently running unRAID Server 4.5.x, 4.4.x, 4.3.x or 4.2.x, please copy the following files from the new release to the root of your Flash device: bzimage bzroot memtest Interestingly enough I had a bzroot.456 and a bzimage.456 turns out I did upgrade this server from 4.5 to 4.6 so I just copied the two files over after renaming the old ones. Also for good measure I copied the entire usb drive to a directory on my server. Going to reboot and sacrifice a lamb (just kidding about the last part)

I posed this question before and I Was looking for the reference. Thank goodness I don't upgrade often enough to remember. By config page do you mean my devices? So is realy 4.7 just those two files you have me renaming? I just want to make sure I don't screw this up. Currently I am at 4.5 so I don't know if that will make a difference... Neil

Ok great now I am going to upgrade to 4.7 and replace the suspect drive. Wish me luck! Please god don't let me mess this up

Here are the results of the -V. Can you tell me if this looks ok? ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 117 6 ok 60178126 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 68 66 45 near_thresh 32 Temperature_Celsius = 32 34 0 ok 32 Hardware_ECC_Recovered = 51 44 0 ok 60178126 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 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. Is this drive ok and ready to use now? Thanks! Neil

If you think it was near the end you can use the "-V" option It will skip to the verification phase. (the post read phase) = Step 1 through 9 skipped, verify phase will be performed next = Step 10 of 10 - The MBR is NOT verified un-aligned cleared. = However, its MBR is verified cleared for 4k-alignment = starting on sector 64 = Post-Read in progress: 0% complete. ( 1,645,056,000 of 2,000,398,934,016 bytes read ) 104 MB/s Disk Temperature: 34C, Elapsed Time: 0:00:18 So I don't know if this is ok or not? Any thoughts? I wasn't sure if the -V would tell me if everything was kosher?

I got two more drives cooking in another server. No one ever answered my question about the script 1.7 vs. 1.9? See about two or three comments higher. Thanks, Neil

Crap I was afraid you would say that. I mean being 24 hours in to whats another 30 hours

I am running 1.7 and I noticed 1.9 is out?! Can I replace the script while it is being ran for one drive so I have the latest for the other? Is 1.9 a significant update? Is there a changelog anywhere? Can I rename 1.9 to preclear_disk1.sh and run that in addition if I can't replace the existing one? Thanks!

Server crashed. Any way to recover or do I have to restart the preclear?!

root@Storage:/tmp# ps -a | grep "dd" 8672 pts/0 00:00:00 dd That first number is growing so I don't know what it means

root@Storage:/# tail -f /tmp/zerosdi 953397+1 records in 953397+1 records out 1999419203584 bytes (2.0 TB) copied, 26129 s, 76.5 MB/s 953680+1 records in 953680+1 records out 2000012697600 bytes (2.0 TB) copied, 26140.4 s, 76.5 MB/s dd: writing `/dev/sdi': No space left on device 953864+1 records in 953863+1 records out 2000396836864 bytes (2.0 TB) copied, 26148.9 s, 76.5 MB/s This a good sign?

I am stupid I didn't realize X was a variable there. Sorry for the confusion. I don't have that results directory should I make it or will it be made when the script is finished? Thank god for Joe! Neil

yes, a summary reoprt is written to /boot/preclear_reports directory and to the system log. If it is in the "write" phase you can follow along somewhat by typing tail -f /tmp/zerosdX where sdX = the three letter device name for your disk. Press Control-C to stop the "tail" command. Joe L. The tail didn't work it said no such file and I don't have the directory preclear_reports ? I know the process is still running because I see DD running with preclear.sh running as well?

Ok I screwed up and I can't watch the progress of my preclear but I know it is running! Is there any results written via file at the end of the process so I can make sure everything looks kosher? I can not reconnect to my telnet session unfortunately

Joe, Can one preclear a drive and pull it out and put it on the shelf for a rainy day spare? I say the shelf because I have two different unraid servers and I would like to interchangeably put that spare in either machine. Is that possible? Thanks! Neil

I onlyl did one for each of my two servers. I am too impatient to do more than that. Knock on wood no issues.

Yeah It just takes FOREVER! The slow one was more than 35 hours!!! I am not that patient Neil

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

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#

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.

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

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