Froberg

Fair warning for anyone who manages to read this before updating. My transmission update today resulted in the nulling of all download locations, immediately triggering a few TB's of downloads before I caught it. Not sure what went wrong, all my settings seem to be there, but the "move to x folder" history was lost and everything was reset to the standard downloads folder.

Agreed.. been unsuccesful thus far in reviving it.. 502 Bad Gateway. The DB is up, as I could upgrade it through console, which I assume required DB connectivity.. so I'm a bit stumped atm.

"Fix" worked for me, at least I can access the db through phpmyadmin again. Nextcloud is still b0rked though. Have to get some rest, but specifically the fix that worked in my case: And then switching to :latest.

Never happened yet. Even replaced my dual 250G drives with dual 1TB drives just to eliminate that the drives themselves were faulty. Never at risk of running out of space on cache now, not even with large data ingress.

Hi all All issues I've had running UnRaid, without fail, for the last few years, has been down to the RAID1 cache in my system. I am, once again, moving everything off the cache, suffering the Docker downtime because of it, and reformatting. It's taken all day so far. (Plex has soooo many files..) I am pondering splitting up my two 1TB drives and simply using one as an "unassigned device" as a backup location or even a hotswap if the primary drive fails. I have yet to have an SSD die on me though, so it's doubtful anything should happen.. I've just had so many issues by now and it's frustrating to keep restarting and spending days of time relocating files in the process. Any thoughts on this? Am I alone in suffering these corruption and filesystem problems with the RAID1 cache under BTFRS?

I just set up additional logging and diagnostics in Tips and Tweak CA so if it happens again I should have more to go on.

The cache is barely a month in to operation with these new drives so it's extremely odd for me. I hadn't noticed any corruption warnings though. I'll follow your guide and set up the notifications to be alerted. So you reckon' this is the cause of my problems?

Did a scrub yesterday when ChatNoir mentioned it, no errors fixed or detected.

Yeah that cache is irksome to say the least. I rebuilt it because it kept throwing errors and causing problems - ON NEW DRIVES - and still it persists. That's just.. hurtful at this stage. But yes, I strongly suspect BTFRS and the cache/Docker to be at the root of much of this. Side note: Plex is now fixed by recovering an earlier backup DB.

Oh, the reason I suspect Docker is because when Plex broke earlier in the day I logged on to My Servers from work and checked the server remotely. Everything seemed fine, but I couldn't load the docker page - at all. Then when I tried to reboot it via the interface it would just hang and not do anything, maybe from failing to halt the docker service. Log didn't really illuminate me. Ended up phoning the wife for a hard-reset which resolved it, but left Plex with the corrupt DB. Which I still haven't addressed as yet in case troubleshooting illuminates something that might fix it.

Thanks for taking the time. Syslog attached. System has been stable for... six years or so and is using ECC memory, I hadn't really considered memory being an issue considering it's not being manipulated at all. It also seems to be entirely docker-container related, the issues I'm having.. array seems fine. I'm assuming the 5 errors that keep popping up during parity checks are down to the marvell controller which is being addressed. fortytwo-diagnostics-20210527-2140.zip

Hi I'm in a bit of a bind and I think I need help to perform proper diagnostics to finally resolve my issues. My UnRaid has been.. temperamental.. of late and I noticed a lot of BTFRS errors in the log and while they were curable they kept cropping up. So I replaced both cache drives from 2 x 256 to 2x1TB and rebuilt cache, docker file system and everything from scratch. So far, so good. Now I am, however, getting infrequent crashes which mainly seem to affect docker - but docker is handling all my operations. It just happened again today, and now my Plex instance won't start claiming database corruption: Starting Plex Media Server. Error: Unable to set up server: sqlite3_statement_backend::prepare: malformed database schema (113616) for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE) Stopping Plex Media Server. This is GOD-AWFUL considering the amount of media I have in my library and how I've been painstakenly managing it inside Plex, but then again, I've had Plex decide to be an *@*!*#* before so it's not exactly the first time. It is however entirely too unstable and I really want it fixed. I don't think it's purely docker related as it happened last week, suddenly everything was inaccessible while I was on holiday, and even "My Servers" in UnRaid said that the server was offline. So there's *something* going on.. but I am having a hard time locking down what it may be. I am also using a marvell-based controller at the moment, since my non-marvel one doesn't want to address all the disks for whatever reason, so please disregard that. I'm starting to think running BTFRS cache is just cursed, as it's not the first time this configuration has given me extreme issues. I am half tempted to just yolo it and run with a single cache drive and just rely on backup of application data instead. If anyone has any insight I'd greatly appreciate it. fortytwo-syslog-127.0.0.1-20210527-1338.zip fortytwo-syslog-20210527-1342.zip

Cheers mate. Reading your suggestion made me realize "hey, it wasn't that tough setting up in the first place.." so I just changed the folder and started over. Back up n' running. Thanks for the help though!

Help please. I just moved everything away from cache to replace my dual 256G drives with dual 1TB drives. Everything seems to have transferred nicely, but nginx is broken - and as a consequence as is my Nextcloud instance. nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-5/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-5/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) Is what it's saying in the log file. I assume I must have lost something in transit. I tried removing the container and re-adding it, hoping that would help resolve it. So what do I do? Transfer any necessary configs, remove the old directory and start over? Please advise I'm a bit out of my depth on this one.

I just use the update button in the unraid interface. I've never actually seen an update inside the webUI.

I posted a bit above you about this exact same issue. No response. Have you gotten it fixed? I hate that it keeps resetting itself to Google. I don't want to use Google.

Can someone tell me why or how the DNS settings keep resetting themselves to google? I actively avoid Googles DNS and it's frustrating to log on and find that it's been using google again for weeks. Is there something I can do. Is it a bug that it just resets the DNS provider?

It takes a while to index the files before transferring starts usually. An hour seems like a long time though.

How many remote files can the clients see?

I really didn't expect drama like this coming out of UnRAID, I have to say. Sympathize with both sides of this particular argument, but I do hope the impacted developers see the olive branch being offered as genuine and come back to the fold. We'll all be stronger for it.

I know. But this is automated

Got this running now. Is it possible to have it just keep a copy of the flashdrive backup in .zip format instead? I like that it's at least ON a disk this way, but having a few copies wouldn't hurt, either. Or maybe it's unnecessary and I'm making it overly complicated.

If the missus ain't complaining they're probably good. I think I'll pick a few up, can't beat that price/performance ratio.. not as far as I can tell.

@JaY_III How happy are you with those Toshibas? I'm looking at the MG07ACA14TE because it's actually the cheapest option per TB at the moment..

That seems odd. I'm at 12TB parity and that takes me about 24-26 hours.