Hey All,

I get the following error when checking notifications: ENOENT: no such file or directory, scandir '/tmp/notifications/unread'

I did google the error and someone mentioned try uninstalling the unraid connect plugin which I have done.

When rebooting the server everything seem fine for a 'while' and then I get the error.

Thank you for your help in advance.

homeserver-diagnostics-20260305-2036.zip

Does it happen in safe mode?

Hey JorgeB,

I've just booted the server into safe mode so will check tomorrow, it normally takes a while to go from working to not working.

Thank you

P

Hey JorgeB,

I've just checked the notifications on my server and they seem to be normal.

If a plugin is causing this issue would you be able to narrow it down from the diagnostics?

Thank you

Peter

Do any of your user scripts use Notifications?

Hey trurl,

I don't think so. Attached are my user scripts. I haven't touched them in a while.

I do pipe out notifications to Discord.

Thank you

Peter

Edited March 8Mar 8 by pete748

Hi Pete, did you manage to fix this?

2 hours ago, siiire said:

Hi Pete, did you manage to fix this?

Morning Siiire,

I did, after removing all my plugins and scrips, and still having the issue it led me to the method of transcoding I was using. As far as I understand unraid runs in ram and so do the notifications which made me think it was my ram disk. I changed the location of jellyfins transcode to use /dev/shm instead of this extra parameters in the docker container --mount type=tmpfs,destination=/tempdl,tmpfs-size=1000000

Edited May 18May 18 by pete748

23 hours ago, pete748 said:

Morning Siiire,

I did, after removing all my plugins and scrips, and still having the issue it led me to the method of transcoding I was using. As far as I understand unraid runs in ram and so do the notifications which made me think it was my ram disk. I changed the location of jellyfins transcode to use /dev/shm instead of this extra parameters in the docker container --mount type=tmpfs,destination=/tempdl,tmpfs-size=1000000

Thank you so much! You've fixed my issue. I had my transcodes simply mapped to /tmp, seems like it didn't play well with unraid notifications strored in tmp memory.

2 hours ago, siiire said:

Thank you so much! You've fixed my issue. I had my transcodes simply mapped to /tmp, seems like it didn't play well with unraid notifications strored in tmp memory.

Great news mate :) glad I could help.