I recently ran out of room on my root partition. I had to expand the volume in esxi, then extend the partition with ubuntu partition manager. This worked just fine, but when the server reloaded the libraries are missing.
I also created a symbolic link for the folders “Plug-in Support” & “Media” folder to another drive to save space (this was working). My question is, if there is any obvious reason why extending a partition would cause this issue? are there any file xml configurations I can validate/modify to fix this issue? it seems like the database files and meta data still present, just not loading correctly.
I still have the content, I can re-create the libraries if I must; however, i’d prefer to do this in a new clean method, any recommendations?
Expanding a volume shouldn’t make any change because that action is transparent (growfs)
Creating a symbolic link to another path – that could cause problems because, as the link is traversed, user plex:plex must minimally have execute (traverse) permission to follow the link down to the final target directory.
That’s what I assumed. I’ve moved the database files back from /media/cache/ to /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-in Support/ and removed the symbolic link, but no change. After reviewing more closely it looks like my drive wasn’t mounted correctly on /media/cache/ thus it was writing to /dev/sda1 anyway. The database files may have become corrupt.
For a clean upgrade/installation what files should I remove without having to reconfigure my server settings?
Thanks for the info, I’ll read up on this. My system running kde (kubuntu 20.04 LTS). I haven’t had an issue in regards to automounting or permissions as far as I’m aware. I’m fairly sure this broke simply because my ssd wasn’t mounted to that mount point (/media/cache) and the local hard drive was near full.
To remove the erroneous configuration files and rebuild my library what files / folders should I clean out?
