• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ezro

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for the reply Squid! With this approach, is it possible to expose both of the storage through the main unraid server as a single network share? I don't mind adding additional path mappings for the docker containers, but for PCs on the network I'd really like to expose it as a single storage that way people don't have to worry about which network share has space / where their content is, etc.
  2. Hi everyone, My setup currently is a single server with the following: Docker Containers * Radarr * Sonarr * Transmission * Nextcloud Shares * media - used by Jellyfin server as a mapped network drive * share - used by PCs on the network for misc. storage, usually mapped as a network drive * recordings - used by an OBS machine and editing machine as a mapped network drives I'm expecting that we may run out of space on the server by the end of the year so I want to try to plan out how to expand the storage proper
  3. Hi everyone, I currently have a working LetsEncrypt (port forwarded 443 -> 444) + DuckDNS for all of my docker containers hosted on my unRAID. I added a new machine to my network that is running Windows 10 and hosting a Jellyfin instance. If I want to use a different domain (not DuckDNS) for Jellyfin, how should I set things up that way I can keep my existing DuckDNS + my new domain all as HTTPS? Edit: I was able to get it working by pointing my CloudFlare DNS to my public ip, and creating the appropriate proxy-conf with the server_name set to my non-Duck
  4. I'm able to connect to GitLab and it appears to be running correctly, but an error keeps spamming my logs: ==> /var/log/gitlab/prometheus/current <== 2019-12-04_06:09:35.37530 level=info ts=2019-12-04T06:09:35.375Z caller=main.go:293 msg="no time or size retention was set so using the default time retention" duration=15d 2019-12-04_06:09:35.37547 level=info ts=2019-12-04T06:09:35.375Z caller=main.go:329 msg="Starting Prometheus" version="(version=2.12.0, branch=master, revision=)" 2019-12-04_06:09:35.37555 level=info ts=2019-12-04T06:09:35.375Z caller=main.go:330 build_context="(go=g
  5. I decided to give this a go and was able to successfully mount to my NFS share for Plex. In doing some testing, though, I'm noticing that both SMB and NFS have pretty bad (relative) scan times when it comes to my Plex libraries (around 2-10 Mbps in my Windows network throughput graph). On my Windows machine (PMS), I've tried changing the mount to use nolock and have also tried TCP / UDP / TCP + UDP for the NFS client. On my unRAID server, I've tried Auto / Yes for the the Tunable (enable Direct IO) setting. The machines are connected via ethernet on the same
  6. It doesn't look like it. I tried switching the port that the HBA card is plugged into and that also didn't work. I'm not sure if the power outage possibly fried the card itself or if it's my motherboard's ports. It'd be weird if an unused port was fried out, though, so I'm more inclined to believe that it's the HBA card. Do you know if there's possibly a bios property that could have been switched if the bios reset?
  7. Hi everyone, Last week my server shut down unexpectedly and I've been working on fixing it; after bringing it back up I'm seeing all of the disks as missing except for the boot device. I have a feeling it may be something with the SAS HBA, but it's been a while since I've done any work on this server. If anyone has any ideas / tips to try to get the OS to recognize the drives again it'd be greatly appreciated. Attached is the diagnostics. Regards, Ezro tower-diagnostics-20190806-1738.zip
  8. I disabled all of the other devices in the bios (not just the boot order) and that did the trick! Now it's time to rebuild all of the settings and containers. Sorry if I came across brash, this has been causing me a lot of stress. Thank you everyone for your assistance.
  9. That's fair. I'm able to boot into FreeDOS if I unplug my LSI card, which leads me to believe that the LSI card is the problem. Because of that I'd like to flash my LSI card and remove the bios, but I don't know how to boot into FreeDOS with the LSI card installed. I tried taping the pins, but that didn't work.
  10. I feel like I'm missing something for my understanding. I'm still trying to boot into FreeDOS with my USB. In my bios, I disabled every boot *except* for my FreeDOS USB, but it's still booting into MPT2BIOS-7. I understand that I want to remove the bios from the LSI card completely, but I'm not quite sure how to do that when it's not respecting the BIOS boot order to begin with. I've also tried electrical taping pins 5 and 6 (as per the SAS HBA crossflashing article), but I'm seeing the same results. Also, from the other previous link, the outcome I'm expect
  11. @jonathanm @johnnie.black I'm starting to look back into this and am noticing that I'm still not able to boot into my FreeDOS USB in order to attempt to flash the LSI card. In running the configuration utility, it does look like my card may have been pre-flashed when I bought the server. I've attached a picture showing the card's firmware which shows it running Do you guys have any other advice on what could be the issue?
  12. Thankfully I labeled my drives on the physical chassis, so the assignment shouldn't be too bad. Also, I don't have a backup of the diagnostics zip or anything, but I still have the email for my Pro Key; hopefully all I have to do is restart using the new SanDisk USB and enter that into the web UI.
  13. Thanks for confirming. After I flash the LSI card, I'm afraid that my OS stick is already borked from Windows repair; if I have a new install on another USB, will it recognize the drives and the data? (Does it matter what the sequence is? Boot into OS, restart with LSI vs Boot into OS w/ LSI on first start)
  14. Thanks for the link. I didn't flash the card at all in the past, but what's weird to me is that it would sporadically work without it flashed. I can try flashing it, but I think Windows corrupted my initial Kingston USB by "repairing" it (I can no longer see the file hierarchy in Windows), so that's another thing I need to resolve after this HBA boot issue.