aiden

You'll have no problem moving it here if you decide it's not for you. It's a fantastic unRAID platform.

Anyone wanting to read about unRAID on the Microservers should go here . And yes, you have to use ECC memory I believe.

Ever tried a picoPSU, like this - http://www.mini-box.com/picoPSU-160-XT? You can also add external bricks to increase the power. But if you're only going to run a few drives, 160W should be plenty.

Obviously you're trying to create something audiophile in nature by removing mechanical spindle noise. I would humbly submit it is possible to eliminate such noise using a well sound-proofed case and passively cooled PSU. It would be a much less expensive alternative to using SSDs, which have a less then stellar reliability compared to their mechanical brethren.

+1 GRC is an amazing company, and their free tools are indispensable for security.

Just deployed 3 Versatek POE injector/splitter combinations over a standard gigabit network and it works perfectly. Injector - $36.99 Splitter - $27.99

Plenty of people here are running unRAID with 16GB of memory. The limitation you'll run into with RAM will be the hardware you use, not unRAID.

I can't argue with that. They really shouldn't have it advertised unless it is reality, and they should have taken it down when they realized it wasn't happening.

We all have our little hot buttons and wants, but I have to say one of the biggest advantages to me of unRAID is its simplicity. If I want to pull a drive and put in another machine, I can do so and recover ALL the data on that drive by simply mounting it. No striped parity scheme can pull that off. I don't understand the want of huge write speeds, but then again, I use my server as an archive, not a working file server with living documents. But by design, striping has always been a faster way to write parity. And the 3TB arguments are so tired.

I feel compelled to explain that HDI has had the Netflix code written and waiting for over a year now. The issue for them has been Netflix's reluctance to approve the Dune lineup. Feel free to sign this online petition directed towards Netflix. I doubt it will have any impact, and I'm just as irritated by the lack of movement on their part as you have shown in the MPC Club forums.

My system is 12 drive capable, in an 8 bay case with 4x 3-in-2 hotswap drive slots. A lot of people go for the 24 drive Norco because it's just so damn cost effective, and it gives you to the maximum number of drives possible in an unRAID build.

Yes. I always run 3 passes, even on 3TB drives. I have found failures in the 3rd pass that didn't happen in the first 2.

This is the case I'm currently using for my 12 drive server. It's a great case for the price, and has lots of ventilation options.

This should be easy enough to configure using the plugin system and providing an easy GUI for the settings. Perhaps even updates of the fan status. I have one additional challenge for you, though. In my case, I have 4 drive cages, with their own PWM fans. I want to configure the fan script so that it addresses each fan speed according to the drives available for THAT cage. AHA!!! Since invoking the script 4 times is not efficient, you would need to go back to the arrayed drive approach to configure one set of drives per fan control. I was planning on visiting this in my original script, but yours is much more advanced, including the detection loop that bypasses the need to configure all the drives. Being able to independently control the fans isn't critical, and the script works fine pushing all the fans to the same speed based on the hottest drive. Think of this as more of a fine tuning.

Thanks for updating this, Dan. I am clearly a novice at linux and bash scripting, so while I wanted to write it with proper functions and loops, I didn't have the experience to do so. I might add that the script I wrote was in fact a modification of the script started by Starcat. You might want to include him in your author list in the opening comments. Also, I wanted to mention that my comment about this script working for v5 was based on beta-11, which was the last beta to use the 2.6.37.6 kernel. beta-12a uses 3.0.4. Now that may or may not have anything to do with your difficulties, but I don't want you to feel like I just "phoned in" my comment without checking.

That's good enough for me.

Okay, now I have a question. According to Hitachi, the 3TB drives they manufacture are not 4K aligned drives, and in fact use 512 byte sectors. Preclearing using the non-AF switch did indeed start them at sector 63. However, when formatting them with GPT via unRAID they were forced to start on sector 1. I thought unRAID would respect the precleared sector alignment and maintain it, but in fact it did not. Isn't that a bad situation if the drive isn't aligned the way it was manufactured to be? Does GPT require AF alignment, or was this just an assumption? Is there a way to realign the drives to sector 63 AFTER they have been partitioned, and without data loss? This is with v5b11.

Reiserfs is arguably one of the better features in unRAID. It has an incredible resiliency that other file systems simply do not have. I know there are plenty of people here who can attest as much.

Can you browse for your server using the Network Browser in your Dune? This assumes you have Samba turned on for your share. Also, what version of unRAID? Are your shares still visible and correct in unRAID?

According to Zoneminder's website, it works with most types of surveillance cameras. Webcams are not generally designed for surveillance applications.

Why not purchase one of the Supermicro cooling solutions... passive or active.

That is an intake fan, so it is designed to bring air into the PSU to cool it, and exhaust out the back. You can mount the PSU with the fan pointing either up OR down, depending on your needs.

WD bought Hitachi because Hitachi makes a better drive. The WD's haven't been as reliable from what I've seen. Personally I'm scared of what WD will do to Hitachi's drives.

That's not something you have to have in the go script. This is the relevant code in my go script: # Insert fan_speed.sh into crontab chmod +x /boot/scripts/fan_speed.sh crontab -l >/tmp/crontab grep -q "fan_speed.sh" /tmp/crontab 1>/dev/null 2>&1 if [ "$?" = "1" ] then crontab -l | egrep -v "control unRAID fan speed based on temperature:|fan_speed.sh" >/tmp/crontab echo "#" >>/tmp/crontab echo "# control unRAID fan speed based on temperature" >>/tmp/crontab echo "*/2 * * * * /boot/scripts/fan_speed.sh 1>/dev/null 2>&1" >>/tmp/crontab cp /tmp/crontab /var/spool/cron/crontabs/root- crontab /tmp/crontab fi

Running 5.0-beta11 on mine with no issues. Since it doesn't have Realtek nics, I don't think 12a will be a problem.