MowMdown
Members
-
Joined
-
Last visited
Everything posted by MowMdown
-
/mnt/user0 is almost the same thing as /mnt/user with the exception that it does not contain any pooled devices so it’s only the array devices. You can just ignore /mnt/user0, however if you delete files from /mnt/user0 they will be deleted from the system. They are not duplicate files. If anything shows up under /mnt/user0 it’s been moved to your array disks (disk1, disk2, etc)
-
did you put your plex container on the same custom docker network as your reverse proxy?
-
yes your sata power cables and data cables should be checked/replaced. disks are assumed to be dropping from the system due to potentially bad cables.
-
I do the same method for plex. I have it streamed through SWAG (linuxserver nginx reverse proxy container) and I don't expose any ports except for 443. I've even disabled the remote access within plex's settings. I then had to add both http://plex.domain.com,https://plex.domain.com to the discovery URLs for plex to recognize and serve over the internet. I have not noticed any issues like you're describing. Who is your domain and DNS host, I use cloudflare but I do not proxy it through their dns proxy. I also use adguard on my local network to do a DNS re-write to forward any internal dns requests that hit my domain to my local IP so the lookups don't have to go out to the internet. Here is the plex subdomain config I use
-
It was working and connected to my router, I did a reboot of my router due to a firmware update and that's when I noticed the wifi was giving me a red antenna instead of white or blue and the logs were telling me wifi failed to start. Additially if I disable it in the settings and re-enable it, i get the same error message in the logs and DNS resolution stops working until I make a change in the ethernet settings and save it, then DNS comes back. wifi worked, not sure if the kernel update did something but once my pre-clear is done ill reboot unraid and check wifi again. Oct 24 23:56:00 PlexRAID rc.wireless: Starting WiFi network... Oct 24 23:56:00 PlexRAID rc.wireless: ip link set wlan0 up Oct 24 23:56:00 PlexRAID rc.wireless: ip link set shim-wlan0 up Oct 24 23:56:00 PlexRAID rc.wireless: iw reg set US Oct 24 23:56:00 PlexRAID rc.wireless: WiFi network... Failed. Oct 24 23:56:19 PlexRAID rc.wireless: Restarting WiFi network... Oct 24 23:56:19 PlexRAID rc.wireless: Stopping WiFi network... Oct 24 23:56:19 PlexRAID rc.wireless: ip addr flush dev wlan0 Oct 24 23:56:19 PlexRAID rc.wireless: pkill --ns 3107873 wpa_supplicant Oct 24 23:56:19 PlexRAID rc.wireless: iw dev wlan0 disconnect Oct 24 23:56:19 PlexRAID rc.wireless: rm -f /var/local/emhttp/wireless.ini Oct 24 23:56:19 PlexRAID rc.wireless: WiFi network... Stopped. Oct 24 23:56:20 PlexRAID rc.wireless: Starting WiFi network... Oct 24 23:56:20 PlexRAID rc.wireless: ip link set wlan0 up Oct 24 23:56:20 PlexRAID rc.wireless: ip link set shim-wlan0 up Oct 24 23:56:20 PlexRAID rc.wireless: iw reg set US Oct 24 23:56:20 PlexRAID rc.wireless: WiFi network... Failed. plexraid-diagnostics-20251025-0937.zip
-
/var/log/phplog was just filling up with errors that called out plexstream specifically. I wish I kept the log file bit it was errors like when you have incorreect or missing arguments from code calls. like throwing exceptions. My guess is the php version was updated and now doesn't recognize something your plugin is trying to do. The plugin didnt stop working or anything just filled my phplog file up.
-
Plugin and Unraid 7.2.0RC2 are not playing nice together. Filled up phplog to 90Mb almost filling up my /var/log entirely.
-
Enable mover logging under Settings > Scheduler > Mover Logging Enabled Run mover and post new diagnostics
-
Have you tried to manually create the USB? The Usb creator tool isn't the best and sometimes has "false blacklists"
-
You're confusing your disk pool "downloads" with your share you created "Downloads" These two things are not related other than in name only.
-
Either something is not powered or you over-provisioned your PCIe lanes on the new motherboard and are using a deactivated PCIe slot which would result in your disks not appearing. Or the BIOS needs adjustment to permit the hardware.
-
Those are showing under the "Historical" section, disks it once detected as unassigned (not currently unassigned). You need to check the system BIOS to see if the drives can been seen there.
-
No need to move any data. It should be a non-destructive process.
-
what's weird is the most recent log isn't showing issues with the cache drive /dev/nvme0n1 but the other previous logs do. you probably want to run a smart test on the cache drive. Im not sure if the drive is failing or just needs to be re-formatted. I would prepare for the worst and backup the data in case the drive is dying. Recreating the docker.img is simple and can be done at any time by stopping docker service, deleting the docker.img file and starting the service back up. It will auto generate a new docker.img. The exception is if you use the Nextcloud AIO container you will lose the data in this specific container. Otherwise you will just need to reinstall the conatiner images by going to Community Apps and clicking on "previous apps" and then checking the box for each container you had installed it will go through and install them for you and get you back up and running. You shouldn't need to reconfigure any containers just any custom docker networks you may have created.
-
Your cache drive is having read/write errors and your docker.img is corrupted.
-
Your docker.img is likely corrupted not the cache pool. Please post diagnostics
-
No sure what the deal is with the call-traces but your logs are spammed full of ssh connections....
-
Settings > Scheduler > Parity Check
-
In addition to what Frank1940 said, check the motherboard manufacture's QVL to make sure the RAM you are using is on that list of memory. I personally do not experience issues deviating from the QVL but you mileage may vary.
-
Are the parity checks happening after a reboot? Are they just randomly happening? If these are happening after you are rebooting your server it's not shutting down cleanly and something is preventing a proper shutdown. If they're just randomly happening your server may be rebooting itself which is indicative of faulty hardware. Next time it happens and it wasn't after you manually cause a reboot, check the server uptime in the upper right corner of the webgui. You need to enable the remote syslog server and also please post your diagnostics zip (still need this)
-
Nextcloud + Immich + iMazing (paid software) and you'd have to run in a VM Best you're gonna get outside apples walled garden
-
Parity Check Tuning plugin is likely the culprit, you can try removing that plugin. Parity checks happen when there is an unclean shutdown. Have you had any issues with shutting down or sudden restarts? Also please attach your diagnostics.zip
-
I would double check the SATA cables and/or replace. Might have bumped something loose when cleaning. I didn't see any corruption errors. Also your docker.img needs to be corrected or deleted and recreated.
-
You can also run a 24 hour minimum memtest from the boot menu to see if you have bad ram if you want to try and test all of it at once.
-
Use the Custom Tab plugin and you can pin any unraid page to the header bar.
