#19585011 ReadyDLNA crashing after v4.2.22 & v1.0.25

[TonyKL]

Hi guys,
I've updated my Ultra 4 to firmware version 4.2.22 and ReadyDLNA is 1.0.25 so latest all round.
However, after the factory reset, I restored my Video files only to find that the DLNA (minidlna) is no longer scanning correctly and is crashing out, either with a panic or with floating point error.

It seems the biggest problem is with mpegts files, all these files used to be ok but no longer scan.
I've even tried to run minidlna with -R -d options and watched the output.

I created an empty directly and then copied a normal video file (which is fine) across and that failed too.

2012/09/27 21:33:10] metadata.c:883: debug: Container: 'mpegts'

Anyone got any ideas?

[TonyKL]

I believe if I revert back to 4.2.21 then ReadyDLNA will again work, can anyone confirm this?
Thanks.

[TonyKL]

Downgrade to 4.2.21 fixes the problem for me.

[xstof256]

4.2.22 is bad for my ReadyNAS Ultra2 as well.

After the upgrade, I had the same behaviour as you described above: DLNA scan never finished.
The scan did register the music library and the photo library, but the MPEG-2 library (.TS files) on the share where the ForTheRecord server dumps recorded TV, was invisible to our DLNA compatible TVs and ipads.

Downgrading to 4.2.21 fixed the issue for me as well. I have now deactivated "Automatically check for updates" for the device and will stick with 4.2.21, as streaming recorded TV in TS format is the primary reason why we have the NAS in the first place.

I do hope the developers will fix this issue in some patch (and hope they are reading this thread).

[dsm1212]

Same problem here. This is a horrible bug. Has anyone reported it?

[dsm1212]

I went ahead and submitted case #19585011. Someone can update the title of this issue if they have access. Downgrading fixed it for me too by the way.

[Mika015]

I am having the same issue with my Ultra2 on Radiator 4.2.22 and ReadyDLNA v1.0.25.

Enabling the debug mode on ReadyDLNA showed the media scan consistently ended prematurely on any .MTS or .M2TS video file (most were from my own camera, but some were not).
Moving the offending files out of the scan-folder and a rescan would continue until the next MTS of M2TS file.

For example

[2012/10/28 20:05:22] scanner.c:731: info: Scanning /c/media/media/Pictures/2011_03_22
[2012/10/28 20:05:23] scanner.c:731: info: Scanning /c/media/media/Pictures/2012-06-10
[2012/10/28 20:05:23] metadata.c:883: debug: Container: 'mpegts' [00001.MTS]
[2012/10/28 20:05:40] minissdp.c:351: debug: Sending SSDP notifies
[2012/10/28 20:06:11] minissdp.c:351: debug: Sending SSDP notifies
etc...

and

[2012/10/28 21:39:40] scanner.c:731: info: Scanning /c/media/media/Videos/Movies/Apocalypto
[2012/10/28 21:39:40] metadata.c:241: debug: Parsing .nfo file: /c/media/media/Videos/Movies/Apocalypto/APOCALYPTO.nfo
[2012/10/28 21:39:40] metadata.c:883: debug: Container: 'mpegts' [APOCALYPTO.m2ts]
[2012/10/28 21:40:08] minissdp.c:351: debug: Sending SSDP notifies
[2012/10/28 21:40:39] minissdp.c:351: debug: Sending SSDP notifies
etc...

My previous Radiator (I think v4.2.20) and ReadyDLNA (v1.0.25) version had no problem scanning these.

I have downgraded to Radiator v4.2.21 with v1.0.25 and all is well again:

[2012/10/28 22:33:53] scanner.c:727: warn: Scanning /c/media/media
[2012/10/28 22:33:53] scanner.c:727: info: Scanning /c/media/media/Test
[2012/10/28 22:33:53] metadata.c:853: debug: Container: 'mpegts' [00001.MTS]
[2012/10/28 22:33:53] metadata.c:1282: debug: Stream 0 of 00001.MTS is h.264
[2012/10/28 22:33:53] scanner.c:727: info: Scanning /c/media/media/Test/...

[kylen]

How are you downgrading? Mine automatically upgraded and I don't see a way to download 4.2.21

[mdgm-ntgr]

To downgrade you can follow the instructions to do a local update here: http://www.readynas.com/RAIDiator_x86_4_2_21_Notes

[TonyKL]

Please remember to disable automatic updates otherwise after the downgrade you will find yourself back up to 4.2.22

[mdgm-ntgr]

Update settings can be found under System > Update > Settings in Frontview.

[mwevans]

I'm also suffering from this scanning lockup issue on my PRO Pioneer. I only upgraded to 4.2.22 as it fixed the random power-on problems I was encountering, but guess I will have to revert to 4.2.21 and physically switch the device off whilst the scanning issue is being resolved.

Mark

[rockdj]

Just hit the same issue on my NVX Pioneer with 4.2.22. Any potential issues with downgrading to 4.2.21?

