ColonelRhodes

I just did all of this, but before starting the array I see this message next to the parity disk: "All existing data on this device will be OVERWRITTEN when the array is started" Should I still continue? This is a new parity drive since originally I was swapping this one out for a new disk.

Seems like all the data is still there. Should I try to mount inside the array again?

Looks like it does mount within UD.

Also if it helps, here is the output of wipefs for that device: # wipefs /dev/sde DEVICE OFFSET TYPE UUID LABEL sde 0x200 gpt sde 0x3a3817d5e00 gpt sde 0x1fe PMBR

@JorgeB Ok, I opened the case back up and made sure all of the SATA connections are snug and fit. Booted UnRaid back up and see that Disk3 is showing "Unmountable: wrong or no file system". Attaching diagnostics here. All of my disks are formatted for btrfs if that matters. tower-diagnostics-20250717-1033.zip

tower-diagnostics-20250716-0836.zip

I had a 12 TB Parity drive start to show some errors. It was still under warranty so I powered down the array and swapped in a replacement 12 TB drive to start a parity sync. Now that the parity sync is in-progress, I'm seeing a massive amount of read errors on Disk 3 in the array (over 400k errors). I'm not sure what the best case scenario is at this point. I have the old parity drive still (have not erased data on it). Should I allow the parity sync to complete? Should I stop the sync, replace the old parity drive, then replace the failing Disk 3? For the most part, Unraid is still working fine except the syslog is getting hammered with lines like this: md: disk3 read error, sector=4472505808

I'm going to also try rolling back for my issue discussed here. Unless anyone else have seen a similar issue.

My Deluge docker no longer recognizes what I input for Download/Upload speed. I can set the max download to 100kbps and it will still download at a full 10Mbps which is maxing out the rest of my network. Any idea of what is going on here? It seems like deluge is overriding my settings with Unlimited bandwidth.

I thought it might have been, but both ports are forwarded properly and I use DuckDNS and it's reporting the proper IP

I know it's not much to go off, basically I used to be able to login from my phones web browser and download the .ovpn file to use to make the auto login profile. It still does that, but never actually connects. I'm going to try on a different iOS device. Maybe it's something due to the version I'm running.

This docker was working for me until a few days ago. I'm using the iOS OpenVPN Connect app and when I try to connect it just hangs and no logs on iOS are seen. Any suggestions?

Is there a best way or guide to set up passwordless ssh access to unraid from a Linux or Mac OS X machine? Obviously I need the settings to stay through a reboot of my unraid server.

I still can't roll back to version 12. I get the following error: Error: layers from manifest don't match image configuration Running UnRaid 6.2

Im curious, with this Docker (or any other Docker where config files are changed), how do you edit your files with a text editor? Obviously vim can be used from terminal, but I'd rather mount my appdata share and use a decent text editor to make changes to config files. What is the best way of doing this? I was getting permission errors sometimes while mounting through SMB.

It looks like the docker contains the necessary set up for Z-Wave, yes.

