More > JRiver Media Center 27 for Mac
Just installed NAS, MC doesn't work properly
macdonjh:
I just installed a QNAP NAS. Our NAS is connected via ethernet cable to our wireless router. My Mac Mini is also connected to our router via an ethernet cable. I have connection/ communication with the internet and the NAS. I've started a new library, mapping to the folders on the NAS as the source of my media files.
Here's my problem: I configured Auto Import and started it. MC imports a few hundred of the thousands of files and then "stops responding suddenly" (my Mini's "words"). I've restarted MC and restarted Import several times with the same result.
Does anyone know why Auto Import or Import won't work properly across our network (that's a grand word for the hardware we have)?
HaWi:
--- Quote from: macdonjh on August 04, 2021, 07:52:31 pm ---I just installed a QNAP NAS. Our NAS is connected via ethernet cable to our wireless router. My Mac Mini is also connected to our router via an ethernet cable. I have connection/ communication with the internet and the NAS. I've started a new library, mapping to the folders on the NAS as the source of my media files.
Here's my problem: I configured Auto Import and started it. MC imports a few hundred of the thousands of files and then "stops responding suddenly" (my Mini's "words"). I've restarted MC and restarted Import several times with the same result.
Does anyone know why Auto Import or Import won't work properly across our network (that's a grand word for the hardware we have)?
--- End quote ---
What is your OS? How do you access the media folder on your NAS from the Mac? SMB? NFS?
There could be stability issues and your shared folder is dropped from the Mac and that leads to the process being interrupted. I have had issues like that before. I found that using NFS to mount the media folder is more stable but I also employ ConnectMeNow to remount the share automatically when it gets dropped.
EDIT: Typo
bob:
Someone reported a similar issue, specific to the M1.
Would you try disabling the auto-imports then doing the import manually by doing the "Import a Single Folder" function at the top level of your desired folder of imports and report back?
This will isolate one of the variables in the process.
Thanks.
macdonjh:
HaWi, my operating system is OSX, I just updated from Catalina to Big Sur last night. I had this trouble yesterday with Catalina and I have it today with Big Sur. I have no idea what protocol is being used to transfer or access files from the NAS. I can ask QNAP tech support.
Bob, I will do that. I currently have auto-import configured to import from four or five sub-folders of the same main folder on the NAS. Just a point of clarification, I've had no trouble for the past several years with external, USB-connected hard drives. This new NAS is giving me fits. I'm glad IT isn't my day job.
bob:
--- Quote from: macdonjh on August 05, 2021, 09:17:44 pm ---HaWi, my operating system is OSX, I just updated from Catalina to Big Sur last night. I had this trouble yesterday with Catalina and I have it today with Big Sur. I have no idea what protocol is being used to transfer or access files from the NAS. I can ask QNAP tech support.
Bob, I will do that. I currently have auto-import configured to import from four or five sub-folders of the same main folder on the NAS. Just a point of clarification, I've had no trouble for the past several years with external, USB-connected hard drives. This new NAS is giving me fits. I'm glad IT isn't my day job.
--- End quote ---
Something you might want to check is whether you are connecting with APFS or SMB/CIFS.
APFS might try to support file change notification. I'm almost certain SMB cannot.
Since NAS APFS support is open source software and is absolutely not free of errors you might have uncovered a bug in it.
MC uses file notification to watch for changes on supported filesystems when you have it setup to auto-import.
Navigation
[0] Message Index
[#] Next page
Go to full version