efrishgesell

XFS

Is there any issue with downgrading the cache drive from 1TB to 500GB? Don't really use the full 1TB and I could find use for the drive elsewhere, but im cautious of screwing anything up in the process. Thanks!

Thank you for your help!

Thanks for the info. Sorry if this is a dumb question, but what do you mean by "docker image Is"? Is that a specific command? Secondly, I understand the premise of changing the version number back to the original, but do you know how to go about that? When installing previous apps, it trys to download the image based on whatever my previous settings were (as you can tell) and I don't see any obvious way to modify those before attempting the download.

In an attempt to update my NextCloud instance, I was messing with some Docker settings and one of the settings I changed made my NetxtCloud Docker Container disappear. I can now see it is an orphaned image, and I attempted to install it back through Apps -> Previous Apps, but the installation failed. The attached screenshot is what it shows when the installation fails. I've highlighted the portion that I believe is the problem, as I was changing the version number while trying to update (think I misunderstood directions, but I digress). I'm not exactly sure if I have backups of my Dockers, it's been some years since I did much with my server in that way. Does anyone know how I might be able to fix this? Mainly hoping to just get back to my out-of-date version of NextCloud so I can attempt to update again.

Thanks for the reply. If I create a new backup of the cache drive, would that not backup the corrupt file system and carry it over to the reformatted drive?

TLDR: My dockers aren't working properly due to read-only file system error. My server crashed for whatever reason, I've seen this happen rarely before, and I wasn't too concerned. I rebooted, and ever since then, I've been getting a read-only files error in all my dockers. For example, here's the specific error from Plex, "failure detected. Read/write access is required for path: ~PATH~". Here's another example from Nextcloud: "cannot create regular file '/config/nginx/site-confs/default.conf.sample': Read-only file system". Fix Common Problems identified an error with my cache drive. The error message is "Drive mounted read-only, or completely full". This obviously points to my cache drive being the problem, but doesn't really help fix it. It is not full. Fixes I've tried: - looked into my Users to make sure the relevant ones have read/write - Ran the 'Docker Safe New Perms' tool and rebooted My server has been online for almost 2 years now. Everything was working fine, and I decided to update to 6.12.4. It worked fine after this update for a week or so, I don't think this is detail it related to the problem, but I wanted to include it just in case. Diagnostics attached. claptrap-diagnostics-20240204-2004.zip

not sure off the top of my head, but it's working at the moment and getting back to bios is a bit of a hassle with my headless system. If I ever have another issue with it I'll come back to this.

An update on my situation, it really was as simple as the pc not booting from the flash drive. Who knows how the bios changed, but glad it was an easy fix. Thanks JorgeB for the advice!

I'm using a high quality Samsung drive, about 1 year old. I don't have a flash back (regret). Is there a way I can recover what's on the current flash and move it to a new one? Could it be as simple as copying and pasting to a new drive? I imagine if it's a corruption problem using the old drive wouldn't work.

I've done it this time. I rebooted my array from the unraid UI while the the array was stopping (it was stuck). When the server powered back on, unraid won't load up. It's stuck on a black screen with a blinking underscore. Is there anything I can do?