ufopinball

I have 10 of these babies in my unRaid system as well, but they are the Samsung variety. I actually ordered two of the above just 10 days ago (for $129 ) and they are the newer Seagate variety. The NewEgg feedback shows problems with some recent drives, but the two I got seem to be doing okay. No DOA, and each has completed a full pre-clear cycle. They're on round 2 right now ... so far, so good. I'm somewhat tempted to buy more since the price is good, but it makes more sense to space out drive purchases to keep a variety of manufacturing times in the system. Anyway, I don't know that I actually *need* more drives right now, just wanted to have a few spares ready to go, if/when something happens. I should really hold off, since prices will probably continue to go down anyway.

lionelhutz: The time looks correct on the server. This issue has been prevalent since I started watching the system logs ... here's an excerp from February: Feb 15 13:20:36 Tower ntpd[4344]: time reset +1.824718 s Feb 15 13:21:18 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 13:37:16 Tower ntpd[4344]: time reset +1.827630 s Feb 15 13:38:53 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 13:52:52 Tower ntpd[4344]: time reset +1.619187 s Feb 15 13:56:33 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 14:08:27 Tower ntpd[4344]: time reset +1.808663 s Feb 15 14:08:57 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 14:24:58 Tower ntpd[4344]: time reset +1.780413 s Feb 15 14:26:55 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 14:40:58 Tower ntpd[4344]: time reset +1.819013 s Feb 15 14:41:24 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 14:57:19 Tower ntpd[4344]: time reset +1.783335 s Feb 15 14:58:24 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 15:13:19 Tower ntpd[4344]: time reset +1.844454 s Feb 15 15:14:17 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 15:29:21 Tower ntpd[4344]: time reset +1.672699 s Feb 15 15:30:12 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 15:46:10 Tower ntpd[4344]: time reset +1.852655 s Feb 15 15:48:02 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 16:03:11 Tower ntpd[4344]: time reset +1.807470 s Feb 15 16:03:31 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 16:19:34 Tower ntpd[4344]: time reset +1.805922 s Feb 15 16:20:31 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 16:36:27 Tower ntpd[4344]: time reset +1.829539 s Feb 15 16:38:11 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 16:53:22 Tower ntpd[4344]: time reset +1.760835 s Feb 15 16:53:35 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 17:09:34 Tower ntpd[4344]: time reset +1.943465 s Feb 15 17:10:20 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 17:26:21 Tower ntpd[4344]: time reset +1.851357 s Feb 15 17:26:55 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 17:42:56 Tower ntpd[4344]: time reset +1.776809 s Feb 15 17:44:38 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 Feb 15 17:59:46 Tower ntpd[4344]: time reset +1.781927 s Feb 15 18:01:17 Tower ntpd[4344]: synchronized to 72.18.205.157, stratum 3 I haven't had a chance to pick up a battery yet. Since the server seems largely unaffected, it's more of a background concern than a serious worry.

Thanks BRiT ... the system has been on-line in excess of a month. I'll check the CMOS battery though, that's a good thought!

Is it normal to see so many "time reset" entries in the Syslog, especially since every 15-20 minutes it seems to be off by nearly 2 seconds? Would this otherwise point to an "irregular" motherboard RTC? I'm not having any other problems with the array. I'm running 4.7, if that matters. Mar 12 13:24:27 Tower ntpd[4344]: time reset +1.935324 s Mar 12 13:25:33 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 13:41:34 Tower ntpd[4344]: time reset +1.933601 s Mar 12 13:42:11 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 13:58:09 Tower ntpd[4344]: time reset +1.917152 s Mar 12 14:01:41 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 14:14:43 Tower ntpd[4344]: time reset +1.928331 s Mar 12 14:15:53 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 14:29:47 Tower ntpd[4344]: time reset +1.804823 s Mar 12 14:30:09 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 14:45:10 Tower ntpd[4344]: time reset +1.807665 s Mar 12 14:46:44 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 15:01:49 Tower ntpd[4344]: time reset +1.921322 s Mar 12 15:02:54 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 15:17:42 Tower ntpd[4344]: time reset +1.911500 s Mar 12 15:19:58 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 15:32:56 Tower ntpd[4344]: time reset +1.817606 s Mar 12 15:34:06 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 15:47:58 Tower ntpd[4344]: time reset +1.810125 s Mar 12 15:50:23 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 16:04:19 Tower ntpd[4344]: time reset +1.899462 s Mar 12 16:06:32 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 16:19:33 Tower ntpd[4344]: time reset +1.802038 s Mar 12 16:20:40 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 16:34:35 Tower ntpd[4344]: time reset +1.813973 s Mar 12 16:34:57 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 16:50:57 Tower ntpd[4344]: time reset +1.921427 s Mar 12 16:52:04 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 17:06:55 Tower ntpd[4344]: time reset +1.913367 s Mar 12 17:07:26 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 17:23:21 Tower ntpd[4344]: time reset +1.911000 s Mar 12 17:25:10 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Mar 12 17:40:10 Tower ntpd[4344]: time reset +1.905497 s Mar 12 17:40:55 Tower ntpd[4344]: synchronized to 204.9.136.253, stratum 2 Thanks!!

This is more of a quick-fix than an actual solution, but from the Run prompt, can you just type in "\\tower\disk1" and have it work? Maybe just create some shortcuts on your desktop? I actually mapped my unRAID volumes to drive letters on my Windows box, because I am basically porting an existing local disk array to the NAS, and this will keep things running smoothly until I find the time to work out something better.

Thanks guys, I ended up getting the Husky 3" x 4 1/2" Deep Reach C-Clamp and it's a good thing I did because it can easily reach the back tabs from the front of the case. With the motherboard tray in place (not easily removable, if at all), you don't have access from the back on the motherboard side of the drive bays. My only issue was the handle on the crank seriously needed to be bigger. Anyway, if it helps, I got it from Home Depot. UPC Code 8 11187 01352 9 It only took an evening (I had some distractions), and now I have all three of the ICY DOCK 5-in-3 drive cages installed. Thanks again!

I have been building my own unRAID server, based on the recommendations on the site. So far, I have purchased the LIAN LI ARMORSUIT PC-P50 case, as well as three of the ICY DOCK MB455SPF-B (5-in-3 drive cages). My issue is that the upper three 5.25" drive bays include those "helpful" tabs to guide an incoming drive, but end up blocking the smooth installation of the upper 5-in-3 drive cage. I have tried bending them with a pair of pliers, and while I can make some progress, the poor angle and limited space make this for a complicated operation. Any ideas on how best to remove these guys? Thanks!! Bill