Drift King

Not sure if this is explicitly because of the pre-clear updates, but I'm pretty these started showing up on the day of the pre-clear update. Any thoughts on this? root@NAS:/usr/bin# ls -la run* -rwxr-xr-x 1 root root 1036 May 10 2016 run-parts* lrwxrwxrwx 1 root root 16 Nov 5 18:29 runcon -> ../../bin/runcon* root@NAS:/etc/cron.daily# ls -la total 8 drwxr-xr-x 2 root root 80 Dec 30 10:24 ./ drwxr-xr-x 48 root root 2600 Dec 25 00:03 ../ -rwxr-xr-x 1 root root 3912 Nov 7 06:36 exportrotate* -rwxr-xr-x 1 root root 129 Apr 17 2015 logrotate* None of the permissions on any of these is 644 or 444 - are they supposed to be? Neither of the two files in /etc/cron.daily contains the text "tor", so it doesn't appear to be something that is being called from there, and the only reference to "tor" in run-parts is in the word "directory". I'm a bit lost... Same issue here... =(

Agreed, I also run 2 servers that are pretty dang close to yours. I have a bunch of 3/4TB reds too, and just made the switch to Seagate Archive drives. Haven't got them yet, still a bit worried about overall performance of them. No issues here with the 8TB Archive drives. Half of them have been in service for 6 months. They perform just as well as the Red's (with writes being just a tad slower). I use my servers for media storage so the slower write speeds are not an issue. I do wonder about longevity, but only time will tell. I figure, by the time these guys start degrading, I will have upgraded to bigger/faster drives. In fact, I am looking forward to getting my hands on a Seagate ST8000VN0002 once they drop down to a more reasonable price.

I just wanted to say thank you to jbrodriguez for this great plug-in. I just completed the migration of almost 160 TB's of data across my 2 UNRAID servers while completing the upgrade to the XFS file system. Over 2 months of data movement and it all went along without a snag. Thanks again!