Merijeek

I've recently setup, and I had it working (I'm just using it for access to Unraid from remote devices) as an alternative to Tailscale. However, I did a reboot and, while everything was fully functional, after a reboot of my server I can't get anywhere. Everything seems to start fine, I can still connect my remote client to it, but from that client I can't ping or open the unraid server. Any suggestions on how to troubleshoot that?

Interesting, whenever I look, I see basically minimal RAM usage: It's basically always right around 20% when I look. Any chance we're just looking at a bad RAM stick? Can you point me to info on limiting RAM for services?

Here you are: unraid-diagnostics-20250227-0857.zip

Typically, I'll just come down in the morning to do something and find my mapping from my desktop disconnected. Then I'll see my dockers are unresponsive, etc. The system will ping, that's it. No SSH. I have to do a force shutdown with the power button to get it back to life. syslog-192.168.1.44 - Copy.log I can probably connect a monitor to it if necessary, but I'd really love to avoid that if possible. If anyone can give me an idea what I could have going on here, I'd appreciate it.

Tried running an extended SMART test and it quit at 10% with a read failure. Attaching what files there are. I've got a replacement ordered already, but it'll be like 2-3 days if I'm lucky. Any suggested steps for trying to get it back online, or is it just likely gone? unraid-smart-20240825-1527.zip

Silly question....how? If there's an obvious option, I'm not seeing it. NVM, found it. Not the most intuitive thing out there.

When you say "the pool" you're referring to my single cache drive, correct?

Diagnostics attached. Happened some point overnight. unraid-diagnostics-20240725-0919.zip

Noticed that all my dockers were throwing fits. Went in and looked, and am seeing this kind of thing in the logs: 2024-07-24 12:00:02.706862 [info] Host is running unRAID 2024-07-24 12:00:02.734310 [info] System information: Linux UnRAID 6.1.99-Unraid #1 SMP PREEMPT_DYNAMIC Tue Jul 16 10:06:03 PDT 2024 x86_64 GNU/Linux 2024-07-24 12:00:02.758340 [info] Image tags: IMAGE_RELEASE_TAG=1.40.5.8761-1-01 2024-07-24 12:00:02.790806 [warn] TRANS_DIR not defined,(via -e TRANS_DIR), defaulting to '/config/tmp' 2024-07-24 12:00:02.853498 [info] SHARED_NETWORK not defined (via -e SHARED_NETWORK), defaulting to 'no' 2024-07-24 12:00:02.885870 [info] PUID defined as '99' 2024-07-24 12:00:02.953527 [info] PGID defined as '100' 2024-07-24 12:00:03.557877 [info] UMASK defined as '000' 2024-07-24 12:00:03.588423 [info] Permissions already set for '/config' 2024-07-24 12:00:03.625671 [info] Deleting files in /tmp (non recursive)... chmod: changing permissions of '/config/supervisord.log': Read-only file system Glutun example: 2024-07-24T19:08:28Z INFO [firewall] enabled successfully 2024-07-24T19:08:29Z INFO [storage] merging by most recent 19425 hardcoded servers and 19425 servers read from /gluetun/servers.json 2024-07-24T19:08:29Z ERROR writing servers to file: open /gluetun/servers.json: read-only file system 2024-07-24T19:08:29Z INFO Shutdown successful Essentially, it looks like everything on my /mnt/user/prod (where my docker files go) has become unwriteable to my containers. I've done the docker-safe new permissions. Doesn't seem to have made a difference. So...kind of stuck as to what I should be doing next.

OK, will do. Changed from macvlan to iplan and did the update.

Ah there you go. It was from the flash drive. Here's the one from that share. syslog-192.168.1.44.log

I thought I had. There a setting I'm missing?

...no, not that. Running off the array and already crapped out again. First I lost dockers, then WebUI, then SMB, and finally, ssh. Attaching syslog and diagnostics. unraid-diagnostics-20240717-2100.zip syslog

...okay, right. Hosed docker.img and macvlan. Fixing those and rebuilding my dockers... And got a ways through re-adding them all when I got: ETA super exciting update. I moved my docker.img to my main array and was able to install everything. Problems with my cache drive?

Alright, problem the first. Noticed a docker acting funny. Went to restart it. Got a "server error". Refreshed Docker page, saw the container (Audiobookshelf) was stopped. Tried to start it and got a Server Error 403. Since a 403 is a forbidden in the world of http I went ahead and ran docker-safe permissions and...nope. So right now I've got one I just plain can't start. Then I stop a couple others and...can't start them either: syslog