readydlna v4.2.22 & v1.0.25 scan in progress stuck

Here is a snap shot of the Pro DLNA button in frontview not finishing

Wow its not like no one to have an answer or point me in the right direction, haven't been on the forum for a while, didn't know it changed so much.

Anyone can help ????

Skywalker ?
Chirpa ?
Bueller :) ?

You could try downgrading to 4.2.21 and doing a full rescan

I did that, still same issue, I posted what I did in the main post.

I even downgraded the OS and dlna still have same problem,
upgraded back to OS 4.2.22 & 1.0.25 still have same problem,
and downgraded to dlna v 1.0.24.5 same problem

OK so I had to downgrade 4.2.21 to fix this.

1) In frontview go to "Streaming Services" and uncheck the following:
******* a) Automatically update database.
******* b) ReadyDLNA, enables playback of videos, music and pictures from DLNA/UPnP AV network media players.
2) Make sure both boxes are empty and then hit apply. (I initially did not do this and this is why my first downgrade did not work)
3) Reboot
4) Downgrade your OS to 4.2.21.
5) After downgrade is finished clear your browser cache.
6) Log back into frontview.
7) In frontview go to "Streaming Services" and only check "ReadyDLNA, enables playback of videos, music and pictures from DLNA/UPnP AV network media players." box and hit apply.
'8) It took my NAS pro about 17 minutes to finish scanning and build the database. It may take longer for some I would give it a hour. (or you can check to see if DLNA is finished or still working by SSH into you box and check to see if the file located at /var/cache/minidlna/files.db is still updating, I use WINCP, this is only recommended for experts).
9) Eventually the DLNA will finish re-building the db file and then you can upgrade to DLNA version 1.0.25.
10) In frontview go to "Streaming Services" Click on the "Rescan Media Files" button, repeat step "8"
11) Eventually the DLNA will finish re-building the db file and then you can go into frontview - streaming services and check the automatic update database box.

There now you have OS 4.2.21 and DLNA 1.0.25 working.

It seems that OS 4.2.22 has changed the way it interacts with DLNA.
Once I was finished with fixing my DLNA I disabled my DLNA and upgraded to OS 4.2.22 and then downgraded my DLNA to 1.0.24.5 and when I activated the DLNA I still encounter the same problem as I did with OS 4.2.22 and DLNA 1.0.25.

If anyone from netgear support is reading this please check OS 4.2.22 for any changes that may have an affect on DLNA and post a fix.

Thank You !

Hopefully they will fix this issue in 4.2.23

I had this very same issue. Im rolled back to 4.2.21 and problem solved. Until Netgear document that this issue is fixed I wont upgrade the Readynas Firmware. 4.2.22 was released in September so hopefully it will get fixed soon.

Thanx sdouek for your tutorial.
Anyway probably the thing is more complex.
I had the same issue on a Ultra 2 Plus and followed your instructions step by step (I'm sure I've followed them correctly).
The problem remains after two re-installs of 4.2.21 (in frontview the scan in progress button stays greyed out).
Moreover the scanning is incomplete: I can only see a part of my music files (even after repeated scans the files I can see from my network with various dnla/upnp clients are always the same: a small part). This probably means that the dlna/upnp scan process stops when the process meets an indigestible file (even with 4.2.21).
This is a serious bug.
The use of a nas , infact, is stricly connected with the dnla/upnp function.
Hope the next release will works better with dnla

Hello

A bit "me too!", but I have just been bitten by this problem.

Dec 23 16:25:06 nas kernel: minidlna[29540] trap divide error ip:80664d0 sp:ff9c1260 error:0 in minidlna[8048000+42000]
Dec 23 17:10:35 nas kernel: minidlna[1674] trap divide error ip:80664d0 sp:ff8510d0 error:0 in minidlna[8048000+42000]
Dec 23 17:13:39 nas kernel: minidlna[2440] trap divide error ip:8066480 sp:fff93df0 error:0 in minidlna[8048000+42000]
Dec 23 17:21:54 nas kernel: minidlna[3016] trap divide error ip:8066480 sp:ffed0f90 error:0 in minidlna[8048000+42000]

Downgrading to .21 does appear to have "fixed" it.

Regards

Martin A. Brooks