[Cannot write to cache]

Received this error. I tried a number of things including rebooting. I then uninstalled Plex docker (linuxserverio) and installed a different docker plex app but same issue and I cannot connect to the webui of plex anymore. Diagnostics attached.

unraid-diagnostics-20240331-1932.zip

[Cache unmountable: wrong or no filesystem (SOLVED)]

I tried following the steps to delete and re-create but eventually just formatted the cache drive and that worked. Marking this as solved.

[Cache unmountable: wrong or no filesystem (SOLVED)]

Thank you @JorgeB. I ran that command and then did a reboot and it seems to have cleared the prior warnings. But now am seeing the errors below again when I run FCP. This is what I saw before a couple or few times over the last few months, but a reboot would (temporarily) seem to fix it.

 

 

Looking at the Docker page I see these:

 

 

The cache has plenty of spare space:

 

When I click the Container Size button I see these, which doesn't look right to my unskilled eye:

 

unraid-diagnostics-20230530-0850.zip

[Cache unmountable: wrong or no filesystem (SOLVED)]

Fix Common Problems is reporting a "Cache unmountable: wrong or no filesystem" warning for all of my shares. Attaching diagnostics. 

I am running the latest stable build of unRAID (6.11.5). I'm not sure what do do/check. My cache drive is an NVME SSD, about 2 or 3 years old. For the past few months I've been getting errors every few weeks saying that the cache was full or read-only, but neither was the case so I'd reboot and that seemed to solve the issue. Today I did the same and now getting the below warnings.

 

Screenshots of my settings:

unraid-diagnostics-20230529-1610.zip

[Unraid OS version 6.10.0 available]

Just upgraded with no issues. Working perfectly for me. One thing I have noticed - my HD temps are much lower than before, from ~109 down to 100. I haven't changed anything other than the update.  

[[Solved] Cannot write to public unraid share]

Squid thank you! This solved it. I kept trying things on the linux client side and didn't think it would be an unRAID feature to fix these permissions. Thank you!

[[Solved] Cannot write to public unraid share]

Thanks so much Squid - I had no idea that the New Permissions was a feature! Running it now with fingers crossed. Will report back on result.

[[Solved] Cannot write to public unraid share]

Been stumped on this for quite some time - have tried everything.

Using unRAID 6.8.3 (latest version as of writing), with a share named 'media' (path /mnt/user/media)

I am currently using Ubuntu linux to try to access the share but I have tried it with many different linux distros with same failure.

The media share on unraid is set to public. I am able to access it and read using the file manager (Gnome) in Ubuntu. But when I try to write a file to it I receive this error:

------------

Error while copying "myfile.mkv".
There was an error copying the file into smb://unraid/media/TV/ShowDir.

Permission denied

-----------

Note that I *CAN* write to the root "TV" share/directory but cannot to any of the directories within it.

I've tried everything, from a secure share with a named user (same username as my linux login), as well as NFS share, etc. For simplicity sake I'm trying to stick with SMB for now and if I can get this working I may switch to NFS.

 

Bottom line: I cannot write to any of the directories on the share, even though it is set to 'public' in unRAID.

[Empty HD SMART Failure - Can I just Pull the Drive and not replace it? (SOLVED)]

Thanks - that worked. Am now building parity.

[Empty HD SMART Failure - Can I just Pull the Drive and not replace it? (SOLVED)]

Last month when I started to evaluate unRAID for use as my home server, I set it up on an older i3-3245 with 8GB of ram system with a 10TB shucked EasyStore WD drive for parity, and an 8TB shucked EasyStore WD drive as my lone data drive. Along with those, I threw a 256GB SSD drive for cache.

Everything ran great for a month so I went ahead and purchased the license and also decided to replace my existing desktop PC hardware, which allowed me to replace the older unRAID server hardware with an i7-6700 cpu and 16GB of ram.

 

While I had the case open, I happened to have an a WD Red 3TB (about 4 years old) sitting around unused so I added it to the unRAID server.

Within a few days I started getting SMART failures for that drive.

 

Fortunately, there is no data on that drive, so I just disabled it in unRAID. I don't think it's bothering anything as is now that it's disabled but it annoys me to have a red X on my dashboard : ) I was about to physically just pull it out of the case but wanted to check here first:

 

1. Is that safe to do? I do not want to replace it. Eventually I'll get another 8TB drive to add but no need now as I only have about 5GB of data on my server.

2. Attached is the diagnostics. It seems from reading the forums that sometimes these SMART errors are not to be worried about?

unraid-diagnostics-20190727-1317.zip

[Out Of Memory errors detected on your server]

unRAID Version 6.7.2 2019-06-25
 

I installed unRAID about a week ago and enjoy it but last night I received a notification via the Fix Common Problems app:

Out Of Memory errors detected on your server

Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the unRaid forums

 

Link to download diagnostics: https://my.pcloud.com/publink/show?code=XZR7i37ZYHmGLsQlHg4B9m76pd9kApSs8xX0

 

System specs: i3 3245 CPU / 8GB RAM

Disks:
256GB SSD Cache Samsung EVO

10TB WD Parity Drive

8TB WD Data Drive

 

Following apps installed and working:

Mariadb

NextCloud

PlexMediaServer

qBitorrent

 

I have one VM: OpenSuse Tumbleweed, with 3072MB allocated to it (I installed that VM last night and got this error since then, so perhaps this is the cause? I can delete it no problem as it was just to preview the distro).