cakes044

I'd appreciate please avoiding language like this as it's elitist, general users who don't have a technical background in I.T. should not be labelled as "not smart", it's unfair and reductive. This is pretty much the thing I agree with. Having an option to ignore errors is up to the end user IMO for things like this, sure the database is most likely not going to backup correctly and prone to corruption but that decision should be left up to me as a user and it's not the tools fault at all. I simply don't want some of my services to have outages at all at the cost of an "incomplete" backup, I'm totally okay with this option and it should just be made clear that these are the risks to the person making these changes. We can get caught up in semantics and best practices all day, just feels like the simplest thing to do here will be to give an option to ignore some of these errors if an end user chooses to. Like mentioned above, for most cases people in my scenario mainly care about configuration files, of course this isn't all cases but again my problem to deal with personally. Any important applications that I use with a DB in this case does it's own backups daily/weekly whatever cadence and I'm happy to have THOSE files as my restore option.

That’s right. I remember the ipmi2json not being quite smooth had to do some manual switches to get it to work. Once the board.json is configured the ipmifan will just work fine now 👌🏼 Glad to see it working

Hi All, Here is the forked repo with the details of my "fix", keep in mind this is only for X570D4U and X570D4U-2L2T users, I purposely didn't include this to be backwards compatible because I didn't have those boards to do the proper testing or the time to make this backwards compatible. This is the commit in question that has my "fix", I also fixed some minor bugs with the shell commands: https://github.com/lucasteligioridis/IPMI-unRAID/commit/49281fd8 I can't quite remember if the ipmi2json script works flawlessly or not, I may have hacked in some values on the first run, full disclosure I haven't used that one since I first put it together and used it. But the ipmifan script works wonders with these boards, haven't had a problem with it since implementation. You essentially want to copy the two files mentioned from here: https://github.com/lucasteligioridis/IPMI-unRAID/tree/master/source/ipmi/usr/local/emhttp/plugins/ipmi/scripts Into the correct location on the Unraid system, which is here: - /usr/local/emhttp/plugins/ipmi/scripts You will have to restart the ipmifan service in the Unraid UI and it all should hopefully work, at the very worse the ipmi2json script might not work perfectly as intended, but it will at least generate some of the json correctly. Let me know how it goes, happy to help further. I'm not at home at the moment and don't have SSH access to validate the above just yet. To have this fix "permanent" I just copy the ipmifan script into the above directory whenever the machine boots, because the plugins get reloaded each time Unraid restarts so the old code will be restored. Obviously any updates to the plugin will have the same effect. If I get more time I'd love to fix this into a proper patch and merge it upstream.

Sorry I never posted my actual solution ages ago, I was actually going to fork the plug-in and submit a PR but I thought the author was going to do it. Ill post my changes that have a working solution for these boards later in the day, essentially it was a change to the ‘ipmi2json’ and the ‘ipmifan’ scripts.

Yeah totally, these kinds of things are expected but you do get a board that has all the bells and whistles that are not being offered in other boards for this price. If it gives you any confidence my friend has been using the 2L2T with no issues so far with Unraid. So fingers crossed most of the major bugs have been ironed out No worries, was happy to help. 👍

Might be late to the party but everything has been working fine on this board with Unraid apart from all the IPMI fan stuff which I hacked together a solution that you can see in that post. There is actually a bug on this board that you may not have noticed yet, but RX traffic on the network adapters with the specific version of the firmware/BIOS is actually degrading the network performance to 1/3 of the speed. Again, only on RX. I have already raised this issue with Asrock Rack and they have confirmed the issue with a specific AMD driver combination after many many emails and actually sending my board back. A friend of mine has the X570D4U-2L2T and doesn't have this issue, so its only for the X570D4U where the firmware has been affected. Other than that, this board is killer. I have not found another board on the market that is anything like this for this price tag. Happy to answer anything else.

