ReadyData 5200 OS6 6.9.5 Freezeing , kernell panic

[Alein]

Hi,

since upgrading the new firmware to 6.9.5 , I have a lot of freezes.

One  I was able to catch on a console with information about kernel panic, 2nd one just happens. 

I would like support to check the logs and perhaps there is a simple solution.

Also, a long time ago I had encrypted volume. Today I saw, that OS is still trying to mount it. But it was correctly removed.

[Marc_V]

Hi @Alein

RD5200 is not running OS6 FW. You can always contact Support for ReadyData issues so the experts will be able to assist you especially if it needs escalation.

You can login to my.netgear.com with the account that you have registered your RD5200 with and create a case.

Regards

[Alein]

Marck,

I think, that I know what OS version  I use for years.

I only removed 4 last digits from the serial number.

[Marc_V]

Hi @Alein

I see so you have converted the OS to ReadyNAS OS 6. Unfortunately, this conversion is not supported by NETGEAR and will not be assisted through Support. However, the community is here to help.

Regarding the issue you may want to send us a link to download your logs, (Google drive)

Regards

[Alein]

OK 

https://mega.nz/#!W4xllSRT!88E_qAittRCmOENHCv8RfT2PwaWIJuyjrRxK2qzXrnU
https://mega.nz/#!mghHEIBa!urZ09k8m6I2jWBmEanuty6ThAvTlh42cLlhoYk7jXxc 

[StephenB]

@Alein wrote:

OK 

https://mega.nz/#!W4xllSRT!88E_qAittRCmOENHCv8RfT2PwaWIJuyjrRxK2qzXrnU
https://mega.nz/#!mghHEIBa!urZ09k8m6I2jWBmEanuty6ThAvTlh42cLlhoYk7jXxc 

---

There are some hardware issues being reported

Feb 25 15:31:47 NAS-X readynasd[6955]: 3VSB voltage in enclosure Internal is out of spec. (0.00 V).
Feb 25 19:20:17 NAS-X readynasd[6955]: 3VSB voltage in enclosure Internal is out of spec. (0.26 V).
Feb 25 19:20:17 NAS-X readynasd[6955]: Vbat voltage in enclosure Internal is out of spec. (4.08 V).

...
Feb 26 01:10:49 NAS-X readynasd[6955]: AVCC voltage in enclosure Internal is out of spec. (0.00 V).
Feb 26 01:45:18 NAS-X readynasd[6955]: System temperature in enclosure Internal exceeded safety threshold. (110 C).

...

Mar 01 01:58:01 NAS-X readynasd[6955]: +3.3V voltage in enclosure Internal is out of spec. (0.00 V).
Mar 01 15:14:32 NAS-X readynasd[6955]: AVCC voltage in enclosure Internal is out of spec. (0.00 V).
Mar 01 21:44:28 NAS-X readynasd[6955]: 3VSB voltage in enclosure Internal is out of spec. (0.08 V).
Mar 02 20:58:59 NAS-X readynasd[6955]: Fan System in enclosure Internal speed is below threshold. (373 rpm).

Mar 03 05:47:12 NAS-X readynasd[6955]: 3VSB voltage in enclosure Internal is out of spec. (0.53 V).
Mar 03 05:47:12 NAS-X readynasd[6955]: Vbat voltage in enclosure Internal is out of spec. (2.05 V).
Mar 03 09:24:59 NAS-X readynasd[6955]: Fan System in enclosure Internal speed is below threshold. (186 rpm).

Mar 03 15:42:42 NAS-X readynasd[6955]: 3VSB voltage in enclosure Internal is out of spec. (0.08 V).
Mar 03 16:25:44 NAS-X readynasd[6955]: Fan System in enclosure Internal speed is below threshold. (186 rpm).

Looks like there is also something wrong with iscsi.

[Sat Feb 16 16:44:33 2019] Unable to load target_core_iblock
[Sat Feb 16 16:44:33 2019] Unable to load target_core_pscsi
[Sat Feb 16 16:44:33 2019] Unable to load target_core_user
[Sat Feb 16 16:44:35 2019] FILEIO: Thin LUN /Purple/UFB/.iscsi/iscsi_lun_backing_store used blocks exceeded [2061583974]
[Sat Feb 16 16:44:36 2019] nfsd: last server has exited, flushing export cache
[Sat Feb 16 16:44:36 2019] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[Sat Feb 16 16:44:36 2019] NFSD: starting 90-second grace period (net ffffffff88d5f440)
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Found referenced iSCSI task_tag: 17392823
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 17392823
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Found referenced iSCSI task_tag: 17392824
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 17392824
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Found referenced iSCSI task_tag: 17392825
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 17392825
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Found referenced iSCSI task_tag: 17392826
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 17392826
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Found referenced iSCSI task_tag: 17392823
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 17392823
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Found referenced iSCSI task_tag: 17392824
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 17392824
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Found referenced iSCSI task_tag: 17392825
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 17392825
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Found referenced iSCSI task_tag: 17392827
[Sat Feb 16 16:45:35 2019] ABORT_TASK: Sending TMR_TASK_DOES_NOT_EXIST for ref_tag: 17392827
[Sat Feb 16 16:47:50 2019] iSCSI Login timeout on Network Portal 192.168.244.10:3260

