cyrnel

Little red asterisks are used in most or all docker templates but I've never seen mention of what they mean. Required field? Beware? Convention would be to reference it somewhere on the page but I haven't seen anything, with or without "help", and searching for * or asterisk is pure humor. Yes, I'm barely involved in IT these days so am testing the boundaries of common knowledge. :help:

We're discovering we have fewer duplicates than we thought which is going to necessitate more drives than will fit in this Q25. I have a single pciex8 slot available. Are port multipliers still the best for this sort of thing? Another 4 bays would be nice. Slightly annoying this board can drive 14 sata but I can only fit 7 3.5s in this little case. Thanks!

Forgot to mention. I know I'm showing the rails at the back of the cage. I only split the rails at the front, between the fan and the cage, since I think blocked inflow is the root of the problem.

Sorry, can't show the rails right now - running a parity check - but look at the gap they block. The rubber mounting donuts supplied for the lower mount points worked to test before I broke out the saw.

A stupid-simple change to mounting hot-swap drives in my Q25 made for 2+ degrees fahrenheit drop in drive temps. I'd been going to cut out much of the offending aluminum but knew it'd look like butchery afterwards. As a test, I used the rubber washers instead of rails to mount drives, then cut out the center section of the rails and did it to the rest. It doubles the opening for air to travel from the fan across the cage drives.

Thinking back now... I do recall it's faster to add your parity disk after you copy files. Makes ~10MB/s difference on this system which could add up over multiple TB copies.

A guy steps away from the console for a few years and suddenly he forgets all the obvious stuff... Thanks all, I can use it!

Of course that makes sense with a soft error. Wish the parity check interface would say something like "corrected x errors on Disk n".

Just for reference, my brand new 6.1 system with a Xeon 1271v3, 16GB, a black parity drive and 5900rpm data drives receives long files at about 45-55MB/s with rsync over a smb connection. The same operation jumps to 55-60MB/s if the temp files are built on an ssd. The same system rebuilds parity at about 150MB/s until the the last few percent where it slows to ~80MB/s. I use rsync unless the other system is being scavenged, in which case I pull and attach drives directly.

I just had an unclean shutdown on my new 6.x box when its UPS died. Rebuilt parity and all the drives show clean but the parity message is "Last checked on Mon 01 Feb 2016 12:21:22(today), finding 1 error." Up above each drive is listed with "Errors 0". How does one track this down?

The only thing I've found painful with this build is getting to the mb for new cables, usb drive, etc. The supply sits right above the mb and even though it's sfx it makes all but a few connectors unavailable without either sliding the power supply back or the mb back and down, each requiring removal of 4 screws. A quick release system for the power supply is inevitable. Next to add drive activity lights...

It fit perfectly I wouldn't have known the board wasn't made for the case. The SFX power supply was an important factor. The fit would have been much more difficult without. Modular isn't as important. The 500 is larger than the 450 anyway so even with modular cables you're mostly buying a cosmetic improvement. I was disappointed Silverstone only provides two SATA modular power ports on the supply. I guess they expect it to be firing a larger video card and not a bunch of drives.

Very slick system! Yes, this is my first 6.x exposure. I realized my 1150/1151 error in time to stop the first CPU shipment and instead get a 1271v3. The system went together smoothly. I see why people like these cases. Not inexpensive at all: $240 mb, $340 Haswell Xeon, $124 16GB (2x8) ECC RAM, 240GB cache SSD, plus spinners. But it's so much nicer than my previous budget builds! Rebuilding parity at 140-150MB/sec. Slightly warm on parity drive. I'll bump up the front fan speed. Wonderful selection of fan connectors and control on this board. -ASRock E3C224D4I-14S MB, Intel Xeon 1271v3, 2x8GB low profile ECC, 240GB cache, WD Black 5TB parity, other spinners, in a Lian Li Q25B

Looking forward to this build. It's been awhile.

