Tybio

Members
  • Posts

    610
  • Joined

  • Last visited

Everything posted by Tybio

  1. Nice! That's exactly what I'm looking at, any chance you've messed with the LED control in the BIOS? I know you can set the MB LEDs to colors there, but does the RAM respect that setting?
  2. Hurm, I think I need to look into what the "auto" setting does . Perhaps I should just turn it on.
  3. Hey all, While I was an expert in things back around 2012 when I built my current Xeon system, I've spent quite a few years just letting it run and now I'm worried that I'm missing something in this new build. With that in mind, my thought was to down-size from my 24 bay rack mount to a dual use server/Desktop. I will likely do light gaming, PBUG...WOW etc, but nothing in the realm of "serious". I'm also finding the current 8 threads I have amazingly limited as I run multiple test VMs (Mostly Linux) that do large scale processing (Work for a software company and have to convince people it will do what it says). I'm also doing light Plex transcoding (no more than 4 concurrent) and all my content is 1080p, some of it (and more by the day) remuxes. I fell in love with the Shogun build, so I've already got the case + PSU + 5-in-3s and all the fans needed. So what I'd like is a single system I can sit in my office that will power my desktop needs, a few Linux VMs (Normally not all thrasshing at the same time) and to some level not lock me in. Here is what I've come up with: https://pcpartpicker.com/list/ZtyyKB CPU: TR 1900x Memory: 4x8GB Trident Z Motherboard: Asrock Taichi 1 USB controller passed to Desktop VM Cooler: Noctua TR4 Desktop VM Drive: 970 500G (Passthrough) Desktop Video: TBD (Passthrough) . <---- Waiting a few months to see if prices continue to come down to normal, I'd do a 1080 ti at list, but not at what they are going for right now. As I have a Microcenter near by, I can get the 1900x for $349 (Or the 1950x f0r $699!!!) My thought on the CPU was that it looks like a refresh is coming this fall, so rather than dump huge on the TRs out now, I could go lower end and see what AMD releases. Worst case I still have double the threads of what I have today that are over 33% faster than the ones in my current box. Anyway, I've rambled. Anyone have any thoughts?
  4. Auto, this is a recent upgrade so I'm still settling into 6.5. I could turn it on, not going to hurt anything, but with a nice 'net facing firewall I don't really see the point so I left it defaulted.
  5. Just updated and I'm getting connection_reset messages when trying to go to the plugin. I've disabled, and re-enabled a few times. Syslog looks fine, and the process is running. Not sure what other debugging would be helpful? Ok, I'm not running SSL and it looks like things are broken: root@Storage:/mnt/disk1/Backups# cd /usr/local/emhttp/plugins/unbalance root@Storage:/usr/local/emhttp/plugins/unbalance# killall unbalance root@Storage:/usr/local/emhttp/plugins/unbalance# ./unbalance I: 2018/05/12 20:42:12 app.go:51: unbalance v5.2.0-1070-aea11c7-v2018.05.12 starting ... I: 2018/05/12 20:42:12 app.go:59: Using config file located at /boot/config/plugins/unbalance ... I: 2018/05/12 20:42:12 server.go:54: Starting service Server ... I: 2018/05/12 20:42:12 server.go:71: Serving files from /usr/local/emhttp/plugins/unbalance I: 2018/05/12 20:42:12 server.go:130: Server started listening https on :6237 I: 2018/05/12 20:42:12 array.go:46: starting service Array ... I: 2018/05/12 20:42:12 planner.go:52: starting service Planner ... I: 2018/05/12 20:42:12 core.go:101: starting service Core ... W: 2018/05/12 20:42:12 core.go:116: Unable to read history: open /boot/config/plugins/unbalance/unbalance.hist: no such file or directory I: 2018/05/12 20:42:12 app.go:73: Press Ctrl+C to stop ... echo: http: TLS handshake error from 192.168.1.7:56665: tls: first record does not look like a TLS handshake echo: http: TLS handshake error from 192.168.1.7:56666: tls: first record does not look like a TLS handshake echo: http: TLS handshake error from 192.168.1.7:56667: tls: first record does not look like a TLS handshake echo: http: TLS handshake error from 192.168.1.7:56668: tls: first record does not look like a TLS handshake
  6. Fixed for me too, great work as always!
  7. So looking at the new Zen+ CPUs, I'm really eyeing that 2700 with the 65 TDP, it seems to keep up with the + in all but gaming, and even there it is close enough. I'm seeing benchmark results all over the place on encoding (which I use to compare between processors as few do "transcoding" testing). It would be very cool to actually /drop/ my TDP from my 77 Xeon and get ~5k more passmarks and double the threads..but it almost seems too good to be true. Anyone have any input here on what I might not be accounting for? Details: Migrating from a E3-1275 v2 on an OLD Supermicro board, want to be able to have a windows VM as a desktop replacement (Desktop is an older i7) for light gaming while not over-taxing the server.
  8. All good! Just wasn't sure if it was me not following, or a typo!
  9. Perhaps pedantic, but as a guy who consults with ISPs world wide on their networks...I have to point out that a class C is /24, a class A is /8 and contains 65,536 class C networks. Reference: https://en.wikipedia.org/wiki/Classful_network With that in mind, am I reading this line correctly? webgui: Add class C (/8) network mask
  10. Greetings, I'm looking at upgrading my long serving Xeon to a 1950x at some point this year, however with all the MB and RAM options being "Gaming" focused I'm seeing a lot of LED options with software control. For MBs I can just turn it off, but for some of the RAM it defaults to some sort of "Color Wave" unless you install software to configure it. I've /no/ experience in the new LED control world, are these devices just USB elements (which in theory could passthrough fine if you can figure out which one they are)...or do they show up in some other way? Or, worst case for me, are they totally ignored in passthrough options as an unsupported feature? I know it is kind of a generic question, but I've searched and really couldn't find any useful information.
  11. The options for this are under the Scheduler in Settings, you can disable it from there or remove the plugin if you don't have any other SSDs. It looks like it is detecting an unassigned device that was removed, that's a bit of a corner case. Does the 320GB drive still show in unassigned devices?
  12. Update on results: Before this change and adding 3x140mm fans at the back of the chamber my drives were spiking into the 50's with the default fans. After the change, I've had to turn the fans down to let the drives hit the sweet temp spot (high 30s). With these fans (and the Noctua 140mms in the back) I'm able to run them under 50% which means dead silent operation other than the sound of air moving through the case which I have to lean down and get within a few inches to clear. So I'm labeling this a success, I hope others find this information useful! Next on tap for me is likely swapping out my 8 year old xeon with a threadripper and setting up a gaming VM so I can retire my desktop and get back down to a single computer.
  13. What motherboards are you guys using?
  14. So we've been chatting in the Shogun thread over in the Compulsive forum, and a few people have asked about the mods I'm doing to my 5-in-3 cages, so I thought I'd document them in a thread that makes it easy to search. The goal is to have a quiet server, I'm not going to repost a build thread as I basically just built Shogun with my old rack-mount guts as the components. Other than the D600, the other main thing I had to sort out was the 5-in-3s. What I did was remove the cowl and fan that come with the drive and replace them with Noctua fans. So first the parts list: iStarUSA BPDN-DE350SS: https://www.amazon.com/iStarUSA-BPN-DE350SS-BLACK-3x5-25-5x3-5-Trayless/dp/B008RRZI14 Fans: https://www.amazon.com/gp/product/B00NEMG62M/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1 PWM Hub: https://www.amazon.com/SilverStone-System-Cables-Black-CPF04/dp/B00VNW556I 2 packs of 10 machine bolts:https://www.lowes.com/pd/Hillman-10-Count-4-to-40-x-1-1-4-in-Round-Head-Zinc-Plated-Phillips-Slotted-Combination-Drive-Standard-SAE-Machine-Screw/3036648 Weather Striping: https://www.lowes.com/pd/Hillman-10-Count-4-to-40-x-1-1-4-in-Round-Head-Zinc-Plated-Phillips-Slotted-Combination-Drive-Standard-SAE-Machine-Screw/3036648 Process: 1> Remove Cowl 2> Unplug 3-pin fan connection 3> Toss both in the freaking trash, they are junk 4> Cut Weather stripping to form a "Box" around the fan stand-offs (see pictures) a> Make a small snip in the flat rubber between the two "D"s and pull them apart, you only want it one wide; This also makes it easy to cut matched pairs 5> Test the lengths before you remove the tape and expose the adhesive a> Don't worry about covering the 3-pin connection or the fan selector switch (mine overlap the latter slightly) as you will not ever use either again. 6> Expose adhesive and attach but don't press down hard, let the fan do that. 7> Seat replacement fan over stand-offs 8> Take out one screw and one screw, use the bolt as a spacer by spinning it up the length of the screw until it nexts against the head. 9> Screw fan into cage. a> Make sure before you tighten that the weather stripping has contact with the fan all the way around. b> Before you tighten, if it looks good you can press the stripping into place...the glue is nice and secure but I made sure they were well seated before tightening the fans. 10> .Position PWM hub in a nice space with easy access to the fans (I used the double sided tape it came with to mount out of the way 11> Connect fans to hub, hub to MB 12> Spend a few hours trying to sort out the auto-fan-control plugin to sort out what PWM header is the right one and get all the options set. I hope this was helpful! I've attached some pictures
  15. The problem with direct writes (for /me/) is that it causes disks to spin up a lot. In the evening during the TV season I'll get 2-5+ episodes a night, spinning up the drives in a staggered way for each one is pointless when I can cache them and then move them at once. For the Movies share, it would make sense to do that as those tend to be larger and less frequent additions. ie: it is a balance, usage management combined with cache size :).
  16. The only options I had were 1 1/4th and 1", I only picked up the longer ones as the 1" seemed too short, would only have threaded 2 or 3 rotations. The Noctua fans I used are .98" (According to their specs) so I didn't risk it.
  17. Ok, for anyone down the road that is wondering: The iStarUSA case fans can be replaced with 4-40 machine screws, the length is a little under 1-1/4 inch, I was able to find them at lowest with the right size/thread but not length: https://www.lowes.com/pd/Hillman-10-Count-4-to-40-x-1-1-4-in-Round-Head-Zinc-Plated-Phillips-Slotted-Combination-Drive-Standard-SAE-Machine-Screw/3036648 I then used the nuts as spacers so I didn't have to modify the screw. Basically spin the nut until it is nested up against the head of the screw, use it to attach the 80mm fan of your choice. Using the existing stand-offs for the fan without the cowl however leaves a gap of about 1/4-1/3rd of an inch between the fan and the cage. I'm debating using electrical tape to seal that gap so the air is forced to come in via the cage...what do you all think?
  18. I haven't seen anyone running one that's posting, EPYC is only available from custom builders I believe, they don't sell the chip alone last I saw...but I haven't been paying much attention. I guess I'm wrong! Who knew :). Though it looks like they don't score as well as the TRs...not sure what's up with that.
  19. Got it, thanks for clarifying! That's great information, I think what I'll do is use some Molex runs with SATA adapters, that way I can get it down to 5 drives per PSU run with one of the runs "splitting" to feed the two SSDs on the side. I'd think that's going to be about as good as I can possibly balance things.
  20. Help me out, I don't think I'm following. If startup is 2A then how could one avoid going over 1.5A for SATA power even with dedicated PS-drive modular cables? (Not to mention that most modular PSUs only have 4/5 "accessory" connections for things like drives) I'm sure I'm not following and we are somewhere in the middle. Like for 15 drives use 3xSATA power split properly or somesuch. Remember, the cages have 2xSATA power each, so by definition the best I can do is 2.5 drives per SATA power.
  21. There is a post here about ordering extras, the PSU is this one: https://www.amazon.com/gp/product/B01HXYRJYK/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 so fully modular. Another user posted a source for cables, perhaps I'll just get 2 more as the Seasonic comes with 2xSATA Power and 4xSATAPower. I could home run all my devices with 4 of the 2x cables and never have to worry about power again.
  22. The Seasonic has a 6-pin connector on the PS side :). I'm sure that the power supply can deliver the load, the reason I'm checking in is to make sure that the SATA cable can carry enough power for 3 5-in-3 cage from the power supply to them (2xSATA power connection for each cage).
  23. Quick question all, I'm getting a seasonic 650W for my new build, but it only comes with 6xSATA power, I need to run 3 5-in-3's that each take 2 connectors and 2 SSDs outside of the 5-in-3s. In my old system I just had a sea of Molex splitters and ran off of two power supply lines...however I'm wondering if you can run 3x5-in-3 off one 6-pin connection to the power supply via an extender, or if I should split them between two (which would mean ordering another cable). This will power 15 drives, Mostly 8+TB IronWolfs at this point.
  24. This is great info! Thanks a lot for posting, I've been working around a lack of 6-pins for a while...much better to get the right ones than do adapters and splitters!
  25. Ugh, I think these are #2 width, at least according to home depot, the smallest they had in the store was #6...which looks to be way too wide for the little plastic socket they screw into. I guess I'll try the default fans and see what I can figure out.