HALPtech

Members
  • Posts

    49
  • Joined

Everything posted by HALPtech

  1. For anyone who stumbles upon this topic - changing the ethernet cable (assuming it was faulty) and disabling network bonding (I only have one interface) seems to have done the trick. I'll update if I notice it happening again.
  2. I've been experiencing some issues with my Unraid rig losing its network connection every so often. It happens briefly, and when it does, I usually can't connect to the web interface and any streaming freezes until it comes back up. Note: I've noticed this only happens when an application on it is being actively used. It doesn't happen overnight when everything is quiet. Here are the relevant logs (with diagnostics attached) - I'm not sure what promiscuous mode is, but I can see that something is happening to my network device (eth0) during these times: Jul 22 08:00:29 unraid kernel: device eth0 left promiscuous mode Jul 22 08:00:29 unraid kernel: bond0: now running without any active interface! Jul 22 08:00:29 unraid kernel: br0: port 1(bond0) entered disabled state Jul 22 08:00:32 unraid ntpd[1770]: Deleting interface #228 br0, 192.168.121.12#123, interface stats: received=9, sent=9, dropped=0, active_time=56 secs Jul 22 08:00:32 unraid ntpd[1770]: 216.239.35.0 local addr 192.168.121.12 -> <null> Jul 22 08:00:32 unraid ntpd[1770]: 216.239.35.4 local addr 192.168.121.12 -> <null> Jul 22 08:00:32 unraid ntpd[1770]: 216.239.35.8 local addr 192.168.121.12 -> <null> Jul 22 08:00:32 unraid ntpd[1770]: 216.239.35.12 local addr 192.168.121.12 -> <null> Jul 22 08:00:44 unraid kernel: r8169 0000:04:00.0 eth0: Link is Up - 100Mbps/Full - flow control rx/tx Jul 22 08:00:44 unraid kernel: bond0: (slave eth0): link status definitely up, 100 Mbps full duplex Jul 22 08:00:44 unraid kernel: bond0: (slave eth0): making interface the new active one Jul 22 08:00:44 unraid kernel: device eth0 entered promiscuous mode Jul 22 08:00:44 unraid kernel: bond0: active interface up! Jul 22 08:00:44 unraid kernel: br0: port 1(bond0) entered blocking state Jul 22 08:00:44 unraid kernel: br0: port 1(bond0) entered forwarding state Jul 22 08:00:46 unraid ntpd[1770]: Listen normally on 229 br0 192.168.121.12:123 Jul 22 08:00:46 unraid ntpd[1770]: new interface(s) found: waking up resolver Jul 22 08:07:04 unraid emhttpd: read SMART /dev/sdf Jul 22 08:07:14 unraid emhttpd: read SMART /dev/sdd Jul 22 08:07:14 unraid emhttpd: read SMART /dev/sdc Jul 22 08:13:22 unraid kernel: r8169 0000:04:00.0 eth0: Link is Down Jul 22 08:13:22 unraid kernel: bond0: (slave eth0): link status definitely down, disabling slave Jul 22 08:13:22 unraid kernel: device eth0 left promiscuous mode Jul 22 08:13:22 unraid kernel: bond0: now running without any active interface! Jul 22 08:13:22 unraid kernel: br0: port 1(bond0) entered disabled state Jul 22 08:13:25 unraid ntpd[1770]: Deleting interface #229 br0, 192.168.121.12#123, interface stats: received=28, sent=28, dropped=0, active_time=759 secs Jul 22 08:13:25 unraid ntpd[1770]: 216.239.35.0 local addr 192.168.121.12 -> <null> Jul 22 08:13:25 unraid ntpd[1770]: 216.239.35.4 local addr 192.168.121.12 -> <null> Jul 22 08:13:25 unraid ntpd[1770]: 216.239.35.8 local addr 192.168.121.12 -> <null> Jul 22 08:13:25 unraid ntpd[1770]: 216.239.35.12 local addr 192.168.121.12 -> <null> Jul 22 08:13:36 unraid kernel: r8169 0000:04:00.0 eth0: Link is Up - 100Mbps/Full - flow control rx/tx Jul 22 08:13:37 unraid kernel: bond0: (slave eth0): link status definitely up, 100 Mbps full duplex Jul 22 08:13:37 unraid kernel: bond0: (slave eth0): making interface the new active one Jul 22 08:13:37 unraid kernel: device eth0 entered promiscuous mode Jul 22 08:13:37 unraid kernel: bond0: active interface up! Jul 22 08:13:37 unraid kernel: br0: port 1(bond0) entered blocking state Jul 22 08:13:37 unraid kernel: br0: port 1(bond0) entered forwarding state Jul 22 08:13:38 unraid ntpd[1770]: Listen normally on 230 br0 192.168.121.12:123 Jul 22 08:13:38 unraid ntpd[1770]: new interface(s) found: waking up resolver unraid-diagnostics-20210722-0818.zip
  3. I've been having an issue where I receive the attached error message after logging into the web UI. The only fix is to restart, as nothing is accessible beyond that point. Any idea what might be causing this? (Diagnostics included as well.) es-unraid-diagnostics-20210115-0824.zip
  4. Looks like I'm having the exact same issue with Radarr that some other folks were having, but I don't see a resolution for it in this thread. I have reverse proxies set up for Sonarr and Radarr in NGINX Proxy Manager almost identically (both with a scheme of 'http'), with the only difference between their port. Both work great. I began following this guide (which is fantastic, by the way - thank you) to set up Authelia and was successfully able to route Sonarr through Authelia on the first try. However, when I perform the exact same steps with Radarr and Portainer (add the rules to the Authelia conf file, add Protected Endpoint conf block in the advanced tab for each proxy host in NPM), Authelia redirects the subdomain to http://radarr.subdomain.com instead of https://radarr.subdomain.com and throws an error. (I can access it just fine if I manually add an 's' to 'http' myself.) Note that I've used the exact same Protected Endpoint conf as Sonarr, replacing only the container name for Radarr/Portainer. I have no idea why Sonarr is the only one being automatically redirect to https right off the bat. Edit: It looks like this is an NPM issue - I was able to resolve it using the recommended fix per this support thread. Essentially, replace this line in OP's original config: auth_request_set $target_url $scheme://$http_host$request_uri; with this: auth_request_set $target_url https://$http_host$request_uri;
  5. Wow, uploading the files made me realize I was making a terrible mistake - the tunnel with the most recent updated settings was set to inactive. It now works once activated! Sorry for the false alarm. Edit: I can now establish a handshake, but I still can't connect to anything within the network. Any thoughts? Screenshots attached.
  6. I recently installed the Wireguard plugin and used both instructional guides I found on the Unraid forums as well as the official Unraid instructions to install it, but I can't get any peers to work (I've tried remote access to LAN and remote tunneled access). I've followed the instructions exactly as written, and also performed the following steps: Reset my router's IP address distribution/subnet/addresses to be 192.168.177.0, etc. instead of 192.168.1.0, etc. (This was a major pain in the ass but I'm hoping it will have been worth it moving forward.) Toggled 'Local server uses NAT' to 'Yes' and 'No' (I have no idea what this means in regard to my server) Deleted 'network.cfg' from BOOT and rebooted the server Added a Peer DNS of 8.8.8.8 Confirmed port forwarding is directing UDP at Wireguard's port to my server's internal IP address I'm using the ISP router that comes along with my Verizon Fios subscription - not pfSense or anything like that. Every time I made a change to the network or peer, I regenerated the peer profile and re-scanned it into my phone's Wireguard application. Despite all of this, I still can't get it working. I try to ping it from the Wireguard settings and I get no reply - it isn't even making a handshake. Any thoughts? I'm tearing my hair out here.
  7. Can you advise what running a scrub is or how to do it? I'm not sure what that means and the linked post doesn't go into details into what running a scrub entails other than correcting issues.
  8. Thanks for the response. I was already using that script, which is what notified me there were errors. I may have accidentally unplugged one of the cache SSDs while the system was still on (long story), so I reset the stats per the post you linked to and will wait to see if any further errors occur (unless there's something I manually need to run to fix it after having run into an issue like that).
  9. I bought a new HDD and had to reconfigure some things in my case last night to add it and tidy things up, and after rebooting, my two-SSD BTRFS cache started throwing errors (although both were existing and working fine before). I unplugged and replugged them back in to make sure everything was seated correctly and they were. Any thoughts on what might be happening here? emrys-diagnostics-20200828-0725.zip
  10. Unfortunately not. They remove anything in the folder, regardless of what the metadata settings are set to. You can preserve things on import (from the folder being downloaded/imported), but any existing files are trashed.
  11. I run Sonarr and Radarr, which automatically remove any existing files from movie folders when they upgrade a movie folder. I'd like to lock them out (via file permissions) from being able to edit jpg/png/nfo files. Is this possible in Unraid?
  12. How can I update to the latest stable version of PMS 1.20 using this container? I don't want to be on the beta release because I don't want to test new features or bugs, but I'd like access to the new Plex Movie agent and installing this container from community apps only pulls down v1.19.
  13. I'm currently using the binhex-Plex Docker container instead of this one (I do have the lifetime Plex Pass) and am interested in the new Plex movie scanner introduced in v1.20. The regular binhex-Plex container is still on 1.19 so I'm contemplating upgrading to binhex-plexpass so I can take advantage of the new scanner. Is this version actually prone to experiencing bugs and issues that might pop up, given it's on the faster release track? And would I be able to maintain all of my settings if I backed up the Plex Media Server folder from the regular version and restored it after installing the PlexPass container?
  14. Unfortunately the rogue folder is empty, so that isn't much help.
  15. Any idea where I can start digging to find out why this is happening? I checked the Docker configs and nothing there references a 'Media' folder. And I checked user scripts as well - nothing there.
  16. Edit: All of my disks show the 'media' folder, but only disk 3 shows the 'Media' folder. Can I delete it? I'm not sure if that will make a difference considering 'media' isn't listed under Shares in the web UI - only 'Media' is. Also, attached are my diagnostics. emrys-diagnostics-20200813-1032.zip
  17. Do you have any idea why they wouldn't both be visible under the 'Shares' tab in the Unraid web UI then?
  18. I store all of my movie and TV show files in a share called 'media'. I've been working on updating all of the media info over the last couple of days (mostly adding NFO files), and this morning a duplicate share appeared called 'Media'. It shows as empty, and when I navigate into it and then back out in Windows File Explorer, my 'media' share is highlighted, indicating that the two are linked somehow. After 10-15 minutes of having my server booted, everything disappears from my 'media' share and only comes back after a reboot. I checked all Docker configs and nothing is referencing a capital M 'Media' share - only 'media'. In the 'Shares' tab only 'Media' shows - I can no longer see my 'media' share with the actual files. I'm really nervous that I'm going to somehow lose the share and the data on it and am hoping someone can help me resolve the issue. I'm thinking the worst case scenario is me just moving the files to another share and then deleting both media shares and recreating them?
  19. I have two identical directories in Unraid (one to store movie info - NFO files, posters, etc., and one to store actual movies). I'm trying to find a script that will automate copying all the metadata files in the first directory into the directory with the actual media on a daily basis. When I try to run this: #!/bin/bash bash cp -R mnt/user/metadates/movies/. mnt/user/movies/ I get this error: /bin/cp: /bin/cp: cannot execute binary file Does anyone have any thoughts on how I can accomplish this with User Scripts?
  20. I'm having the same issue. I just rebooted and despite seeing my folders in the terminal, can't view them anywhere else (SMB, Krusader, etc.). This is frustrating.
  21. Hey, sorry I'm seeing this so late - were you able to resolve this?
  22. Here you go. Docker actually crashed on restart, so this is probably a good time to post the diagnostics. emrys-diagnostics-20200701-0832.zip
  23. I'm getting the impression it's related to Docker, but once a day (or if I'm lucky, every two days) my Docker servers will crash and stop unexpectedly until I restart Unraid. I ran the MemTest and it did not come up with anything. Is there somewhere else I shoud be looking? The first log shows what I saw this morning when I logged in and noticed that all of my Docker containers had been stopped. There weren't any errors in the log, but I could see that the Docker services had been stopped. The second log with the errors shows what happens when I tried to restart the containers. Edit: I've noticed that it sometimes acts up when I manually trigger parity checks or the mover.
  24. Hi. I'm having trouble getting rclone to actually mount using spaceinvaderone's guide. When I view my Dropbox mount from the terminal in rclone (reclone lsd Dropbox:) I can see all of the folders in the root of my Dropbox. However, when I try to mount it using the following script, nothing appears in the /mnt/disks/Dropbox folder: mkdir -p /mnt/disks/Dropbox rclone mount --max-read-ahead 1024k --allow-other Dropbox: /mnt/disks/Dropbox & Why can the terminal see my Dropbox folders and files but not Krusader when I run the mount script?