blackbullitt

That resolved the cert issue, thanks!

Here is what I get if I have CertCheck turned on. ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:05880002:x509 certificate routines::system lib ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:05880002:x509 certificate routines::system lib ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:05880002:x509 certificate routines::system lib ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:10000080:BIO routines::no such file ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:FFFFFFFF80000002:system library::No such file or directory ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:10000080:BIO routines::no such file ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:10000080:BIO routines::no such file ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:FFFFFFFF80000002:system library::No such file or directory ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:05880002:x509 certificate routines::system lib ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:10000080:BIO routines::no such file ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:FFFFFFFF80000002:system library::No such file or directory ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:05880002:x509 certificate routines::system lib ERRORTue Nov 07 2023 04:32:20Could not set certificate store location: error:05880002:x509 certificate routines::system lib

When I updated it would not download anything unless I change cert check to no under Security in the settings. I would get an abundance of TLS cert errors. The ideal fix was to pull a new pem file from nzbget.

No the other issue I have is to pull a new cacert.pem from nzbget.net which resolves a tls connection error. SpaceInvader covered it a long while back. However the path is no longer vaild to remove the old pem file and pull a new one.

I constantly get stuff stuck on unpacking on mine, even with the new update. Also, the new update that dropped I can't seem to find where the cacert.pem file is located in order to fix that issue. It was located in /usr/local/bin/nzbget/, but now nzbget is showing as a file and not a folder anymore since the update. Any fixes for these issues?

Anybody having an issue with Unmanic taking a full movie that plays the full length before transcoding and then the transcoding chops it down to 20 minutes or less? TV shows seem to be fine, it's only movies. ***Edit*** I think I found the cause of the issue. As the file is being moved to the array, unmanic detects it and starts transcoding before the file has completely moved over to the array.

I have had the remux plugin, so that wasn't the case for me. I systematically removed the new plugins one at a time and rescanned the library and watched each time to see if the pending tasks number went up. It seems that the ignore file type by extension was causing me the heartache. Since all the new plugins were removed I turned on cancel all pending tasks on restart, restated Unmanic, and rescanned the library and no pending tasks came up, which is how it was prior to this. I have added back in only the remove all subtitles plugin to the plugin flow and reran the library scan. I will have to wait and see how many pending tasks I have and take note of it and check it, again, on the next library scan to compare numbers. I'll keep everyone posted. ***Update*** My issues seems to be resolved. I'm leery of adding back in the ignore file types by extension.

Has anyone experienced where Unmanic will take a completed task and add it back to pending tasks after a library scan? I have added a few extra plugins (remove all subtitle streams, reject file if larger than original, limit library search by file extension) and ever since it will add all the media files back into pending tasks on the next days library scan that it had previously completed. When the worker processes the files, again, I see this in the scrolling log and then moves it to the completed tasks: 2023-08-09T11:07:34:WARNING:Unmanic.Melkree-Worker-1 - [FORMATTED] - No Plugin requested for Unmanic to run commands for this file It has successfully converted my library to AAC and H265 in the past and had never added completed tasks back into pending tasks. My intentions are to strip the subtitles and use bazaar and pull external ones. Bazaar is set to add the srt file to the existing folder the media file resides in. I don't see that being an issue, although I see when it runs a test scan it does pick up the existence of the srt files added to the same folder the media resides in.

I am on 6.11.5 and I was getting the same error. I had to restart the php-fpm constantly. I attempted to go into the settings of the GPU statistics and it would instantly lock up, again. I removed the plugin and it seems to have resolved my issue. I can move from screen to screen without it being sluggish or not responding at all.

