• Posts

  • Joined

  • Last visited

Everything posted by Dro

  1. As I've mentioned I had already gone through that previous thread and applied all the suggestions none of that has helped. Is it being suggested that I need to change my hardware based on that thread? When no hardware is actually plugged into the slot that is throwing the error?
  2. Any ideas? I would really love to get this fixed and not reboot my server every day to clear the logs then to have them fill back to 100% after 1hr.. 🥲
  3. Here you go! Thanks! unraid-diagnostics-20210830-0953.zip
  4. Hello, I've been dealing with this issue for awhile and i still can't seem to resolve it. Anyone know how to fix it? My BIOS has been fully updated to the latest version, I don't have any devices plugged into the PCIE slot in question with the issue. I have also appended this in my syslinux.cfg file as found in another support thread. pci=nommconfto to try to just ignore the error all together and it still hasn't helped. It seems the device in question is in one of the screenshots below.. I have also disabled all power management. I never used to have this issue, nothing has really changed it just started happening randomly about a month or so ago and hasn't stopped since. The only PCIE devices I have are a dualport solarflare 10gb SFP+ NIC and a LSI 9211-8i HBA. Motherboard is ROG STRIX Z370-H GAMING BIOS 2603
  5. All of a sudden now I can no longer get into Ombi. I am using my plex username and password. I tried to research this issue for quite awhile and ran a few potential fixes myself but still can't seem to figure out what is happening. Everything is completely updated to latest version, all docker containers and unraid. Any idea how to resolve this? Logging into Plex works fine with the same username/password. I do have 2FA setup but I have had it setup the first time it became available and have had no issues with Ombi. This just started this week.. My is the workstation I am trying to login from and the other is my gateway but I am not sure what it means when it tries to authenticate from that IP. I am trying to login from the same location each time on the same PC. Also, inside plex I do not see any OMBI devices. I was hoping I could just remove it and have it generate a new token. But it's not there. Thank you!
  6. Sorry if I missed it, can you share the manual? I want to try to setup unRAID as an ISCSI target for an ESXi cluster using multiple SSD pools/MPIO
  7. Awesome work. Any idea on the release of the plug-in?
  8. I think there is still a lot of confusion about this. We have people running multiple sizes and whatever the free is (larger then smallest) they are able to utilize that space on their raid1 cache pool. For example if you have a 250gb and a 500gb that will show around 378 gb of useable space. In a traditional raid1 set only 250gb of that should be useable (smallest disk) However, in the BTRFS raid1 set it appears it does allow you to fill what it reports as this is how it's supposed to work with BTRFS raid1.. it's not a traditional RAID1. So is this really a visual bug? If you do the BTRFS RAID calculation and compare to what shows in your cache pool it's almost dead on. What is the clarification on why some people say one thing and some people say another? Examples https://seravo.fi/2015/using-raid-btrfs-recovering-broken-disks Explained well here with how it caculates https://amp.reddit.com/r/btrfs/comments/a95kbz/usable_space_calculation/
  9. Is this still a known bug with BTRFS in unRAID RAID 1 set with multiple drive sizes in a cache pool? What happens if it reports more then the smallest size drive, you go over that size, does it just copy to the array?
  10. Thank you, this one installed i had issues with the actual link.
  11. Agree, I asked the same thing in the previous thread and got no response. How can we update the CSS to change just that to say, black? I tried to find it myself but couldn't seem to locate it.
  12. Thank you Saarg, I didn't even know that was there. Works now
  13. Issues stuck on step 4 as well.. but my CLI is telling me i'm at the latest version.. any ideas how to get around this? I thought there was a .step file somewhere but cannot find it that can be deleted?
  14. Looks great, any idea why I am missing the lighter color grey header? I had to change the font colors to see it.. Also, where in the CSS can i change the color of the array utilization indicator text circled in red? I would like to make it black or darker grey it's too hard to see in the green. Thanks!
  15. Best part about unRAID is the ease of storage expandability! I'd like to see iSCSI support the most so it can be used as an ESXi SAN type device with it's own 10gb iSCSI storage network.
  16. Exactly my use case. Right now no native ISCSi is a dealbreaker for me for an ESXi cluster for shared storage on an ISSCi network. Don't want to use FreeNAS. Would be nice to get ZFS and ISCSi bundled as in my mind these two go together well in a future release.
  17. There still seems to be an issue with the Dockers not being able to "apply update" downloading 0 bytes from the repository. As originally reported here https://forums.unraid.net/bug-reports/stable-releases/dockers-wanting-to-update-but-dont-in-the-end-r618/?fbclid=IwAR1MYec7WcYbrpVuwywsf1-IL8gkmuQuFoqifM8cpphAPAWs-d6JeG4FFvQ Upgraded from 6.7.2 which I originally ran the user script on to resolve the update issue, was working fine, the update broke it again. After updating to 6.8 the docker update issue was still a problem thinking it was supposed to be fixed. I ran the user script again and was able to apply updates without issue. Still seems to be present as we are having other users reporting the same on our unRAID Facebook group.. Thanks!
  18. I actually found the problem for some reason with 6.7rc5 it disabled perl. Once I re-enabled it, updated it, I was able to reinstall 5.8 and the plugin just fine.. I had no clue that got disabled but that was the cause.. and thanks i do see above he mentions "to fix on reboot" I will change it.
  19. Dro


    Maybe I am missing something here with SNMP. This would seem to be a pretty basic feature that should be available natively. The current SNMP plugin is broken even with the available SNMP net-snmp5.8 pkg which was the workaround to get the plugin to work. Doesn't appear the plugin is being supported anymore but I'm curious why the native OS doesn't have this available? I've been monitoring a bunch of servers with Zabbix and now since the plugin is completely broken I've lost SNMP functionality.. Anyone feature request? Or fill me in on what I'm missing? Thanks!
  20. unfortunately this workaround isn't working anymore. Even with net-snmp.5.8 the SNMP plugin is failing on 6.6.7 and 6.7rc5 . Also ive noticed when rebooting the server it reverts back to the net-snmp5.7 version and you have to reinstall it each time then reload SNMP plugin.. But I guess that's beside the point now since the plugin isn't working any longer. I wish they would just build in SNMP, doesn't seem too difficult.
  21. Do you mind sharing your banner? Thanks!
  22. Excellent Job everyone the new dashboard is fantastic. Nice to get proper Temp placement and realtime utilization across all aspects on the dashboard.
  23. Is there a way on the backend to default it to use port 587? If I wanted to use the web interface it seems by default it uses port 25 and I haven't found a way to change it.. Since my ISP blocks outbound port 25 this is an issue.. Emails get delivered if i setup an SMTP relay with port 587 but i cannot use that solution going forward it was for a test... I also cannot receive any emails which I am not sure why yet but am able to telnet to my server and can see a connection on the interface so i know inbound port 25/587 is open and working. Looks like most stuff is ending up in the "queue" and just stays there.
  24. So that was the issue! Now you can see proper connection! Awesome! now the fun begins to change all my stuff over to the custom docker network which I am not even sure some of the stuff I run behind proxy can be set to a custom bridge that it must stay as a host! but at least I know what the fix is! I've actually had the custom docker network setup before but must have never fully implemented it! Now I understand about the proper dns resolution between the containers. Never realized by default the bridge didn't do it. Thank You for pointing me in the right direction!