[Bug] Scanning a single source triggers disk activity on unrelated sources

Server Version#: 1.43.0.10492-121068a07

When initiating a library scan for a specific source, the system unexpectedly wakes up and accesses other storage devices that are not related to the selected source.

Steps to reproduce:

  1. Open the media server interface

  2. Locate a specific source in the sidebar

  3. Click the three dots next to the source and select “Scan Library Files”
    (Alternatively: open the source, then use the three dots next to the source name in the top-left and select the same option)

Expected behavior:
Only the selected source should be scanned. No other sources or storage devices should be accessed.

Actual behavior:
Other drives (e.g., external hard drives) are spun up and accessed during the scan, even though:

  • The sources are fully isolated

  • There are no symlinks or shared paths between them

Additional context:

  • Example setup includes separate sources on a microSD card and an external hard drive

  • The issue occurs regardless of how the scan is initiated (sidebar vs. source view)

  • This behavior was not observed in the last stable release (late 2025)

Notes / Debugging suggestion:
This should be straightforward to trace by logging disk reads per source path or device, as unrelated devices are being accessed during a scoped scan.

Lastly, I request for me is to have a toggle state in settings to not do a scan on startup of the app. E.g. if I update Plex Media Server, all external drives are spun up automatically even though I know there are no changes in any of the sources.

1 Like