-
[Support] HaveAGitGat - Tdarr: Audio/Video Library Analytics & Transcode Automation
(I had ChatGPT summarize my long and fruitless conversation on solving this issue, hence the AI-ish feel of the text below) 🛑 Issue: Transcoded file not found — still writes to /tmp despite configured cache pathHi everyone, I'm running into a persistent issue with my setup and could really use some help. Even after configuring a proper cache location and setting up path translators, my node still writes temp files to c:/tmp on the Windows node and then fails to move/copy the transcoded file back to the library because it can’t find it. ⚙️ SetupServer version 2.46.01 running in Unraid docker Node version 2.46.01 running on Windows 11 Library cache directory set to /mnt/media/tdarr-cache Path translators configured as: "pathTranslators": [ { "server": "/mnt/media/Movies/", "node": "T:/Movies" }, { "server": "/mnt/media/TV/", "node": "T:/TV" }, { "server": "/mnt/media/tdarr-cache", "node": "T:/tdarr-cache" } ] ⚡ ErrorHere’s the relevant part of the log: 2025-09-11T12:47:54.357Z: "/mnt/media/Movies/Back to the Future Part III (1990)/Back to the Future Part III (1990) Remux-1080p.mkv" 2025-09-11T12:47:54.362Z: "/tmp/tdarr-workDir2-l4CR8eXuxhu/Back to the Future Part III (1990) Remux-1080p-TdarrCacheFile-wClKc7deJ.mkv" ... 2025-09-11T12:47:55.405Z: File move error: {"errno":-2,"code":"ENOENT","syscall":"rename","path":"/tmp/tdarr-workDir2-l4CR8eXuxhu/Back to the Future Part III (1990) Remux-1080p-TdarrCacheFile-wClKc7deJ.mkv","dest":"/mnt/media/Movies/Back to the Future Part III (1990)/Back to the Future Part III (1990) Remux-1080p-TdarrCacheFile-j5vEo-aB9d.mkv"} 2025-09-11T12:47:55.419Z: File copy error: Error: ENOENT: no such file or directory, lstat '/tmp/tdarr-workDir2-l4CR8eXuxhu/Back to the Future Part III (1990) Remux-1080p-TdarrCacheFile-wClKc7deJ.mkv' 📝 What I’ve TriedSet the Tdarr transcode cache folder to /mnt/media/tdarr-cache Added correct path translators between /mnt/media/tdarr-cache on the server and T:/tdarr-cache on the node Restarted both the server and the node Verified that T:/tdarr-cache exists and is writable on the node 🤔 ProblemDespite this setup, the Windows node writes the working files to /tmp/tdarr-workDir..., which is c:\tmp\, and when the move/copy step happens, it fails because the expected transcoded file is missing from the cache — resulting in a 0-byte file in the destination. It seems like the node never actually uses the configured cache path and the transcoding job produces no output file. 💬 Any Ideas?Why is it ignoring the configured cache directory and still writing to /tmp? Is there something else I need to set for a mapped node to use the shared cache folder properly? Any advice would be hugely appreciated — thanks!
-
[Plugin] Spin Down SAS Drives
Thanks Doron for such a quick reply! I'm disabling my plugins one by one, hope to catch the causing this. Also appreciate the additional details on the controller not having to be reflashed and the Seagate drives not spinning down. I'll keep digging.
-
dunee started following [Plugin] Spin Down SAS Drives
-
[Plugin] Spin Down SAS Drives
I can't figure this out on my own. Dec 14 11:44:17 Tower emhttpd: spinning down /dev/sdm Dec 14 11:44:17 Tower emhttpd: spinning down /dev/sdj Dec 14 11:44:17 Tower emhttpd: spinning down /dev/sdk Dec 14 11:44:17 Tower emhttpd: spinning down /dev/sdh Dec 14 11:44:17 Tower emhttpd: spinning down /dev/sdg Dec 14 11:44:17 Tower emhttpd: spinning down /dev/sde Dec 14 11:44:17 Tower emhttpd: spinning down /dev/sdc Dec 14 11:44:17 Tower emhttpd: spinning down /dev/sdl Dec 14 11:44:17 Tower emhttpd: spinning down /dev/sdi Dec 14 11:44:17 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdj Dec 14 11:44:17 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdh Dec 14 11:44:17 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdg Dec 14 11:44:17 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdk Dec 14 11:44:17 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdi Dec 14 11:44:17 Tower SAS Assist v2022.08.02: Spinning down device /dev/sdl Dec 14 11:44:35 Tower emhttpd: read SMART /dev/sdm Dec 14 11:47:54 Tower emhttpd: read SMART /dev/sdg Dec 14 11:48:12 Tower emhttpd: read SMART /dev/sdh Dec 14 11:48:23 Tower emhttpd: read SMART /dev/sdi Dec 14 11:48:36 Tower emhttpd: read SMART /dev/sdj Dec 14 11:48:48 Tower emhttpd: read SMART /dev/sdk Dec 14 11:49:00 Tower emhttpd: read SMART /dev/sdl I have a mixture of SATA and SAS drives. The SATA drives stay spun down, the SAS drives spin up, one after the other, within a few minutes. I've shut down my dockers, this still happens. The open files plugin does not show any files being touched when the drives spin up - especially since the SAS drives have no files on them. root@Tower:~# /usr/local/emhttp/plugins/sas-spindown/sas-util SAS Spindown Utility (v20210201.01) ls: cannot access '/dev/disk/by-path/*-sas-*': No such file or directory Error: No SAS drives detected. Now exiting. root@Tower:~# ls /dev/disk/by-path/ pci-0000:00:1a.0-usb-0:1.2:1.0-scsi-0:0:0:0@ pci-0000:02:00.0-scsi-0:0:12:0-part1@ pci-0000:02:00.0-scsi-0:0:6:0@ pci-0000:00:1a.0-usb-0:1.2:1.0-scsi-0:0:0:0-part1@ pci-0000:02:00.0-scsi-0:0:1:0@ pci-0000:02:00.0-scsi-0:0:6:0-part1@ pci-0000:02:00.0-scsi-0:0:0:0@ pci-0000:02:00.0-scsi-0:0:1:0-part1@ pci-0000:02:00.0-scsi-0:0:7:0@ pci-0000:02:00.0-scsi-0:0:0:0-part1@ pci-0000:02:00.0-scsi-0:0:2:0@ pci-0000:02:00.0-scsi-0:0:7:0-part1@ pci-0000:02:00.0-scsi-0:0:10:0@ pci-0000:02:00.0-scsi-0:0:2:0-part1@ pci-0000:02:00.0-scsi-0:0:8:0@ pci-0000:02:00.0-scsi-0:0:10:0-part1@ pci-0000:02:00.0-scsi-0:0:4:0@ pci-0000:02:00.0-scsi-0:0:8:0-part1@ pci-0000:02:00.0-scsi-0:0:11:0@ pci-0000:02:00.0-scsi-0:0:4:0-part1@ pci-0000:02:00.0-scsi-0:0:9:0@ pci-0000:02:00.0-scsi-0:0:11:0-part1@ pci-0000:02:00.0-scsi-0:0:5:0@ pci-0000:02:00.0-scsi-0:0:9:0-part1@ pci-0000:02:00.0-scsi-0:0:12:0@ pci-0000:02:00.0-scsi-0:0:5:0-part1@ I have an Dell R730xd with an H330 controller in HBA mode (so not flashed to IT mode). Looks like it is presenting all drives as SCSI drives. The recalcitrant SAS drives all appear to be Seagates. Anyone has any ideas on how to fix this? I got an H330 controller so I wouldn't need to flash to IT mode, but at this point I'm seriously considering it. Just worried I'll mess up. Thanks!