December 4, 20214 yr First, I apologize if this is in the wrong location. It has to do with HOW unraid handles moved data within itself, but also with Emby/docker and how it apparently still works after a move which makes no sense. I will try to clarify... backstory: I am in the process of moving my dockers and data from OpenMediaVault to UNRAID and I have a situation with Emby that is kinda stumping me. The location My original share created on unraid array was just "z" (I was copying from a windows machine with a drivepool shared as "z" so I was just keeping it simple. Inside of "z" were folders such as "!Media" (/tv /movies etc inside) as well as "Downlaods", "Documents" and a few other folders. So, I am on a clean, new install of undraid, with essentially nothing going on, and I install an Emby docker. Emby /mnt <--> /mnt/user/z/!Media all was fine... then I used Krusader to MOVE /mnt/user/z/!Media to just /mnt/user/!Media (I decided NOT to keep everything in a subdir called "z" but... everything in emby kept working... but in terminal (or remote connected via WinSCP) the folder at /mnt/user/z shows empty.. no symlinks that I could see, nothing. yet... emby still worked fine (after a full reboot of the unraid box no less). So I verified in the docker settings, yes, still set to /mnt/user/z/!Media which is what I don't understand. so... I play something in emby and it still works.. then I deleted (the empty) "z" folder and then it broke emby (the way I expected it to break when I MOVED all of the content in !Media up one level to the user folder... again... I then just fixed the docker settings and let it rebuid/restart (without the /z in the path) and it works as expected... I just REALLY expected that it would have broke WHEN I moved the data, and need to grok why it did not. TIA to anyone that took the time to read this and explain what I am not understand about the way things work (and maybe even where I should have posted this!) -G
December 6, 20214 yr Best guess (from a non-Emby user), Emby didnt rescan your media library after you moved the files and thus was unaware that anything had changed. Furthermore is it possible that you tried to play a file that you had recently played? If so maybe emby had an already transcoded version in its cache and didnt bother trying to actually read the file?
December 7, 20214 yr Author I appreciate the response, but Emby had scanned the library completely since this was the first time the media had ever been on the server at all... and I purposefully played new content each time one I moved it to the new folder... it acted like some type of symlink or equivalent, since moving the folder !Media from /mnt/user/z/!Media to just /mnt/user/!Media still worked as long as the /mnt/user/z folder was hanging out there (empty from what I could see in terminal and via WinSCP) but as soon as I actually removed the empty "z" folder, emby broke... so I updated the docker with the correct new path and all was well... Its fine that it all works as expected now... I just REALLY feel like I need to understand why it worked to the extent it did... It seems like it should NOT have. -G
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.