NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
DaveJF
Nov 12, 2024Aspirant
ReadyNAS 104 Disks thrashing
I have a ReadyNAS 104 at home and I often only access it in the evenings. Normally the unit has gone into standby mode and there is no disk activity. Almost every time I go to use my PC the disks are...
DaveJF
Nov 21, 2024Aspirant
"allow snapshot access" was checked on most shares. So I have unchecked as per you recommendation.
I had another period of 6 hours of disk thrashing earlier in the week. At that time there were log references to possibly corrupt video file. The full set of errors is
Nov 17 00:03:58 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] start time for stream 2 is not set in estimate_timings_from_pts
Nov 17 00:03:58 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] Could not find codec parameters for stream 1 (Audio: pcm_dvd, 0 channels): unspecified sample rate
Nov 17 00:03:58 NRN1 minidlnad[29030]: Consider increasing the value for the 'analyzeduration' and 'probesize' options
Nov 17 00:03:58 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] start time for stream 0 is not set in estimate_timings_from_pts
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] start time for stream 0 is not set in estimate_timings_from_pts
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] start time for stream 0 is not set in estimate_timings_from_pts
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] Could not find codec parameters for stream 2 (Audio: pcm_dvd, 0 channels): unspecified sample rate
Nov 17 00:03:59 NRN1 minidlnad[29030]: Consider increasing the value for the 'analyzeduration' and 'probesize' options
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg2video @ 0xb4251500] Invalid frame dimensions 0x0.
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg2video @ 0xb4251500] Invalid frame dimensions 0x0
Unfortunately no filename is mentioned. Is it likely this is in one of the other log files?
Also, is it OK just to delete browse through the UI and delete old snapshots manually?
Many thanks for your continued help.
Dave
StephenB
Nov 21, 2024Guru - Experienced User
DaveJF wrote:
Also, is it OK just to delete browse through the UI and delete old snapshots manually?
Yes. Though personally I found that to be tedious to maintain, which is why I recommend using custom snapshots with limited retention.
DaveJF wrote:
"allow snapshot access" was checked on most shares. So I have unchecked as per you recommendation.
I had another period of 6 hours of disk thrashing earlier in the week. At that time there were log references to possibly corrupt video file. The full set of errors is
Nov 17 00:03:58 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] start time for stream 2 is not set in estimate_timings_from_pts
Nov 17 00:03:58 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] Could not find codec parameters for stream 1 (Audio: pcm_dvd, 0 channels): unspecified sample rate
Nov 17 00:03:58 NRN1 minidlnad[29030]: Consider increasing the value for the 'analyzeduration' and 'probesize' options
Nov 17 00:03:58 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] start time for stream 0 is not set in estimate_timings_from_pts
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] start time for stream 0 is not set in estimate_timings_from_pts
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] start time for stream 0 is not set in estimate_timings_from_pts
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg @ 0xb44ffa70] Could not find codec parameters for stream 2 (Audio: pcm_dvd, 0 channels): unspecified sample rate
Nov 17 00:03:59 NRN1 minidlnad[29030]: Consider increasing the value for the 'analyzeduration' and 'probesize' options
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg2video @ 0xb4251500] Invalid frame dimensions 0x0.
Nov 17 00:03:59 NRN1 minidlnad[29030]: [mpeg2video @ 0xb4251500] Invalid frame dimensions 0x0
Unfortunately no filename is mentioned. Is it likely this is in one of the other log files?
Did you see other timestamps, or only 03:58 and 03:59? If this were the cause of the thrashing, you'd expect to see timestamps covering the full 6 hour period.
There was a debug toggle for DLNA in OS-4 systems, but unfortunately that was dropped with OS-6.
One option (tedious) is to create a temporary share, and move half of the media files into it. Then rescan. If the problem disappears, then the problem is with one of the files you moved. If you repeat that process, you can narrow down the number of files that might be the cause, until you find it.
This looks like it might be an mpg2 dvd rip, which might also help narrow it down.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!