July 1, 20224 yr Community Expert 16 minutes ago, Jeff in Indy said: This CAME from a backup. Was this backup also in appdata? Do you have an older appdata backup on the array? If your plex database is corrupt and there isn't a good backup you may have to start over with it. Since this all started by filling cache, I checked your diagnostics again. What is the purpose of the cache-prefer share t--p ?
July 1, 20224 yr Author The database isn't corrupt, that's why I restored from a backup that worked. But when I restored it, now I'm being told that it's read only.
July 1, 20224 yr Community Expert 4 minutes ago, Jeff in Indy said: It's "temp". I'm not sure why it's there, but it's emply. Were you using it for transcoding perhaps?
July 1, 20224 yr Community Expert 6 hours ago, JorgeB said: It's not a pool problem. Was taking a second look since the first one was on the phone and it's not so easy to look at the log, and I did miss this line: Jun 30 17:43:58 Kaokulk kernel: BTRFS error (device nvme0n1p1): incorrect extent count for 19382927360; counted 1535, expected 1532 Fs is not going read-only, so this might not be the problem, but it is a problem, first time I remember seeing this error, so not sure how serious it is, you should make sure backups are up to date and attempt to repair the filesystem, or backup and re-format the pool, there's also this which I saw before: Jun 30 17:43:51 Kaokulk kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 Jun 30 17:43:51 Kaokulk kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Some data corruption was found at some time earlier, it might be from a while ago, still this is usually a sign of bad RAM or other hardware issue, if you don't re-format the pool you should reset the stats ad keep monitoring.
July 1, 20224 yr Author 11 minutes ago, trurl said: Can you write anything to cache? Yes. I copied a file from my desktop's Downloads folder to my Data share. Quote Were you using it for transcoding perhaps? Probably.
July 1, 20224 yr Author 1 hour ago, JorgeB said: Some data corruption was found at some time earlier, it might be from a while ago, still this is usually a sign of bad RAM or other hardware issue, if you don't re-format the pool you should reset the stats ad keep monitoring. Yeah, back in May I had a bad memory stick and replaced the memory.
July 1, 20224 yr Community Expert Filesystem might have other damage, like the other issue, recommend backup and re-format.
July 1, 20224 yr Author I restored from a quite old copy of Plex, seems to work OK. The rebuild should be complete late tonight, but I won't have time to work on the pool til probably Monday. I'll update when I get to it.
July 6, 20223 yr Author So I’m using the steps on the website to back up the cache to the array. I changed the shares to Yes where appropriate and started the Mover. It took the cache from 600+GB to 483GB used. it hasn’t moved in the past couple of hours. The mover is still running, but nothing is happening. How can I see what’s happening, and why it’s stopped moving?
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.