powerchoke

I'm pretty sure I saw bestbuy has these same drives for same price yesterday. You guys might check there.

I made some slight mods to my /boot/packages/mail-ssmtp-unmenu-package.conf to download and install v2.64 obtained from here: http://packages.debian.org/source/squeeze/ssmtp. I commented out the lines referencing v2.62 and replaced them with 2.64 directly below where necessary, updated the md5 checksum, and added an additional step to rename the ssmtp dir to conform to that required by the installation script. It works great for me, but of course, use at your own risk. mail-ssmtp-unmenu-package.conf

I concur with Helmonder - get it off the internet. A secure password is not enough IMO. When I think I'll need to be accessing mine from the outside I temporarily open the firewall in my router to allow the narrowest access required.

See here: http://forums.sabnzbd.org/viewtopic.php?t=10378 Similar fix was necessary for my v14 (and perhaps others). I had to mod <SABnzbd install dir>/interfaces/Plush/templates/queue.tmpl in a similar way. It seems v15 won't even start without this fixed. v14 just fails to display the queue section. Cheers

Thanks for the response RobJ. I'm going to run preclear two more times over the weekend and if everything checks out I'll install them. BTW, preclear took just over 19hrs to complete both drives (in parallel).

Bigdady92 - did you preclear them? I just finished my preclear of same drives and need reassurance that the high Spin_Retry_Count and End-to-End_Error threshold values are nothing to worry about. (http://lime-technology.com/forum/index.php?topic=4068.msg172474#msg172474). If you precleared them did you notice same?

I just completed the first preclear runs on two Seagate ST2000DM001's and had results nearly identical to khuong's. I, too, am concerned about the near_thresh report by preclear for Spin_Retry_Count and End-to-End_Error. These are both brand new hdd's - why such high thresholds for these parameters? Also, there was no diff between pre- and post- read for these values so I'm guessing it's reported in the 'Changed' summary because the values are close to the threshold values. ============================================================================ ** 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 = 112 100 6 ok 42522288 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 66 71 45 near_thresh 34 Temperature_Celsius = 34 29 0 ok 34 No SMART attributes are FAILING_NOW Thanks Joe for the excellent script! I read the entire thread (and a few tangential ones along the way). Your wealth of knowledge is impressive, your contribution greatly appreciated and your patience with repeat questions is commendable. This is such a great board! preclear_finish__S2F01FZA_2012-04-05.txt preclear_start__S2F01FZA_2012-04-05.txt preclear_rpt__S2F01FZA_2012-04-05.txt