starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

[10.11.0]Migrating backups from different computers results in invalid media libraries #7470

New Issue
Closed
opened 2026-02-07 05:02:12 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-07 05:02:12 +03:00
Owner
Copy Link

Originally created by @tanmoumou252 on GitHub (Oct 21, 2025).

Description of the bug

A network drive with drive letter X was deployed on a VMware virtual machine. Jellyfin had already completed its scan when the backup was created. After moving this backup to the host for restoration, the media library scan displayed the error: 'the path in the database is not the correct path on the filesystem'.

Of course, the network drive on the host naturally also uses the X drive letter.

Can see in the Task Manager that there is no disk scanning being performed, but the CPU usage spikes to around 80%

Reproduction steps

  1. Create a backup
  2. Restore on another host

What is the current bug behavior?

Media on the home page cannot be loaded, showing a spinning animation

What is the expected correct behavior?

The virtual machine and the host use the same disk path, which is completely identical, so the media library can scan normally after recovery

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.11.0

Environment

- OS:
- Linux Kernel:
- Virtualization:
- Clients:
- Browser:
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration:
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Jellyfin Data Storage:
- Media Storage:
- External Integrations:

Jellyfin logs

[19:15:06] [INF] [7] Emby.Server.Implementations.Library.LibraryManager: Validating media library

[19:15:25] [INF] [21] Emby.Server.Implementations.ScheduledTasks.TaskManager: Attempting to cancel Scheduled Task 扫描媒体库

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

Originally created by @tanmoumou252 on GitHub (Oct 21, 2025). ### Description of the bug A network drive with drive letter X was deployed on a VMware virtual machine. Jellyfin had already completed its scan when the backup was created. After moving this backup to the host for restoration, the media library scan displayed the error: 'the path in the database is not the correct path on the filesystem'. Of course, the network drive on the host naturally also uses the X drive letter. Can see in the Task Manager that there is no disk scanning being performed, but the CPU usage spikes to around 80% ### Reproduction steps 1. Create a backup 2. Restore on another host ### What is the current _bug_ behavior? Media on the home page cannot be loaded, showing a spinning animation ### What is the expected _correct_ behavior? The virtual machine and the host use the same disk path, which is completely identical, so the media library can scan normally after recovery ### Jellyfin Server version 10.10.0+ ### Specify commit id _No response_ ### Specify unstable release number _No response_ ### Specify version number _No response_ ### Specify the build version 10.11.0 ### Environment ```markdown - OS: - Linux Kernel: - Virtualization: - Clients: - Browser: - FFmpeg Version: - Playback Method: - Hardware Acceleration: - GPU Model: - Plugins: - Reverse Proxy: - Base URL: - Networking: - Jellyfin Data Storage: - Media Storage: - External Integrations: ``` ### Jellyfin logs ```shell [19:15:06] [INF] [7] Emby.Server.Implementations.Library.LibraryManager: Validating media library [19:15:25] [INF] [21] Emby.Server.Implementations.ScheduledTasks.TaskManager: Attempting to cancel Scheduled Task 扫描媒体库 ``` ### FFmpeg logs ```shell ``` ### Client / Browser logs _No response_ ### Relevant screenshots or videos _No response_ ### Additional information _No response_
OVERLORD added the bugduplicate labels 2026-02-07 05:02:12 +03:00
OVERLORD commented 2026-02-07 05:02:15 +03:00
Author
Owner
Copy Link

@tanmoumou252 commented on GitHub (Oct 21, 2025):

By the way, the network disk x is actually a local hard drive mounted using raidrive, just for testing
To prevent jellyfin from forcibly modifying nfo files, so write protection is set using raidrive

@tanmoumou252 commented on GitHub (Oct 21, 2025): By the way, the network disk x is actually a local hard drive mounted using raidrive, just for testing To prevent jellyfin from forcibly modifying nfo files, so write protection is set using raidrive
OVERLORD commented 2026-02-07 05:02:17 +03:00
Author
Owner
Copy Link

@tanmoumou252 commented on GitHub (Oct 21, 2025):

In the end, I still copied the entire %USERPROFILE%\AppData\Local\jellyfin
Then it could only display the content under the media library. During scanning, it still showed the media library as invalid. I finally realized that even the %USERPROFILE% part must be consistent.

This means that when User 2 uses User 1's backup, User 2's name must also be changed to User 1's.

@tanmoumou252 commented on GitHub (Oct 21, 2025): In the end, I still copied the entire `%USERPROFILE%\AppData\Local\jellyfin` Then it could only display the content under the media library. During scanning, it still showed the media library as invalid. I finally realized that even the `%USERPROFILE%` part must be consistent. This means that when User 2 uses User 1's backup, User 2's name must also be changed to User 1's.
OVERLORD commented 2026-02-07 05:02:18 +03:00
Author
Owner
Copy Link

@tanmoumou252 commented on GitHub (Oct 21, 2025):

https://forum.jellyfin.org/t-moving-server-to-new-system-with-different-username

After seeing this, I modified the content of two tables in %USERPROFILE%\AppData\Local\jellyfin\data\jellyfin.db: BaseItems and BaseItemImageInfos.

Finally, there are no more issues.

@tanmoumou252 commented on GitHub (Oct 21, 2025): https://forum.jellyfin.org/t-moving-server-to-new-system-with-different-username After seeing this, I modified the content of two tables in `%USERPROFILE%\AppData\Local\jellyfin\data\jellyfin.db`: `BaseItems` and `BaseItemImageInfos`. Finally, there are no more issues.
OVERLORD commented 2026-02-07 05:02:20 +03:00
Author
Owner
Copy Link

@theguymadmax commented on GitHub (Dec 2, 2025):

Dupe of: #15653

@theguymadmax commented on GitHub (Dec 2, 2025): Dupe of: #15653
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label bug duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#7470
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?