NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
"Device is Offline" (OS 6.1.4) Frozen / Hung
A new ReadyNAS 516 running OS 6.1.4 with five new WD2003FYYS RE4 2 TB drives configured RAID-6. The NAS has been powered ON for about 10 days without a reboot (total accumulated time). No "Apps" are i...
Follow-up status from original post -
ReadyNAS 516 running OS 6.1.4 with five new WD2003FYYS RE4 2 TB drives configured RAID-6. No "Apps" are installed. Defrag started about 18-Nov-2013 21:33 MST. System generated the expected status email ("Defragmentation started for Volume 'Data'"), and I closed the browser Frontview page for the evening.
The NAS was non-responsive in the morning with browser displaying "Device is Offline", but not dead. I performed a forced reboot about 47 hours later (hold front panel power button), at about 20-Nov-2013 20:21 PM MST. The NAS appeared to successfully reboot. I downloaded log archive (System -> Logs -> Download Logs), and uploaded the archive for review (Case 22280603). A brief inspection shows "kernel BUG" logged in kernel.log file. Note the following:
status.log:
[13/11/18 21:33:23 MST] notice:volume:LOGMSG_DEFRAGSTART_VOLUME Defragmentation started for Volume 'Data'.
[13/11/20 20:22:14 MST] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
kernel.log:
Nov 18 21:51:22 flo516 kernel: kernel BUG at fs/btrfs/ctree.c:1152!
The Netgear support engineer suggested OS re-install, but the suggestion was rescinded after reviewing the logs. Google search "kernel BUG at fs/btrfs/extent-tree.c" shows other btrfs systems also impacted with potentially related kernel BUG in fs/btrfs/extent-tree.c. This appears to be an active btrfs bug in the wild (or multiple bugs).
Although the NAS appeared to reboot successfully, how can I trust the integrity of the OS and data? I don't see btfsck invoked on ReadyNAS 516 (it's new code).
Although the time of crash did not appear to be correlated with snapshot (snapshot runs at midnight for daily intervals), I disabled snapshot on all volumes. Antivirus never enabled. The device completed two "Defrag" cycles, but it is difficult to assess any positive effect because the device does not produce any fragmentation statistics.
25-Nov-2013 10:58 PM Defragmentation started for Volume 'Data'.
25-Nov-2013 11:26 PM Defragmentation completed for Volume 'Data'.
26-Nov-2013 08:48 AM Defragmentation started for Volume 'Data'.
26-Nov-2013 09:15 AM Defragmentation completed for Volume 'Data'.
Thanks, Greg
ReadyNAS 516 running OS 6.1.4 with five new WD2003FYYS RE4 2 TB drives configured RAID-6. No "Apps" are installed. Defrag started about 18-Nov-2013 21:33 MST. System generated the expected status email ("Defragmentation started for Volume 'Data'"), and I closed the browser Frontview page for the evening.
The NAS was non-responsive in the morning with browser displaying "Device is Offline", but not dead. I performed a forced reboot about 47 hours later (hold front panel power button), at about 20-Nov-2013 20:21 PM MST. The NAS appeared to successfully reboot. I downloaded log archive (System -> Logs -> Download Logs), and uploaded the archive for review (Case 22280603). A brief inspection shows "kernel BUG" logged in kernel.log file. Note the following:
status.log:
[13/11/18 21:33:23 MST] notice:volume:LOGMSG_DEFRAGSTART_VOLUME Defragmentation started for Volume 'Data'.
[13/11/20 20:22:14 MST] info:system:LOGMSG_READYNASD_ABORTED_NOINFO ReadyNASOS service or process was restarted.
kernel.log:
Nov 18 21:51:22 flo516 kernel: kernel BUG at fs/btrfs/ctree.c:1152!
The Netgear support engineer suggested OS re-install, but the suggestion was rescinded after reviewing the logs. Google search "kernel BUG at fs/btrfs/extent-tree.c" shows other btrfs systems also impacted with potentially related kernel BUG in fs/btrfs/extent-tree.c. This appears to be an active btrfs bug in the wild (or multiple bugs).
Although the NAS appeared to reboot successfully, how can I trust the integrity of the OS and data? I don't see btfsck invoked on ReadyNAS 516 (it's new code).
Although the time of crash did not appear to be correlated with snapshot (snapshot runs at midnight for daily intervals), I disabled snapshot on all volumes. Antivirus never enabled. The device completed two "Defrag" cycles, but it is difficult to assess any positive effect because the device does not produce any fragmentation statistics.
25-Nov-2013 10:58 PM Defragmentation started for Volume 'Data'.
25-Nov-2013 11:26 PM Defragmentation completed for Volume 'Data'.
26-Nov-2013 08:48 AM Defragmentation started for Volume 'Data'.
26-Nov-2013 09:15 AM Defragmentation completed for Volume 'Data'.
Thanks, Greg
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
