interwebtech

SABnzbd reports 0 B Free Space (Temp Folder) when I try and download nzb files. That led to opening the syslog and its completely full of repeating errors of not finding any of the folders emhttpd: error: get_fs_sizes, 7834: No such file or directory (2): statfs: /mnt/user/SABNZB_downloads Likely related to the data rebuild that is running. I need some help. tower-diagnostics-20241208-0012.zip

Just noticed the Format option is showing for Disk 1. Should I stop and do that or will the rebuild take care of it?

New drives came today. Trying to replace bad drive disk 1 (removed couple days ago) and replace/upgrade good drive disk 8. Dual parity so it should be okay, right? I am getting an error on drive 1 "Unmountable: wrong or no file system" but it appears to be participating in the data rebuild (drive writes incrementing). Drive 8 is also participating but is showing the weird capacity values like drive 1 did before (see previous post) Size: 2.4TB, Used: 18.4EB, Free 9.53TB (this looks right, it was a 12 now being replaced with a 20). I just started the data rebuild. What's going on here? (ps pic is just first 9 disks) tower-diagnostics-20241207-1829.zip

The answer to both questions was YES. Started array and cache pool was restored. All dockers appear to be present.

Need some reassurance I'm on the right path to restore my cache pool. I have setup (not committed yet) the pool based on the device IDs unRaid had assigned to the drives (see pic). The cache was formatted as BTRFS. Do I need to specify that in the cache Settings or will "auto" pick it up automatically? (see other pic)

UPDATE: I'm returning the disk with odd behavior. So basically I need help getting my Cache Pool back online. (I have 2 more disks coming Saturday so disk 1 will be replaced soon)

EDIT: ignore the stuff about disk 1 weirdness (its being replaced). I do still need help with my cache Pool. How can I recover it? I just spent the last 2 days replacing 2 disks (older wd 5400 shucked drives with wd red pro 20TB) in my array. I have dual parity so I was doing both at the same time. Disk 1 (the problem child) and disk 18 (seems to be okay). So the rebuild completed with no errors today. Last night I noticed something odd on the Main page where disk 1 was showing odd capacity stats (far right column). It claimed to be 2.5TB with 18PB free space. Since it was otherwise doing okay I figured it was cosmetic issue. Once the rebuild completed the capacity oddness remained so I figured I'd try a reboot. That's where it went sideways. On reboot it hung trying to mount disk 1 (problem child). I let it go for a far amount of time but it was obvious a hang. Both parity and disk 1 LED where lit solid no blinking. I forced a reboot (reset button) and it got stuck at the same place. I got the idea to zap the volume on disk 1 and see if it would rebuild properly a second time. I deleted the volume using disk management on my windows laptop w/external drive via USB. Added the drive back to server and started up but didn't recognize that the disk had changed and hung again. I shut down and pulled the drive, restarted to get to a "missing disk" state. That worked BUT now it would not let me start the array because my cache pool config disappeared (error: Wrong Pool State cache - too many wrong or missing devices). I have 4x 1TB nvme that was confg'd as 2TB RAID1. I don't have any idea which order thay were in so I'm reluctant to start added a new pool. Not sure what to do at this point. I'm ready to try and exchange disk one for a new one if that would help but I really need my plex server back up in the meantime. Not sure if diags will tell the whole story as there were multiple reboots during this process. tower-diagnostics-20241205-1416.zip

Its showing now with no changes made. Must have been some server mischief.

The title sez it all.

What does "Enable NVME power monitoring" do? Found in global disk settings. Toggling Help doesn't provide any context. Google fu fails me.

Welcome aboard!

Uneventful update. Nothing to report. Thanks team!

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

Grats!

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)

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 )'

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 )'

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.

If you refer to the web page login for the docker webui, try admin/admin than change it.

Excellent! I have UI now. Thanks.

192.168.254.81 laptop webui link opens up (correct ip for unraid box): http://192.168.254.70:8080/

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

FYI - (RC3) is now showing correctly on Dashboard but still missing in System Profiler.