Server Version#: v1.42.0.9975-6b2b441e1
Player Version#: N/A
Hello all, I moved my Plex from Windows to an Unraid container earlier this year and I’ve been having this issue where the database is apparently getting corrupted. The symptoms are: 1. If I try to play a live TV channel it will display a throbber for a few seconds then state “Playback Error Could not tune channel” (tuner works fine through the HDHomeRun app) & 2. some, but not all, DVR recordings are missing from the DVR library (the recording files do exist on the drive). Each time this occurs I have to use the DB repair tool. This has occured 3 times over the last 3 months. Any ideas why the DB keeps getting corrupted? I’m using the binhex-Plexpass container.
Assuming that you are only using local storage and don’t spin down your disks, then you have a hardware problem with your storage.
Only other thing I can think of is if you have another program that is accessing the Plex database and holding a lock to long. Restore the last backup and see how it goes.
Disk Spin down delay is set to ‘Never’, but the database is on a cache disk which consists of 2 NVMe drives in a mirror, so I wouldn’t thin spin down would be an issue.
I’m not aware of any other programs that should be accessing the Plex DB.
I’m sure their is plenty of glowing testimony in the UNRAID forums for placing Plex on the cache disk but unless special care is taken with regard to the db files this will happen. If UNRAID claims there is no issue then that would leave one of your NVMe’s as suspect.
The database is already trying to cache data and putting an abstraction layer between it and its files (including the -shm and -wal ) is likely to lead to your condition. If you need that speed it would be better to place it on dedicated NVMe storage.
DVR tuner info is not usually portable from Windows → Linux because Windows supports many in-computer tuners whereas there are not as many for Linux.
If this is a network tuner then there is more hope.
Different Tuner IDs does have impact (which I do not undertstand)
Next is where recordings are stored (which is different between the two OS’s)
I would like to learn more about the container config.
I have an unraid system here (development box) which runs without issue.
One obvious caveat – It was created on the Unraid machine. I have never attempted to port another OS to unraid.
It is a network tuner (HDHomeRun Connect Quatro). I don’t remember if i re-setup the tuner config after migrating from Windows. Might it help to remove the tuner from Plex and re-add it?
DVR recordings are stored on a ‘DVR Pool’ of 5 HDDs, but I don’t think the DVR storage is an issue since even though I cannot tune a channel in the Plex client, the recordings don’t show up in the DVR library, and all show a ! with “An Unknown Error Occurred” in the DVR schedule, the recordings are being completed and stored on the DVR pool/share. After I repair the DB and rescan the DVR library, the recordings then show up and I can watch them.
Here is some container config, let me know if there’s something specific you’re looking for:
<UNRAID Container Config>
Repository: ghcr.io/binhex/arch-plexpass
Network Type: Host
Console shell command: Bash
Privileged: Off
Path: /config: /mnt/user/appdata/binhex-plexpass (appdata is on Primary Cache)
Path: /media: /mnt/user (allows access to all Unraid Shares)
Variable: TRANS_DIR: /config/transcode
Variable: NVIDIA_DRIVER_CAPABILITIES: all (N/A I have an Intel CPU w/ Quick Sync)
Variable: NVIDIA_VISIBLE_DEVICES:
Variable: PLEX_CLAIM:
Variable: SHARED_NETWORK: no
/dev/dri: /dev/dri
<DVR Config In Plex>
DVR Folder: /media/DVR_new/Recorded TV (DVR_new is on the DRV pool)
Convert video while recording: Off
Use hardware-accelerated video encoding: Yes
Transcode Quality: 99
Resolution: Prefer HD
Replace lower resolution items: No
Allow partial airings: Yes
Minutes before start: 1
Minutes after end: 10
Postprocessing script: None
Detect commercials: Detect Commercials and mark for skip
Perform refresh of program guide data: Yes
Well, it happened again, I checked in the Unraid forums and found a thread of folks having the same issue with an earlier version of Unraid, but they say it was fixed with v7 which is what I’m running… oh fun
