[Downgraded back to 6.6.7 due to Sqlite corruption]

2 minutes ago, Abzstrak said:

yeah, just been lazy... was thinking of doing that as well as shooting out an email/sms message to my phone letting me know its corrupt. its been 10 or 11 days since my last corruption, so... motivation isn't all there either

 

haha i feel you - i was extremely motivated when it was dying every day but now with 2-3 weeks in between, there is not much motivation and hopefully this gets sorted out by the dev team!

[Downgraded back to 6.6.7 due to Sqlite corruption]

9 hours ago, Brian H. said:

I would recommend keeping backups once in a while as well just in case you are unable to recover the database. I tried at least 6 separate times, and each time the test at the command line after re-importing the data reported problems. So, I have given up on that process.

 

I should probably clarify I do keep the 3 days backup from Plex as well as a daily app data backup.

 

Is just restoring from backup is a pain as depending on how close I am to the 3 days backup I will lose tv shows progress (our household consume a lot) or I will need to extract the app data backup. Much easier for me to just run a single script to drop a couple of index, dump the db and rebuild as it will take me less then a minute.

[Downgraded back to 6.6.7 due to Sqlite corruption]

1 minute ago, Addy said:

Rip i set it to scan the library's every 2 days and it only lasted 24 hours lol

 

log being spammed with 

