More > JRiver Media Center 21 for Linux

"file could not be found" error

(1/2) > >>

TheGreatBiguini:
Running MC 20 and 21 on Linux Mint, having the same problem with both versions. My files are in a directory on a second drive named D. Drive is permanently installed in the machine, it is not a USB, network, or external drive. I import the files into the main library and it works. However, each time I re-start the machine I need to re-import the library or I get the "File could not be found, check that the filename in the library matches the file name on disk" error. The files are present and have not moved, and I can browse to them, but MC does not see them. If I re-import it works, until the next reboot. TIA for any advice you can give me!

TheGreatBiguini:
I see what's going on, or rather what isn't - looks like the OS isn't auto-mounting the second physical drive, and thus MC does not initially see it. If I boot up, manually browse to drive D, and then open Media Center, then it works. So this is not a big deal of course, and not really a J River issue as such, but if anyone can tell me how to find a workaround that happens automagically I'd appreciate it. Tried running an xdg-open command at startup but it doesn't seem to work.

blgentry:
You need to auto mount that disk at startup.  There seem to be several ways of doing this in Linux Mint.  Do a google search and you'll probably find one that works for you.  Then reboot and test to see if the disk is mounted and MC can see the files.

Good luck.

Brian.

BryanC:

--- Quote from: TheGreatBiguini on October 08, 2015, 10:01:43 am ---I see what's going on, or rather what isn't - looks like the OS isn't auto-mounting the second physical drive, and thus MC does not initially see it. If I boot up, manually browse to drive D, and then open Media Center, then it works. So this is not a big deal of course, and not really a J River issue as such, but if anyone can tell me how to find a workaround that happens automagically I'd appreciate it. Tried running an xdg-open command at startup but it doesn't seem to work.

--- End quote ---

Editing fstab has always worked for me. The newer methods have been hit or miss.

blgentry:
^ Yeah, but did you use vi to do it?   I heard it doesn't work if you don't.













(This is humor in case something thinks I'm serious)

Brian.

Navigation

[0] Message Index

[#] Next page