mbryanr

Strange..works on my setup <see below> Should probably go in the SImpleFeatures thread to get more attention. Simple Features.... Line 61: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs cache_dirs process ID 857 started, To terminate it, type: cache_dirs -q Line 62: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs ---------------------------------------------- Line 63: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs movies Line 64: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs ---------- caching directories --------------- Line 65: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs version=1.6.6 Line 66: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs command=find -noleaf Line 67: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs max_depth=9999 Line 68: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs max_seconds=10, min_seconds=1 Line 69: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs vfs_cache_pressure=10 Line 69: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs vfs_cache_pressure=10 Line 70: 2012-07-01 19:43:40 notice 192.168.1.108 user cache_dirs command-args=-w -B -m1 -M10 -d9999 -eAutumn -e Documents -e music -imovies Earlier unMENU install Line 536: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs cache_dirs process ID 3755 started, To terminate it, type: cache_dirs -q Line 537: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs ---------------------------------------------- Line 538: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs music Line 539: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs movies Line 540: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs Documents Line 541: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs Autumn Line 542: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs ---------- caching directories --------------- Line 543: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs version=1.6.5 Line 544: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs command=find -noleaf Line 545: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs max_depth=9999 Line 546: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs max_seconds=10, min_seconds=1 Line 547: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs vfs_cache_pressure=10 Line 547: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs vfs_cache_pressure=10 Line 548: 2012-06-24 12:39:03 notice 192.168.1.108 user cache_dirs command-args=-w -m 1 -M 10 -d 9999 -a -noleaf

Looks like you had a drive with previous errors (607 sectors reallocated, 52 sectors pending re-allocation) Those 52 sectors pending re-allocation were successfully rewritten after zeroing the disk. Raw Value = 0 Looks like a Samsung drive. If I guessed I'd say a HD154UI? Anyways, the Reported_Uncorrect were (read) errors that could not be corrected with ECC (lower number better) Although "OK" - I would run another preclear cycle.

I'm interested in your build as a second/test server for myself. Primarily to learn Ubuntu and run Crashplan. unRAID was my first foray into the Linux OS world and I've been impressed with the performance. I like the Helios, but will probably choose something different for improved cable management. You may find the fans dB to be excessive for the bedroom. A fan controller helps some. A possibility is disconnecting the large 230mm fan. I was tempted to do that when I had 3 drives installed. Replacement of the stock fans is another option you mentioned. btw, I like your choice in power supplies, although it may not run as efficiently as a smaller PSU, Seasonics are solid, modular is a plus for cable management, and I will bet that your build grows to 10-12 drives! One valuable addition to your build - UPS. I found mine to be invaluable in protecting the server, and avoiding those long parity checks - especially when they occur <1 day after completing a scheduled check. Welcome to the forum and enjoy! Edit: Remember to check the serial number on your Samsung drives and update the fw if necessary.

What version of pre-clear were you using? IIRC the pre-clear dialog states: http://lime-technology.com/forum/index.php?topic=2817.msg23246#msg23246 1. True. -a = force MBR-unaligned. -A = force starting sector to be on sector 64 for 4k alignment. 2. Note: The -A is not required if you have the "MBR-4K Aligned" set as default in your device settings. Any drive can be formatted to start on sector 64 http://lime-technology.com/forum/index.php?topic=10198.0 I believe you can: (verify with more experienced users) 1. Set "MBR-4K Align" in the unRAID management page 2. Run this command from telnet- dd if=/dev/zero of=/dev/sdX count=2 where sdX = the device for the disk being cleared. This will clear the MBR of your disk. Edit: Found Joe created the preclear -z option to accomplish the same. Can someone verify this is the correct procedure? Thanks. http://lime-technology.com/forum/index.php?topic=2817.msg102326#msg102326

Thanks. The SATA Cables are from www.monoprice.com (another great site I learned about from this forum). They are KGear GC18AKM SATA3 cables. I ordered them color-coded. Red = Data Blue = Parity Black = Cache Dang! That's a nice idea. Next time when I need more cables, I'll see if I can order a rainbow set. They have Limetech green as well. Mine is setup as Limetech Green - Parity Blue = Data.

Very nice Steven! Makes me feel like my new server was made out of wood.

Joe, I noticed the Load Cycle Count increase <pre-->post>. It got me thinking about the WD high LCC issue. I found a decent summary in the Syno forum (I have a 210j), but nothing yet in the unRAID wiki. Is it something that should be notated or a non-issue? http://lime-technology.com/forum/index.php?topic=5086.msg53803#msg53803 http://forum.synology.com/enu/viewtopic.php?f=124&t=11682#p49067

Joe can confirm, but it looks good. Here are (2) quick starter instructions for interpreting results http://lime-technology.com/forum/index.php?topic=2817.msg53337#msg53337 http://lime-technology.com/forum/index.php?topic=8278.msg81032#msg81032 @somewhatlost That value is a RAW value, which change frequently and are used by manufacturers. Reference http://xpt.sourceforge.net/techdocs/nix/disk/general/disk18-DiskTestHealthMonitoring/ar01s06.html