Hawat

Thank you. I changed the wireguard endpoint again from ca-ontario to ca-toronto and now it works. So frustrating. I made this change a couple of times with no success, but now....

My installation of binhex - SABnzbdVPN has been working and solid for at least a year now. But now I cannot connect to the docker container unless I disable the VPN within the container settings. I have tried to change the endpoint of the wireguard vpn to no avail either. Any suggestions? I do have this section of the log that appears to have something to do with this potentially? 2026-06-08 15:44:58,361 DEBG 'start-script' stdout output: [info] WireGuard 'peer' not found, attempting to cycle WireGuard interface... 2026-06-08 15:44:58,362 DEBG 'start-script' stdout output: [info] Attempting to bring WireGuard interface 'down'... [debug] Running WireGuard kernel implementation... 2026-06-08 15:44:58,369 DEBG 'start-script' stderr output: Warning: `/config/wireguard/wg0.conf' is world accessible 2026-06-08 15:44:58,373 DEBG 'start-script' stderr output: wg-quick: `wg0' is not a WireGuard interface 2026-06-08 15:44:58,373 DEBG 'start-script' stdout output: [warn] Failed to bring 'down' WireGuard kernel implementation 2026-06-08 15:44:58,374 DEBG 'start-script' stdout output: [info] Configuring WireGuard... 2026-06-08 15:44:58,516 DEBG 'start-script' stdout output: [info] Successfully downloaded PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' 2026-06-08 15:44:58,519 DEBG 'start-script' stdout output: [info] Successfully generated PIA token for wireguard [debug] PIA generated 'token' for wireguard is 'aEW9UxXS4TTYzGDTHITc2i66SM19Y406nmDoQbBzvSTvv7_4zPYwmmQ+Y8BryeoQsAqVlzTawjoCT09gYUGCAHtl2YStMrcYZORuxAH5gjcTs8zhOq3Jz9NaJ+g=' 2026-06-08 15:44:58,519 DEBG 'start-script' stdout output: [info] Trying to connect to the PIA WireGuard API on 'ca-ontario.privacy.network'... Any thoughts? binhex-sabnzbdvpn log.txt

In preparation from moving from reiserfs to xfs, I enacted the mover command "start mover -e disk5 |& logger &". The mover started and was going well as files were being transferred. But now, after about 12 hours, i just noticed that there is no activity. There is still 5TB to go but nothing is happening. What should I do? Should I reboot and start again? Mover button on the main tab is greyed out and says "running". Any help would be appreciated. unraid-diagnostics-20250928-1936.zip unraid-syslog-20250928-2336.zip

JorgeB - very sorry its been a couple of very busy days. But just to catch up, i did end up rebooting the server but did so before you posted about the opening a terminal window to pull the log. But since then, everything seems to be working just fine, so fixing the filesystem appears to have worked. I can put files on the array and the mover does its job with no errors. Also, I can reboot and the docker containers are right where they are supposed to be. So, thank you very much for all the help with this. I really appreciate it.

Do you think it is safe to stop the array out of maintenance mode and re-launch in normal mode? All the drives are off. The main tab shows this:

Opened in Edge as well. Same thing . I can get to every tab (Dashboard, Users, Docker, etc) but once I click on Disk 4 on the Main tab, it goes into neverland

Ok, started the fix about an hour ago and i'm in spinning wait on the refresh of the page again. It seems to be done. There is no activity on the server but I cannot get a refresh. Even if I open another tab. It will open to the Main screen, I can see all the drives, but when I click on Disk 4, I go into wait mode. Suggestions?

Its crazy it just refreshed after about 10 minutes. I got the response back which i attached to below. The key things, I think are this: 6 found corruptions can be fixed when running with --fix-fixable ########### reiserfsck finished at Tue Sep 23 07:53:45 2025 ########### bad_indirect_item: block 34244486: The item (67985 82359 0x21d58001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (122) to the block (34381981), which is in tree already bad_indirect_item: block 34244486: The item (67985 82359 0x21d58001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (286) to the block (34382145), which is in tree already bad_indirect_item: block 34244486: The item (67985 82359 0x21d58001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (476) to the block (34382335), which is in tree already bad_indirect_item: block 39911562: The item (67990 82355 0x5e66001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) has the bad pointer (542) to the block (40119350), which is in tree already vpf-10640: The on-disk and the correct bitmaps differs. So, not sure how to or where to run this --fix-fixable command. Any help here? The FAQ doesnt cover reiserfs any more. So there is no mention of what to do. reiserfsck 3.6.27.txt

Ok, so I started the filesystem check 2 hours ago. I refreshed the WEB GUI tab to see if there was any progress but page wont refresh - the notification in the tab is just spinning. Is this normal? The FAQ states: 7. Monitor progress: Monitor the progress in the output box. Use Refresh if required. So I assume this page should refresh. Am I stuck? Or wait it out? Do you have any idea on how long this should take?

No problem. Man, i thought I was just blind. Thank you so much for the help. Once this finishes (sometime overnight) I will run the file system check and will see what that turns up.

I really do appreciate the help, and I'm sorry, but I am not seeing any reference to the "Check Filesystem" on the page you linked to me. When I click the link it takes me to "Checking Array Configuration" which includes "Parity Check" and "Read Check". I did a search for "file system" and came across this: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/file-systems/#checking-a-file-system. I assume you meant this section? Also, there is no mention of my way outdated reiserfs in the article. It appears that I handle it like XFS? Checking array devicesRegularly checking your Unraid array is crucial for maintaining data integrity and identifying potential issues before they result in data loss. You can initiate a check using the Check button under Array Operations. Depending on your array's configuration, this button allows you to conduct either a parity check or a read check. For convenience, you can schedule these checks to run automatically at intervals that suit you by navigating to Settings → Scheduler. It's advisable to perform automated, non-correcting checks on a monthly or quarterly basis to ensure the ongoing health of your data. Parity & Read checksParity checks Read checks

I very sorry, but maybe I don't understand. Under the read check in the FAQ, it says to replace the disk if it shows errors. I just got in front of this and replaced the disk. No where in this section of the FAQ does it say anything about fixing the filesystem. Are you saying that when this replacement disk gets done being rebuilt I might have the same problem? Under read checks it says this: When to use a read checkConsider running a read check in the following situations: No parity devices assigned: When your array lacks parity protection. Verifying disk integrity: To confirm the integrity of each disk without making any corrections. Post-hardware issue resolution: After fixing hardware issues, to ensure all disks are healthy. What to do if errors are foundIf your read check reports errors, here are some steps to follow: Review SMART reports: Check the SMART reports for the affected disks to understand their health status. Inspect connections: Ensure that physical connections and cables are secure. Consider replacements: If a disk shows persistent errors, think about replacing it. Backup critical data: Move important data off any disks reporting errors as soon as possible to prevent data loss.

Thank you and understand. I just replaced the disk and it is in rebuild mode right now. So, can I reinstall my containers while the rebuild is going on or should I wait until it is complete?

While my array is rebuilding itself, can I reinstall a container? Or should I wait until the rebuild is complete?

So I ran a parity check a couple of days ago and had no errors reported. But are you saying that this disk 4 is throwing an error and causing my system to be in read only mode (from what I am reading in what was posted)? If so, I will replace it and let's see what happens. OK, Disk 4 replaced and now let's hope for the best during the rebuild. And, yes, I am aware of the filesystem change. I was just about to start that process when this problem developed. Hopefully I can get to that soon. .