Those are pretty different power supplies, no? I'd be surprised if the pcb weren't different as well as caps, etc. Someone who knows ps testing can chime in but I'd think the specs are just what fell out of testing while performing against their limits, including noise levels. They call both fans "silent" but I only see a dba rating for the 80mm. Or I could be completely wrong.

Yep, the 120 fan and modular cabling decided it for me. Everything I need should be on the way!

I bumped up to the 1230v5 for HT and newness, after confirming ASRock support. garycase, thank you for mentioning the SFX supplies. That was my next hurdle. What do people think about Silverstone supplies? I'm looking at their ST45SF-G 450W - 80+ Gold, Single +12V Rail, 80mm Fan, Active PFC, SFX to ATX bracket. I'd usually go SeaSonic but their SFX supplies didn't inspire me. Edit: The only modular SFX on newegg is the SX500-LG. Ouch.

Okay, here's my cart so far: ASRock E3C224D4I-14S Extended mini ITX Kingston 8GB DDR3 1333 ECC Unbuffered x 2 Intel Xeon E3-1220V3 Haswell 3.1 1150 Again, this will be going into a Lian Li q25b. Thoughts?

Huh, looks like my reply post didn't. Anyway, good info. Thank you! That's too bad about the ECC minimums. Has anyone worked with the E3C224D4I-14S version of that board with built-in SAS2? It's a little more expensive but has 12 sata right on the motherboard, if unraid supports it. Downside is it's extended mini itx, like we need another form factor!

It's time to replace my original Unraid 4 box. I'm largely out of touch with mb/cpu progress these days so need assistance with the build. It'll be a media and backup server for a home office. 6-8 big drives should last awhile. I'll also be making use of vms and a bit of encoding/decoding. - I have a Lian Li Q25 case I'd love to use, which means mini-itx, but feel free to push me into something else small if the MB choices are better. - i5 or better. Depends on vm or chipset restrictions. - ECC support - At least one pcie slot for the future. Probably just for external drives. Thanks! Final build was: Lian Li Q25B ASRock E3C224D4I-14S MB Xeon E3-1271v3 CPU (fairly rare right now) w/stock cooler 2x Kingston 8GB 240-Pin DDR3 1333 ECC Unbuffered Very Low Profile RAM (not necessary) Silverstone SFX SX500-LG PS Patriot Blaze 240GB SSD for cache drive WD Black 5TB for parity & 5x green 5TB data This motherboard is impressive. A second pcie slot, and at least one x16 would make it amazing. If buying again I'd choose Silverstone's lower-end non-modular power supply. It's smaller so you don't lose space with the extra connectors and $50 cheaper. Don't sweat the low profile RAM. It's nice to have but I doubt anything normal would cause fitment trouble. The Patriot Blaze SSD was on the shelf from a black friday deal. I'm still deciding between another ssd for a pool or remove the cache completely. Will probably try different fans for the front and/or rework the restrictive sideways airflow to the hotswap drives.

I imagine many of us have 2GB. Both of my boxes do.

Thanks. I'll try it again, with some effort this time. I'm leaving this stuff on the cache drive in the hopes of reasonable performance. It'll be rsyncd to the array for safety. I'll post back as I get time. Seemed strange I didn't see many posts about this. Usually means it's stupid simple or there are better ways. Hmmm...

Basically, just looking for 5.0 compatible httpd pointers. Is anybody using owncloud on 5.0? With what web server, and were there obstacles? So far I've only tried SF's webserver and it won't get beyond "stopped". My only other add-on is unmenu. SF is new to me so I may be doing something wrong.

Well, I had a seizure and ran that as a CORRECTING check. So, no more errors detected, whatever they were. The massive error log from last night still has me concerned. Would be nice to have some idea what might have caused the avalanche that vanished just as quickly. Depends on the errors, no?

Interesting. Started another nc parity check. Those errors show up almost immediately. Total size: 3 TB Current position: 2.58 GB (0%) Estimated speed: 73.62 MB/sec Estimated finish: 679 minutes Sync errors corrected: 2 Again, the Device Status Errors column above is all zeroes.