SOLVED "KCS: Failed to start write" and other errors

[glauco]

Hi everybody!
Out of the blue, one day my FreeNAS box (see signature for hardware details) has started giving me these errors in /var/log/messages.
I have searched these forums and the internet for clues but I couldn't even figure out if there is a hardware failure on my motheboard.
What I'm worried about is my fans are managed by @Glorious1 's script and normally spin slowly and quietly, but these errors somehow cause the BMC to reset cold and my fans to run at full speed, which is driving me nuts.
The only way I have found to stop these errors from appearing is to shutdown the server. Switch off the power supply. Leave it off for a couple of hours and they switch it on again.
Can anybody suggest how to proceed?
My top priority is to stop the BMC from resetting so that my fans can run at reasonable speed again.
Thank you!

Code:

Jun 22 14:45:58 freenas ipmi0: KCS: Failed to start write
Jun 22 14:46:10 freenas ipmi0: KCS Error Data ff
Jun 22 14:46:22 freenas usbd_setup_device_desc: getting device descriptor at addr 19 failed, USB_ERR_SHORT_XFER
Jun 22 14:46:22 freenas ugen0.3: <vendor 0x0557 product 0x7000> at usbus0
Jun 22 14:46:22 freenas uhub1 on uhub0
Jun 22 14:46:22 freenas uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 19> on usbus0
Jun 22 14:46:22 freenas uhub1: 4 ports with 3 removable, self powered
Jun 22 14:46:23 freenas ugen0.4: <vendor 0x0557 product 0x2419> at usbus0
Jun 22 14:46:23 freenas ukbd0 on uhub1
Jun 22 14:46:23 freenas ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 20> on usbus0
Jun 22 14:46:23 freenas kbd2 at ukbd0
Jun 22 14:46:23 freenas ums0 on uhub1
Jun 22 14:46:23 freenas ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 20> on usbus0
Jun 22 14:46:23 freenas ums0: 3 buttons and [XYZ] coordinates ID=0
Jun 22 14:46:28 freenas ipmi0: KCS Error Data ff
Jun 22 14:46:34 freenas ipmi0: KCS: Error retry exhausted
Jun 22 14:46:38 freenas ugen0.4: <vendor 0x0557 product 0x2419> at usbus0 (disconnected)
Jun 22 14:46:38 freenas ukbd0: at uhub1, port 1, addr 20 (disconnected)
Jun 22 14:46:38 freenas ukbd0: detached
Jun 22 14:46:38 freenas ums0: at uhub1, port 1, addr 20 (disconnected)
Jun 22 14:46:38 freenas ums0: detached
Jun 22 14:46:40 freenas ugen0.4: <vendor 0x0557 product 0x2419> at usbus0
Jun 22 14:46:40 freenas ukbd0 on uhub1
Jun 22 14:46:40 freenas ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 21> on usbus0
Jun 22 14:46:40 freenas kbd2 at ukbd0
Jun 22 14:46:40 freenas ums0 on uhub1
Jun 22 14:46:40 freenas ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 21> on usbus0
Jun 22 14:46:40 freenas ums0: 3 buttons and [Z] coordinates ID=0
Jun 22 14:46:40 freenas ipmi0: KCS: Failed to start write
Jun 22 14:46:44 freenas ipmi0: KCS error: ff
Jun 22 14:50:40 freenas ugen0.3: <vendor 0x0557 product 0x7000> at usbus0 (disconnected)
Jun 22 14:50:40 freenas uhub1: at uhub0, port 9, addr 19 (disconnected)
Jun 22 14:50:41 freenas ugen0.4: <vendor 0x0557 product 0x2419> at usbus0 (disconnected)
Jun 22 14:50:41 freenas ukbd0: at uhub1, port 1, addr 21 (disconnected)
Jun 22 14:50:41 freenas ukbd0: detached
Jun 22 14:50:41 freenas ums0: at uhub1, port 1, addr 21 (disconnected)
Jun 22 14:50:41 freenas ums0: detached
Jun 22 14:50:41 freenas uhub1: detached
Jun 22 14:50:51 freenas ipmi0: KCS: Failed to start write
Jun 22 14:51:03 freenas ipmi0: KCS Error Data ff
Jun 22 14:51:12 freenas usbd_setup_device_desc: getting device descriptor at addr 22 failed, USB_ERR_SHORT_XFER
Jun 22 14:51:13 freenas ugen0.3: <vendor 0x0557 product 0x7000> at usbus0
Jun 22 14:51:13 freenas uhub1 on uhub0
Jun 22 14:51:13 freenas uhub1: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 22> on usbus0
Jun 22 14:51:13 freenas uhub1: 4 ports with 3 removable, self powered
Jun 22 14:51:13 freenas ugen0.4: <vendor 0x0557 product 0x2419> at usbus0
Jun 22 14:51:13 freenas ukbd0 on uhub1
Jun 22 14:51:13 freenas ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 23> on usbus0
Jun 22 14:51:13 freenas kbd2 at ukbd0
Jun 22 14:51:13 freenas ums0 on uhub1
Jun 22 14:51:13 freenas ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 23> on usbus0
Jun 22 14:51:13 freenas ums0: 3 buttons and [XYZ] coordinates ID=0
Jun 22 14:51:21 freenas ipmi0: KCS Error Data ff
Jun 22 14:51:25 freenas ugen0.4: <vendor 0x0557 product 0x2419> at usbus0 (disconnected)
Jun 22 14:51:25 freenas ukbd0: at uhub1, port 1, addr 23 (disconnected)
Jun 22 14:51:25 freenas ukbd0: detached
Jun 22 14:51:25 freenas ums0: at uhub1, port 1, addr 23 (disconnected)
Jun 22 14:51:25 freenas ums0: detached
Jun 22 14:51:27 freenas ipmi0: KCS: Error retry exhausted
Jun 22 14:51:28 freenas ugen0.4: <vendor 0x0557 product 0x2419> at usbus0
Jun 22 14:51:28 freenas ukbd0 on uhub1
Jun 22 14:51:28 freenas ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 24> on usbus0
Jun 22 14:51:28 freenas kbd2 at ukbd0
Jun 22 14:51:28 freenas ums0 on uhub1
Jun 22 14:51:28 freenas ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 24> on usbus0
Jun 22 14:51:28 freenas ums0: 3 buttons and [Z] coordinates ID=0

 

[glauco]

I solved it by resetting the BIOS settings to default. Not that I had changed them before the errors started appearing, so I haven't really figured out what caused them.

 

[Glorious1]

Do you think it is the script that is causing it? There is code to reset the BMC if fans seem to be out of control, and some users reported serial resets. I haven't really reviewed the code and posts and figured out what's going on. But if resetting your BIOS fixed it, oh well.

 

[glauco]

@Glorious1 , I have no idea what caused those errors, but definitely not your script. It must have been some wrong settings in the BIOS. After reverting to defaults and making a few necessary changes, everything, including your script, is running smoothly again.

 

[nikkon]

I got the exact same issues when I created a VLAN interface on igb1. if I delete it the errors go away
In my case, this error is completely not relevant to the action i am performing