asherbig

I just deleted and recreated the docker vdisk, and this is what I see at the bottom of the page. At a glance it looks like an error, but closer inspection shows "no errors found" so maybe this is all just informational. I clicked "correct file system erorrs" and clicked scrub, which seemed to just refresh the page. What does this mean? Is that what you meant by "correcting scrub"

Oh, I forgot to mention, but I also saw a new error on my cache ssd when I checked on it today, while investigating the docker service issues. I haven't had problems with this drive in the past. When running a short SMART scan, no issues were found with the disk though.

Hello, one day after a power cycle (probably unexpected power cycle), I now get "Docker Service failed to start" when viewing the docker tab. I've tried restarting the server, but the message still persists. I've also tried increasing the vdisk size from 100GB to 150GB, thinking it might be a space issue, but this also did not start the service successfully. Attached is my diagnostics. tower-diagnostics-20250101-1823.zip

I ran the command you asked, and this is the result from my end. I am also experiencing this issue now (it started yesterday) sh-5.2# grep -P -o 'crl-verify' < /root/start.sh crl-verify crl-verify crl-verify crl-verify

I got a warning with Array has 1 disk with read errors Disk 4 - H7280A525SUN8.0T_0016034KANUV_2EKKANUV_35000cca23bc8a384 (sdg) (errors 2) This is on a drive that was acting problematic earlier with some possible formatting mismatches. But I've since reformatted the drive and rebuilt it from parity. Then I created a share to specifically target this drive (and one other), and that's about when this warning appeared. This drive has no data on it aside from some dummy files I was testing. tower-diagnostics-20240509-2241.zip

I don't, but I've switched ethernet cables with another computer that I know to be working. I'll see if the error still happens. It's hard to know if it's fixed or not because it happens so randomly

Oh, I didn't see it in the logs in the diagnostics, but in some logs for programs that were running around the time of the Internet cutting out.

This has happened again. I've attached another diagnostics report. This one happened early in the morning. Based on the logs from some services, I think this outage happened right around 2AM. (1:59:00, logs look okay, 2:00:37, logs show issues) tower-diagnostics-20240508-1506.zip

What else could the problem be? The router seems like the only other relevant part of this system, but this behavior has only ever happened to the Unraid server.

It was around 10:40pm, it should be 3 or 4 minutes before the first diagnostic

It finally happened again. There were 2 diagnostics taken, one manually by me, and another when rebooting failed and it had to force reboot. tower-diagnostics-20240429-2241.zip tower-diagnostics-20240429-2244.zip

I was doing a decent amount of network work on the day this incident happened. I restarted my router multiple times. My internet just got fixed today, so I had to restart my router to get the internet working. Then I restarted it at least twice to change some settings on the router. So many of those are legitimate. Not sure if that covers all of them or not. > I assume you only pulled the cable once? Yes, to fix the issue, I pulled the cord once, around 10:24pm, but the diagnostics was taken way before then. I ended up needing to restart the machine to get everything fully working again though. Some containers weren't able to recover, even after restarting them. The issue started suddenly around 9:20pm.

This has happened to me twice. I'll just be working on my server, and all the sudden, it goes completely dark from my network. The only way I'm able to interact with it is via command line on the machine itself. The first time, I "fixed" it by restarting my machine. The second time. I "fixed" it by unplugging and re-plugging the ethernet cord from the computer. Here's a diagnostics file I took shortly after the second time it happened. tower-diagnostics-20240411-1828.zip

Hello! First I want to say thank you for all your work on the delugevpn container, it's been a core part of my setup for almost 2 years now! Recently I've been having issues with the container though. More specifically the proxy. I'm hoping that it's just an issue with the proxy part of the container and not an issue with the vpn connection itself, but I'm not sure how to tell if that's the case. I created a github issue here describing my problems with the proxy. https://github.com/binhex/arch-delugevpn/issues/347