14 minutes ago, toughiv said:

Surely this is an UnRaid issue?

If it is, then it's specific to your setup, so very difficult for Unraid to fix.

 

So it restarts with no containers or VM's while in safe mode?

1 hour ago, JonathanM said:

If it is, then it's specific to your setup, so very difficult for Unraid to fix.

 

So it restarts with no containers or VM's while in safe mode?

 

- Running both [Safe Mode] & [GUI w/o Array] didn't cause any crashes.

- It seems turning on the array is causing crashes...and the crashes happen more frequently if i run all my docker containers.

 

I do not run VMs at this time, only docker.  It is something to do with docker i think, given it only crashes when i turn the array on.

 

However, i did the change to IPVLan rather than MacVLan. My setup doesn't seem too unique, i have one ethernet port, that feeds into my pfSense router. The pfSense has vlan tags of: 0, 1 & 2. The networks on UnRaid match those tags and get assigned ip addresses from the router, not frmo the Docker network. That's it.

 

Im currently running a grand total of 2 containers, one being Plex.

 

 

 

To confirm, booting in safe mode and starting the array, while leaving the docker and VM still reboots?

On 8/24/2024 at 10:03 AM, JorgeB said:

To confirm, booting in safe mode and starting the array, while leaving the docker and VM still reboots?

Sorry for late reply - i've been between houses, but should be settled now.

 

Do you mean go into safe mode, turn on the array and do not start docker or vms ?

Yep

On 9/16/2024 at 2:26 PM, JorgeB said:

Yep

So I have had it in Safe Mode (GUI) for one week with Docker turned on (not running VMs) and no crashes.

 

Im guessing that means it is a plugin or something that is causing the crash? I am running minimal plugins. Literally the NVidia, Community and Common Problems only i think...

2 hours ago, toughiv said:

Im guessing that means it is a plugin or something that is causing the crash?

Possibly.

On 10/20/2024 at 12:55 AM, JorgeB said:

Possibly.

so almost 2 weeks - no crashes.

Thankfully the NVIDIA drivers still can be passed through to my containers.

 

What i have ended up doing is no using templates for anything, i.e. because im in Safe Mode - Community Apps arent available to me. 

 

So I have had to:

 

curl -L "https://github.com/docker/compose/releases/download/v2.29.7/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose

sudo chmod +x /usr/local/bin/docker-compose

 

then maintain my own compose files. 

 

definitely could be worse!

Edited October 25, 20241 yr by toughiv

@JorgeB

Maybe i spoke to soon

It crashed for the first time last night.

The only operation that could have been occurring at the time would have been a move operation. Perhaps I should use hardlink instead. However, does that mean one of the disks is likely bad? And if so - do you have any tips on how I might diagnose which one? They all have a smart status of perfect/fine.

You can leave the persistent syslog running to see if it catches something.

@JorgeB - what i have done is turn off tranmission for the last few days and no crashes. I think there is something there about all the file operations of moving to the "completed" folder and then that file being moved again by another docker container. 

 

Have you heard of that as an issue? I.e. i can imagine transmission not releasing the lock on the file, then the other container causing issue on the array?

7 minutes ago, toughiv said:

I.e. i can imagine transmission not releasing the lock on the file, then the other container causing issue on the array?

I could see that causing an issue with the user shares, for example, but not crashing or restarting a server.