Jun 23, 2019 21:42:08.128 [0x14eb10b44700] ERROR - SQLITE3:(nil), 11, statement aborts at 9: [select statistics_bandwidth.id as 'statistics_bandwidth_id', statistics_bandwidth.account_id as 'statistics_bandwidth_account_id', statistics_bandwidth.device_id as 'statistics_bandwidt
Jun 23, 2019 21:42:08.128 [0x14eb10b44700] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x14eb314d1700: sqlite3_statement_backend::loadOne: database disk image is malformed
Jun 23, 2019 21:42:08.129 [0x14eb10742700] ERROR - SQLITE3:(nil), 11, database corruption at line 79051 of [bf8c1b2b7a]
Jun 23, 2019 21:42:08.129 [0x14eb10742700] ERROR - SQLITE3:(nil), 11, statement aborts at 9: [select statistics_bandwidth.id as 'statistics_bandwidth_id', statistics_bandwidth.account_id as 'statistics_bandwidth_account_id', statistics_bandwidth.device_id as 'statistics_bandwidt
Jun 23, 2019 21:42:08.129 [0x14eb10742700] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x14eb312d0700: sqlite3_statement_backend::loadOne: database disk image is malformed
Jun 23, 2019 21:42:08.130 [0x14ea9d71c700] ERROR - SQLITE3:(nil), 11, database corruption at line 79051 of [bf8c1b2b7a]
Jun 23, 2019 21:42:08.130 [0x14ea9d71c700] ERROR - SQLITE3:(nil), 11, statement aborts at 9: [select statistics_bandwidth.id as 'statistics_bandwidth_id', statistics_bandwidth.account_id as 'statistics_bandwidth_account_id', statistics_bandwidth.device_id as 'statistics_bandwidt
Jun 23, 2019 21:42:08.130 [0x14ea9d71c700] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x14eb312d0700: sqlite3_statement_backend::loadOne: database disk image is malformed
Jun 23, 2019 21:42:08.131 [0x14eb137f5700] ERROR - SQLITE3:(nil), 11, database corruption at line 79051 of [bf8c1b2b7a]
Jun 23, 2019 21:42:08.131 [0x14eb137f5700] ERROR - SQLITE3:(nil), 11, statement aborts at 9: [select statistics_bandwidth.id as 'statistics_bandwidth_id', statistics_bandwidth.account_id as 'statistics_bandwidth_account_id', statistics_bandwidth.device_id as 'statistics_bandwidt
Jun 23, 2019 21:42:08.131 [0x14eb137f5700] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x14eb314d1700: sqlite3_statement_backend::loadOne: database disk image is malformed

I should maybe get my SAS card and SSD's this week so hope moving to cache fixes the issue 

Ah that sucks - with so many variation definitely to pin point exactly what is going on.

 

I haven't done any of the suggested fix as I am still waiting for my coffee lake replacement to come in (US to Aus from Amazon is taking unusually long gonna take almost 4 weeks....)

 

Once I have fully rebuild my unRaid server with proper parts i can join in the testing.

[Downgraded back to 6.6.7 due to Sqlite corruption]

Well I would be happy to get a cache drive if it resolve the issue but waiting on more confirmation. Also unRaid should probably specify that cache drive is a necessity and not optional if that is the case.

[Downgraded back to 6.6.7 due to Sqlite corruption]

Just now, Addy said:

do you have an actual cache drive? 

 

I brought a ssd the other day and am going to put it in my tower, wondering if that will help

No cache drive and my appdata is still using "user" instead of "diskX"

 

Haven't bothered changing the above as it seems people are still experiencing issue anyway.

 

I believe from reading this thread even people with cache drive is also experiencing the same issue?

[Downgraded back to 6.6.7 due to Sqlite corruption]

6 minutes ago, Addy said:

I think I moved my plex to /mnt/disk1/appdata on the 17th so around 3 days for me

 

Yeah I see where you are coming from, by making sqlite scan library's less frequently we therefor reduce the chance of corruption, I say chance because we seem to think its happening randomly?

 

I added a movie to plex yesterday, was prob what caused the corruption - not many tv shows coming out and its the only thing ive added within those three days I think

 

fyi for others

someone pm'd me and asked where my plex backups where 

they here \Plex\Library\Application Support\Plex Media Server\Plug-in Support\Databases 

 

Maybe its because the mapped locations of our server are on a share somewhere or another, what if I made a directory outside of shares?

Yes I still don't know exactly what corrupts it as obviously my plex will scan new files just fine (i do about 3-5 new episodes every day for the shows that sonarr track and others on top so is fairly regular for me) and is only yesterday after 3 weeks that it occurred.

 

This show with regards to probability in my case that chance of corruption is fairly low.

[Downgraded back to 6.6.7 due to Sqlite corruption]

8 minutes ago, Addy said:

I can give this a go - but I'm unsure why this would fix the issue - there is no real tether between sonarr and radarr as far as I'm aware? my plex is setup to scan disks when changes are found which is the only connection realistically? 

 

(sonarr puts a file somewhere plex can see it)

 

The backend of my plex just died with error

Thread: Uncaught exception running async task which was spawned by thread 0x14582b083700: sqlite3_statement_backend::loadOne: database disk image is malformed

yet another backup restore for me, its getting a bit out of hand. I don't want to downgrade, I'd prefer to help but we don't seem to be making much process and the dev's are no where to be seen, have they had any progress finding issues? I'd gladly upload anything they require

 

Addy 

I wouldn't say this fix this issue but it mitigate/reduce the corruption as mine just corrupted again last night (but its been 3 weeks since the last one and the previous corruption before then was about 2-3 weeks too). From what I can tell you guys are experiencing corruption a lot more frequent?

 

From what I can tell it seems that it only gets corrupted when plex does too many queries/update/insert in a short span of time. By only doing hourly scan it seems to be less prone to corruption.

 

I only notice this when I was redownloading all my files to 265 and I would get corruption every 30-60 min which lead me to the above and it seems to work.

 

So obviously there is a bigger underlying issue that still need to be fixed but at least now it has become less annoying...

 

Hopefully one the dev can figure it out.

 

ps. I have given up in using backup - now i just dump the db and rebuild the db from the dump. A lot easier to restore it and I can probably make a script to trigger this but i haven't been bothered as it doesn't happen as often.

[Downgraded back to 6.6.7 due to Sqlite corruption]

Am I the only one that have "solved/mitigated" the issue so far by disabling the connection between sonarr/radarr to plex and just doing a manual hourly scan for new files.

 

Have anyone tried the above and have eliminated or reduced the occurrence of corruption? It has been almost 3 weeks since my last corruption now.

 

I also figured out my radarr db corruption completely unrelated i had to dump it and remove a few values that was causing an issue and it is working fine after recompiling it.

[Downgraded back to 6.6.7 due to Sqlite corruption]

Just now, Toobie said:

And as a alternative to sqlite is mariadb may a better way to work with?
Could this may help?

Sent from my MI 6 using Tapatalk
 

 

Don't think the developers of those application would be keen in re-developing their app in MariaDB just for unRaid!

[Downgraded back to 6.6.7 due to Sqlite corruption]

Just now, Toobie said:

Can you please shortly explain to me, how do you recognize the corrupt data?
Just to check my system as iam following this thread but hopefully will not affected in my system with this problem.

Sent from my MI 6 using Tapatalk
 

When your plex no longer work and you check the log and it says is corrupted

[Downgraded back to 6.6.7 due to Sqlite corruption]

I have been experiencing this since I upgraded to 6.7.0 (i think i posted in one of the reddit post as someone had this issue on reddit).

 

The thing that has reduce the amount of corruption for me was to turn off notification from sonarr and radarr to plex when a new episode and/or movie gets downloaded (can't remember the exact name for this).

 

It seems when plex trys to update its DB every minute or two it corrupts the db?

 

I now just have a library scan every hour and i think i only had a corruption or two in the last month since I did this. 

 

ps. I have started a fresh plex, sonarr and radarr and it still does it and i haven't changed my config to diskX as it is still in user.

pss. My radarr is completely screwed though the db is always corrupted and you need to restart the docker to fix it but it dies fairly quickly after that but i have just given up and since movies doesn't come out that often I am not to fussed.

 

Haven't look into this as my board carked it a week ago and i am currently running unRaid with a jerry rigged hardware with the bare minimum to get it going. Waiting on replacement to arrive before trying to look into this again.

[[Plugin] Linuxserver.io - Unraid DVB]

Hopefully someone could enlighten me - i have been trying to use this plugin and i have tried all version of libreelec that is available and I keep getting Checking MD5's: failed!

 

I am running Unraid 6.6.1 and I have been crawling through this thread, the forum and google in general and cannot find any information as to why this is the case.

 

**update** fixed it by looking at install.php and finding out what to download and where to copy the downloaded file. No idea why the install script fail at the md5 check...

 

**update #2** looks like I can't seem to get the adapter driver to detect, currently using Sony PlayTV as my tuner and as per the earlier post it seems that 6.5.3 is the version that works but I am getting the following. Any suggestion?

 

**update #3** After spending the last day trying to figure this out - finally found an obscure post with regards to the Sony PlayTV not working correctly when using USB 3.0 ports - plugged it into my USB 2.0 port and it shows that is detected!