markswift

Members
  • Content Count

    79
  • Joined

  • Last visited

Community Reputation

1 Neutral

About markswift

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Sadly I've had no luck getting my Asrock x470D4U working. I can successfully run the 'configure' (which detects the fans and speeds them up etc), but activating the temperature controls and starting fan control does nothing. I can confirm sending a command like: "ipmi-raw -h 192.168.1.11 -u admin -p admin 00 3a 01 00 32 48 48 64 00 00 00" works just fine. Does anyone use this board, or can help me figure this out? Many thanks.
  2. Hi all, Well, following my previous posts (above), I've been trying to get this working for over a week with no luck. I even bought a new fan to populate header_6 to see if that made a difference - it didn't. If anyone has any ideas why it might not be working with my board (but is for others), I'd love some help! It's strange that the configuration ramps up the fans and recognises everythign correctly, but auto / temp control doesn't work
  3. Hi, I've already checked that - no luck sadly I'm wondering if it's related the config / layout of my fans, as it did work briefly when they were attached to other headers. I tried to swap them back, but no luck... Tried a clean install too. Is there a chance you could share your board.json so I can compare it? Thanks in advance. To summarise: Config runs and I hear the fans ramping up, RPM is correct for each. Running in debug shows an incorrect raw command (unless I'm interpreting it wrongly). IPMI shows correct percentag
  4. Okay, upon activating debug it seems the issue is caused by a wrong RAW command being sent? I see: 2020-11-12 19:07:19 ipmi-raw 00 3a 01 00 00 44 44 44 44 00 -h '192.168.1.11' -u 'admin' -p 'xxx' --session-timeout=5000 --retransmission-timeout=1000 2>&1 Shouldn't the command include another '00' @dmacias? Would love to get this working, my rack sounds like a jet turbine Edit: reinstalled to test, no luck, debug log below: Sleep 60 seconds. Highest temp is 33ºC DECLARED VARIABLES: Array ( [debug] => 1 [prog] => ipmifan [lockfile] =>
  5. Hello, I have an ASROCK x470D4U board. I have installed and configured the plugin (sensors etc work), but it appears temperature control doesn't. The raw commands do work, so that's not the issue. board.json: { "ASRock": { "raw": "00 3a 01", "auto": "00 00 00 00 00 00 00 00", "full": "64 64 64 64 64 64 64 64", "fans": { "FAN1": "01", "FAN2": "01", "FAN3": "01", "FAN4": "01", "FAN5": "01", "FAN_POS6": "01", "FAN_POS7": "01",
  6. It appears that /dev/disks does not exist on my system, has something changed?
  7. Howdy, when I try to run this I get: plugin: installing: https://raw.githubusercontent.com/StevenDTX/unRAID-open-vm-tools/master/openVMTools_compiled.plg plugin: downloading https://raw.githubusercontent.com/StevenDTX/unRAID-open-vm-tools/master/openVMTools_compiled.plg plugin: downloading: https://raw.githubusercontent.com/StevenDTX/unRAID-open-vm-tools/master/openVMTools_compiled.plg ... done Kernel Version: 4.19.33-Unraid -------------------------------------------------------------------------- Sorry, OpenVMTools has not yet been compiled for your unRAID version
  8. I'm running 6.6.3 - tried to install manually but it also give an error, I'll also do some digging and see what I can find...
  9. Still fails here, I've never installed before, do I need to manually import / create some folders prior to installing via the PLG URL?
  10. Hi Alex, tried to install: plugin: installing: https://github.com/arberg/dynamix/blob/master/unRAIDv6/dynamix.cache.dirs.plg plugin: downloading https://github.com/arberg/dynamix/blob/master/unRAIDv6/dynamix.cache.dirs.plg plugin: downloading: https://github.com/arberg/dynamix/blob/master/unRAIDv6/dynamix.cache.dirs.plg ... done plugin: file doesn't exist or xml parse error
  11. Would love to get to the bottom of this - the fact is worked perfect before... I don't like the thought of my 3x1TB drives going TRIMless... Hope this can be solved.
  12. Seems there's actually a problem with the latest releases, my Samsung Pro connected to a SAS2008 (compatible with TRIM) no longer works, it did in prior releases...
  13. My LSI SAS2008 based var worked with my Samsung 840 Pro prior, but now I experience the above, so this is a recent unRaid issue IMO.