2024-12-19, 01:12 PM
This sounds like a permission issue on the content that is being scanned; often I run into this issue when I strip certain things from a file using ffmpeg and forget to re-apply the correct permissions to the newly created one.
I would try to run
and then try to scan it again.
I would try to run
Code:
sudo chmod -R 775 /path/to/the/problematic/media
and then try to scan it again.
Server specs => OS: Debian 12 | GPU: Arc A380 | CPU: Ryzen 5 5600X | 64GB RAM | 56TB