My first server, and following issues

[iGo]

Hello everyone
I'm new to the forum and I have made my first server a week ago(stoked). I had heard good things about Unraid being customizable and thought I could use it to learn, so I decided to try this instead of a basic Windows setup. With absolutely no Linux experience I feel like i'm in deep water already with the small problems I have encountered and no idea how to solve. Googling after answers I find forum posts with similar issues, but the answers are only cmd/terminal liners to paste and run which I do not want to do without understanding them. 
 I got 3 seperate problems as of now, but first -

rig:
B560 TOMAHAWK WIFI 
16gb memory
3x 4tb ironwolf disks(1parity)
1x 512 nvme cache
unraid- corsair 32gb flashdrive

Intel® Core™ i5-10400 CPU

no gpu


Its running and things seem ok. I made a few shares, and transferred some files. Array and parity is OK. Root password set.
However the log is filled with the below: 
Apparently the server has done a shutdown in the night aswell (uptime only 3 hours), and I cant see why because the log has been filled with this shit and removed what happened.

Problem 1: bluetooth needs to be disabled somehow.
Problem 2: usb 1-2 disconnect and reconnects all the time?
Problem 3: After I restart my server it says it was a bad shutdown and I need to do paritycheck. 

Dec 17 15:16:22 DEFINE7 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Dec 17 15:16:22 DEFINE7 kernel: Bluetooth: hci0: Intel Read version failed (-22)
Dec 17 15:16:22 DEFINE7 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Dec 17 15:16:22 DEFINE7 kernel: usb 1-2: USB disconnect, device number 94
Dec 17 15:16:22 DEFINE7 kernel: usb 1-2: new full-speed USB device number 95 using xhci_hcd
Dec 17 15:16:22 DEFINE7 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Dec 17 15:16:22 DEFINE7 kernel: Bluetooth: hci0: Intel Read version failed (-22)
Dec 17 15:16:22 DEFINE7 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Dec 17 15:16:22 DEFINE7 kernel: usb 1-2: USB disconnect, device number 95
Dec 17 15:16:23 DEFINE7 kernel: usb 1-2: new full-speed USB device number 96 using xhci_hcd
Dec 17 15:16:23 DEFINE7 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Dec 17 15:16:23 DEFINE7 kernel: Bluetooth: hci0: Intel Read version failed (-22)
Dec 17 15:16:23 DEFINE7 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Dec 17 15:16:23 DEFINE7 kernel: usb 1-2: USB disconnect, device number 96
Dec 17 15:16:23 DEFINE7 kernel: usb 1-2: new full-speed USB device number 97 using xhci_hcd

 

 

Edit:  problem 4 has appeared in the logs   This is greek to me. 
Dec 17 15:59:36 DEFINE7 kernel: usb 1-2: USB disconnect, device number 41
Dec 17 15:59:36 DEFINE7 kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot 11 ep 4 with no TDs queued?
Dec 17 15:59:36 DEFINE7 kernel: xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr
Dec 17 15:59:36 DEFINE7 kernel: xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is pending.
Dec 17 15:59:36 DEFINE7 kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.

 

 

Any help appreciated. Also looking for tips/links to other posts if there are some extra steps/settings I should do that is smart for a new build.

[trurl]

attach diagnostics to your NEXT post in this thread

[iGo]

Attached is the requested file

define7-diagnostics-20211217-1637.zip

[iGo]

Small update. I am now wondering if the server is restarting because the logfile is filling up 100% of memory. Its rebooted again 1 hour ago 

[Squid]

Unlikely the syslog filling would directly cause a reset.  But, your bluetooth dongle is giving the system a heart attack.  Try a different USB port, ideally one of the 2.0 ports on the back of the board.

 

Also, have you run a memtest yet?  You might also considering disabling the overclock (XMP) on the memory within the BIOS

 

Your BIOS is also out of date on the motherboard.

[iGo]

I see.
I had the usb in 2.0 and moved it with no change. I will move it back to one of those ports.
There is nothing connected to the computer apart from power, ethernet and the unraid USB.(no bluetooth dongle) Got a laugh out of your comment though

Is it possible to do bios changes from Unraid or will I have to connect a monitor/keyboard to it physically again to do this? I have not ran hardware diagnostic since I set it up the first time, but all parts passed then.

[Squid]

Honestly, with any random motherboard if you're not going to be utilizing the component, it should get disabled in the BIOS (ie: Wifi, Bluetooth, serial ports, any lights etc if you can't see them etc).  If nothing else, you save the power and in theory it's always a more stable system.

 

And you should be able to do a BIOS update within the bios itself, but will need a monitor and keyboard attached.

[iGo]

