cybrnook

Members
  • Posts

    613
  • Joined

  • Days Won

    2

Everything posted by cybrnook

  1. Well, in case anyone is interested I have made some progress, but not quite there yet. I have been able to detect the smbus (of my board) that holds the I2C address of the SPD EEPROMs (which for me is "0", where I have all 8 x SPD EEPROMs). The catch now though is I need to have an eeprom driver baked into the kernel (namely the ee1004 eeprom driver/kmod). @ich777 you think your kernel toolbox might be up for the challenge? (https://www.spinics.net/lists/linux-i2c/msg32331.html)
  2. I want to be able to get my memory timings from CLI, but out of the box all I see is just a high level view with lshw -C memory -disable SCSI *-bank:0 description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2934 MHz (0.3 ns) product: HMA82GU8AFR8N-UH vendor: Hynix physical id: 0 serial: 72446CE5 slot: DIMM 0 size: 16GiB width: 64 bits clock: 2934MHz (0.3ns) I want to also be able to pull the memory timings. Looking online, seems the best way to do this is using i2c-tools (namely decode-dimms). So I pulled down and installed the slackware package: https://packages.slackonly.com/pub/packages/14.2-x86_64/system/i2c-tools/i2c-tools-4.1-x86_64-1_slonly.txz But.... seems I need to be able to modprode eeprom before decode-dimms can actually read anything: (Screenshot was from an old version of i2c-tools 3.1.1, I since updated to 4.1. Needed for DDR4) Is there a way to get this information?
  3. I think you should pickup the 1920X I have 🙂 . There is nothing wrong with it, as I have been running my unraid system with it for about 6 months now. You lose 4 cores and you don't get PBO, but confirmed working on what I am running at least.
  4. @RockDawg check this out too: https://www.phoronix.com/scan.php?page=news_item&px=ECC-DRAM-Overclocking-TR Good stuff! I'm up to 2800 on my Hynix (From stock 2400), and exited to see what happens with 2nd Gen TR when it comes in since it has a better IMC.
  5. They are discontinued now, but I got 8 x sticks of this in there: https://store.supermicro.com/16gb-ddr4-2400-mem-dr416l-hv01-eu24.html MANUFACTURER Hynix MEMORY CAPACITY 16 GB MEMORY TECHNOLOGY DDR4 MEMORY SPEED 2400 MHz VOLTAGE 1.2 V ECCVLP ECC UDIMM RANK 2 rank CAS LATENCY CL17 MANUFACTURER PART NUMBER HMA82GU8AFR8N-UH WARRANTY 5 year warranty (here is the current equivelant: https://store.supermicro.com/memory/ddr4/16gb-ddr4-mem-dr416l-cv02-eu26.html) Also, if you need a TR for cheap, let me know. I jumped on the 2950X deal, so want to sell off my 1920X for about $220 shipped. (I'm in SE Michigan, seemingly right above you)
  6. Been running it for a few months now and love it, it's been super stable (disabled C states and set power supply idle control to typical in BIOS). Both Intel NIC's work out the box and register as 10Gb and the IOMMU groupings are nice as well. Details of my system are in my signature. I am on the latest 6.9.0Beta25 using a recompiled Kernel to add Nvidia Drivers from @ich777 's nice docker tool - Here For BIOS and BMC: BMC Version - 1.30.00 - Download BIOS Version - L1.37 (BETA BIOS I requested from Support) - Download For the BETA BIOS, it's been rock solid. The difference with this one is not only (current release bios doesn't even have bifurcation) does it allow you to set bifurcation, but it does so on a per PCIe slot basis. BETA BIOS prior had PCIe slots setup in groups. So if you wanted to set one slot to x4x4x4x4, then you got two slots as x4x4x4x4, I didn't like that. I am posting it in my onedrive for you since I find it a requirement.
  7. Are you on a clean IOMMU grouping, meaning you are not trying to pass through a grouping with multiple GPU's or something?
  8. @binhex hope you are well. Still loving a good handful of your dockers 🙂 Just wanted to ask if you still are following the "tags" of Jackett to then push updates? I noticed my Jackett docker hadn't updated in a few days, so I checked their tags and looks like we're on "Jackett Version 0.16.991.0" when Jacket has tags up to 0.16.1017.0, which means we are four releases behind. https://github.com/Jackett/Jackett/tags Just wanted to make sure something in your automation wasn't going awry.
  9. I have been running my P2200 with the Official Plex docker for over a year, no issues. I am using a compiled Kernel using @ich777's docker Kernel Helper. Outside of that, you just need to add two Variables to your container and then enable HW acceleration from within Plex itself. Custom Kernel with Nvidia Drivers Docker Variables I had to add HW Accell enabled Proof
  10. Yep, just remove your credentials from the opensubtitles portion of the docker template, save and restart.
  11. Doubtful has anything to do with Unraid. I would say make sure your nvme SSD is plugged into the right M.2 slot, since that card seems to support 1 x nvme and 1 x SATA, I assume the M.2 slots are labeled appropriately. Then like @trurl pointed out, make sure your BIOS can see it. This card would need to go into the one free PCIe x16 slot that MB has, so need make sure that slot is compatible with x4x4x4x4. The manual for that board is thin, but doesn't mention what that slot supports. https://download.gigabyte.com/FileList/Manual/mb_manual_ga-h110-d3a_e.pdf So if you don't see it in the BIOS, then Unraid won't see it either.
  12. I guess I will set this to closed as everything I pointed out so far seems to be either specific to me or expected. Thanks @bonienl for explaining in detail my concerns. Perhaps it was timing, or something else on my side, but without having Host Access enabled, my custom br0 dockers were not able to talk to one another, at least at the time. Which is what led me down this path anyways. regardless, so far using a VLAN has removed the call traces I was seeing, and with the rules in the firewall , everyone can talk to everyone, so I guess that's good enough 🙂
  13. This may explain it then. Is this a hard requirement that in order to use some docker containers with static IP's, then ALL my docker need to be set to use a static IP? I can't have one using host, a few using bridge, then a handful using custom br0, they would all need to be custom br0?
  14. Thanks for the response @bonienl that helps paint of picture of what's going on. To your line I quoted above. I would say this option is needed for those who want to assign a static IP to your docker containers, but also don't want to have to go through the trouble of setting up a separate VLAN for those docker containers because either it's too hard, or their equipment does not support it. What I found in the past was that when you assign static IP's to your docker containers, Unraid by default blocks those containers from talking to one another. So if you have a setup like mine (and I assume others run something similar for automation) Sonarr and Radarr need to be able to talk to Jackett, they also need to be able to talk to your torrent client to pass information back and forth. Without this option enabled, this won't work. Or, creating a separate network for these dockers, hence the need for a VLAN.
  15. Just to add, I ended up breaking down and building out another VLAN for dockers in the meantime. However, I think this is a bug as the MAC of unraid should not be changing. Way too much of a pain in the butt though, when the check box should have avoided this all together 🙂
  16. Been scratching my head all afternoon on this one, but I think I finally narrowed it down. What I found is that when you have "Host access to custom networks" enabled in the Docker options, it's fudging the MAC address of the Unraid server as a whole. I found this out because I was attempting to debug the "macvlan" Call Trace issue when we have custom IP's assigned to Docker Containers. To me, having custom IP's (Custom br0) is a requirement so I can implement firewall rules on a per docker container basis. As well, just taking the approach of creating another VLAN on my network is not a suitable workaround because that just adds additional complexity when trying to route to those containers from my primary network. Anyways..... I thought what the hell, let me swap in a different network card to see if it makes a difference (Intel X550 vs X540 vs 82599ES etc..) since the assumption is some people have this issue and others don't, perhaps it's a hardware or driver issue? So, I installed my different network card, and proceeded to do the usual, set static IP in unraid, then in pfsense make sure I tag the proper MAC address (the new one) to make sure I also assign the same static IP. This is where it started getting weird.... The actual MAC of my adapter begins with D0 and ends with 9C: So when I went into pfsense, I was ready to tag D0..9C, but didn't see it. So I checked the ARP table, and low and behold I saw a MAC of 36...52: If I disable "Host access to custom networks", then the real MAC comes back: At least for me, this is an issue as this means that when enabling this option, any static IP assignment I have in my router would be ignored since the MAC is randomized each time with macvlan. As well, I am not sure of the additional macvlan ramifications of this when the MAC for an IP is changing. Perhaps this is working as designed, but I wanted to bring this to light as it may be related to the calltrace for macvlan, and for sure surely breaks my static IP rule that I define in my router. And yes, I know of course that I could set a static IP in unraid (which I do). But I also like to make sure that IP is static in my router as well, as I have had occasions where I needed to nuke the network.cfg file, and still want to come up on the same IP. @limetech I am tagging as "other" for now since I can't make out if this is Urgent, Annoyance, Other or by design.
  17. @ich777 thanks for updating the plugin to only display on what is actually installed, much appreciated!
  18. Your variable should go in the Extra Parameters section like so:
  19. Ask and you shall receive: cat /var/local/emhttp/smart/parity smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.7.8-Unraid] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0004 129 129 054 Old_age Offline - 112 3 Spin_Up_Time 0x0007 151 151 024 Pre-fail Always - 440 (Average 431) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 346 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000a 100 100 067 Old_age Always - 0 8 Seek_Time_Performance 0x0004 128 128 020 Old_age Offline - 18 9 Power_On_Hours 0x0012 099 099 000 Old_age Always - 9248 10 Spin_Retry_Count 0x0012 100 100 060 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 86 22 Helium_Level 0x0023 100 100 025 Pre-fail Always - 100 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 486 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 486 194 Temperature_Celsius 0x0002 240 240 000 Old_age Always - 27 (Min/Max 17/45) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
  20. Reboot sorted it out, but figure I will leave this here anyways JIC.
  21. Just noticed a drive in my system that's apparently going into nuclear meltdown. noah-diagnostics-20200717-2159.zip
  22. Is there supposed to be a new/different variable other than the regular true/false Beta Build value? Instead of saying "true" should I put "beta25" instead? EDIT, just tested and YES seems instead of putting "true", the value "beta25" also works, so no having to copy, very cool!