Tiller

My rebuild just finished successfully. While searching, I found this old thread: https://forums.unraid.net/topic/132371-unraid-crashes-during-data-rebuild/ So just to eliminate the possibility, I changed out the battery on my motherboard before trying another rebuild. Turns out it worked. Array is back up and 0 errors during the parity check. Thanks to anyone who looked through the logs to see if they could find anything.

It failed again during the rebuild. I've attached the syslog. I don't really see anything so far, so I'd appreciate if anyone could take a look and see if they get any clues as to what's going on. syslog

I did not have syslog mirroring to flash, so I just enabled that while my third attempt at a rebuild is running. If it crashes again, I'll post the syslog afterwards in here. Until then, I did pull a diagnostics file if anyone thinks it might be helpful. tower-diagnostics-20231218-1843.zip

I'm trying to replace an 8TB drive with a 16TB drive. I started the rebuild like I have done in the past and it looks like it's working normally. But after about 4 hours, the web GUI became unreachable and I couldn't ping the server from the Windows PC. I restarted the server and was able to get back to the web GUI. It had a popup saying the parity check / rebuild finished in 4 hours, but obviously it didn't and starting the array again just started another rebuild. But that failed again after about 4 hours. I can't put the original 8TB drive back in, because now it thinks the 16TB drive is the original one and says the 8TB is smaller than "the original". What can I do here? And what could be causing the crash after 4 hours? The drive I'm adding is a WD Red Pro and I checked and erased it using Data Lifeguard Diagnostic for Windows before trying to add the first time. Let me know if you need any more information from me. Thanks in advance for the help.

I'm having an issue with a specific tracker. It has the status of "Not working" and the message says "Host not found (non-authoritative), try again later". The tracker in question is PrivateHD and the site doesn't seem to be having any issues. Yesterday I rolled back to an old version and was able to add a torrent from PrivateHD and it started without issue. Today, though, I added another torrent, still on the older version, and it's having the same issue. I tried updating again to the newest version, but it didn't change anything either. Any ideas on what the issue could be or why rolling back only temporarily worked?

I just performed an update and afterwards I am only seeing this screen. I believe this happened back in November after an update as well. Is there a reason this is happening multiple times after performing an update for this application? I did some searching and saw sometimes this happens if the database is corrupted, so I started following one of Spaceinvader One's videos on fixing a corrupt Plex DB. But when I got to the step of performing a "PRAGMA integrity_check", it came back as "ok" without any errors. Do I just need to wait for the migration to finish? I still don't understand why this has happened multiple times, though, and only immediately after an update. So any guidance or explanation would be appreciated. Thanks in advance.

I did already have VPN enabled in the settings. However, I was able to fix it thanks to your image. When I changed the network type to custom, for the subnet out to the right it had "192.168.4.0/22". So I changed it back to Bridge and put that value in the LAN_NETWORK field and now it works. So thanks for the help!

I have attached the log file to see if anyone can see something I don't. supervisord.log

The only new error I saw was for trying to add the route with the new IP. I changed the LAN_NETWORK setting to include both with a comma between them -- "192.168.1.0/24,192.168.4.0/38". The 1.0/24 address gets added as a route without issue, but the error for the 4.0/38 is obviously still there. And with both of them in the LAN_NETWORK setting, or either one individually, it doesn't matter. I still can't access the web UI. I don't see any other errors that would explain it. There are some other errors/warnings, but they have seemingly always existed as they also show up in older logs when it was previously working.

I set up a new router and now I can't access the web UI for this Docker. Other containers still work -- Plex, Sonarr, and Radarr. But SABnzbd and qBittorrent are both broken at the moment. While watching Docker logs, it looks like it goes through the whole process and says listening on port 8080 at the end. But trying to connect to the web UI just times out and never loads. The only thing I have tried changing is the LAN_NETWORK setting in the config. My network ID changed from 192.168.1 to 192.168.4, so I changed LAN_NETWORK to 192.168.4.0/38 from 192.168.1.0/24. Is there something else I need to look at or change?

I had the same issue. I updated and then the web UI would no longer load. Tried to restart the container a couple times but nothing changed. I rolled back to the previous version and it loads just fine, so I'm not sure what the issue was.

I hooked up a keyboard and monitor while the server was still on, but the display said there was no signal. So I couldn't even attempt to enter any commands. One second push of the power button didn't do anything, so I held to force the shutdown. I turned the server back on. So far, it seems like it has booted up normally. Like you said, it was an unclean shutdown so another parity check will be required when I start the array. Which I won't do yet until someone can look over the attached diagnostics and I can see if I will just have the same problem again. When I booted up, there was a notification saying the parity check ended at around 4 hours with 0 errors. But obviously it didn't actually finish in that short of a time span and when it says it ended is when I lost connection with the server last night. Like I said, I've attached the diagnostics. I also went ahead and made a new backup of the flash drive with the hope that the config directory is good at least. We'll see. tower-diagnostics-20211012-1956.zip

I was out of town over the weekend and at some point a power outage happened at the house. It must have lasted long enough that my battery backup also went down because I came home to the Main Menu screen in the Web UI saying there had been an unclean shutdown and when I started the array then a parity check would be performed. Okay, fine, no problem. About four or five hours into the parity check, I lost connection to the server. I can't view any share folders through Windows trying to view a network location. I can't connect to the Web UI. Pinging tells me the destination host is unreachable. I left it alone overnight in the hopes that somehow the parity check was still going on and maybe it would allow me to connect when it finished. That was over 24 hours ago, and for my system the check usually takes about 18 hours. Still can't connect and pinging gives me nothing even though the server is still powered on. After some Google searches, I am worried maybe my flash drive is failing or has failed but I'm not sure how to check it. Should I just press the power button on my server to force a shutdown and then try plugging the flash drive into my Windows PC? Or am I way off base and is there something else I should try or check first? Any help or guidance would be appreciated. Thanks in advance.

I've been having some weird issues with QBittorrent. Over the past month or so, when I add a new torrent it just goes straight to the Errored state. If I delete the perms file and restart the Docker, then it works fine for a day or so. Well now today the Docker won't restart. I keep getting this message in the logs: 2021-05-19 17:07:03,545 DEBG 'start-script' stdout output: [warn] Unable to successfully download PIA json to generate token from URL 'https://privateinternetaccess.com/gtoken/generateToken' [info] 12 retries left [info] Retrying in 10 secs... I have tried changing the OpenVPN endpoint file to like five or six different countries, something that has sometimes helped in the past, but it's still not working. Anyone have any ideas on what could be the issue?

Thanks for the quick reply. You helped me solve it -- I had to add the leading "/" and change "Downloads" to "data".