MowMdown
Members
-
Joined
-
Last visited
Everything posted by MowMdown
-
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.
-
I have no idea if this is related but I have a suggestion. Bear with me for a second because it's relevent. I recently switched my gaming pc over from windows to arch linux. Everything went smooth and was working great except for one thing, shutting down my PC would go like 99% of the way off except not quite. The fans went dead, leds turned off, but the PC would not respond to button presses to start back up nor would shorting the pins on the board itself. What I discovered in my case is that I had the "Wake by PCIe" setting enabled in the BIOS to allow my pc to respond to Wake-On-Lan magic packet. Well apparently for reasons only known to the linux kernel (6.16 in my case) it does not like this setting enabled. What I noticed is that my ethernet lights would remain lit up and flashing like data was still flowing to an otherwise "powered off" system. Long story short, reset your BIOS back to factory defaults and try booting and shutting down the system.
-
glad to hear it was just bad ram
-
Specifically /mnt/user/media_share(1)/tv|movies(2)/Series|Title(3)/Seasons|movie.ext(4)/episode.ext If you want to keep whole series together, you choose a split level 2 directories as required as itimpi said. This would in essences create a media_share folder on each disk and then create a movie and tv show folder under each one, then everything below those folders would be kept on the same disk only moving to another disk when the fill allocation is met
-
My advice would be to use a reverse proxy like SWAG to handle everything.
