hoejholm

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

651 profile views

hoejholm's Achievements

Noob

Noob (1/14)

9

Reputation

  1. If you want to be really nice, you add an explainer where in the script you added the or check, and how you found out what to put there
  2. I think my setup would work, its on page 6 if memory serves me right. But, I think there was another person who layer posted a script for x570/similar that was a lot cleaner than my hack
  3. I was on 6.12.3 when I experienced the same after rebuilding my server, i downgraded to 6.12.2 and that fixed it. I did this based on other forum posts speaking about the AVX issue.
  4. Seems I've gotten this to work on my AsrockRack ROMED8-2T. The ROMED8 seems to use the same raw commands as used in the x570 fix here: https://github.com/lucasteligioridis/IPMI-unRAID/tree/master/source/ipmi/usr/local/emhttp/plugins/ipmi/scripts This fix however did not work and seemed to crash ipmifan and other stuff, but with the raw commands known and a compare i was able to screw up the plugin... which a friend with a pretty huge dolphin then spend 6 hours basically teaching me how coding works. Important note: 1: I have no idea what I'm doing here! 2: These config files include hardcoded changes to the raw command used throughout, so this will not work on other boards than those who need those. - I do not have access to any other Asrock boards and therefore cannot verify on other hardware, but since the core changes came from an x570 fix, there is a chance this might work for more recent boards. Setup: AsrockRack ROMED8-2T Bios: P3.70 (Latest at this time) BMC: 2.02.00 (Latest at this time) Unraid: 6.12.2 IPMI interface Settings needed: Settings -> FAN settings -> FAN Mode -> Set FAN control mode to "Manual" for all fans. (Adjust above under "Set fan duty for manual mode if you need to manage your fans until the script takes over) 0: Disable fan control if running in gui 1: Make a backup of your old ipmifan and ipmi2json located here: /usr/local/emhttp/plugins/ipmi/scripts/ Note: I highly suggest to compare my files with original before using them, Notepad++ has a nice compare plugin that will allow you to see the differences, the changes are small so even a person with no coding knowledge can verify nothing evil is present (Aka, don't just install random scripts from guys on the internet ) 2: Copy over the new ipmifan and ipmi2json to /usr/local/emhttp/plugins/ipmi/scripts/ 3: Run configure via GUI, this will generate a board.json in /boot/config/plugins/ipmi/ At this time you could test fan control. You should be able to adjust fans, but the fans are most likely not aligned (eg fan2 settings are pushed to fan1 and fan1 can't be controlled). 3: Modify your board.json, for me there was a FAN_Pos* line as the first fan, pushing everything by one. Moving this line below FAN7 solved the mapping. Attached is my board.json which you can also just copy into /boot/config/plugins/ipmi (overwrite), notice this will set all 7 fans as "configured" in the GUI. 4: Configure your fans via gui so we know the script will kick in. My HDD's where up at 30c so time to get the fans working. Set all fans to HDD temp. Set minimum temp to 20, max to 25, set max speed to the following (fan1, fan2...) (replace sensor with anything hotter than 25) 37,5 48,4 53,1 64 70,3 79,6 87,5 Apply but do not enable fan control. 5: via terminal in /usr/local/emhttp/plugins/ipmi/scripts/ run the following ipmifan --quit ipmifan --quit (I do it twice as the output changes if it was running) ipmifan --debug Your fans should spin up now and your terminal will fill with info. ctrl-c to stop it (otherwise it will refresh every few seconds). Scroll up, you are looking for this part: [cmd_str] => ipmi-raw 00 3a d6 24 31 34 41 45 51 56 14 14 14 14 14 14 14 14 15 2>&1 [fanopts] => [current_hex] => d6 24 31 34 41 45 51 56 14 14 14 14 14 14 14 14 (Note how the currect hex is short a number, this caused ipmifan to crash, not sure why its missing so I hard coded the 15 value in to make it work) Now go to your IPMI fan control and refresh, you should see the approx. % number you assigned. 6 run ipmifan --quit again, c in IPMI interface, set all fans to 20% In unraid, configure your fans as you want them, apply and enable fan control. refresh IPMI interface and you should now see the values have been adjusted away from 20% (Pending your config, of course). Things that are not yet tested: If anything is overwritten during a reboot. Edit: Appears to get overwritten doing boot by the plugin, needs to be setup to overwrite these doing boot Troubleshooting: in step #5 running ipmifan didn't work. *If you get the output including the ipmi-raw command, then maybe this fix isn't for your board, google and see if 00 3a d6 is the correct raw for your board, you can run the command manually with 64 as the number for all fans (Replace 24 34 34... with 64 all the way) this sets fans to 100% *if the script only told you the hottest HDD and then crashed, the command must have failed and quite certainly this is not for your board *It works but the fans are in wrong order - google a hex -> decimal converter and then convert the numbers in the raw command into % numbers, check that up against what happends in your IPMI interface, adjust your board.json until it fits. Question: Does anyone know of a way to bypass Asrock's 20% minimum fan RPM? - Would like to be able to go to 0% on some fans depending on temp. Edit: Asrock support confirmed: It cannot be set below 20%, no way of doing it and no plans on changing this in the future board.json ipmi2json ipmifan
  5. @Visuals Using this: https://outervision.com/power-supply-calculator When i punch in your data + random stuff in the places you didn't tell (memory eg), with 2nvme and 10 sata 7200rpm I get you need 17,2A on the +5v https://www.bequiet.com/en/powersupply/1280 says your PSU is max 15A on +5v... Could very well be your issue. Also, I get a combined 3,3+5v to be 131W, your PSU max is 110W Same spec but bumped to 20 HDD +2 NVME, we hit: +3,3v: 13A +5v: 22,5A - Combined 157w +12v: 26,1A I have had great experience using Intertech's ASpower PSU. This model fits your case model: https://www.inter-tech.de/en/products/psu/server-psu/aspower-r2a-mv0700 (There are other models, look up your model and look under acc.) The specs says: +3,3v: 30A +5v: 30A Combined max: 200w +12v: 58A This should keep you well in the clear, unless you have some crazy poweruser in the rack you didn't mentioned... Plus, its redundant. Notes: The website is a calculator, take everything as an estimate. (with 20+ drives the difference between power hungry and power-saving drives becomes a thing...)
  6. I have 2, one is parity and one is in the array together with my other drives. Parity: Last check completed on Tuesday, 25 January 2022, 18:07 (nineteen days ago) Finding 0 errors Duration: 1 day, 2 hours, 29 minutes, 35 seconds. Average speed: 188.7 MB/sec I've uploaded my benchmark to the drive database: http://strangejourney.net/hddb/index.cfm?View=Drives&Vendor=Toshiba&Model=MG09ACA18TE - mines the 4301 revision Reliability:... Well... I have 22 days of power on and so far none of them have failed Noise: They have only been under load while in my rack, and can't tell their noise apart from all the other stuff, so can't help there.
  7. What I did to solve the problem - Terminal, cd to the config folder nano motioneye.conf input random text and save, to make nano create the file. Remove random text and save, to leave an empty file Start docker. Below is my log output for the docker, first before I did the above, then after: ---Before--- CRITICAL:root:failed to read settings from "/etc/motioneye/motioneye.conf": [Errno 2] No such file or directory: '/etc/motioneye/motioneye.conf' -----After-------- INFO: hello! this is motionEye server 0.42 INFO: hello! this is motionEye server 0.42 INFO: main config file /etc/motioneye/motion.conf does not exist, using default values INFO: cleanup started INFO: wsswitch started INFO: tasks started INFO: mjpg client garbage collector started INFO: server started
  8. I just received my new case, an Inter-tech 4u-4724 Link: https://www.inter-tech.de/en/products/ipc/storage-cases/4u-4724 The case has two USB 2.0 frontpanel connectors, the wires are seen here: (only 1 of 2 cable sets in picture) https://imgur.com/a/FdUwJHx Found this pinout explanation, giving me the pin-names needed: Motherboard manual shows the pinout for the onboard USB connectors https://imgur.com/a/AqOxUyA Model: Asrock D1541D4U-2O8R Now, I have crossed out the SSTX and SSRX connectors, as they won't be used, but that leaves me with a problem. The VCC,Data+,data- connector from the frontpanel is combined, with gnd being separate. So, two options: 1: Motherboard and case maker have a disagreement on how the connectors should be* 2: I've misunderstood and the IntA_P_SSRX- and IntA_P_SSRX+ are in fact the connectors I need for Data+ and Data- Can anyone confirm if its 1 or 2? *Edit: Or, the case was just designed to only go into a USB 2.0 connector, and not to support being used in usb 3.0 boards... (Sidenote: Browser wouldn't upload files to the forums, so resorted to imgur links instead)
  9. ... even luck can help me there... Nothing special for Unraid. I split my home network up into vlans and blocked in/outbound on everything a few years ago, when I needed to refresh my memory on how basic network works.. (Not having internet access is a great motivator to figure out how old HP switches work with VLANs.... And figuring out is a great motivator to get new switches...) Since then I've just made it a norm to keep all non-client devices "offline".. No need for them to connect to stuff thats not needed... And [insert religious term of your choice] things will connect left and right, but the setup is coming under pressure as more and more stuff gets hosted in the cloud and therefore switch IP's faster than I can refresh the FW logs
  10. Hi, I'm expecting to receive the last bits for a new server next week, and will be setting up my first unraid NAS, replacing an old Synology that (literally) has a paperclip stuck in the ATX power plug, and duct tape on the inside keeping things together.. considering all the hours I spend keeping it alive, it will be an emotional last data-transfer.... One thing I would like to get ready is my firewall setup. The vlan where the unraid will reside is filtered on both inbound and outbound traffic, so I will need to setup access lists to anything the server needs to connect to. Does anyone know the IP/Addresses that Unraid needs to connect to? - OS updates - License check during trial period Community Applications needs git I can see, I'll handle that in case I need to install any, haven't made up my mind yet. Anything else where Unraid makes use of internet?