May 30, 20188 yr Having this issue go on sometimes. Sometimes after a reboot it doesn't show up but sometimes it does. May 29 21:39:23 Tower kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: Timeout waiting for interrupt! May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: Transaction timeout May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: Failed terminating the transaction May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: Transaction failed May 29 21:41:54 Tower kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! This then stops and doesn't happen again while the server remains on, only after reboots. Currently running 6.5.2. Followed all instructions before upgrading.
January 4, 20197 yr Anyone ever find a solution to this? I've got this message filling my logs and it makes looking at them near useless. SuperMicro mobo, IPMI plugin up and running. I get temps and fan speeds fine near as I can tell. I've seen mention that IPMI may have something to do with this but was wondering if anyone had solved this. Mobo comes up as: Supermicro - X9DRi-LN4+/X9DR3-LN4+
January 5, 20197 yr Author I've had this happen even on the latest 6.6.6. I've watched it and it only really occurs if the array isn't started, or shortly after the array is started. After that it stops spamming. I never really figured it out but it doesn't seem detrimental.
January 5, 20197 yr 1 hour ago, slimshizn said: I've had this happen even on the latest 6.6.6. I've watched it and it only really occurs if the array isn't started, or shortly after the array is started. After that it stops spamming. I never really figured it out but it doesn't seem detrimental. Oh I SO wish that was the case! 😮 Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
January 11, 20197 yr Snippets of the syslog usually do not help, that is why the troubleshooting FAQ says to post full diagnostics zip file.
February 16, 20197 yr Community Expert On 1/5/2019 at 2:01 AM, BLKMGK said: Oh I SO wish that was the case! 😮 Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:49 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! Jan 4 20:58:50 Minion kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it! I have a X9DR3 and have the same issue, but if i remove system temps plugin it stops. This is running under 6.7.0rc4.
February 17, 20197 yr Try booting in safe mode - the problem should go away. It's caused by a kernel module you have loaded to monitor temperatures. If you have several loaded try removing them one at a time. You might have to settle for monitoring the CPU temperature instead of the motherboard. If you google the error message you'll find several links which may help.
February 18, 20197 yr On 2/16/2019 at 7:16 PM, John_M said: Try booting in safe mode - the problem should go away. It's caused by a kernel module you have loaded to monitor temperatures. If you have several loaded try removing them one at a time. You might have to settle for monitoring the CPU temperature instead of the motherboard. If you google the error message you'll find several links which may help. Most of the searches I've done indicates an IPMI issue, I do run the Dynamix SystemTemp plugin. I've had weird issues with incorrect things getting loaded and have had to occasionally hand modify files on older versions of unRAID. Dynamix detects the proper driver as coretemp nct7904, I've hit the unload button though which takes the drivers out of memory and the issue MAY have gone away 😮 If so I'm much relieved as this has been a nightmare lol. Oddl my temps displayed at the bottom of the web interface are still working. All I've done is hit the unload, the plugin is still onboard. I'll post back if the errors return, this might have solved it at last - thanks!
February 18, 20197 yr Well, the plugin is just the interface with the GUI. It needs kernel module drivers to access the physical sensors. Most systems will detect sensors in the CPU and on the motherboard and load a separate driver for each. You can have the plugin installed and zero, one or more modules loaded, which will give you different options for what the plugin displays. In your case the coretemp module allows the CPU temperature sensor to be read, while the nct7904 module allows sensors in the SuperI/O chip to be read. The latter is where you'll get fan speeds and voltages from if you run sensors from the command prompt. Try just loading the coretemp module and don't bother with the SuperI/O chip and see if the error messages stop being generated. I think the reference to IPMI is a red herring - it's related to the fact that IPMI provides a way of remotely reading the sensors too.
October 24, 20214 yr Anyone ever determine the exact cause of this? I'm seeing this in my log. I've removed both the IPMI Tools and the Dynamix System Temp for now. Still seeing it my logs (although I haven't rebooted yet)
November 16, 20214 yr I think I'm having this issue. I have included my diagnostic zip. Did not see a resolution here.speedwagon-diagnostics-20211115-1814.zip
December 17, 20214 yr Removing the Dynamix System Stats plugin fixed it for me. Maybe it isn't compatible with the IPMI plugin running simultaneously? edit: nevermind, they came back. Lol. However, unloading drivers as @joelrfernandes commented below did work. Edited December 17, 20214 yr by oldsweatyman
December 17, 20214 yr What eventually worked for me was using the "Unload Drivers" option from Dynamix System Temperature plugin (at unraid.local/Settings/TempSettings). That did stop the error message in the logs.
February 10, 20233 yr Confirming, this worked for me as well. Thanks @joelrfernandes! On 12/17/2021 at 12:28 PM, joelrfernandes said: What eventually worked for me was using the "Unload Drivers" option from Dynamix System Temperature plugin (at unraid.local/Settings/TempSettings). That did stop the error message in the logs.
July 9, 20232 yr On 2/16/2019 at 12:55 PM, SimonF said: I have a X9DR3 and have the same issue, but if i remove system temps plugin it stops. This is running under 6.7.0rc4. What do you mean when you say system temps plug in?
July 9, 20232 yr 3 minutes ago, chrismitt2002 said: What do you mean when you say system temps plug in? Forgot to follo2 topic
July 9, 20232 yr Community Expert 35 minutes ago, chrismitt2002 said: What do you mean when you say system temps plug in? Dynamix System Temperature plugin I think, but I have it currently installed on this hardware under 6.10.3
July 9, 20232 yr I have the next to the newest build getting the same error 3 hours ago, chrismitt2002 said: What do you mean when you say system temps plug in? Forgot to follo2 topic Edited July 9, 20232 yr by chrismitt2002
July 11, 20232 yr On 12/17/2021 at 9:28 AM, joelrfernandes said: What eventually worked for me was using the "Unload Drivers" option from Dynamix System Temperature plugin (at unraid.local/Settings/TempSettings). That did stop the error message in the logs. were do i find that the flash drive ?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.