FWIW, I was being facetious when I said "hacked" around, was meaning that I dug into the code and figured out a way to do it just not clean yet. This is the result of that command by the way: root@tower:~# dmidecode -qt2|awk -F: '/^\tProduct Name:/ {print $2}' X570D4U So, I made the ipmi2json script generate the correct json object and then modified the ipmifan tool as well to run with the correct commands. There are some caveats and changes to the way this board needs to run. 1. Fan needs to be put in "manual" mode before the values will actually work. So thats an extra step that needs to take place. In the below I just put ALL the fans in manual mode. $manual_cmd = "ipmi-raw 00 3a d8 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 2>&1 >/dev/null;"; 2. It uses different hex codes for setting manual and auto commands. $auto_cmd = "ipmi-raw 00 3a d8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2>&1 >/dev/null;"; 3. The minimum value for all fan values are now 20% which equals 14 in the hex code, for instance, if I were to only want to change the fan value of the first fan to full speed, it would look like this, even if you aren't using the fans they must be set like this: ipmi-raw 00 3a d6 64 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 So my "hack" was just shoving them in the code to see it all work. Obviously that wouldn't fly with the current ASRock boards and would actually break the implementation of the existing boards. I'm thinking we might need an extra key in the array to indicate some of this stuff, not sure. I'd look to you for what you reckon? First time looking at PHP in like 10 years, so I'm sure you'd do a better job than me. But hopefully thats enough to go on Let me know if you need anything else. Some extra commands you might care about too. Get the fan duty for all fans while in manual mode: $ ipmi-raw 00 3a d7 24 32 32 14 14 14 14 14 14 14 14 14 14 14 14 14 Get the fan control mode: $ ipmi-raw 00 3a db 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 Clean all fans (reset to defaults): ipmi-raw 00 3a dc P.S. In bash a semicolon or an ampersand are command terminators, so some of the commands where you do this is gonna give a syntax error: $cmd .= "ipmi-raw $raw $full $fanopts 2>&1 >/dev/null &; "; Just remove the semi-colon after the ampersands and you're good to go 👍

Okay I hacked around the source code of the fan tools all day and got a working version of it for this board 🎉 Happy to clean it up and submit a patch to the github page. Will have to wait till this weekend though when I have some time just a few different things required for this board.

OKAY Good news! Got back correct command from Asrock. On this specific board, the commands are slightly different and has 16 fan duty options: Set fan to manual mode: ipmitool raw 0x3a 0xd8 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 0x01 Set fan to auto mode: ipmitool raw 0x3a 0xd8 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Set fan duty to 100 the valid values are 14h to 64h (20% - 100%): ipmitool raw 0x3a 0xd6 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 Tested all of them and does exactly as described 👍

Conversation going with ASRock right now about it, just going back and forth, so will 100% tell you the results in here when its all done. 👍

I wouldn't try anything like that Yeah not gonna do that and brick my motherboard I think we’re dead in the water without the correct raw commands, hopefully ASrock get back to me soon and I’ll submit a patch/issue to the GitHub plugin page and refer it back here with the update.

I usually alway update the bios and bmc if there's an update. I guess if depends on the release notes of it's worth it. Yeah I could always update with the 2L2T version of the board: https://www.asrockrack.com/general/productdetail.asp?Model=X570D4U-2L2T#Download Which AFAIK is identical to my one except the 10GB NIC. Just unsure if there are anythings in the firmware that could brick my board, I'm not too familar with the BMC side of things, I would assume that the firmware is separate to the board.

Maybe try ipmitool. Could be a freeipmi problem. Also is the bmc firmware up to date. Yeah tried that with the same results, well the thing is, this is a brand new board and I dont have any drivers to downloads at the Asrock website: https://www.asrockrack.com/general/productdetail.asp?Model=X570D4U#Specifications Never had a BMC board before, is updating the firmware on the BMC wise if not specified by the manufacturer? Might also help to see the output of the sensors and the fans: root@tower:~# ipmisensors -t fan ID | Name | Type | Reading | Units | Event 25 | FAN1 | Fan | 400.00 | RPM | 'OK' 26 | FAN2 | Fan | 4100.00 | RPM | 'OK' 27 | FAN3 | Fan | 1300.00 | RPM | 'OK' 28 | FAN4_1 | Fan | 4000.00 | RPM | 'OK' 29 | FAN4_2 | Fan | N/A | RPM | N/A 30 | FAN5_1 | Fan | N/A | RPM | N/A 31 | FAN5_2 | Fan | N/A | RPM | N/A 32 | FAN6_1 | Fan | N/A | RPM | N/A 33 | FAN6_2 | Fan | N/A | RPM | N/A Fans 4 to 6 have that split, I wonder if that causes some huge difference. Those are 6 pin fan connectors that can be used as 2x3 pin connectors.

Yeah I've tried the dual CPU commands and no results. Yeah all Noctua PWM fans. Here is the output of trying to send the command via the terminal: root@tower:~# ipmi-raw 00 3a 01 00 00 00 00 00 00 00 00 --debug ===================================================== OEM - Unknown Request ===================================================== [ HEX DUMP ..... ] = HEX[ 9B] [ 01h 00h 00h 00h 00h 00h 00h 00h ] [ 00h ] ===================================================== OEM - Unknown Response ===================================================== [ HEX DUMP ..... ] = HEX[ 2B] [ 01h C1h ] rcvd: 01 C1 Looks like the controller is not recognizing it as a valid request.

You are probably correct that the ipmi commands may be different for this board. I would need the correct commands to make it work. I have emailed Asrock support on this to see what the correct commands are, doesn't look like their official guide over here is correct for my board: https://www.asrockrack.com/support/faq.asp?id=38 Are there any ways I can figure out the raw commands to use via the ipmitool that you are aware of? I haven't had much luck searching for that answer, I'm more than happy to debug this at a lower level if I knew where to look.