I've had this issue for a long time, but didn't quite understand what was going on. I would get countless number of "Received packet from invalid interface." from avahi-daemon in my syslogs. I have ruled the issue to being caused by the Home-Assistant docker. I ran an strace on the avahi-daemon and am finding some interesting things. For some reason, three items in my house are being mentioned in the results from strace with that error message. My network printer, my philips hue bridge, and my vizio soundbar with GoogleCast. This is what the errors look like. 09:25:37 recvmsg(13, {msg_name(16)={sa_family=AF_INET, sin_port=htons(5353), sin_addr=inet_addr("172.27.231.1")}, msg_iov(1)=[{"\0\0\0\0\0\1\0\1\0\0\0\0\v_googlecast\4_tcp\5local\0\0\f\0\1\300\f\0\f\0\1\0\0\0\24\0(\17Vizio Sound Bar\v_googlecast\4_tcp\5local\0", 92}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=8, ...}, {cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=2, ...}], msg_flags=0}, 0) = 92 09:25:37 sendto(3, "<28>Sep 4 09:25:37 avahi-daemon[14623]: Received packet from invalid interface.", 80, MSG_NOSIGNAL, NULL, 0) = 80 09:25:37 recvmsg(13, {msg_name(16)={sa_family=AF_INET, sin_port=htons(5353), sin_addr=inet_addr("172.27.234.1")}, msg_iov(1)=[{"\0\0\0\0\0\1\0\1\0\0\0\0\4_hap\4_tcp\5local\0\0\f\0\1\300\f\0\f\0\1\0\0\16|\0&\24Philips hue - 208A86\4_hap\4_tcp\5local\0", 83}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=8, ...}, {cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=2, ...}], msg_flags=0}, 0) = 83 09:25:37 sendto(3, "<28>Sep 4 09:25:37 avahi-daemon[14623]: Received packet from invalid interface.", 80, MSG_NOSIGNAL, NULL, 0) = 80 09:25:37 recvmsg(13, {msg_name(16)={sa_family=AF_INET, sin_port=htons(5353), sin_addr=inet_addr("172.27.224.1")}, msg_iov(1)=[{"\0\0\0\0\0\1\0\1\0\0\0\0\5_http\4_tcp\5local\0\0\f\0\1\300\f\0\f\0\1\0\0\31\10\0$\21Brother MFC-7360N\5_http\4_tcp\5local\0", 82}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=8, ...}, {cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=2, ...}], msg_flags=0}, 0) = 82 09:25:37 sendto(3, "<28>Sep 4 09:25:37 avahi-daemon[14623]: Received packet from invalid interface.", 80, MSG_NOSIGNAL, NULL, 0) = 80

Good to know that information. I will start looking into what may be causing it. The log gets reported constantly, whether or not something is streaming from Plex or not. Seems like it could be due to a bridge set up from the Unraid GUI? https://lime-technology.com/forum/index.php?topic=38684.0 Currently I have... Setup Bridge: Yes Bridge name: br0

What version of Unraid you using? I used to see this in my syslog a few releases back, I remember it being harmless and that archedraft and I both saw the same thing. I am using 6.1.9 No Windows 10 PC's in the house. No Windows machines at all actually. When I open up my syslog in the unraid gui this is pretty much the only log I see repeated to infinity....and it is definitely coming from Plex. Issue persists with v1.0

What version of Unraid you using? I used to see this in my syslog a few releases back, I remember it being harmless and that archedraft and I both saw the same thing. I am using 6.1.9 No Windows 10 PC's in the house. No Windows machines at all actually. When I open up my syslog in the unraid gui this is pretty much the only log I see repeated to infinity....and it is definitely coming from Plex.

Any reason why I am continuously getting Received packet from invalid interface. from my Plex Logs when running docker logs plex?

None of my searchers were working so I removed and re-added them. Getting this message now: Configuration failed: Mapping types: WebClientByteResult -> WebClientStringResult Jackett.Utils.Clients.WebClientByteResult -> Jackett.Utils.Clients.WebClientStringResult Destination path: WebClientStringResult Source value: Jackett.Utils.Clients.WebClientByteResult

Updated PlexPy docker to latest. Can no longer access webUI. PlexPy is still working because I am still receiving push notifications, but still no WebUI. Attempted to erase container and image, reload PlexPy (both with and without old user data), issue persists. 2016-05-02 20:41:32 - INFO :: MainThread : Starting PlexPy web server on http://0.0.0.0:8181/ This is the last line in the log file, obviously not the IP address of my server, but the docker still lists the proper IP address and where it points when selecting the WebUI.

Anybody find the cause of this issue yet?

Does UniFi-Video Controller (NVR) Docker essentially replace the need to have a physical NVR in your home? I was looking into some of their cameras, but the NVR they sell is quite expensive. It would be nice to replicate that on my UnRaid Server.