Logs at 100%

[smaster]

Hello,

I've recently realised that my logs were at 100%.

To see if this was a simple error, I did a restart (clearing the logs).

However in the span of 2-3 days I'm back at ~60%. Clearly, something is filling up these logs and hopefully you can help me determine what it is and how to fix it.

I ran the "fix common problems" plugin and no errors were shown.

 

Thank you for your time.

 

 

 

 

tower-diagnostics-20211006-2244.zip

[trurl]

Log being flooded with these

Oct  5 20:22:47 Tower kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Oct  5 20:22:47 Tower kernel: Bluetooth: hci0: Intel Read version failed (-22)
Oct  5 20:22:47 Tower kernel: Bluetooth: hci0: Intel reset sent to retry FW download

Maybe something you can disable in BIOS?

[smaster]

Hi,

Thanks for your quick response.

Since getting a screen on my unRAID machine is a bit cumbersome and I don't have IPMI, would it be possible for you to tell me what I should disable?

Should I simply disable bluetooth? It might indeed be enabled, if it is by default.

What would you suggest?

 

Thanks again.

[JorgeB]

5 hours ago, sergio.calheno said:

Should I simply disable bluetooth?

Yes.

[smaster]

Thank you for your help.

Unfortunately, I cannot disable the bluetooth device in the BIOS. My motherboard is the Gigabyte Aorus Master z590 and I tried to enable ERP (I saw a few thread saying that could work, but it didn't).

Any other way of resolving this issue? (avoiding having to open up the server, if possible)

 

Thanks again.

[JorgeB]

You can try isolating the device, like if it was being used by a VM, this way Unraid won't load a driver.

[smaster]

Thanks for your response.

If I understood correctly, you meant to create a VM and make the VM use bluetooth, as to avoid getting the logs on unraid but keeping it contained in the VM, correct?

If that's the case I tried to create one, but when choosing the USB devices there is nothing mentioning bluetooth (neither anywhere else for that matter).

I send you a few print screens and also a new diagnostics to make sure that the problem persists in the same way.

 

tower-diagnostics-20211007-2038.zip

 

Thanks again.

[ChatNoir]

1 hour ago, sergio.calheno said:

If I understood correctly, you meant to create a VM and make the VM use bluetooth, as to avoid getting the logs on unraid but keeping it contained in the VM, correct?

I don't think you have to actually create a VM.

 

You should be able to go to Tools / System Devices and select the Bluetooth device there.

[smaster]

This is what I see in Tools -> System Devices:

 

 

I can seem to edit or change anything. Only to press "Done", but nothing happens.

What am I doing wrong?

 

Thanks.

[JorgeB]

You should be able to bind the device (hide it from Unraid) with the USB manager plugin, device you need to bind is this one:

 

[smaster]

This is what my USB manager plugin config looks like:

 

 

This is what I get when going to the newly created "USB" tab:

 

 

The only device that I can press "BIND" on, has the following device log information:

 

 

Is it the correct one to bind, or am I missing something?

 

Thank you very much for your help 🙂

[JorgeB]

Sorry, can't really help since I never used the plugin, you can try posting in the existing plugin support thread.

[smaster]

Trying to ping @SimonF to see if he has a moment to check the thread since it's already well documented.

 

Thank you 🙂

[SimonF]

My plugin will not help. I think the best course of action is to unload the blue tooth usb module btusb.

 

modprobe -r btusb 

 

you will need to unload in the go file to make persistent.

 

i will look at this more tomorrow.

Edited October 8, 2021 by SimonF

[smaster]

Thanks for your time @SimonF.

I will await further instructions, but here is what happened when I put the command in the unraid terminal:

 

Oct  9 00:02:44 Tower kernel: usb 1-14: USB disconnect, device number 18
Oct  9 00:02:44 Tower usb_manager: Info: rc.usb_manager Autoconnect No Mapping found  /dev/bus/usb/001/024 001 024 port 
Oct  9 00:02:44 Tower usb_manager: Info: rc.usb_manager usb_remove   /dev/bus/usb/001/024 001 024 
Oct  9 00:02:44 Tower kernel: usb 1-14: new full-speed USB device number 19 using xhci_hcd
Oct  9 00:02:44 Tower kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Oct  9 00:02:44 Tower kernel: Bluetooth: hci0: Intel Read version failed (-22)
Oct  9 00:02:44 Tower kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Oct  9 00:02:44 Tower kernel: usb 1-14: USB disconnect, device number 19
Oct  9 00:02:44 Tower usb_manager: Info: rc.usb_manager usb_add  /dev/bus/usb/001/025 001 025
Oct  9 00:02:45 Tower kernel: usb 1-14: new full-speed USB device number 20 using xhci_hcd
Oct  9 00:02:45 Tower kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Oct  9 00:02:45 Tower kernel: Bluetooth: hci0: Intel Read version failed (-22)
Oct  9 00:02:45 Tower kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Oct  9 00:02:45 Tower kernel: usb 1-14: USB disconnect, device number 20
Oct  9 00:02:45 Tower kernel: usb 1-14: new full-speed USB device number 21 using xhci_hcd
Oct  9 00:02:45 Tower kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Oct  9 00:02:45 Tower kernel: Bluetooth: hci0: Intel Read version failed (-22)
Oct  9 00:02:45 Tower kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Oct  9 00:02:45 Tower kernel: usb 1-14: USB disconnect, device number 21
Oct  9 00:02:46 Tower kernel: usb 1-14: new full-speed USB device number 22 using xhci_hcd
Oct  9 00:02:46 Tower kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Oct  9 00:02:46 Tower kernel: Bluetooth: hci0: Intel Read version failed (-22)
Oct  9 00:02:46 Tower kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Oct  9 00:02:46 Tower kernel: usb 1-14: USB disconnect, device number 22
Oct  9 00:02:46 Tower kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot 48 ep 4 with no TDs queued?
Oct  9 00:02:46 Tower kernel: xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr
Oct  9 00:02:46 Tower kernel: xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is pending.
Oct  9 00:02:46 Tower kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Oct  9 00:02:46 Tower kernel: usb 1-14: new full-speed USB device number 23 using xhci_hcd

 

 

Thanks again for any help 🙂 

[SimonF]

@sergio.calheno i think you may need to do bluetooth also, have a look at this post. I know this is for 6.10 but should work on 6.9.2 also.

 

 

Edited October 8, 2021 by SimonF

[smaster]

This is exactly it!

To be clear to anyone with similar issues as me, I simple did the following in the unRAID terminal:

mkdir /boot/config/modprobe.d/
echo -e 'blacklist btusb\nblacklist bluetooth' > /boot/config/modprobe.d/bluetooth.conf

 

This will make it so that unRAID created a folder called "modprobe.d" inside your /boot/config/ folder. Then it creates a script inside the "modprobe.d" folder that blacklists your bluetooth device at boot and therefore stops it from causing anymore problems.

 

If you want to reactivate your bluetooth temporarily, you can simply type the following in your unRAID terminal:

modprobe btusb
modprobe bluetooth

 

However, if you'd like to activate your bluetooth completely (persistent after reboot), simple remove the file that you just created.

 

Big thanks to @SimonF for pointing me in the right direction!

Also, thank you to @JorgeB, @ChatNoir and @trurl

 

Have a great weekend!

Edited October 9, 2021 by sergio.calheno

[SimonF]

@sergio.calhenoGlad we could help.

 

For info the bind button in my plugin is to bind to the usbip process but donesn't remove it from the host.

 

The other suggested options would have worked but I dont think you have virtualisation enabled in the BIOS so could not stub the pcie device.

 

https://wiki.unraid.net/Manual/VM_Management#Determining_HVM.2FIOMMU_Hardware_Support

   

 

Edited October 9, 2021 by SimonF