Rescan folders task fails if specific drive is added to root paths #2650

New issue

Open

opened 2026-02-20 13:00:26 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 13:00:26 -05:00

Owner

Originally created by @PartTheSeas on GitHub (Apr 1, 2023).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

Rescan folders task fails when adding specific root path to Lidarr, e.g. in my case /mnt/20TB16/Music/. If that root path is added, scanning all files fails, leaving many other artists on other drives without any track files, too. All 6 music drives I have music media on are mounted exactly the same, yet this one drive is causing trouble and I'm not sure why

Expected Behavior

Complete Rescan folders task with any drive added as root path and scanning all track files properly

Steps To Reproduce

No response

Environment

- OS: Kubuntu 23.10
- Lidarr: 1.1.4.3009
- Docker Install: Yes
- Using Reverse Proxy: Nginx_Proxy_Manager
- Browser: Chrome latest stable
- Database: Sqlite 3.40.1

What branch are you running?

Nightly

Trace Logs?

Trace logs on Hastebin

Originally created by @PartTheSeas on GitHub (Apr 1, 2023). ### Is there an existing issue for this? - [X] I have searched the existing open and closed issues ### Current Behavior Rescan folders task fails when adding specific root path to Lidarr, e.g. in my case `/mnt/20TB16/Music/`. If that root path is added, scanning all files fails, leaving many other artists on other drives without any track files, too. All 6 music drives I have music media on are mounted exactly the same, yet this one drive is causing trouble and I'm not sure why ### Expected Behavior Complete Rescan folders task with any drive added as root path and scanning all track files properly ### Steps To Reproduce _No response_ ### Environment ```markdown - OS: Kubuntu 23.10 - Lidarr: 1.1.4.3009 - Docker Install: Yes - Using Reverse Proxy: Nginx_Proxy_Manager - Browser: Chrome latest stable - Database: Sqlite 3.40.1 ``` ### What branch are you running? Nightly ### Trace Logs? [Trace logs on Hastebin](https://hastebin.com/share/emuzuyuluh.yaml)

deekerman added the

labels

2026-02-20 13:00:26 -05:00

deekerman commented

2026-02-20 13:00:27 -05:00

Author

Owner

@PartTheSeas commented on GitHub (Apr 2, 2023):

Hey again,

so the workaround for now was to split the library into 3 smaller libraries, which worked and Lidarr is now finally scanning the content successfully :)

Would still be interested in why this didn't work out well with the entire library at once if somebody has an idea 💯

@PartTheSeas commented on GitHub (Apr 2, 2023): Hey again, so the workaround for now was to split the library into 3 smaller libraries, which worked and Lidarr is now finally scanning the content successfully :) Would still be interested in why this didn't work out well with the entire library at once if somebody has an idea :100:

deekerman commented

2026-02-20 13:00:27 -05:00

Author

Owner

@bakerboy448 commented on GitHub (May 15, 2023):

Logs missing or deleted

@bakerboy448 commented on GitHub (May 15, 2023): Logs missing or deleted

deekerman commented

2026-02-20 13:00:27 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (May 15, 2023):

👋 @PartTheSeas, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our troubleshooting guide.

@github-actions[bot] commented on GitHub (May 15, 2023): :wave: @PartTheSeas, In order to help you further we'll need to see logs. You'll need to enable trace logging and replicate the problem that you encountered. Guidance on how to enable trace logging can be found in our [troubleshooting guide](https://wiki.servarr.com/lidarr/troubleshooting#logging-and-log-files).