runraid

No. I ran on /mnt/disk without touching those files via the cp command. It corrupts every few days while on /mnt/disk. I’m on the cache drive as of this morning and I’ll keep you all posted how that goes. @Squid

@saarg yup, starting fresh. No media was lost. Just meta data. Not so bad. Lesson learned. Btw, thank you all for the continued effort in finding a fix for this.

@saarg before I knew about "mover" I had did a "cp" to cache awhile back via ssh as root. Lastnight I started the move with "mover" but the existing files screwed it up. At that point I was in a mixed state. I'm just starting fresh. I just want to get past this corruption and will do whatever it takes now.

Ok, trying to move the plex appdata to /mnt/cache did something weird. I had to start over. I lost a few years of history I'm on /mnt/cache now but it'll have to regenerate the database. Plex will need to scan the library and download all metadata again. Fresh start 😞

@jonathanm /mnt/disk3/appdata/plex

Thank you very much for the update @limetech whats the the best way to move data to /mnt/cache/appdata/plex? Do we simply do a cp? I thought I read somewhere we should use a “mover”. Just wanted to Confirm then I’ll do this test.

Yet another user facing issues

Thanks @tjb_altf4 but it seems I already had that. See the attached image...

@Squid or anyone else, I've found this error in the log... Jun 18 21:21:37 Tower nginx: 2019/06/18 21:21:37 [error] 3668#3668: *508820 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.18, server: , request: "POST /plugins/dynamix.docker.manager/include/DockerUpdate.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.2", referrer: "http://192.168.1.2/Docker"

Another person hit by this. The actual impact must be fairly substantial given the number of impacted people I’ve seen complain given that most people won’t comment on forums or Reddit.

No version doesn’t matter. It happens across various software that uses SQLite.

I’ve set direct io to “no” yesterday. My plex just corrupted again. I'm running a storage system that corrupts my data. It's doing exactly the thing it shouldn't do.

I’ve set direct io to “no”. Once I get home I’ll repair my db and let you know if it corrupts again.

Ffs. I’m on 6.7.1-rc2 and my plex just corrupted. I’m losing my mind with this. I’m not using fuse. And no, this is not getting the attention it needs. This is data corruption for a storage system. We are paying customers and it seems to me like there’s hostility towards us for wanting this to get more attention. I’m on the verge of going my own way without unraid. I can’t be dealing with corrupting data every couple of days. I’m will to give $200 to the unraid team to help prioritize this. Maybe if we all donate money we can make this a compelling reason to get this fixed.

@Brian H. 6.7.1-rc2 was released. In the release notes I see > shfs: support FUSE use_ino option No idea what that enables though.

@Brian H. your experience mirrors mine. #2, moving to /mnt/disk only buys me about a week before things corrupt — and it seems all SQLite db in multiple containers corrupt at once.

Upgrading in hopes it fixes the SQLite db corruption problem many of us are plagued by since upgrading to 6.7.0

I've upgraded to 6.7.1-rc2 and restored my plex db as it just corrupted today. I'll keep you posted.

This is a major issue and seems to not be getting the attention it deserves. I’m pretty much begging for this to get priority by the unraid devs. My 6.7.0 system is now so unreliable. Data loss or corruption needs to be a top priority. This isn’t isolated. We can point to many people who have this problem. I love unraid and this community, but right now unraid is causing me and a lot of others much pain. I’m willing to donate money for a fix.

Yet again my sonarr db corrupted. It’s accessed directly through /mnt/disk3

> when it last ran Which seems to be not so often. I check for updates pretty regularly by manually clicking the button and more times than not I find an update. This combined with my sqlite db corruption is making my unraid seem unstable 😞 None of this happened before 6.7.0. Regarding the sqlite issue, it got pretty bad for a lot of people. I hope we can get to the bottom of it -- I'm willing to help however I can. Thanks for the help @Squid

@Squid see the attached tower-diagnostics-20190609-1611.zip tower-diagnostics-20190609-1611.zip

@Squid Here's a video that I recorded from my phone. I used my phone because it's easier to record, same experience on my desktop browser though... https://www.dropbox.com/s/p5wn2vfegld38ot/unraid.MP4?dl=0

@Squidyes it's fine. I'll make a video.

I have a few times. No luck.