Forum Discussion
chokobanana
Jul 31, 2013Guide
ReadyDLNA does not find all files (dirs, files missing)
Hi, I just recently purchased a RN102 (6.0.8 ) and loaded all my media files onto it. It's been on for a few days now so any DLNA indexing services should have had more than enough time to finish.. h...
- Aug 02, 2015
You are responding a 2 year-old thread (and I suspect the bug being referred to has already been fixed).
There is no need to use SSH to force a rescan. Just use the rescan button in the web ui.
chokobanana
Aug 03, 2013Guide
I really need to get the DLNA shares working so that I can start using my RN 102 as intended to.
I logged in via SSH and did this:
$ find -name *dlna*
/lib/systemd/system/minidlna.service
/data/.apps/.readydlna
the app data is located in "/data/.apps/.readydlna"
$ ls -l /data/.apps/.readydlna
drwxr-xr-x 1 root root 16 Jul 27 16:50 art_cache
-rw-r--r-- 1 root root 100937728 Aug 3 21:27 files.db
"files.db" is an SQLite DB with the file structure.
I did a copy of it and opened the DB with SQLite Database Browser. In the Object table I then did a search for a photo I know doesn't show up - there is no entry for that file - which means the file has not been indexed into the database. No wonder it doesn't show up.
"/lib/systemd/system/minidlna.service" tells us where the executable is:
[Service]
ExecStart=/usr/sbin/minidlnad -S
So I executed:
$ /usr/sbin/minidlnad -h
Usage:
/usr/sbin/minidlnad [-d] [-v] [-f config_file] [-p port]
[-s serial] [-m model_number]
[-t notify_interval] [-P pid_filename]
[-u uid_to_run_as]
[-w url] [-R] [-V] [-h]
Notes:
Notify interval is in seconds. Default is 895 seconds.
Default pid file is /var/run/minidlna/minidlna.pid.
With -d minidlna will run in debug mode (not daemonize).
-w sets the presentation url. Default is http address on port 80
-h displays this text
-R forces a full rescan
-L do note create playlists
-S changes behaviour for systemd
-V print the version number
Here it's possible to force a rescan. So next I did:
$ systemctl stop minidlna
$ /usr/sbin/minidlnad -S -R
The "-R" is for rebuilding the DB.
The deamon then output:
minidlna.c:972: warn: Starting ReadyDLNA version 1.1.0.
minidlna.c:353: warn: Creating new database at /apps/.readydlna/files.db
minidlna.c:1012: warn: HTTP listening on port 8200
scanner.c:766: warn: Scanning /memories/Music finished (x files)!
scanner.c:690: warn: Scanning /memories/Photos
scanner.c:766: warn: Scanning /memories/Photos finished (x files)!
scanner.c:690: warn: Scanning /memories/Videos
scanner.c:690: warn: Scanning /memories/Videos
scanner.c:766: warn: Scanning /memories/Videos finished (x files)!
playlist.c:125: warn: Parsing playlists…
playlist.c:256: warn: Finished parsing playlists.
This took about 30 min to complete (about 60.000 files)
The DB file increased in size:
drwxr-xr-x 1 root root 16 Aug 3 22:27 art_cache
-rw-r--r-- 1 root root 105984000 Aug 3 22:54 files.db
.. and all the files that I was missing now appeared! :D
There's still a bug in there though.. the auto/rescan function does NOT work as it should. And the manual button makes absolutely no sense. At least write in the log that something is happening.
I logged in via SSH and did this:
$ find -name *dlna*
/lib/systemd/system/minidlna.service
/data/.apps/.readydlna
the app data is located in "/data/.apps/.readydlna"
$ ls -l /data/.apps/.readydlna
drwxr-xr-x 1 root root 16 Jul 27 16:50 art_cache
-rw-r--r-- 1 root root 100937728 Aug 3 21:27 files.db
"files.db" is an SQLite DB with the file structure.
I did a copy of it and opened the DB with SQLite Database Browser. In the Object table I then did a search for a photo I know doesn't show up - there is no entry for that file - which means the file has not been indexed into the database. No wonder it doesn't show up.
"/lib/systemd/system/minidlna.service" tells us where the executable is:
[Service]
ExecStart=/usr/sbin/minidlnad -S
So I executed:
$ /usr/sbin/minidlnad -h
Usage:
/usr/sbin/minidlnad [-d] [-v] [-f config_file] [-p port]
[-s serial] [-m model_number]
[-t notify_interval] [-P pid_filename]
[-u uid_to_run_as]
[-w url] [-R] [-V] [-h]
Notes:
Notify interval is in seconds. Default is 895 seconds.
Default pid file is /var/run/minidlna/minidlna.pid.
With -d minidlna will run in debug mode (not daemonize).
-w sets the presentation url. Default is http address on port 80
-h displays this text
-R forces a full rescan
-L do note create playlists
-S changes behaviour for systemd
-V print the version number
Here it's possible to force a rescan. So next I did:
$ systemctl stop minidlna
$ /usr/sbin/minidlnad -S -R
The "-R" is for rebuilding the DB.
The deamon then output:
minidlna.c:972: warn: Starting ReadyDLNA version 1.1.0.
minidlna.c:353: warn: Creating new database at /apps/.readydlna/files.db
minidlna.c:1012: warn: HTTP listening on port 8200
scanner.c:766: warn: Scanning /memories/Music finished (x files)!
scanner.c:690: warn: Scanning /memories/Photos
scanner.c:766: warn: Scanning /memories/Photos finished (x files)!
scanner.c:690: warn: Scanning /memories/Videos
scanner.c:690: warn: Scanning /memories/Videos
scanner.c:766: warn: Scanning /memories/Videos finished (x files)!
playlist.c:125: warn: Parsing playlists…
playlist.c:256: warn: Finished parsing playlists.
This took about 30 min to complete (about 60.000 files)
The DB file increased in size:
drwxr-xr-x 1 root root 16 Aug 3 22:27 art_cache
-rw-r--r-- 1 root root 105984000 Aug 3 22:54 files.db
.. and all the files that I was missing now appeared! :D
There's still a bug in there though.. the auto/rescan function does NOT work as it should. And the manual button makes absolutely no sense. At least write in the log that something is happening.
- hovisheadAug 01, 2015Aspirant
Chokobanana, thank you for posting the below, sadly I am a SSH/linux/unix (I don't even know what OS it is!) newbie, so have tried to follow the instructions, but am stuck. I expect I am making a simple mistake and hope you can help!!!
I have a MS2110 Netgear NAS, and have managed to SSH in to root access, and I was able to search for the minidlna process, and also got similar from the help file (no "-S changes behaviour for systemd", but the rest was the same word for word), as below:
"Usage:
/usr/sbin/minidlna [-d] [-f config_file]
[-a listening_ip] [-p port]
[-s serial] [-m model_number]
[-t notify_interval] [-P pid_filename]
[-w url] [-R] [-V] [-h]
Notes:
Notify interval is in seconds. Default is 895 seconds.
Default pid file is /var/run/minidlna.pid.
With -d minidlna will run in debug mode (not daemonize).
-w sets the presentation url. Default is http address on port 80
-h displays this text
-R forces a full rescan
-V print the version number"I've tried to force a full rescan with the below command:
bash-3.2# /usr/sbin/minidlna -R
but all that happens is the help opens again. I notice you used $ systemctl stop minidlna to stop the process, but systemctl doesn't appear to be a command in my version. Instead I've tried rebooting the NAS figuring that would stop the process and I could try to start the full rescan command on a clean boot, but this also had the same effect of opening the help rather than rescanning.
I've tried:
/usr/sbin/minidlnad -R
/usr/sbin/minidlna -d -R
and other variations with no luck
Can you tell me what I am doing wrong please? What do I need to type into the terminal to force a rescan?
Many thanks!!!
- StephenBAug 02, 2015Guru - Experienced User
You are responding a 2 year-old thread (and I suspect the bug being referred to has already been fixed).
There is no need to use SSH to force a rescan. Just use the rescan button in the web ui.
- kohdeeFeb 01, 2016Administrator
hovishead wrote:
I have a MS2110 Netgear NAS, and have managed to SSH in to root access, and I was able to search for the minidlna process, and also got similar from the help file (no "-S changes behaviour for systemd", but the rest was the same word for word), as below:
Storas are pretty old now and haven't been updated in quite some time -- maybe you could consider upgrading to a newer NAS :)
I'm closing this thread as there's a solution. Please open a new thread if necessary.
- StephenBFeb 01, 2016Guru - Experienced User
kohdee wrote:
hovishead wrote:
I have a MS2110 Netgear NAS, and have managed to SSH in to root access, and I was able to search for the minidlna process, and also got similar from the help file (no "-S changes behaviour for systemd", but the rest was the same word for word), as below:
Storas are pretty old now and haven't been updated in quite some time -- maybe you could consider upgrading to a newer NAS :)
Stora has its sub-forum. If you have issues with the Stora, post them at https://community.netgear.com/t5/Stora-Legacy/bd-p/stora?topic-zoom=&sort-by=&date-range=all
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!