So does anyone know where has this bug been reported? Is it an upstream issue with Minidlna or the ReadyNAS packaging?

EDIT: The 'Scan in progress' button on my admin interface is stuck like this as minidlna crashed during scanning. Anyone know where the flag is to turn this back?
EDIT2: To clear the 'Scan in progress' state, remove the file /ramfs/.upnp-av_scan. 🙂

[dpk]

rockdj wrote:
Just hit the same issue on my NVX Pioneer with 4.2.22. Any potential issues with downgrading to 4.2.21? So does anyone know where has this bug been reported? Is it an upstream issue with Minidlna or the ReadyNAS packaging? EDIT: The 'Scan in progress' button on my admin interface is stuck like this as minidlna crashed during scanning. Anyone know where the flag is to turn this back?

Could you please start a support ticket with Netgear. We would have to verify whether this indeed is a bug and if so we would like to take a look at your settings so that we can reproduce the scenario.

[dsm1212]

Wait a minute 19585011 was my submission for this. It was pretty clear what happened and I thought you had all the info you needed. Are you saying you resolved the ticket just because I downgraded but didn't have what you needed to fix the problem? It's very easy to reproduce. Get your hands on any .m2ts file and let the minidlna server in 4.2.22 scan it. It will crash on that file.

[jlaptops]

I appear to have the same problem as the OP. New case submitted as 19837731 awaiting response.

I bought my Ultra 2 a few weeks ago specifically to put a pair of 3Tb drives into it - when received it didnt detect them since the firmware was outdated. Latest RAIDiator 4.2.22 installed and disks work fine, but included in the new firmware was ReadyDLNA 1.0.25 and so my media scan is stuck 'in progress' so I can't see a way to revert back to an older ReadyDLNA without reverting to an older RAIDiator which then would mean my disks don't work... thus leaving the whole point of my purchase pointless!

[StephenB]

You should be able to downgrade to 4.2.21, as all versions since 4.2.16 have supported 3 TB drives.

[rockdj]

jlaptops wrote:
I appear to have the same problem as the OP. New case submitted as 19837731 awaiting response.

I'm sure you will, but please let us know the details of the response. Thanks!

If necessary, I'll submit an issue as well, but since it's exactly the same, surely that's unnecessary.

[sdouek]

bump ... any progress yet ???

[xstof256]

sdouek wrote:
bump ... any progress yet ???

Doesn't seem so, since the latest available firmware at NetGear is still the broken 4.2.22.

[pfzone]

Found some kind of solution for you, as Netgear seems to ignore the problem :
Just get a static version of minidlna to replace the current broken on. I suspect Netgear broke some libraries needed by minidlna in the current 4.2.22. A static compiled version doesn't need thoses libraries as they are embedded in the binary file. So it is bigger (much bigger), may not be fully compatible, but it may works.

Some tradeoff though (better than nothing). If you take the 1.0.25 version, you have segmentation fault when parse malformed mkv. It doesn't happen when you use 1.0.24. But first scan find 10% of my files only. You have to trigger inotify (by renaming folders) to force rescan of dirs.

Hopefully, minidlna is provided with sources AND a static version. Just follow thoses steps

First, backup.

cp /usr/sbin/minidlna /usr/sbin/minidlna_rdn

Then get the file from sourceforge, untar it then move it to replace the old one.

wget http://sourceforge.net/projects/minidlna/files/minidlna/1.0.24/minidlna_1.0.24_static.tar.gz
tar -xf minidlna_1.0.24_static.tar.gz

First test if everythings OK. Start minidlna in debugging mode, show lots of stuff but you might find what's not working if it's the case.

./minidlna -R -d

Replace

mv usr/sbin/minidlna /usr/sbin/minidlna

If you want to clean up (be careful) :

rm -r usr etc minidlna_1.0.24_static.tar.gz

Finally, stop and start the service from the web panel (Services>Streaming Services). Untick, apply, tick.

:x What I hate about this situation :
minidlna has been developed by and for Netgear products. Not doing anything about what could bring this NAS a good multi purposes platform is a big shame.
minidlna is your product you don't even test it, nor want to fix it ? Telling people to downgrade to fix it ?? Seriously !

Everything I need to achieve with my NAS need to be done by hosting multiple vbox, which doesn't cope well with bridge on bonded interface, but doing stuff the nas just can't do. First because it's a Debian etch (dinosaurs were not extinct yet), so nothing (almost recent) can compile without hassle, then because simple nothing is usable out of the box ! Lamp is outdated like hell, Mysql is ... well... and any useful "module" is hosted by some guy needing funds for that ! Seriously ....

Ok, I paid for a NAS, not a web server, but hey ! Please Netgear, have some consideration for people paying more than 1000$ a box that do... nothing but storing bytes... Look at your competitors ! LVM and soft RAID alone won't help you this time.

Thank you.
An IT pissed of losing his time on such small pb.