["No space left on device error"]

18 hours ago, ps0111 said:

I had this issue just now but I don't have a cache and I ran a backup of the Flash drive and then reboot the Unraid server and once it came back up I didnt have the issue and I was able to add new docker containers and start all of my containers without issue. I will keep and eye on my server to see if it pops back up.

If any one knows what the issue really is then I would like to know so that I can implement a proper fix.

I was able to reboot now and am also able to create new dockers. Strange issue.

["No space left on device error"]

I am also having the same issue. I just updated to 6.12.1.

My cache drive has plenty of room. I can't create new docker containers.

The Error I receive when installing the docker.

docker: Error response from daemon: failed to start shim: symlink /var/lib/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/188f4efc137e795b0291fc2f1f613e04f0bcb7de1933f3da68f6bf8840c45c63 /var/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/188f4efc137e795b0291fc2f1f613e04f0bcb7de1933f3da68f6bf8840c45c63/work: no space left on device: unknown.

In the unRaid logs it looks like the docker network is blocking a port for some reason.

Jun 23 10:41:57 unRaid-Plex kernel: docker0: port 6(veth9051fe0) entered blocking state
Jun 23 10:41:57 unRaid-Plex kernel: docker0: port 6(veth9051fe0) entered disabled state
Jun 23 10:41:57 unRaid-Plex kernel: device veth9051fe0 entered promiscuous mode
Jun 23 10:41:57 unRaid-Plex kernel: docker0: port 6(veth9051fe0) entered disabled state
Jun 23 10:41:57 unRaid-Plex kernel: device veth9051fe0 left promiscuous mode
Jun 23 10:41:57 unRaid-Plex kernel: docker0: port 6(veth9051fe0) entered disabled state

 

[Dockers Stopping/Crashing Issue]

On 7/19/2020 at 6:48 AM, DigitalDivide said:

Hi, problem went away after replacing my drive with a new ssd. Haven't had any problems since.

What make and model did you get? I'm currently having a bear of a time with my Samsung SSDs and even got a newer Samsung that is also giving these errors.

[[Plugin] Linuxserver.io - Unraid Nvidia]

On 6/28/2020 at 4:55 AM, blade316 said:

I installed a new GPU recently into my unraid server, and I have been getting hundreds of these errors in the system log:

 

NVRM: GPU - RmInitAdapter failed!
NVRM: GPU - rm_init_adapter failed, device minor number 0
NVRM: GPU - Failed to copy vbios to system memory

I also have installed a GPU and am receiving these errors, but my issue is only on boot for the PlexInc Docker. Typically I can manually restart the docker and it will boot fine, but it seems CA Backup/Restore might be causing some issue for me or it just makes the issue more prevalent.

[[Support] binhex - Plex Pass]

On 7/8/2020 at 1:10 AM, binhex said:

have you got any plex plugins installed?, if so if possible see if you can remove them and see if this fixes the issue, i would assume by the fact there is only 2 posts for this issue that its something specific that you and @GermGerm both have installed.

 

also can you screenshot your settings for the container, left click, edit, click on advaneced view, click on 'show more settings', screenshot.

I have no Plex plugins installed.

I've also verified /tmp 

[[Support] binhex - Plex Pass]

On 6/2/2020 at 4:29 PM, sittingmongoose said:

2020-06-02 19:23:42,027 DEBG 'plexmediaserver' stderr output:
ERROR: Could not open the input file (No such file or directory)

 

Getting this error in Plex now...Plex keeps going down every half an hour or so.

I am also getting this error. Is this a docker error or a Plex error? I'm having trouble googling info on this.