Merrrp

I just stumbled by this thread from Google fixing my own corrupt Plex DB on the binhex plexpass image. I thought I'd drop my findings here since I used this thread to solve my issue. My original error in the container logs for anyone searching for similar: Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: metadata_agent_providers for SQL: update metadata_agent_providers set online = 0 (N4soci10soci_errorE) I fixed my DB using the tool linked above by running the following commands from the container console: cd / pacman -S wget --noconfirm wget https://github.com/ChuckPa/PlexDBRepair/archive/refs/tags/v1.0.4.tar.gz tar xf v1.0.4.tar.gz rm v1.0.4.tar.gz cd PlexDBRepair-1.0.4 chmod +x DBRepair.sh ./DBRepair.sh Then running automatic repair when the tool's menu appears. You'll ideally need to have stopped Plex running somehow before running a repair, mine was stuck in a crash loop so I got it to run in between starts following a crash, and that apparently worked.

@writablevulture You're welcome, glad it helped! I've checked my configuration and I see the same paths showing in the SSMS server properties window, but when I check the contents of the paths I've configured I can see things appear to be going in the correct places on disk. After some digging I've realised I think it's just the naming of things being confusing. The two settings in the template are for the container paths whereas it sounds like you want to configure the server DB defaults within the container? If so I suspect what you want might be these docs: MSSQL_BACKUP_DIR Set the Default backup directory location. MSSQL_DATA_DIR Change the directory where the new SQL Server database data files (.mdf) are created. MSSQL_LOG_DIR Change the directory where the new SQL Server database log (.ldf) files are created. MSSQL_DUMP_DIR Change the directory where SQL Server will deposit the memory dumps and other troubleshooting files by default. It's a little while since I looked at this so I'll sort out updating my template in due course, hopefully it helps folks get started.

I set my RAM clock down to 1866Mhz, disabled C states, and set power supply idle control to typical. I've managed to complete a parity rebuild overnight now and got everything started up etc, it looks as though all is well so far, so that may well have done the trick. Thanks once more for your help, much appreciated!

Oh wow I didn't realise it need to be as low as 1866Mhz for 4 sticks, I'll try reconfiguring and giving it one more go.

So the read check seemed to be going fine with no read errors, I grew impatient and cancelled it about 2 thirds through to set off a parity rebuild which seemed to be going fine so I went to bed with it at about 60/70% with no errors. This morning it was unresponsive, there was a kernel panic error on the monitor attached (I may be misremembering the error), so I forced it off and booted up again. Everything appeared fine so I tried setting another rebuild off this morning that's been going all day, and at about 90-95% the web UI suddenly dropped and there's a kernel panic error on the monitor. I've forced it off again, and it's booted up again appearing as though everything's fine. I think I'm going to have to switch back to the previous motherboard, as much as I wanted the extra slots after the trouble I've had with it in other builds in hindsight I don't know what I was thinking using it in this system. I've attached the diagnostics from after booting up following each crash in case that helps shed light on the situation. Thanks again for your help, hopefully swapping back will get me up and running again. risa-diagnostics-20200708-1119.zip risa-diagnostics-20200708-1933.zip

Thanks, I guess I must've got lucky with the last board (Gigabyte B450M DS3H). Rather than swap motherboards I've got version 6.9.0-beta22 on now and I've set off a read check, fingers crossed. As an aside I realised the reason my array was auto starting when I thought I'd configured it not to, was because when it's in a somewhat broken state (for example when I stop the array) none of the settings pages that I've tried work, the HTTP requests just hang so I hadn't actually changed that setting technically.

Oh I see, I was previously on a B450 and never encountered any issues on that so I just assumed X470 would also be fine being from the same generation. I've checked and indeed the 3 drives with read errors are the only array drives on the onboard controller. The cache pool was also running from the onboard controller but I hadn't noticed any issues with that, but I might have just missed them if there were. I've forced the system off for now, I'll look at swapping back to my old B450 motherboard later on since that worked fine despite sadly having less PCIE slots. I wonder if trying some different BIOS versions might help since there are so many issues with the BIOS on this MSI board but I don't think it's worth the hassle at this point. Thanks for your input, I'll post an update when I've swapped everything back over again this evening.

Background I moved my Unraid box in to a new case the other day and moved it on to a new motherboard in the process, as well as adding a new PCIE SATA card for more ports. Initially Unraid started up and found all my drives perfectly fine and all seemed well. Shortly after there were a phenomenal amount of errors (turning a monitor on attached to the Unraid box was a hyperspeed mess of constant errors), the web GUI became barely responsive, and after an hour or two of being unable to get it to power off cleanly I had to force it off. I checked cables/connectors etc, all fine, then realised the issue was my motherboard BIOS version (MSI X470 with 3rd Gen Ryzen BIOS version but running a 2nd Gen Ryzen) so I downgraded back as far as MSI will allow me to the last 2nd gen Ryzen version. Starting Unraid back up again everything seemed to be running ok for about a day, the array started on boot and began a parity check, despite me setting it not to auto start the array as I was going to run disk checks (some errors had logged about xfs needing repairing). I let it continue and about 60% of the way through I was at 3 errors. Current Issue(s) When I looked at Unraid again today my parity drive has been disabled following whatever happened with the parity check, that disk has over 20 billion read errors, the parity check finished with lots of errors, and 2 more drives in the array have millions of read errors, and my log is at 100% (syslog is the one taking up the space I think). Unraid was performing a 'read check' but had stopped, initially I resumed it but then changed my mind and instructed it to stop the array. I am currently unable to cleanly shut down or reboot, the array shows as stopped in the web GUI but the status at the bottom says 'Array Stopping Sync filesystems...'. Can anyone offer me some help in trying to fix this situation please? I'm a bit out of my depth at this point to be honest. Diagnostics attached. Edit: I'm using Unraid v6.8.3 (nvidia driver version) risa-diagnostics-20200707-0949.zip

I've been attempting to set up MS SQL Server too, I seem to get it up and running fine pointing the paths at /mnt/cache etc. (I'm using my own template repo here if it helps anyone, I'd also welcome any feedback on cleaning that template up a bit). I haven't given it any serious work to do yet so I may still run in to more issues. The only issue I'm having currently is getting Unraid to detect available updates, I currently always get 'Not Available' - is anyone aware of a workaround for that other than an occasional force update? I'm guessing it's to do with MS using the mcr.* repo but I'm quite new to tinkering with Docker and these Unraid templates.