kayjay010101

Members
  • Content Count

    23
  • Joined

  • Last visited

Community Reputation

1 Neutral

About kayjay010101

  • Rank
    Newbie
  1. Did you end up going for the M6720? How is it in regards to unRAID and (presumably) non-HP drives?
  2. I too would like to have an update on what the status is for the 6.9 patch. Hopefully @AnnabellaRenee87 has managed to recover well.
  3. Fantastic work, really nice of you to do this for the community! Could you add the HP ProLiant DL380 G7? There's the 8 bay SFF model, a 16 port bay model (which I have) and a 6 bay LFF model
  4. THANK YOU! Copied over every bz* file in the 6.8.3 zip and booted again, Web UI is back up on the old stick! Thanks again for your help!
  5. Thanks for the advice. In the meantime after posting this post I tested with a new stick running a fresh install of unraid. No problems, it got a DHCP from the ISP router and I can access the Web UI from my laptop. I am using a quadport NIC for the PfSense VM- but there's two NICs built into the motherboard that I actually use for Unraid, the quadport card is passed through. When I connected to the NICs on the motherboard itself it is now working with DHCP. This did not work on the old stick. The old stick still recognized a link when I ran without a network.cfg file, and the
  6. Just connected up the old ISP router (ew) and it's working for every device apart from the unraid box. DHCP doesn't work when booting without a network.cfg file and when using the old one it says link not detected. I'm at my wits end here
  7. Hey everyone, would love some help as I'm about to pull my hair out after 3 days of troubleshooting. Recently moved my server into a new room as I was adding a disk shelf and the noise would be unbearable, so it had to go into the storage room. Anyway, after turning the server on again after the move, it seemed that the web UI never was available. So I tried pinging the IP, and nothing. All right, shut it down, plug in the GPU from my main computer and check the console. All looks fine, it still has the same IP and everything. But it's not possible to ping anything on the network.
  8. Maybe dedicate two to a PfSense VM (WAN in, LAN out) then have the two remaining as main and fallover in case of one dying. Or for separating networks. One for IOT stuff that's separate from the rest of the network for security reasons, for example. That being said, getting a quad ethernet card off ebay is like $50 at most and you won't have to deal with separating the NICs if they're in the same IOMMU group. And the saved money by going with a dual NIC motherboard instead could maybe cover the cost of buying a quadport NIC. I have a dual NIC Supermicro board with a quadport ethernet card for
  9. unRAID does not require a GPU to boot. My server runs without a GPU entirely. Having a server that is meant to be headless require a GPU would be a dumb decision
  10. 128GB DDR4 2400MHz ECC. Got it for free from work, apparently our datacenter has a massive DDR4 surplus and actually a DDR3 deficit. So they just have a bunch of DDR4 ECC lying around.
  11. Can I ask why you went for 4x4TB drives instead of going with something like 2x8TB? The 4TB drives will draw more power overall, take more space, and you're limited to only 4TB if you want to have parity protection.
  12. Strange, going under my drives it does say "Enabled" under SMART. Are you running HP-branded drives? Also, did you get temperatures per drive to work in any capacity?
  13. Did you manage to get SMART and drive temps to work in Unraid with the P2000 G3? I've managed to get everything setup myself, but drives lack SMART capability and report 0C as their temp. SMART works according to the drive shelf's web interface, but as always with HPE products it's severely lacking in ease of use, and I'd like to have it reported in Unraid.
  14. Not one that communicates over U.2 and I have no M.2 slots as of now, I actually have a ASUS Hyper M.2 card on the way and will transfer two NVMe SSDs into that soon and will test then. For now that drive is sitting idle. I think it's a driver issue, as this is probably not an ssd anybody else has been using on unraid. Found some drivers on the huawei website, and I heard limetech could include them in the next version of Unraid if I pop them an email, but I'm not sure about Linux drivers and distros and such, so I don't know if these drivers would work with Unraid or not.
  15. Upgraded to 69-beta1, still getting the issue when I ran badblocks on it.