Thanks. I will look around in the Bios if I can turn those off.
I was able to miss the part where Unraid is impossible to run over wifi as a start, thats why i got the 6e wifi motherboard. I got powerful cabled mesh AP's at home and wifi would have sufficed for my use. Now I got it in a bad place with cable... 

Il report back after updating and trying to shut off those functions.
 

[iGo]

Bios is now on latest version. XMR is turned off(Does this make it more stable?) I turned off both intel wifi and bluetooth in bios.
Usb-stick is in usb. 2.0 slot

However the logspam is still happening: 

Thank you again in advance

Dec 18 20:15:43 DEFINE7 kernel: usb 1-2: USB disconnect, device number 71
Dec 18 20:15:43 DEFINE7 kernel: xhci_hcd 0000:00:14.0: WARN Event TRB for slot 28 ep 4 with no TDs queued?
Dec 18 20:15:43 DEFINE7 kernel: xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr
Dec 18 20:15:43 DEFINE7 kernel: xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is pending.
Dec 18 20:15:43 DEFINE7 kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 18 20:15:43 DEFINE7 kernel: usb 1-2: new full-speed USB device number 72 using xhci_hcd
Dec 18 20:15:44 DEFINE7 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Dec 18 20:15:44 DEFINE7 kernel: Bluetooth: hci0: Intel Read version failed (-22)
Dec 18 20:15:44 DEFINE7 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Dec 18 20:15:44 DEFINE7 kernel: usb 1-2: USB disconnect, device number 72
Dec 18 20:15:44 DEFINE7 kernel: usb 1-2: new full-speed USB device number 73 using xhci_hcd
Dec 18 20:15:44 DEFINE7 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Dec 18 20:15:44 DEFINE7 kernel: Bluetooth: hci0: Intel Read version failed (-22)
Dec 18 20:15:44 DEFINE7 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Dec 18 20:15:44 DEFINE7 kernel: usb 1-2: USB disconnect, device number 73
Dec 18 20:15:44 DEFINE7 kernel: usb 1-2: new full-speed USB device number 74 using xhci_hcd
Dec 18 20:15:45 DEFINE7 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Dec 18 20:15:45 DEFINE7 kernel: Bluetooth: hci0: Intel Read version failed (-22)
Dec 18 20:15:45 DEFINE7 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Dec 18 20:15:45 DEFINE7 kernel: usb 1-2: USB disconnect, device number 74
Dec 18 20:15:45 DEFINE7 kernel: usb 1-2: new full-speed USB device number 75 using xhci_hcd
Dec 18 20:15:45 DEFINE7 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Dec 18 20:15:45 DEFINE7 kernel: Bluetooth: hci0: Intel Read version failed (-22)
Dec 18 20:15:45 DEFINE7 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Dec 18 20:15:45 DEFINE7 kernel: usb 1-2: USB disconnect, device number 75
Dec 18 20:15:45 DEFINE7 kernel: usb 1-2: new full-speed USB device number 76 using xhci_hcd
Dec 18 20:15:46 DEFINE7 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
Dec 18 20:15:46 DEFINE7 kernel: Bluetooth: hci0: Intel Read version failed (-22)
Dec 18 20:15:46 DEFINE7 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
Dec 18 20:15:46 DEFINE7 kernel: usb 1-2: USB disconnect, device number 76

[SimonF]

42 minutes ago, iGo said:

logspam

This may help

 

[iGo]

That thread might be onto something. However I got an error saying its in use. How do I proceed?

root@DEFINE7:~# modprobe -r bluetooth
modprobe: FATAL: Module bluetooth is in use.

root@DEFINE7:~# modprobe -r btusb
root@DEFINE7:~# modprobe -r bluetooth
modprobe: FATAL: Module bluetooth is in use.

root@DEFINE7:~# lsmod | grep "bluetooth"
bluetooth             380928  5 btrtl,btintel,btbcm,btusb
ecdh_generic           16384  1 bluetooth
 

[SimonF]

10 minutes ago, iGo said:

That thread might be onto something. However I got an error saying its in use. How do I proceed?

root@DEFINE7:~# modprobe -r bluetooth
modprobe: FATAL: Module bluetooth is in use.

root@DEFINE7:~# modprobe -r btusb
root@DEFINE7:~# modprobe -r bluetooth
modprobe: FATAL: Module bluetooth is in use.

root@DEFINE7:~# lsmod | grep "bluetooth"
bluetooth             380928  5 btrtl,btintel,btbcm,btusb
ecdh_generic           16384  1 bluetooth
 

Do this and a reboot this will stop it loading.

 

mkdir /boot/config/modprobe.d/

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

 

Edited December 18, 2021 by SimonF

[iGo]

My server has been running for 24 hours now and the command above has stopped the errors in the log!
Thank you.