Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About lrroberts87

  • Rank
  • Birthday July 2


  • Gender
  1. Additionally, I swapped the stock phanteks case fan and hyper 212 fans out for noctuas and dropped 12db on the overall sound coming from the server. Both measurements taken 6in above center of server case AVG before 45ish AVG after 33ish Ordered a CyberPower CP1500PFCLCD, to finally connect my server via UPS.
  2. Just got over some hurdles with my unraid server but here is the build. Dual Xeon 4650s Hyper 212 evo cooling 64gb ecc 1066 ddr3 ram (64gb more in reserve) ASRock EP2C602-4L/D16 mobo 2x 3TB HGST Deskstar 1x 4TB HGST Deskstar 1x 6TB Seagate IronWolf (Parity) 1x 250gb Crucial Mx500 (Cache) Phanteks Enthoo pro case Evga supernova 1000w gold standard San Disc usb drive Primary use is currently plex. Installing a VM as we speak to attempt to run a 7 days to die server for myself and some friends. Suggestions? I have the domains share set to Cache only as well for those wondering.
  3. Alrighty, so that totally worked just fine. Thank you Johnnie.Black for the grate insight.
  4. Currently 3% further than any previous attempt. ~8 hours left
  5. Current diagnostics after reboot and starting parity rebuild sephiroth-diagnostics-20190106-1219.zip
  6. Oh crap, thanks, I did not read that. I will switch them to the blue ports and post an update.
  7. Thanks for the reply sephiroth-diagnostics-20190105-2113.zip
  8. So now you have network connectivity? I ran into a similar issue and ended up stemming from an incorrect system time in the motherboard bios.
  9. I am going to try and form this long story into short story form. I upgraded my server to below specs: Dual Xeon 4650s Hyper 212 evo cooling 64gb ecc 1066 ddr3 ram ASRock EP2C602-4L/D16 mobo Phanteks Enthoo pro case Evga supernova 1000w gold standard usb drive Anyways, had network connection issues upon start. The classic eth0 interface is down. Worked on some solutions there by deleting network.conf file and such. Ended up being a bad system time on the motherboard. Unfortunately, in the process, and not thinking I erased my usb and lost my config for my server. I have done this before and rebooted fresh with 0 issues. The case is not so this time. My parity now refuses to sync with one of my Hdds in particular. I have tried swapping sata cables and booting the server up without the drive which causes the issue but when i add it back in my parity hits the 25% mark and begins failing after about 300 errors found on this drive. What information can i provide that can help diagnose the issue.
  10. Update: Swapped my USB back to 2.0 at the suggestion to do so. Swapped the cpu for a quad-core a8-5500 (Much better cpu overhead) Currently working to get the Mellanox sfp+ as NIC
  11. Thanks for the information. My BIOS is currently set to only use the USB as the boot, but you never know. 😀
  12. Well, given the issues, would i be able to shutdown my server and swap my usb back to USB2 with no errors finding the flash drive on there or affecting my install config?
  13. Is this an ongoing issue with using an internal header for usb3 or is it all usb3 ports in general? I have only had mine up for a week thus far, but no issues
  14. I figured that i had an open usb 3.0 header so i used the following cable + san disk drive https://www.amazon.com/gp/product/B007PODI1W/ref=oh_aui_search_detailpage?ie=UTF8&psc=1 instead of https://www.newegg.com/Product/Product.aspx?Item=N82E16815201028 I know that most will say it doesnt generally make a difference but i was updating the build so no harm, correct?