I just recently started seeing this happen within the past few days. It starts filling up my log file every time Unmanic transcodes media. After Unmanic completes its jobs it stops restarting the service. I have also noticed that every job that starts it drops a unmanic_file_conversion-xxxxxx.cfg in /boot/config/share and never removes it. Is there a way to stop it from doing this? I have all my conversions written to my cache SSD drive. Below is the output of a tail I ran on the log file as Unmanic was running. Also, attached is the diagnostics file. Any help would be appreciated. Jan 3 09:08:03 WhiteNoiseMedia avahi-daemon[9614]: Registering new address record for ::1 on lo.*. Jan 3 09:08:03 WhiteNoiseMedia avahi-daemon[9614]: Registering new address record for 127.0.0.1 on lo.IPv4. Jan 3 09:08:03 WhiteNoiseMedia emhttpd: shcmd (588173): /etc/rc.d/rc.avahidnsconfd restart Jan 3 09:08:03 WhiteNoiseMedia root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Jan 3 09:08:03 WhiteNoiseMedia root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jan 3 09:08:03 WhiteNoiseMedia avahi-dnsconfd[9650]: Successfully connected to Avahi daemon. Jan 3 09:08:04 WhiteNoiseMedia avahi-daemon[9614]: Server startup complete. Host name is WhiteNoiseMedia.local. Local service cookie is 2464313616. Jan 3 09:08:05 WhiteNoiseMedia avahi-daemon[9614]: Service "WhiteNoiseMedia" (/services/ssh.service) successfully established. Jan 3 09:08:05 WhiteNoiseMedia avahi-daemon[9614]: Service "WhiteNoiseMedia" (/services/smb.service) successfully established. Jan 3 09:08:05 WhiteNoiseMedia avahi-daemon[9614]: Service "WhiteNoiseMedia" (/services/sftp-ssh.service) successfully established. Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: [2023/01/03 09:08:26.380498, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: [2023/01/03 09:08:26.380589, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1 Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: [2023/01/03 09:08:26.380615, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 172.31.200.1 Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: [2023/01/03 09:08:26.380967, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: [2023/01/03 09:08:26.380996, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 10.0.1.7 Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: Jan 3 09:08:26 WhiteNoiseMedia nmbd[9533]: ***** Jan 3 09:14:00 WhiteNoiseMedia emhttpd: Starting services... Jan 3 09:14:00 WhiteNoiseMedia emhttpd: shcmd (589237): /etc/rc.d/rc.samba restart Jan 3 09:14:00 WhiteNoiseMedia nmbd[9533]: [2023/01/03 09:14:00.961518, 0] ../../source3/nmbd/nmbd.c:59(terminate) Jan 3 09:14:00 WhiteNoiseMedia nmbd[9533]: Got SIGTERM: going down... Jan 3 09:14:00 WhiteNoiseMedia winbindd[9555]: [2023/01/03 09:14:00.961563, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Jan 3 09:14:00 WhiteNoiseMedia winbindd[9555]: Got sig[15] terminate (is_parent=1) Jan 3 09:14:00 WhiteNoiseMedia wsdd2[9543]: 'Terminated' signal received. Jan 3 09:14:00 WhiteNoiseMedia wsdd2[9543]: terminating. Jan 3 09:14:00 WhiteNoiseMedia winbindd[9557]: [2023/01/03 09:14:00.963225, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Jan 3 09:14:00 WhiteNoiseMedia winbindd[9557]: Got sig[15] terminate (is_parent=0) Jan 3 09:14:03 WhiteNoiseMedia root: Starting Samba: /usr/sbin/smbd -D Jan 3 09:14:03 WhiteNoiseMedia smbd[10568]: [2023/01/03 09:14:03.198337, 0] ../../source3/smbd/server.c:1741(main) Jan 3 09:14:03 WhiteNoiseMedia smbd[10568]: smbd version 4.17.3 started. Jan 3 09:14:03 WhiteNoiseMedia smbd[10568]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Jan 3 09:14:03 WhiteNoiseMedia root: /usr/sbin/nmbd -D Jan 3 09:14:03 WhiteNoiseMedia nmbd[10570]: [2023/01/03 09:14:03.223392, 0] ../../source3/nmbd/nmbd.c:901(main) Jan 3 09:14:03 WhiteNoiseMedia nmbd[10570]: nmbd version 4.17.3 started. Jan 3 09:14:03 WhiteNoiseMedia nmbd[10570]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Jan 3 09:14:03 WhiteNoiseMedia root: /usr/sbin/wsdd2 -d Jan 3 09:14:03 WhiteNoiseMedia wsdd2[10589]: starting. Jan 3 09:14:03 WhiteNoiseMedia root: /usr/sbin/winbindd -D Jan 3 09:14:03 WhiteNoiseMedia winbindd[10590]: [2023/01/03 09:14:03.304017, 0] ../../source3/winbindd/winbindd.c:1440(main) Jan 3 09:14:03 WhiteNoiseMedia winbindd[10590]: winbindd version 4.17.3 started. Jan 3 09:14:03 WhiteNoiseMedia winbindd[10590]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Jan 3 09:14:03 WhiteNoiseMedia winbindd[10592]: [2023/01/03 09:14:03.309425, 0] ../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache) Jan 3 09:14:03 WhiteNoiseMedia winbindd[10592]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Jan 3 09:14:03 WhiteNoiseMedia emhttpd: shcmd (589242): /etc/rc.d/rc.avahidaemon restart Jan 3 09:14:03 WhiteNoiseMedia root: Stopping Avahi mDNS/DNS-SD Daemon: stopped Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Got SIGTERM, quitting. Jan 3 09:14:03 WhiteNoiseMedia avahi-dnsconfd[9650]: read(): EOF Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface veth78b348a.IPv6 with address fe80::fcc2:5dff:fe24:83c1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface vethd250376.IPv6 with address fe80::8ca7:d4ff:fefd:1651. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface veth0921b5f.IPv6 with address fe80::f480:a3ff:feaf:b99. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface veth24f364e.IPv6 with address fe80::c4b9:f5ff:fe3a:6f44. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface vethe296c85.IPv6 with address fe80::3407:bdff:fe99:c7f8. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface vethcf331ec.IPv6 with address fe80::6094:cbff:fe0b:4873. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface veth672dfc9.IPv6 with address fe80::9c2f:75ff:fe54:f749. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface veth86c5452.IPv6 with address fe80::d4b1:eff:fe9d:443e. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface veth3cad5f9.IPv6 with address fe80::f8f3:aaff:fe28:fb2b. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface veth2cbf9c7.IPv6 with address fe80::e84c:4fff:fed5:21db. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface veth4da326b.IPv6 with address fe80::e844:62ff:feae:5c9b. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface vethdb2af57.IPv6 with address fe80::88ef:69ff:feeb:a491. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface veth565eca3.IPv6 with address fe80::84de:5dff:fe89:88b5. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe9e:7271. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface shim-br0.IPv6 with address fe80::4ee:ceff:fe13:b2b8. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface shim-br0.IPv4 with address 10.0.1.7. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface br-c8f6898ee13a.IPv6 with address fe80::42:9bff:fe9d:c254. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface br-c8f6898ee13a.IPv4 with address 172.18.0.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface br-bb44d3963d17.IPv4 with address 172.31.200.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface docker0.IPv6 with address fe80::42:eff:fe1d:71bb. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface br0.IPv4 with address 10.0.1.7. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface lo.IPv6 with address ::1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: Leaving mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[9614]: avahi-daemon 0.8 exiting. Jan 3 09:14:03 WhiteNoiseMedia root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Successfully dropped root privileges. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: avahi-daemon 0.8 starting up. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Successfully called chroot(). Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Successfully dropped remaining capabilities. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Loading service file /services/sftp-ssh.service. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Loading service file /services/smb.service. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Loading service file /services/ssh.service. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface veth78b348a.IPv6 with address fe80::fcc2:5dff:fe24:83c1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface veth78b348a.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface vethd250376.IPv6 with address fe80::8ca7:d4ff:fefd:1651. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface vethd250376.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface veth0921b5f.IPv6 with address fe80::f480:a3ff:feaf:b99. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface veth0921b5f.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface veth24f364e.IPv6 with address fe80::c4b9:f5ff:fe3a:6f44. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface veth24f364e.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface vethe296c85.IPv6 with address fe80::3407:bdff:fe99:c7f8. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface vethe296c85.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface vethcf331ec.IPv6 with address fe80::6094:cbff:fe0b:4873. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface vethcf331ec.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface veth672dfc9.IPv6 with address fe80::9c2f:75ff:fe54:f749. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface veth672dfc9.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface veth86c5452.IPv6 with address fe80::d4b1:eff:fe9d:443e. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface veth86c5452.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface veth3cad5f9.IPv6 with address fe80::f8f3:aaff:fe28:fb2b. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface veth3cad5f9.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface veth2cbf9c7.IPv6 with address fe80::e84c:4fff:fed5:21db. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface veth2cbf9c7.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface veth4da326b.IPv6 with address fe80::e844:62ff:feae:5c9b. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface veth4da326b.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface vethdb2af57.IPv6 with address fe80::88ef:69ff:feeb:a491. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface vethdb2af57.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface veth565eca3.IPv6 with address fe80::84de:5dff:fe89:88b5. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface veth565eca3.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe9e:7271. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface vnet0.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface virbr0.IPv4 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface shim-br0.IPv6 with address fe80::4ee:ceff:fe13:b2b8. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface shim-br0.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface shim-br0.IPv4 with address 10.0.1.7. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface shim-br0.IPv4 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface br-c8f6898ee13a.IPv6 with address fe80::42:9bff:fe9d:c254. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface br-c8f6898ee13a.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface br-c8f6898ee13a.IPv4 with address 172.18.0.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface br-c8f6898ee13a.IPv4 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface br-bb44d3963d17.IPv4 with address 172.31.200.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface br-bb44d3963d17.IPv4 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:eff:fe1d:71bb. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface docker0.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface docker0.IPv4 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface br0.IPv4 with address 10.0.1.7. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface br0.IPv4 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface lo.IPv6 with address ::1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface lo.IPv6 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: New relevant interface lo.IPv4 for mDNS. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Network interface enumeration completed. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::fcc2:5dff:fe24:83c1 on veth78b348a.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::8ca7:d4ff:fefd:1651 on vethd250376.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::f480:a3ff:feaf:b99 on veth0921b5f.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::c4b9:f5ff:fe3a:6f44 on veth24f364e.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::3407:bdff:fe99:c7f8 on vethe296c85.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::6094:cbff:fe0b:4873 on vethcf331ec.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::9c2f:75ff:fe54:f749 on veth672dfc9.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::d4b1:eff:fe9d:443e on veth86c5452.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::f8f3:aaff:fe28:fb2b on veth3cad5f9.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::e84c:4fff:fed5:21db on veth2cbf9c7.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::e844:62ff:feae:5c9b on veth4da326b.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::88ef:69ff:feeb:a491 on vethdb2af57.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::84de:5dff:fe89:88b5 on veth565eca3.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::fc54:ff:fe9e:7271 on vnet0.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for 192.168.122.1 on virbr0.IPv4. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::4ee:ceff:fe13:b2b8 on shim-br0.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for 10.0.1.7 on shim-br0.IPv4. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::42:9bff:fe9d:c254 on br-c8f6898ee13a.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for 172.18.0.1 on br-c8f6898ee13a.IPv4. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for 172.31.200.1 on br-bb44d3963d17.IPv4. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for fe80::42:eff:fe1d:71bb on docker0.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for 172.17.0.1 on docker0.IPv4. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for 10.0.1.7 on br0.IPv4. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for ::1 on lo.*. Jan 3 09:14:03 WhiteNoiseMedia avahi-daemon[10623]: Registering new address record for 127.0.0.1 on lo.IPv4. Jan 3 09:14:03 WhiteNoiseMedia emhttpd: shcmd (589243): /etc/rc.d/rc.avahidnsconfd restart Jan 3 09:14:03 WhiteNoiseMedia root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped Jan 3 09:14:03 WhiteNoiseMedia root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jan 3 09:14:03 WhiteNoiseMedia avahi-dnsconfd[10634]: Successfully connected to Avahi daemon. Jan 3 09:14:04 WhiteNoiseMedia avahi-daemon[10623]: Server startup complete. Host name is WhiteNoiseMedia.local. Local service cookie is 3665214217. Jan 3 09:14:05 WhiteNoiseMedia avahi-daemon[10623]: Service "WhiteNoiseMedia" (/services/ssh.service) successfully established. Jan 3 09:14:05 WhiteNoiseMedia avahi-daemon[10623]: Service "WhiteNoiseMedia" (/services/smb.service) successfully established. Jan 3 09:14:05 WhiteNoiseMedia avahi-daemon[10623]: Service "WhiteNoiseMedia" (/services/sftp-ssh.service) successfully established. Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: [2023/01/03 09:14:26.257528, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1 Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: [2023/01/03 09:14:26.257609, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 172.18.0.1 Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: [2023/01/03 09:14:26.257631, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 172.31.200.1 Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: [2023/01/03 09:14:26.257657, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 192.168.122.1 Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: [2023/01/03 09:14:26.257705, 0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2) Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Samba name server WHITENOISEMEDIA is now a local master browser for workgroup WORKGROUP on subnet 10.0.1.7 Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: Jan 3 09:14:26 WhiteNoiseMedia nmbd[10574]: ***** whitenoisemedia-diagnostics-20230103-1004.zip

I have swapped locations of the CAT6 cable. It was originally on a switch, now it is connected directly to my router.

Got this before it went down, again. BIOS update made no difference. Feb 16 11:06:34 WhiteNoiseMedia dhcpcd[1829]: br0: failed to renew DHCP, rebinding

Thanks for the reply. This NIC is an onboard NIC on the Gigabyte C246-WU4-CF motherboard. It also has the latest BIOS firmware installed. I am, also, using a CAT6 ethernet cable. Although the reel I have of the CAT6 was from Monoprice, so made in China more than likely. I stand corrected, they just released a new BIOS update right after I updated mine a few months back. I'll give that a try as well.

I've been having this issue for a while now where the one NIC I am using will drop and the server become unresponsive. The only thing I can see in the log is the following. Anyone else have this issue? Feb 12 12:58:30 WhiteNoiseMedia kernel: igb 0000:08:00.0 eth0: igb: eth0 NIC Link is Down Feb 12 12:58:30 WhiteNoiseMedia kernel: br0: port 1(eth0) entered disabled state Feb 12 12:58:31 WhiteNoiseMedia dhcpcd[1830]: br0: carrier lost Feb 12 12:58:31 WhiteNoiseMedia dhcpcd[1830]: br0: deleting route to 10.0.1.0/24 Feb 12 12:58:31 WhiteNoiseMedia dhcpcd[1830]: br0: deleting default route via 10.0.1.1 Feb 12 12:58:31 WhiteNoiseMedia dnsmasq[10403]: no servers found in /etc/resolv.conf, will retry Feb 12 12:58:33 WhiteNoiseMedia ntpd[1904]: Deleting interface #1 br0, 10.0.1.7#123, interface stats: received=3509, sent=356 0, dropped=0, active_time=869389 secs Feb 12 12:58:33 WhiteNoiseMedia ntpd[1904]: 216.239.35.12 local addr 10.0.1.7 -> <null> Feb 12 12:58:33 WhiteNoiseMedia ntpd[1904]: 216.239.35.8 local addr 10.0.1.7 -> <null> Feb 12 12:58:33 WhiteNoiseMedia ntpd[1904]: 216.239.35.4 local addr 10.0.1.7 -> <null> Feb 12 12:58:33 WhiteNoiseMedia ntpd[1904]: 216.239.35.0 local addr 10.0.1.7 -> <null> Feb 12 12:58:34 WhiteNoiseMedia kernel: igb 0000:08:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Feb 12 12:58:34 WhiteNoiseMedia dhcpcd[1830]: br0: carrier acquired Feb 12 12:58:34 WhiteNoiseMedia kernel: br0: port 1(eth0) entered blocking state Feb 12 12:58:34 WhiteNoiseMedia kernel: br0: port 1(eth0) entered forwarding state Feb 12 12:58:34 WhiteNoiseMedia dhcpcd[1830]: br0: rebinding lease of 10.0.1.7 Feb 12 12:58:39 WhiteNoiseMedia dhcpcd[1830]: br0: probing for an IPv4LL address Feb 12 12:58:39 WhiteNoiseMedia dhcpcd[1830]: br0: DHCP lease expired Feb 12 12:58:39 WhiteNoiseMedia dhcpcd[1830]: br0: soliciting a DHCP lease Feb 12 12:58:44 WhiteNoiseMedia dhcpcd[1830]: br0: using IPv4LL address 169.254.224.190 Feb 12 12:58:44 WhiteNoiseMedia dhcpcd[1830]: br0: adding route to 169.254.0.0/16 Feb 12 12:58:44 WhiteNoiseMedia dhcpcd[1830]: br0: adding default route Feb 12 12:58:45 WhiteNoiseMedia kernel: igb 0000:08:00.0 eth0: igb: eth0 NIC Link is Down Feb 12 12:58:45 WhiteNoiseMedia kernel: br0: port 1(eth0) entered disabled state Feb 12 12:58:46 WhiteNoiseMedia dhcpcd[1830]: br0: carrier lost Feb 12 12:58:46 WhiteNoiseMedia dhcpcd[1830]: br0: deleting route to 169.254.0.0/16 Feb 12 12:58:46 WhiteNoiseMedia dhcpcd[1830]: br0: deleting default route Feb 12 12:58:48 WhiteNoiseMedia kernel: igb 0000:08:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Feb 12 12:58:48 WhiteNoiseMedia dhcpcd[1830]: br0: carrier acquired Feb 12 12:58:48 WhiteNoiseMedia kernel: br0: port 1(eth0) entered blocking state Feb 12 12:58:48 WhiteNoiseMedia kernel: br0: port 1(eth0) entered forwarding state Feb 12 12:58:48 WhiteNoiseMedia dhcpcd[1830]: br0: soliciting a DHCP lease Feb 12 12:58:53 WhiteNoiseMedia dhcpcd[1830]: br0: probing for an IPv4LL address Feb 12 12:58:59 WhiteNoiseMedia dhcpcd[1830]: br0: using IPv4LL address 169.254.224.190 Feb 12 12:58:59 WhiteNoiseMedia dhcpcd[1830]: br0: adding route to 169.254.0.0/16 Feb 12 12:58:59 WhiteNoiseMedia dhcpcd[1830]: br0: adding default route Feb 12 12:59:00 WhiteNoiseMedia ntpd[1904]: Listen normally on 3 br0 169.254.224.190:123 Feb 12 12:59:00 WhiteNoiseMedia ntpd[1904]: new interface(s) found: waking up resolver Feb 12 12:59:17 WhiteNoiseMedia kernel: igb 0000:08:00.0 eth0: igb: eth0 NIC Link is Down Feb 12 12:59:17 WhiteNoiseMedia kernel: br0: port 1(eth0) entered disabled state Feb 12 12:59:18 WhiteNoiseMedia dhcpcd[1830]: br0: carrier lost Feb 12 12:59:18 WhiteNoiseMedia dhcpcd[1830]: br0: deleting route to 169.254.0.0/16 Feb 12 12:59:18 WhiteNoiseMedia dhcpcd[1830]: br0: deleting default route Feb 12 12:59:19 WhiteNoiseMedia ntpd[1904]: Deleting interface #3 br0, 169.254.224.190#123, interface stats: received=0, sent =4, dropped=0, active_time=19 secs Feb 12 12:59:19 WhiteNoiseMedia ntpd[1904]: 216.239.35.0 local addr 169.254.224.190 -> <null> Feb 12 12:59:19 WhiteNoiseMedia ntpd[1904]: 216.239.35.4 local addr 169.254.224.190 -> <null> Feb 12 12:59:19 WhiteNoiseMedia ntpd[1904]: 216.239.35.8 local addr 169.254.224.190 -> <null> Feb 12 12:59:19 WhiteNoiseMedia ntpd[1904]: 216.239.35.12 local addr 169.254.224.190 -> <null> Feb 12 12:59:20 WhiteNoiseMedia kernel: igb 0000:08:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Feb 12 12:59:20 WhiteNoiseMedia dhcpcd[1830]: br0: carrier acquired Feb 12 12:59:20 WhiteNoiseMedia kernel: br0: port 1(eth0) entered blocking state Feb 12 12:59:20 WhiteNoiseMedia kernel: br0: port 1(eth0) entered forwarding state Feb 12 12:59:20 WhiteNoiseMedia dhcpcd[1830]: br0: soliciting a DHCP lease Feb 12 12:59:25 WhiteNoiseMedia dhcpcd[1830]: br0: probing for an IPv4LL address Feb 12 12:59:30 WhiteNoiseMedia dhcpcd[1830]: br0: using IPv4LL address 169.254.224.190 Feb 12 12:59:30 WhiteNoiseMedia dhcpcd[1830]: br0: adding route to 169.254.0.0/16 Feb 12 12:59:30 WhiteNoiseMedia dhcpcd[1830]: br0: adding default route Feb 12 12:59:32 WhiteNoiseMedia dhcpcd[1830]: br0: offered 10.0.1.7 from 10.0.1.1 Feb 12 12:59:32 WhiteNoiseMedia dhcpcd[1830]: br0: probing address 10.0.1.7/24 Feb 12 12:59:32 WhiteNoiseMedia ntpd[1904]: Listen normally on 4 br0 169.254.224.190:123 Feb 12 12:59:32 WhiteNoiseMedia ntpd[1904]: new interface(s) found: waking up resolver Feb 12 12:59:37 WhiteNoiseMedia dhcpcd[1830]: br0: leased 10.0.1.7 for 86400 seconds Feb 12 12:59:37 WhiteNoiseMedia dhcpcd[1830]: br0: adding route to 10.0.1.0/24 Feb 12 12:59:37 WhiteNoiseMedia dhcpcd[1830]: br0: changing default route via 10.0.1.1 Feb 12 12:59:37 WhiteNoiseMedia dnsmasq[10403]: reading /etc/resolv.conf Feb 12 12:59:37 WhiteNoiseMedia dnsmasq[10403]: using nameserver 10.0.1.24#53 Feb 12 12:59:37 WhiteNoiseMedia dnsmasq[10403]: using nameserver 10.0.1.22#53 Feb 12 12:59:37 WhiteNoiseMedia dhcpcd[1830]: br0: deleting route to 169.254.0.0/16 Feb 12 12:59:37 WhiteNoiseMedia dhcpcd[1830]: br0: pid 1830 deleted default route via 10.0.1.1 Feb 12 12:59:38 WhiteNoiseMedia ntpd[1904]: Listen normally on 5 br0 10.0.1.7:123 Feb 12 12:59:38 WhiteNoiseMedia ntpd[1904]: Deleting interface #4 br0, 169.254.224.190#123, interface stats: received=0, sent =3, dropped=1, active_time=6 secs Feb 12 12:59:38 WhiteNoiseMedia ntpd[1904]: 216.239.35.0 local addr 169.254.224.190 -> <null> Feb 12 12:59:38 WhiteNoiseMedia ntpd[1904]: 216.239.35.4 local addr 169.254.224.190 -> <null> Feb 12 12:59:38 WhiteNoiseMedia ntpd[1904]: 216.239.35.8 local addr 169.254.224.190 -> <null> Feb 12 12:59:38 WhiteNoiseMedia ntpd[1904]: 216.239.35.12 local addr 169.254.224.190 -> <null> Feb 12 12:59:38 WhiteNoiseMedia ntpd[1904]: new interface(s) found: waking up resolver Feb 12 13:00:29 WhiteNoiseMedia nmbd[15000]: [2022/02/12 13:00:29.064983, 0] ../../source3/nmbd/nmbd_incomingdgrams.c:699(pr ocess_get_backup_list_request)

Has anyone seen this error when trying to mount a share? When I click mount this is the error that returns in the log. Haven't had much luck finding any answers. It started when my server went down hard. My setup is mounting a smb share from Unraid to a QNAP server where I backup all of my docker appdata. I have reinstalled the plugin just to make sure it was not corrupted and still get the same issue. When creating the share Unraid sees the QNAP hostname and share after setting the username/password. I have also rebooted both servers. Jan 29 14:28:38 Tower kernel: CIFS: VFS: cifs_mount failed w/return code = -6 Jan 29 14:28:38 Tower unassigned.devices: SMB 1.0 mount failed: 'Retrying with upper case share name mount error(6): No such device or address Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '. ***Update*** It's mounting now. I looked into both my AdGuard setups and it appears it was blocking some DNS. I think this has resolved it for anyone else that runs across this issue. Make sure you go to Filters>Custom filtering rules. Add this line and apply: @@||hostname_of_server_hosting_share^$client='Unraid_IP_Address' I think this may also be the reason my My Servers and getting a Network error: Failed to Fetch.

When I attempted a XFS_repair the first time, I would get errors. I tried again this morning by turning off the docker service, starting the array in maintenance mode, and running the repair on my NVME SSD. It seems to have fixed the issue I was having. Thanks to Squid for showing me the diagnostics tool. Much appreciated!

Thank you for the tip on pulling the diagnostics. Attached below. Thanks! whitenoisemedia-diagnostics-20211223-1022.zip

I am fairly brand new to Unraid, so this is a whole different world for me. I've been having network issues that have locked up the networking on the server to the point of a hard shutdown. I think I have that resolved now. I believe the hard shutdown has corrupted my Cloudflare DDNS docker. I tried to remove the docker via the GUI to just rebuild it and it just hangs. I have attempted to run docker rm <container ID> and have returned with the following error: Error response from daemon: container 8ad0577c37bc2853059494c6ed81f8679a5525d2e586b4594c1fdee8877729fc: driver "overlay2" failed to remove root filesystem: unlinkat /var/lib/docker/overlay2/4db7785c6f2e66893874e8b43db3a47b4dbf8313b28ebcab52d6eb44d760b739/diff/etc/cont-init.d/50-ddns: structure needs cleaning I have followed the path and the specific file looks like this when I do a ls -la: /bin/ls: cannot access '50-ddns': Structure needs cleaning total 0 drwxrwxr-x 2 root root 21 Dec 22 16:18 ./ drwxrwxr-x 3 root root 25 Dec 22 16:18 ../ -????????? ? ? ? ? ? 50-ddns I am running all my dockers on a NVME SSD and when I started the array in maintenance mode and attempted a XFS_repair I received an error when I attempted it. I will have to go back and run it, again, to get the exact error. In the mean time any help would be greatly appreciated. I have been beating my head against the forums and Google for hours to no avail.

Has anyone dealt with this before? This NVME was working. I attempted a search on the forums and found nothing that would resolve this issue. I attempted to format the NVME in XFS and BTRFS. I even swapped locations with the other NVME to make sure this wasn't an issue on the motherboard. I continually get the following errors. And the NVME becomes unmountable. It is brand new and my first unRAID build. Any help would be great. I'm hoping it's not bad from the get go. It's intended use will be for VMs. I have another NVME that will run dockers and an SSD for caching. Oct 28 13:11:14 Tower kernel: blk_update_request: I/O error, dev nvme0n1, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, async page read Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 0, async page read Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 4, async page read Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 8, async page read Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 16, async page read Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 32, async page read Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 64, async page read Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 128, async page read Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 256, async page read Oct 28 13:11:14 Tower kernel: Buffer I/O error on dev nvme0n1p1, logical block 512, async page read ***Update*** Stopped the array to attempt an erase on the NVME and it has dropped off the face of the earth. This happened before when I swapped the NVMEs positions to eliminate the motherboard being the issue. If I reboot it comes back up, but run into the same issues. I'm running a Gigabyte C-246 WU4 mb, 2 m.2 NVMEs, 1 SSD, 32GB RAM, PNY P2200 GPU, Intel i7 9700K, and 4 WD Plus 14TB drives if that's any consolation. After trying multiple t/s steps, I've decided to throw in the towel and send it back. If it's going to drop regardless of which m.2 slot I stick it in, it is apparent this stick it dead.