johnmatt

Thanks all for the help. I'll try a cache SSD and see how that goes

Ah.. ok, so do you think a cache SSD would resolve this issue? What are your thoughts on the inconsistent (all over the place) results that happened the other day? Here's a graph of the writes... a little inconsistent, but probably not an issue?

Hi all, I have looked around the forums, as this is a question that comes up a lot - but I believe answers are all sort of specific to individuals networks/configurations. I am getting less than ideal file transfer speeds. I'm also fairly novice with Unraid (ie, might need specific instructions if you want terminal commands/reports) I'll include a graph of my file transfer (from computer, to server). It started at 110 mb/s and then dropped to ~40. I did this the other day however, and it was ALL over the place - up and down and up and down, dropping as low as 12-14 mb/s?!?! Anyways, hoping someone can help me diagnose! THANK YOU in advance, John

WELL, thank you sir. All good. Appreciate the help. I'm sure I'll be back in here asking more questions again soon haha! John

Ok, so I've moved the SATA cables onto a different set of ports....... sill me may have hooked them up to a MARVEL controller So far, here is my log while I'm starting the parity check... looks better, I'll update if I need more help. Thanks, your humble noob, John

Thanks for the quick reply! I'll move the SATA cable for that drive over to another port and try again, but before I do, how to I run diagnostics?

Hi all, I'm coming over from FreeNAS and trying to get off the ground. I followed the instructions in the startup tutorial videos and all went well, until the parity sync. One of my drives got a red x next to it and the system said parity failed (or something similar). I thought I'd try from scratch. Pulled all drives, formatted, ran chkdsk /f and WD Disk Util, passed both. Formatted the SD card, reinstalled unRAID and tried again... but this time a different disk failed (I know it's a different disk as 3 are WD and the first time it was one of those, but my fourth disk (assigned to parity disk) is the same size (3TB) but a HGST. So again, the first time a WD drive got the red x, now its the HGST (less than 1 year old). Anyone have thoughts? Also, the SMART test's aren't working anymore on any of the drives... before I was downloading them and getting normal outputs on all disks... now I get: And under show SMART error log I get: I'm NEW to unRAID (48 hours new)... here's the log if that helps. Thank you for your help in advance! John

Yeah - it's a little silly when you look at it - I'll try to post some pictures... The fractal fans are 3 pin, the noctua fans are 4... but the noctua fans were failing as well, so not sure what exactly was going on there - but a buddy has a spare fan controller that I'm going to steal so I can ramp them all up just to the point of being able to hear them - then roll them back.

Hi Everyone, I've been up and running for a week or so now, so I thought I'd share some of my feedback. 1) Really... clear CMOS - I'm such a noob lol - but ok, now that we're up and running. 2) I have the server in a Fractal Design Arc XL (as size is not a concern) with 4 - 3Tb WD drives in Raidz, there are 3 140mm Fractal fans that were included w/ the case and 2 120mm Noctua's that I added. The fans are all on direct power to the PSU (more on that later) and I have low-noise adapters wired in so you can't hear her one bit even with nothing else on in the room. Dead silent. 3) IPMI for this type of application is AWESOME. The only things that have ever been plugged into the machine are a power cord and a cat5... it's a huge advantage of the board. 4) I have FreeNAS set up running Transmission and Plex - everything is streaming around the house wonderfully. Torrenting on this machine is awesome as I don't have to leave the big rig powered on. 5) I had some event logs - the fans plugged into the onboard headers would slow enough to trigger an alert, then the CPU temps would overheat triggering an alert there (the fact that this information is all so accessible is amazing - I never would have known otherwise)... Not sure what the problem with the headers was - but in any case everything is wired directly to the PSU (again with low-noise adapters) and everything is silent. Since that changeover - I've been running 24/7 for a couple days downloading torrents and streaming via Plex - 0 problems, 0 event logs. Anyways - just thought I'd put some positive comments out there... the board is sweet and I'd do it all over again, no question. Again, thanks to everyone for your help getting me up and running. John

Haha, yeah I hear you... all the stories of problems with this board make me super nervous... but this is going to be a pretty basic setup - just downloading and streaming over plex... as long as she stays on 24/7 I'm happy. More news to come as I get more time with it this week.

I guess you have to short out the two half moon solder pads with a screw driver or something. Of course with no power and unplugged. They are down and to the right of the battery. For what's it's worth I'm using 2 Corsair Vengeance 4GB DDR3 1600 CMZ8GX3M2A1600C9 and 2 Samsung 4GB DDR3 1600 M379B5273DH0-YK0. Both are non-ECC OK I'm IN!!! The clear CMOS on the half moon jumpers did the trick! Thank you, thank you, thank you, thank you, thank you! Will post more as I get going here - but I'm in the BIOS

Well, I got a different set of Kingston RAM (again, listed as compatible on the Asrock site) inserted one or the other modules into the two primary RAM slots, flashed the BMC multiple times (between different ram configs) and nothing... one time the IPMI preview said "cannot connect to 10.0. blah blah" but every time since it just says system is off or in sleep mode. Sigh. Is there some secret to clearing the CMOS? Anyone have any other ideas? Going to go back to Asrock support next week if it's still not working and RMA the board. John

Yea, the avoton boards have an usually long post time. My new board, the ASRock E3C226D2I, posts nearly instantly in comparison. Also, on a side note, I've been running this new board with a xeon 1230v3 for 48 hours now, no issues. The avoton board would lock up on me after 12 hours. This board has also been a 100x easier to work with, especially since the SATA ports are in a much easier spot to access. There's only 6 ports, but I used a cheap 2 port sata pcie card that seems to do the trick well. At this point in time, until ASRock releases some firmware updates for their boards to address instability, I can't recommend them at all. It's a shame though, the avoton is pretty impressive in what it does. It puts out some good performance without barely even getting hot. Ok - so I'll be home tomorrow and will try resetting the cmos - and though I highly doubt the issue is with the ram, I ordered another kit just to be 100% sure as I've heard all sorts of stories about how finicky this board is with ram. I will say that the Asrock tech support has also been really helpful (via email, they didn't respond to my phone call) and the rep has been emailing me back and fourth with suggestions. He said that sometimes (and that this had recently worked for another customer) flashing the BMC firmware can be a solution, even if it's the same version. I'll try that Friday and post results. Thanks all - I hope to get this board running soon - I think once it's up and running it's going to be a great little rig... I'm just building a basic file server for plex... maybe do some torrenting on it - but in terms of servers it's going to be pretty basic so hopefully it'll work well as a 24/7 system. Well stay tuned.

Hey has anyone else dealt with this issue? I was reading this thread as I waited for my board to arrive (C02550) and I'm having the same issue. I have nothing plugged into the board other than power and ram (supported via Asrocks Memory QVL) - I can access the IPMI but I get the same message (powered off or in standby) and I can't see anything). I've also tried plugging in a keyboard into all available USB ports (both on back and via the internal header) and it keyboard doesn't light up so I'm assuming this isn't an issue with the IPMI. I've moved the ram around a couple of times and I've even tried sticking a stick of my gaming rigs ram in there just to see if it was maybe a faulty stick of RAM - nothing. Thanks in advance for anyone's advice / help. -Edit: I have the two green LED's, the lower LED is constant, the upper ("IPMI LED") is blinking. -Edit: I successfully booted my gaming machine on the ECC RAM that I purchased for the server so the RAM isn't the issue. John