Distinguish an unavailable mount from an intentionally empty collection
A network drive that did not mount can make a library path appear empty even when the original media still exists on its storage device. Before allowing cleanup or rebuilding a collection, identify whether the server can currently reach the expected mounted filesystem. A reachable web interface is not a complete test of the media-storage path.
Read the storage-specific warning
Jellyfin’s storage guide says it reads media directly from the filesystem and that Samba or NFS storage must be mounted by the operating system. It warns that scheduled maintenance can remove library items if triggered while media storage is unavailable. The same guide distinguishes the locally stored database from network media storage. These are separate components with different availability requirements.
Verify storage before a deliberate library operation
For example, after a NAS restart, the administrator can first confirm that the expected mount contains a known authorised file from the server’s own filesystem view. Check that it is the intended mounted location rather than an empty local directory left at the same path. Then review the library state and maintenance timing before initiating a broad scan or cleanup. Preserve useful metadata and a current backup while resolving the storage condition. A missing library record does not by itself prove the original video was deleted. Report the mount’s actual availability and the operation that ran, rather than treating every absent title as a remote catalogue change.
Questions, answered
Is a working Jellyfin login enough to confirm network media is available?
No. Jellyfin reads media from mounted storage, whose availability must be checked separately.