ReadyNAS RN312 Diagnostic Errors ffdetect segfault

[michaeldowns]

Hello,

RN312 Firmware 6.10.2-T49

NAS went offline, had to reboot, then it went into resync mode estimated to take 38 hours!

I checked Diagnostics and found logs data shows error 4. See below (I truncated the number of lines).

The HDDs show no SMART errors.

What is the issue?

Beta bug?

Thanks,

mdd

Successfully completed diagnostics

System

• No errors found.

Logs

• 2019-10-02 12:30:51: ffdetect[3733]: segfault at 38 ip 00000000004042af sp 00007ffc4158e260 error 4 in ffdetect[403000+c000]
• 2019-10-02 12:30:50: ffdetect[3726]: segfault at 38 ip 00000000004042af sp 00007ffefb78b6a0 error 4 in ffdetect[403000+c000]
• 2019-09-08 17:46:26: ffdetect[4168]: segfault at 38 ip 00000000004042af sp 00007ffca191aff0 error 4 in ffdetect[403000+c000]
• 2019-09-08 17:46:26: ffdetect[4172]: segfault at 38 ip 00000000004042af sp 00007ffc244d1b70 error 4 in ffdetect[403000+c000]
• 2019-09-08 17:32:48: ffdetect[3854]: segfault at 38 ip 00000000004042af sp 00007ffff8d37dc0 error 4 in ffdetect[403000+c000]
• 2019-09-08 17:32:48: ffdetect[3856]: segfault at 38 ip 00000000004042af sp 00007fff8d2fab60 error 4 in ffdetect[403000+c000]
• 2019-09-03 16:26:14: ffdetect[31577]: segfault at 38 ip 00000000004042af sp 00007fff15791970 error 4 in ffdetect[403000+c000]
• 2019-09-03 16:26:14: ffdetect[31578]: segfault at 38 ip 00000000004042af sp 00007ffdb06bdde0 error 4 in ffdetect[403000+c000]
• 2019-09-02 14:07:30: ffdetect[4370]: segfault at 38 ip 00000000004042af sp 00007ffdef8e67b0 error 4 in ffdetect[403000+c000]
• 2019-09-02 14:07:30: ffdetect[4371]: segfault at 38 ip 00000000004042af sp 00007ffec9f95990 error 4

[JohnCM_S]

Hi michaeldowns,

Can you download the NAS system logs then provide it to us? We will check what caused the issue. You may do that by uploading it to a file-sharing site then send the download link via PM (private message).

Regards,

[JohnCM_S]

Hi michaeldowns,

I checked what is ffdetect and it appears to be related to Emby. 

The segfault is a memory access violation. It seems that a program, which is Emby, is accessing a memory address outside of its scope.

Regards,

[michaeldowns]

Hi John,

Thanks for this information.

How did you find this?

Do you have a special tool for examining the diagnostic logs.

Please let me know what log file has this information or other means of finding this myself.

Also, is this memory fault what caused the NAS to lock-up and require a reboot?

Since this did not happen with the previous OS is it a Beta OS bug?