mirror of
https://github.com/Lidarr/Lidarr.git
synced 2026-03-02 22:56:57 -05:00
Couldn't import track [Blackhole location] File copy incomplete. [Music folder location] was 0 bytes long instead of 4215251 bytes #4317
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Extras
Area: Import Lists
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Organizer
Area: Parser
Area: Scanning
Area: Tooling
Area: UI
Area: Unit Tests
Area: Update API
On Hold: MetadataAPI Blocking
Priority: High
Priority: Low
Priority: Medium
Status: Accepted
Status: Cannot Reproduce
Status: Confirmed
Status: Don't Merge
Status: Help Wanted
Status: In Progress
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: On Hold
Status: Ready for Review
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
conflict
conflict
no-conflict
not-pulled
radarr-pull
readarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Lidarr#4317
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @gazmeist on GitHub (Oct 17, 2025).
Is there an existing issue for this?
Current Behavior
Ive googled, searched the issues, and can't find anything comparable. Open to this being my problem but can't figure it out. Have checked permission settings, folder access (both source and destintion), checked the files themselves. Everything to me looks perfectly fine.
This began a couple of days ago, manual imports have worked fine for months/years before that, including the last couple of weeks since the metadat issues were resolved and I got a flood of new music coming through.
Below is a specific example of an error. Happening with all my manual importing.
Message
Couldn't import track /downloads/Nelly Furtado - 7 (2024)/14. Untitled.mp3: File copy incomplete. [/Music/Nelly Furtado/7 (2024)/Nelly Furtado - 7 (2024) - 14. Untitled.mp3] was 0 bytes long instead of 4215251 bytes.
Exception
System.IO.IOException: File copy incomplete. [/Music/Nelly Furtado/7 (2024)/Nelly Furtado - 7 (2024) - 14. Untitled.mp3] was 0 bytes long instead of 4215251 bytes.
at NzbDrone.Common.Disk.DiskTransferService.TryCopyFileVerified(String sourcePath, String targetPath, Int64 originalSize) in ./NzbDrone.Common/Disk/DiskTransferService.cs:line 484
at NzbDrone.Common.Disk.DiskTransferService.TransferFile(String sourcePath, String targetPath, TransferMode mode, Boolean overwrite) in ./NzbDrone.Common/Disk/DiskTransferService.cs:line 383
at NzbDrone.Core.MediaFiles.TrackFileMovingService.TransferFile(TrackFile trackFile, Artist artist, List
1 tracks, String destinationFilePath, TransferMode mode, LocalTrack localTrack) in ./NzbDrone.Core/MediaFiles/TrackFileMovingService.cs:line 152 at NzbDrone.Core.MediaFiles.TrackFileMovingService.MoveTrackFile(TrackFile trackFile, LocalTrack localTrack) in ./NzbDrone.Core/MediaFiles/TrackFileMovingService.cs:line 92 at NzbDrone.Core.MediaFiles.UpgradeMediaFileService.UpgradeTrackFile(TrackFile trackFile, LocalTrack localTrack, Boolean copyOnly) in ./NzbDrone.Core/MediaFiles/UpgradeMediaFileService.cs:line 83 at NzbDrone.Core.MediaFiles.TrackImport.ImportApprovedTracks.Import(List1 decisions, Boolean replaceExisting, DownloadClientItem downloadClientItem, ImportMode importMode) in ./NzbDrone.Core/MediaFiles/TrackImport/ImportApprovedTracks.cs:line 240**
Audio-2025_10_18_02_05_PM.txt
lidarr.txt
**
Version 3.0.0.4855
Package Version 3.0.0.4855-ls175 by linuxserver.io
.NET Yes (8.0.12)
Docker Yes
Database Sqlite 3.50.4
Database Migration 80
AppData Directory /config
Startup Directory /app/lidarr/bin
Mode Console
Uptime 15:19:19
Expected Behavior
Should import without issue.
Steps To Reproduce
No idea if it can be reproduced to be fair.
Place mp3 files in Blackhole folder
Under Activity > Queue, attemot manual import.
Check System Events logs
Environment
What branch are you running?
Nightly
Trace Logs?
Audio-2025_10_18_02_05_PM.txt
lidarr.txt
Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.
trace- that are relevant and show this issue.@github-actions[bot] commented on GitHub (Oct 18, 2025):
👋 @gazmeist, 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.
@gazmeist commented on GitHub (Oct 18, 2025):
Sorry about that @bakerboy448
Here's the trace logs. Assume that all you need. Again happy to be told if it's something on my side I'm overlooking.
lidarr.trace.txt
@bakerboy448 commented on GitHub (Oct 18, 2025):
What mounts are /downloads and /Music?
While v3 did get bumped to dotnet8 this seems possibly a file system or hardware issue
@gazmeist commented on GitHub (Oct 18, 2025):
Both are mounts to a sedcond QNAP NAS I have. I did check in File Manager on the same NAS as Lidarr to ensure there wasn't an issue with those mounts, all looks fine. Confirmed the user for those mounts has the permissions to do what it needs to.
@gazmeist commented on GitHub (Oct 18, 2025):
Actually it's just triggered something for me - I think around the same time some firmware updates were installed on both NAS. Don't waste any further time (yet) on this @bakerboy448 . Let me check if there's any issues with those updates first.
@gazmeist commented on GitHub (Oct 18, 2025):
OK so fresh update - found a fresh firmware update waiting for me on the 451D2 NAS that the music is sotred on and mounted via CIFS/SMB to the TS451A (and has always been - but maybe some bug introduced in that initial firmware update).
Ive SSHd into the 451A that Lidarr is on, and opened up the share to view the files, and everything looks ok and still has sizes showing, and full permissions
Checked the mount settings and best I can tell all looks ok, but still getting issues. I'll try recreating the mounts, remapping in my docker compose yaml and restarting things over, see if I can get it behaving. Will report back witn an update.
Thanks for taking that bit of time @bakerboy448 - hopefully I don't have to waste any more of it.
@gazmeist commented on GitHub (Oct 18, 2025):
OK further update - recreated the mount, grabebd the latest mount details to update in my docker yamls, and have restarted.
Whilst doing that it occurred to me that I have the same multi-NAS and using the same mount setup for both Sonarr and Radarr, and both are processing manual blackhole imports without issue even with the firmware distractions above. So supect I've gone down a rabbit hole I didn't need to, but better to be safe than sorry I guess.
If nothing else, this full trace of the restart of Lidarr may provide a little more info to work with? No rush, appreciate the help @bakerboy448 and others. Kept up with all the metadata server work you guys did over the last few months, and wanted to say thankyou on that thread but of course couldn't, so consider yourselves thanked here :)
lidarr.trace.txt
@bakerboy448 commented on GitHub (Oct 18, 2025):
@mynameisbogdan commented on GitHub (Oct 18, 2025):
Sonarr v5 doesn't have a build yet so don't you blame .NET 8. 😝
@bakerboy448 you need to cherry pick
github.com/Sonarr/Sonarr@6660db22ecusing a PR, as it might break the tests.@gazmeist are you using symlinks for that directory? Because then it might need
github.com/Sonarr/Sonarr@ca0bb14027andgithub.com/Sonarr/Sonarr@8cb58a63d8@gazmeist commented on GitHub (Oct 18, 2025):
Confirming:
Radarr/Sonarr does NOT have the same issue - I mentioned it to eliminate the mapping/permissons setup as a possibility
Sure I'll disable Spotify Lists - was not aware they were a problem
777 permissions was just me manually going overboard with ensuring there wasn't a permission issue causing the problem.
Checking my seeings I have
Let me know if anything else is helpful to provide
@mynameisbogdan commented on GitHub (Oct 19, 2025):
Do you use symlinks?
@gazmeist commented on GitHub (Oct 19, 2025):
I thought thats what this setting referenced?
Or am I nistaken?
@mynameisbogdan commented on GitHub (Oct 19, 2025):
No, that's not what I asked. You can externally set symlinks for the structure, so /downloads is a symlink to /srv/media/downloads/etc or /Music is a symlink to /home/user/music/etc and so on. Considering the 0 bytes error and Lidarr's lack of support for symlinks at the time, I'm very certain you're using symlinks.
@gazmeist commented on GitHub (Oct 19, 2025):
Do docker volumes count as symlinks?
Just to reiterate - This has worked fine for months and only started reporting that error a few days ago.
@mynameisbogdan commented on GitHub (Oct 19, 2025):
What changed a few days ago? Remove any lidarr-extended scripts and try again, as it breaks the app sometimes.
@gazmeist commented on GitHub (Oct 19, 2025):
Watchtower updated Lidarr to the latest nightly version roughly my Thursday morning. I also had a firmware update on my NAS' later that day. Howver per earlier in the thread, similar volume setups for Radarr and Sonarr continue to import files from blackhole download locations fine, so am inclined to believe the firmware update isn't a factor here.
@woulf commented on GitHub (Nov 13, 2025):
Hello,
having the same problem after upgrading from 2.x to 3.x on ubuntu 20.04
no docker involved, just some SMB mount
@woulf commented on GitHub (Nov 14, 2025):
i upgrade the OS from 20.04 to 22.04 and it solved the problem on my side so maybe some kind of dependencies problem.
@TheHesster commented on GitHub (Jan 23, 2026):
I'm having this issue as well
@TheHesster commented on GitHub (Jan 23, 2026):
In my case the import succeeds if I have use hardlinks turned on but fails if I have it turned off. I wanted to have it turned off to turn on the Tag Audio Files with Metadate setting. I'll leave that off for now and allow hardlinks.