INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: "file could not be found" error  (Read 3414 times)

TheGreatBiguini

  • Junior Woodchuck
  • **
  • Posts: 50
"file could not be found" error
« on: October 08, 2015, 09:27:48 am »

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!
Logged

TheGreatBiguini

  • Junior Woodchuck
  • **
  • Posts: 50
Re: "file could not be found" error
« Reply #1 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.
Logged

blgentry

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 8009
Re: "file could not be found" error
« Reply #2 on: October 08, 2015, 03:10:20 pm »

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.
Logged

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2554
Re: "file could not be found" error
« Reply #3 on: October 08, 2015, 04:09:01 pm »

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.

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

blgentry

  • Regular Member
  • Citizen of the Universe
  • *****
  • Posts: 8009
Re: "file could not be found" error
« Reply #4 on: October 08, 2015, 04:20:31 pm »

^ 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.
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7367
  • The color of Spring...
Re: "file could not be found" error
« Reply #5 on: October 08, 2015, 05:01:33 pm »

Does Linux Mint include Disks? I know Ubuntu does and that's what I use to auto-mount volumes on boot.
Logged
I don't work for JRiver... I help keep the forums safe from Viagra and other sources of sketchy pharmaceuticals.

Windows 11 2023 Update (23H2) 64-bit + Ubuntu 24.04 LTS Noble Numbat 64-bit | Windows 11 2023 Update (23H2) 64-bit (Intel N305 Fanless NUC 16GB RAM/256GB NVMe SSD)
JRiver Media Center 32 (Windows + Linux) | Topping D50s DAC | Edifier R2000DB Bookshelf Speakers

st1

  • Recent member
  • *
  • Posts: 30
Re: "file could not be found" error
« Reply #6 on: October 16, 2015, 03:38:50 am »

Logged

TheGreatBiguini

  • Junior Woodchuck
  • **
  • Posts: 50
Re: "file could not be found" error
« Reply #7 on: October 22, 2015, 12:50:27 pm »

Thanks everybody - I am pretty much a newbie to Linux, in case it wasn't obvious, so am still figuring this stuff out. Am away from that machine now for a few weeks but I will re-address the issue when i get back. In any case, now that I know what's going on, it's not a big deal, though I would still like to find a workaround...
Logged
Pages: [1]   Go Up