Everything posted by BigNavy
-
[Plugin] Mover Tuning
Thanks @Masterwishx . Got it running on my Test server to see if I've got my settings configured like I want.
-
[Plugin] Mover Tuning
Running UnRaid 7.2.4 and I know a while back there were some issues with the Mover Tuner plugin. Is this plugin working fine on 7.1.4 now? I'd like to check it out after reading the last few pages here. Anything to be aware of or know about in advance. I understand I must disable the default mover from running while using this plugin. Thank you.
-
[Plugin] FolderView3
Yep, same here. I don't have the docker compose plugin. Just did a normal update and lost all my folders.
-
[Plugin] FolderView3
Thanks for your work on this. Do users of FolderView3 still need to manually the http://IP:Port in this version? I recall back in the day that wasn't necessary to open the WebGui but for me I must manually add the IP:Port. Just curious if I missed something and the default is working for other users. Thank you.
-
[Plugin] FolderView2
Agree. However, I wish the Unraid Team would just build this into UnRaid and release into their next update. Seems, a really useful core feature.
-
[Plugin] FolderView2
Morning and thanks for the work on this. Where's the new beta? You mention "first post" but I have 8 pages here and don't see a new beta posted. Thanks.
-
[Plugin] FolderView2
In the Dockers tab, top row, just to the left of the search icon is a green lock. Click it and on the left you will see that you can drag and reorder the folders.
-
[Plugin] FolderView2
Odd. I'm on 7.1.4 also running the beta plugin and I don't have that issue.
-
[Plugin] FolderView2
I'm using the beta as well on 7.1.3 and Autostart works for me. No issues.
-
[Plugin] FolderView2
Just wanted to provide some feedback. I have an UnRaid Backup and Test Servers. On the Backup I had a flash drive issue this morning. Server booted fine and at some point after backing up production server to it became unresponsive connecting via web browser. Connected peripherals to it and I had some sort of odd error on screen and I was booting to BIOS which indicated to me a flash drive issue of some kind. Removed the flash drive, reinserted and rebooted via the CLI. Parity check started and I cancelled it. Backup: Folderview dated 2/26 has been installed but missing the global webgui and most containers are routed through Gluetun VPN. I edited a handful of containers under advanced view and actually typed in the Backup Server IP and port for that container. Viola, I can connect to the container fine on UnRaid 7.1.2 and Folderview (original) dated 2/26/25. So in my test case just editing the container template at WebGUI and just typing in my IP:Port seems to work fine now. Test Server: Running UnRaid 7.1.2. Running Folderview2 Beta via manual install. Just editing the container template at WebGUI like above seems to work fine. Rebooted both Backup and Test and the global WebGUI icon remained. Both boxes took a handful of seconds longer to load the Dockers tab than before but I'm chalking this up to a start after I added the IP:Port to each containers WebGUI template. After they initially loaded, they're quite responsive. Just sharing this easy workaround until a more permanent Folderview2 is further tested and released.
-
[Plugin] FolderView2
So you think you can adjust folderview2 to account for the "container:GluetunVPN"? Like I said, I hadn't see anyone mention routing through a VPN container so I did. :-). Thanks for your efforts on this! Your time and expertise is appreciated. Have a great weekend and I look forward to more testing.
-
[Plugin] FolderView2
@VladoPortos I actually didn't export my previous folderview setting files. It's like 5 minutes or so to setup my containers with folderview2 so I wanted to start from scratch on your beta. However, after rebooting on 7.01, my containers in that snip, stayed that way, all good. I upgraded to 7.1.2 and the container folder stayed the same, all good. Sorry I can't be more help there.
-
[Plugin] FolderView2
@Mattaton Ah I was just reading that. Odd I didn't see those comments at first. Than you.
-
[Plugin] FolderView2
Folderview2 not working in UnRaid 7.1.2? I upgraded my test server to 7.1.2 and it went fine. Except when I try to open any container the local ip is missing from the WebUI. Example: my web browser would be :xxxx where XXXX is the port of the container. The actual container setup does show WebUI http://[IP]:[PORT:8081] but the IP isn't populating. I suspect this is related to Folderview. Known issue since the Folderview2 isn't a supported plugin or is there some tweak I have to do? Thank you.
-
[Plugin] FolderView
Thanks @oceanborn75. That raw file button did the trick.
-
[Plugin] FolderView
Thanks man, that along with getting the Github raw plugin worked.
-
[Plugin] FolderView
I'm using the scolcipitato "original version".
-
[Plugin] FolderView
I updated to UnRaid 7.01 and I can't even export my previous folders. When selecting "Export All", the browser just opens a blank page and gets stuck trying to load "something" but it NEVER completes. I'm holding in place now until next week to see how the further development of the fix comes along.
-
Unraid 7 Mover Stopped Working (No CA Mover Tuning plugin)
Similar issue, Unraid 7.0. My \<SERVER>\flash\config\shares directory *.cfg files were all named correctly. No issues. But after installing OpenFile Plugin, I saw that Fuser wasn't being shutdown. Killing the PID worked, assuming temporarily.
-
Manual Parity Check - Disparity Between Main Info & Log
I rebooted the server and the issue resolved with the previous parity history data appearing in the Parity History log. Thanks Jorge!
-
Manual Parity Check - Disparity Between Main Info & Log
Thank you Jorge. As a follow up any idea on why my Main Tab "Parity History" button/log would be totally empty? Is there a setting? I did look at the log file on the Flash Drive and there is about 7 lines of info, but nothing in the Parity History button/log. Thanks Jorge.
-
Manual Parity Check - Disparity Between Main Info & Log
New UnRaid user and I'm still sorting things out. I have two 14 TB drives as parity and two 14TB drives as data. I ran a manual parity check which started yesterday, 12/28/23. The Main tab shows the parity completed fine with zero errors. Yet the log shows errors. Which data is correct? I ran the manual parity check with the "Write corrections to parity" unchecked, as I just wanted to verify a known good parity. The times the parity check completed seem to align 3:33pm and 3:34pm for the log. Which is correct? Guessing I should run another manual parity with "Write Corrections to parity" checked? Also I noticed my Parity History Log in Main is empty. I don't know why and I can't find a setting that I may have turned off. Main Tab Showing 0 Errors. Log Notification Showing Parity Errors Thank you for reading this and providing your knowledge.