Hope someone can help. This morning the NAS was not reachable on the network and the physical check showed the error message "list_lru_del+2a" on the display. I searched the forum and the web with no information found. Upon hard reboot, the NAS came back to life and is accessible, however admin console system log does not show any errors. Now the status is that I am unable to log into the admin, although the data shares are reachable on the network. Any help or clues are greatly appreciated! Many thanks!

As these messages shown on the LCD are often very cryptic, it would be great for all ReadyNAS-with-LCD owners to have a KB article with basic explanation of the cause or context of it, or even just a clue. In your case, you could try to download the logs from RAIDar and check systemd-journal.log (from the top of my head). A line containing "jenkins" is added to these logs during boot, so look for the last occurrence and check the lines before it for clues.

Disabling Antivirus in case you did not already do might bring back the system to normal behaviour. 6.6.1 has issues with antivirus. In case disabling it addresses your issue please wait for final release of fw 6.7 before enabling it again.

AV is not running and has never been.

Thank you for considering this issue. I have downloaded the logs but there is no such systemd-journal log file or similar included. I have looked through all text files but could not find any clues related to the error message! The only reference to "Jenkins" I found was in the file "dmesg.txt", which appears to document the rebooting sequence steps - but this starts essentially with the reboot process. This is very cryptic and I would really appreciate any insights from Netgear tech/developers related to this error message. While all looks normal now, I am worried that the critical business data stored on this NAS could be at risk. Many thanks!

Well, running OS6, there should be a systemd-journal.log file. I just downloaded the logs from my NAS and here is the line that appears everytime the NAS boots up.Mar 11 01:00:43 nas-hostname kernel: Linux version 4.4.48.x86_64.1 (jenkins@blocks) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Mon Feb 13 18:05:15 PST 2017

Error message on readynas 314 fw 6.6.1

11 Replies

Replies have been turned off for this discussion

jak0lantash
Mentor
Mar 11, 2017
As these messages shown on the LCD are often very cryptic, it would be great for all ReadyNAS-with-LCD owners to have a KB article with basic explanation of the cause or context of it, or even just a clue.

In your case, you could try to download the logs from RAIDar and check systemd-journal.log (from the top of my head). A line containing "jenkins" is added to these logs during boot, so look for the last occurrence and check the lines before it for clues.
- tsteinegger
  Aspirant
  Mar 12, 2017
  Thank you for considering this issue.
  
  I have downloaded the logs but there is no such systemd-journal log file or similar included. I have looked through all text files but could not find any clues related to the error message!
  
  The only reference to "Jenkins" I found was in the file "dmesg.txt", which appears to document the rebooting sequence steps - but this starts essentially with the reboot process.
  
  This is very cryptic and I would really appreciate any insights from Netgear tech/developers related to this error message. While all looks normal now, I am worried that the critical business data stored on this NAS could be at risk.
  
  Many thanks!
  - jak0lantash
    Mentor
    Mar 12, 2017
    Well, running OS6, there should be a systemd-journal.log file. I just downloaded the logs from my NAS and here is the line that appears everytime the NAS boots up.
    Mar 11 01:00:43 nas-hostname kernel: Linux version 4.4.48.x86_64.1 (jenkins@blocks) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Mon Feb 13 18:05:15 PST 2017
Retired_Member
Mar 11, 2017
Disabling Antivirus in case you did not already do might bring back the system to normal behaviour.

6.6.1 has issues with antivirus. In case disabling it addresses your issue please wait for final release of fw 6.7 before enabling it again.
- tsteinegger
  Aspirant
  Mar 12, 2017
  AV is not running and has never been.