Tydell

@cambriancatalystDid you ever solve this? I think I solved mine. The syslog errors have gone away and I think bluetooth remains functional in my home assistant instance. Looks like the syslog flooding was a bug in bluez that they remedied with 5.64. The repos ich777 uses for un-get don't yet have anything above 5.63, but I found a slackware repository with 5.64 (there are higher versions than that, but didn't want to push my luck) and added it to the sources.list file for un-get. I then ran 'un-get update' then 'un-get upgrade' to upgrade bluez from 5.63 to 5.64 and restarted bluez. In detail: Add this line to Flash/config/plugins/un-get/sources.list: https://slackware.uk/slackware/slackware64-15.0/patches/ patches Terminal into Unraid & Run: 'un-get update' then 'un-get upgrade' Force bluez/bluetoothd to stop: sudo pkill bluetoothd Restart bluez: /etc/rc.d/rc.bluetooth start

For what it's worth, I'm running into this as well. I installed bluez via un-get to expose bluetooth to Home Assistant, then started bluetooth via "/etc/rc.d/rc.bluetooth start" and now my syslog is being flooded with roughly 10 entries every second with this:

Ah gotcha, sure thing.....here it is. I see one of my parity drives now has a CRC error count of 1...I'm sure I'm not doing my drives any favors with these hard resets. Thanks! syslog (3)

I'm having an unfortunate issue as of late where my unraid server will completely lock up. It drops off the network and is entirely unreachable. A connected keyboard, monitor, and mouse are also unresponsive when this happens as well, so there's no local console either. The only way for me to recover is to force a reboot. An investigation of my logs hasn't yielded much. I've set my logs to copy to my flash drive to get historical information and there aren't any events that I can discern around the time of the freeze. The logs just kick back in at startup. This server's been pretty solid the last couple years - not sure what's going on! Any help shedding light on the potential cause would be hugely appreciated! diagnostics-20230302-2348.zip

Yep, I sure did. Certs reprovisioned successfully and ssl is set to yes. Still can only get in via http

I don't know about anyone else, but after deleting my certs yesterday, turning SSL back on, and re-provisioning certs, I still can only get in via http, not https.

alternatively, you can just delete the ssl certs from the flash drive (/boot/config/ssl/certs)...i did that and was able to get back in. Not sure which is the preferred method, but just throwing it out there.

Same thing happened to me today. Ultimately I got back in by SSHing in and deleting the certs on the flash drive (ssh into server, navigate to /boot/config/ssl and rename/delete the certs folder), then reboot (sbin/reboot). After doing that, I was able to get to the http ui. Upon redoing my certs (settings/management access) and setting USE SSL/TLS to yes, I'm still unable to use ssl to get to my server. It redirects to port 80 and uses a self-signed cert, not the letsencrypt cert. The WAN Port check also fails even though I definitely have port 443 forwarded to my server. Version 6.10.2 if it matters. Also, I didn't proactively install/update anything recently, though an autoupdate of something certainly could have happened. I've also not made any changes to my network setup either. To my knowledge, I didn't make any changes to my server or network leading up to this. FWIW I have NerdPack installed. Don't remember why I have it tbh.

Same thing happened to me today. Ultimately I got back in by SSHing in and deleting the certs on the flash drive (ssh into server, navigate to /boot/config/ssl and rename/delete the certs folder), then reboot (sbin/reboot). After doing that, I was able to get to the http ui. Upon redoing my certs (settings/management access) and setting USE SSL/TLS to yes, I'm still unable to use ssl to get to my server. It redirects to port 80 and uses a self-signed cert, not the letsencrypt cert. The WAN Port check also fails even though I definitely have port 443 forwarded to my server. Version 6.10.2 if it matters. Also, I didn't proactively install/update anything recently, though an autoupdate of something certainly could have happened. I've also not made any changes to my network setup either. To my knowledge, I didn't make any changes to my server or network leading up to this. FWIW I have NerdPack installed. Don't remember why I have it tbh.

Not sure if related or not, but today I suddenly stopped being able to get to the webgui as well. Shares and apps all worked still without issue. Navigating to http://myserverip resulted in an nginx error. https was giving me a dns error as it was trying to go to the custom myservers url with my hash in it. Ultimately I got back in by SSHing in and deleting the certs on the flash drive (ssh into server, navigate to /boot/config/ssl and rename/delete the certs folder), then reboot (sbin/reboot). After doing that, I was able to get to the http ui. Upon redoing my certs (settings/management access) and setting USE SSL/TLS to yes, I'm still unable to use ssl to get to my server. It redirects to port 80 and uses a self-signed cert, not the letsencrypt cert. The WAN Port check also fails even though I definitely have port 443 forwarded to my server. Version 6.10.2 if it matters. EDIT: Also, I didn't proactively install/update anything recently, though an autoupdate of something certainly could have happened. I've also not made any changes to my network setup either. To my knowledge, I didn't make any changes to my server or network leading up to this. EDIT2: FWIW I have NerdPack installed. Don't remember why I have it tbh.

Just wanted to revisit this and report that I did disable spindown for a few days and after doing so, there were no more errors. I conducted further testing by re-enabling spindown, letting the disk spin down, then initiating a transfer to the array and since this disk was nearly empty, it transferred to this drive. It immediately threw all sorts of errors. I then disabled spindown on the disk again and since then I've had no issues. For that reason, I'm going to conclude that this disk just doesn't play nicely with spinning down. Thanks @Vr2Io!

Just did that...will monitor. Thank you!

I've recently made some changes to my unraid server. I used to have an HBA with a 16 port SAS expander, but then also used onboard SATA ports to fill out my 24 drive bays. I recently purchased and installed a 24-port SAS expander to eliminate my need to use onboard SATA ports as they seemed to be flaky/inconsistent. I also installed a new 8TB drive. Unraid is reporting errors on that drive now and i'm also receiving parity errors on that drive as well. I've checked all the physical connections and have reseated the sata cable on the backplane. Is there anything else I might check? Here are what the recent errors look like: Any ideas as to what I might check next? I super appreciate any help! tyraid-diagnostics-20220204-1359.zip

Nope, no issues....works out of the box. Bought a QNAP QSW-308-1C that works perfectly with it.

😮