interwebtech

Members
  • Posts

    1209
  • Joined

  • Last visited

Everything posted by interwebtech

  1. Uneventful update. Nothing to report. Thanks team!
  2. This is combined "possible bug" report and request for guidance on correct settings. Before a recent change in behavior I had Mover set to not run if a parity check (it also applied to data rebuild) was in progress. I prefer this method. The new behavior has the parity check pause then letting mover run and then resuming the parity check once mover completes. Notifications sent at each step of the process. I experienced this recently with my scheduled quarterly automatic parity check. Fast forward to now... I am at the tail end of a data rebuild (larger disks replacing old array members) and I notice the behavior is slightly different. Mover runs on schedule but data rebuild is NOT paused (at least GUI doesn't indicate it is). No notifications sent (logical since no pause occurred?). Rebuild drops to 3mbps and shows completion expected in several days. Note it was at 97.5% complete when this occurred. I let this process continue figuring maybe an hour or so to move roughly 50GBs (guessing). Several hours later and its still not done yet. This is when I noticed that the rebuild had not been paused before the mover started. At that time I manually paused it. Files were finally moving at a faster pace and should be done shortly. Side note I earlier shut off plex docker & Roon server; external NUC reads unRaid share where music files live; when I noticed they were both running file read/processing maintenance that was likely causing some contentention with the rebuild AND mover also running. Okay so bug report is regarding the different behavior between a parity check vs data rebuild and scheduled Mover runs. I would think they would be consistent (pause, send notifications, etc). Second, how to I configure this new behaviour to NOT pause parity checks or data rebuilds for Mover runs. I prefer the array operations complete as quickly as possible. I want Mover disabled when the array is doing either of these. It used to be a single checkbox that did that. Diagnostics attached. Note these were gathered while data rebuild was manually paused and mover was finishing up its run. tower-diagnostics-20230717-0750.zip PS. I have the Parity Check Tuning plug-in installed
  3. No change with new update. Still got the emails overnight. tower-diagnostics-20230611-0835.zip
  4. The false notifications/emails regarding disk usage have returned with 6.12.0-rc7. Please fix regression. Thanks. tower-diagnostics-20230607-1146.zip
  5. New Notification Features: Unexpected Behavior Love the new notification features, history and all. However I would like to request that when a browser notification is closed via the little X (like the old system) that it be considered "acknowledged" and thus marked as read. Right now, when I close one the little bell icon stays lit up. I can make it go black again by opening menu and selecting Acknowledge even though I have already interacted with the notification. Did I describe that right?
  6. FYI the issue has disappeared with 6.12.0-rc2 (and rc1). 3 or 4 days with no erroneous emails.
  7. Script completes without error. Thanks! Unraid Status: 2022-10-10 00:48 Plex Preloader has finished 0 preloaded (from Disk) / 475 skipped (already in RAM)
  8. Error moved but still persists Script location: /tmp/user.scripts/tmpScripts/Plex_Preloader/script Note that closing this window will abort the execution of this script 2022-10-07 10:16:22 Available RAM: 30G 2022-10-07 10:16:22 Amount of videos that can be preloaded: 482 (each video occupies 61M) 2022-10-07 10:16:22 /tmp/user.scripts/tmpScripts/Plex_Preloader/script: line 106: syntax error near unexpected token `head' 2022-10-07 10:16:22 /tmp/user.scripts/tmpScripts/Plex_Preloader/script: line 106: ` seconds=$(time ( head -c "$preload_head_size" "$file" >/dev/null ) 2>&1 )'
  9. Updated to 6.11.1 last night. This morning, Preloader failed with the following error: Script Starting Oct 07, 2022 07:00.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/Plex_Preloader/log.txt Script Finished Oct 07, 2022 07:00.03 Full logs for this script are available at /tmp/user.scripts/tmpScripts/Plex_Preloader/log.txt 2022-10-07 07:00:03 Available RAM: 39G 2022-10-07 07:00:03 Amount of videos that can be preloaded: 474 (each video occupies 81M) 2022-10-07 07:00:03 /tmp/user.scripts/tmpScripts/Plex_Preloader/script: line 113: syntax error near unexpected token `head' 2022-10-07 07:00:03 /tmp/user.scripts/tmpScripts/Plex_Preloader/script: line 113: ` seconds=$(time ( head -c "$preload_head_size" "$file" ) 2>&1 1>/dev/null )'
  10. FYI I have my parity check set to 90 days so its been a while since it has run. It started automatically last night at 12:20 AM as scheduled. At 12:20 AM tonight I get a notification that the parity check had been PAUSED. Dive into the setting for plugin and see that "Use increments for scheduled Parity Check" had been turned on and the settings had picked up my scheduled parity check start time setting for its "pause time" (unless 00:30 is the default). I have never turned this on so it must have reverted to this as default in an update since the last scheduled parity check was run. No harm done just startled me as I had never seen that notification before lol.
  11. If you refer to the web page login for the docker webui, try admin/admin than change it.
  12. 192.168.254.81 laptop webui link opens up (correct ip for unraid box): http://192.168.254.70:8080/
  13. using PIA/Openvpn. It appears to be running but I can't access webgui. Says it timed out. Log doesn't show any glaringly obvious errors. [redacted] supervisord.log attached. New to this docker but not new to docker. Thanks for any help getting this up and running. supervisord.log
  14. FYI - (RC3) is now showing correctly on Dashboard but still missing in System Profiler.
  15. Logged into server admin just to check on things (issue with Flash Drive being dropped recently) and I happened to notice this block of errors in the log. Is something borked and needs reinstall? Diagnostics attached. Nov 27 00:51:04 Tower webGUI: Successful login user root from 192.168.254.15 Nov 27 00:51:56 Tower nginx: 2021/11/27 00:51:56 [error] 11634#11634: *1314307 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /status?full&json HTTP/1.1", host: "localhost" Nov 27 00:51:56 Tower nginx: 2021/11/27 00:51:56 [error] 11634#11634: *1314317 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?format=plain HTTP/1.1", host: "localhost" Nov 27 00:51:56 Tower nginx: 2021/11/27 00:51:56 [error] 11634#11634: *1314326 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: localhost, request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost" Nov 27 00:51:56 Tower nginx: 2021/11/27 00:51:56 [error] 11634#11634: *1314332 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /stub_status HTTP/1.1", host: "localhost" Nov 27 00:51:57 Tower nginx: 2021/11/27 00:51:57 [error] 11634#11634: *1314343 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?auto HTTP/1.1", host: "localhost" Nov 27 00:51:57 Tower nginx: 2021/11/27 00:51:57 [error] 11634#11634: *1314352 open() "/usr/local/emhttp/stub_status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /stub_status HTTP/1.1", host: "localhost" Nov 27 00:51:57 Tower nginx: 2021/11/27 00:51:57 [error] 11634#11634: *1314359 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /status HTTP/1.1", host: "localhost" Nov 27 00:51:57 Tower nginx: 2021/11/27 00:51:57 [error] 11634#11634: *1314367 open() "/usr/local/emhttp/status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /status?full&json HTTP/1.1", host: "localhost" Nov 27 00:52:16 Tower nginx: 2021/11/27 00:52:16 [error] 11634#11634: *1314573 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /server-status?auto HTTP/1.1", host: "localhost" Nov 27 00:52:17 Tower nginx: 2021/11/27 00:52:17 [error] 11634#11634: *1314582 open() "/usr/local/emhttp/us" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, request: "GET /us HTTP/1.1", host: "localhost" Nov 27 00:52:17 Tower nginx: 2021/11/27 00:52:17 [error] 11634#11634: *1314587 open() "/usr/local/emhttp/server-status" failed (2: No such file or directory), client: 127.0.0.1, server: localhost, tower-diagnostics-20211127-0104.zip
  16. Rebooted. Everything looks to be okay (dockers, shares, etc. have reappeared). Parity check started due to unable to write to USB at shutdown.
  17. ps: email received from server when I ran the diagnostics: "Output from your job 115" mkdir: cannot create directory '/boot/logs': Input/output error sed: can't read /tower-diagnostics-20211125-0138/config/go.txt: No such file or directory Warning: copy(/boot/logs/tower-diagnostics-20211125-0138.zip): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 570
  18. I logged into admin tonight and noticed banner across the top stating "Your flash drive is corrupted or offline." Pulled it out and ran Windows 11 scan/repair. Popped it back in but error banner persists. After futzing around trying to find a backup to restore (news is not good on that, only one I found is from March this year), I pulled the flash and opened it in Windows. I can see all the files in there. I put it back in server and opened the share via network and its empty. Dockers that were already started are still running and accessible (example Plex) but the entire Docker admin is gone. What do I need to do to get this fixed? Its a fairly new drive (SanDisk 64GB Cruzer Fit USB Flash Drive). Diagnostics attached. tower-diagnostics-20211125-0138.zip
  19. Turns out its not buggy BIOS but perhaps looking in the wrong place. Pulled from another thread: root@Tower:~# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 165 model name : Intel(R) Core(TM) i9-10850K CPU @ 3.60GHz https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6100-rc2-available-r1565/?do=findComment&comment=16418
  20. It is running latest BIOS from April. Correction: F20 released 2021/05/26 Update CPU microcode version 0x34 Update Intel Management Engine Firmware 14.1.53.1617 BIOS update to be compatible with 11th Gen Intel® Core™ Processors --- mentions 11th gen but I believe mine is 10th gen reported by unRaid: Gigabyte Technology Co., Ltd. W480 VISION W , Version x.x American Megatrends Inc., Version F20 BIOS dated: Mon 19 Apr 2021 12:00:00 AM PDT