[Tue Mar  5 09:38:10 2019] Unable to load target_core_iblock
[Tue Mar  5 09:38:10 2019] Unable to load target_core_pscsi
[Tue Mar  5 09:38:10 2019] Unable to load target_core_user
[Tue Mar  5 09:38:12 2019] FILEIO: Thin LUN /Purple/UFB/.iscsi/iscsi_lun_backing_store used blocks exceeded [2061583974]
[Tue Mar  5 09:38:12 2019] Detected MISCOMPARE for addr: ffff8800af284000 buf: ffff8800b3ac9200
[Tue Mar  5 09:38:12 2019] Target/fileio: Send MISCOMPARE check condition and sense
[Tue Mar  5 09:38:13 2019] nfsd: last server has exited, flushing export cache

There are other errors in readynas.log and system.log.

I don't know what the root cause here is, or what is needed to fix it.  Have you seen the hardware faults before?

[Alein]

Hi,

yes, sensors data are garbage in OS6.  As I know there is no way to fix it.

I realized some time ago, that when you have ISCSI LUN full than NAS likes to freeze.  But all LUNs are at max  80%.

Currently, I just do not know, what is the reason, NAS is booting for a very long time, and trying to mount not-existing datastore "Black-ENC".

[StephenB]

---

@Alein wrote:

trying to mount not-existing datastore "Black-ENC".

---

And not finding files in various places...

One option is to do a factory reset, reconfigure, and restore data from backup.  Though painful, it might be the fastest path to resolve this.

[Alein]

Not really an option. There is too much data to handle it in an acceptable time.  In the final solution, most likely I will use FreeNAS.

[StephenB]

You could also try deleting/recreating the iSCSI LUNS on purple, and see if that helps.  Those errors appear in both of your logs.

[Sandshark]

I can't help you with the main issue, but for the sensors, make sure the symlink at /etc/sensors.d/system.conf  points to /etc/frontview/.sensors/RN4200V2.conf.

[Alein]

It seems that I have this same kind of problems with 2nd NAS 4200.

But this time there are two additional problems.

1.No spanshots , they just have gone. Old are removed, new ones are not made anymore. Only manual.

2.ReadyNASOS service or process (readynasd) was restarted. It is restarting all the time, I have also no stats in monitoring, web interface is reloading every few minutes.

Mar 17, 2019 20:02:08		System: ReadyNASOS background service started.
Mar 17, 2019 20:02:06		Volume: Less than 20% of volume Main's capacity is free. Performance on volume Main will degrade if additional capacity is consumed. NETGEAR recommends that you add capacity to avoid performance degradation.
Mar 17, 2019 20:02:04		System: ReadyNASOS service or process (readynasd) was restarted.
Mar 17, 2019 20:01:52		Volume: Less than 20% of volume Main's capacity is free. Performance on volume Main will degrade if additional capacity is consumed. NETGEAR recommends that you add capacity to avoid performance degradation.
Mar 17, 2019 20:01:51		System: ReadyNASOS service or process (readynasd) was restarted.
Mar 17, 2019 20:01:43		System: ReadyNASOS background service started.
Mar 17, 2019 20:01:41		Volume: Less than 20% of volume Main's capacity is free. Performance on volume Main will degrade if additional capacity is consumed. NETGEAR recommends that you add capacity to avoid performance degradation.
Mar 17, 2019 20:01:40		System: ReadyNASOS service or process (readynasd) was restarted.

There is no problem with free space.

Filesystem Size Used Avail Use% Mounted on

https://mega.nz/#!Ww4S0ILQ!cHVt2G2KJL-AIKw-tV1Uk6KVj3df75Kw6ybJ6MBtSuE

[StephenB]

---

@Alein wrote:

2.ReadyNASOS service or process (readynasd) was restarted. It is restarting all the time, I have also no stats in monitoring, web interface is reloading every few minutes.

https://mega.nz/#!Ww4S0ILQ!cHVt2G2KJL-AIKw-tV1Uk6KVj3df75Kw6ybJ6MBtSuE

---

dmesg.log:

[Sun Mar 17 20:01:36 2019] w83627ehf w83627ehf.2576: fan2 low limit and alarm disabled
[Sun Mar 17 20:01:48 2019] readynasd[483]: segfault at 30 ip 000000000042cbf2 sp 

kernel.log:

Mar 17 20:01:56 RezDent-NAS kernel: readynasd[483]: segfault at 30 ip 000000000042cbf2 sp 00007fa5b3177700 error 4 in readynasd[400000+168000]
Mar 17 20:01:57 RezDent-NAS kernel: w83627ehf w83627ehf.2576: fan2 low limit and alarm disabled