Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

46 Good

About Marshalleq

  • Rank
    Advanced Member
  • Birthday October 17


  • Gender
  • URL
  • Location
    New Zealand
  • Personal Text

Recent Profile Visitors

706 profile views
  1. Wow, we should really have a disclaimer so people remember to update BIOS'es. If not latest, maybe one version behind. Some people still think it's unnecessary! FYI - I don't need the fake DP on my setup - and it can mean a session is connected when you don't want it to be either... So maybe true for you too.
  2. Hmmm, I wonder if this would be faster on ZFS with my 256GB NVME L2 read cache. I have a strong suspicion it would be advantageous....
  3. I read recently that there's a lot of compression etc happening which is run by the client too, so that would mean there is also a limitation there. I asked this question on the wiki a while back, apparently it's in the docker logs. Edit: I just checked its not.
  4. Can anyone else confirm that they can actually connect to steam using lancache? I tried it a few weeks ago and I was able to do everything in lancache except connect to steam. It resolved DNS etc correctly (actually much faster than steamcache), but steamcache was the only one that would actually let me connect to steam for some reason.
  5. Don't worry about these right now, they're not stopping you from getting it going (I have these and have a working config). I see port forwarded 80 to 180. In your firewall it says that 180 is for unraid not lets encrypt? Of is that just a generic name? Either way, lets encrypt works by forwarding port 443, then to port 80 or 443, then back. I know technically port 80 will redirect itself, but it's another redirect and there is a maximum number. I'm also unsure if you can forward 443 to 1443 via the router, then proxy that to port 443 then back again (I haven't had coffee yet and am feeling very slow this morning!), you probably can, but it's not the way mine is set up, so I can't comment. For mine, I changed the unraid port to 2080 and 20443 to remove this issue. It seemed to make more sense to me. Then just forwarded the 443 port to unraid which is received by lets encrypt as native 443 since unraid no longer uses that port. Letsencrypt docker handles the rest. It's been a while since I set this up, so I may be wrong, but I don't think your array 0 should have port 444, if everything else is being sent to 443. The other part that I can't verify is if that's actually your real IP address that duckdns is sending back. Have you checked this against what your router says? Finally, I take it plex is working, so I assume that means you don't have a private address range assigned by your ISP - that certainly happens with a few ISP's in my country. Hopefully that gives you a few extra thoughts that leads to something positive!
  6. I get nervous when I hear about webdav and reverse proxys to the internet. I hope you didn't expose webdav? As that would certainly result in an undesirable result. To clarify, are you talking about the unraid GUI or the Nextcloud GUI? Have you looked at any logs? I you can't access them, I assume you've tried a reboot?
  7. Thanks, the saga continues. Fixed all this up, but now getting transport endpoint is not connected on /mnt/user. Also lots of segfaults when docker tries to run and the shares have all disappeared. Fun times. I officially dislike BTRFS - even though I recognise it may not be entirely the fault of BTRFS - I have to blame something until I know better!
  8. Thanks but it has impacted both BTRFS on the mirror and the btrfs on the docker image. I assume it must have been caused when I had to force restart the box the other day due to an Nvidia lockup. I don't really expect otherwise, but btrfs does seem to be more picky about such things and I would have thought a scrub or repair would have sorted it. But no.
  9. It's a BTRFS mirror. I wouldn't have chosen BTRFS if I had any other choice. Of the space of the few years I've been using it I've had 3 maybe 4 issues, all different. I think one other where I needed to format and start again, and two related to the mirror not being created as advertised - that's probably an unraid bug more than a btrfs bug though. The context was provided to indicate it wasn't likely a whole system issue impacting disks as one other person on here seemed to think when I dug back into the archives. I'll just invoke the mover and reformat it. I'm half tempted to get rid of the mirror altogether as I think a single disk will have less issues than BTRFS will. But provided it doesn't actually corrupt my data, I'll keep the mirror. Though the jury's out on that one.
  10. Hey, did you ever find out anything further? I've just started getting them too. Personally I suspect it's a typical BTRFS issue - I've heard more than one person say BTRFS often corrupts. But hey, what do I know. It's only BTRFS complaining though, not XFS and not ZFS.
  11. And we are all very grateful for this, thank you.
  12. Does anyone know how to do this? I have two drives that were in the array, where I set the warning and critical thresholds at that time. I've since moved those two drives to a ZFS pool, but hadn't realised the temp settings would carry over. Since I can't mount these drives in unraid GUI, I get no access to change these settings. The drives need a slight adjustment up as they're alerting me about 20 times per day. Thanks.
  13. I get a traceback when running aws-cli anyone else get it to work?
  14. So I had your container disabled and had gone back to steamcache. I double checked why by re-enabling yours today. Basically with yours enabled I get the dreaded steam cannot connect to steam servers (or words to that effect). I'll go over my config again at some stage, but it's fairly defeating to have a game cache if it doesn't allow you to play any games! Thought I'd mention in case anyone else has any input / insight.