NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
btrfs search forward +2d4 error on RN204
For few weeks I get an "btrfs search forward +2d4" error in my RN204 status window and after that the NAS is inaccesable by network PC's and no longer responsive even does not react to pushing power ...
I may have found answer to my problem. This because I wanted to reinstall the OS6.6.0 firmware to see if this would solve my issues.
I then noted in the description that if one installed OS6.6.0 firmware one had to install V6.5.2 first (or system had to be V6.5.2) not shure if my system was 6.5.2. As far as I know latest version I installed before 6.6.0 was 6.5.1. Perhaps this can be found in log files?
So perhaps I upgraded from 6.5.1 directly to 6.6.0, and this is causing my issues, for as I mentioned this brrfs search forward +2d4 error started occuring after I upgraded my system to 6.6.0. Do have the NAS set to auto update, but perhaps 5.5.2 was skipped as versions follow each other quite rapidly.
So here is my questions:
1/. Can someone find out (=or help me how I can check in logs) if NAS was on 5.5.2 before going to 6.6.0
2/. Is there a method to downgrade to 5.5.1, in order to go via 5.5.2 to 6.6.0? If so how would this work
Can anyone tell me how to do this (the build in update utilitiy only allows me to replace 6.6.0 by 6.6.0 (reinstall) but dus not allow me to downgrade to 5.5.2 or 5.5.1)
3/. What is so special in V 5.5.2 and is not changed/installed when I move directly to 6.6.0, and would the system not warn me for this? Feels a bit stupid if Netgear would allow updating to 'incomplete/incompatible' firmware versions. Warning would be in place, similar to not allowing downgrading....
Hope someone knows how to do downgrade
Hans_Kusters wrote:
2/. Is there a method to downgrade to 6.5.1, in order to go via 6.5.2 to 6.6.0? If so how would this work
Can anyone tell me how to do this (the build in update utilitiy only allows me to replace 6.6.0 by 6.6.0 (reinstall) but does not allow me to downgrade to 6.5.2 or 6.5.1)
Netgear says not to attempt this downgrade. The method to do it requires a factory reset, and it has some risks. If it comes to that, you'd be better off just doing the factory reset w/o the downgrade. That would do a clean install.
But wait until mdgm gets back to you on the logs before taking action.
Guess I am correct I did skip the mandatory 6.5.2 version. Guess I have to do factory reset. Or is there other option?
Friend explained how to search logs and here it is (look at first and last line of partial copy of log files below)
ReadyNAS_204
Sat Oct 8 2016 20:42:59 Systeem: Firmware is geüpgraded naar 6.6.0. Sat Oct 8 2016 20:39:24 Systeem: Het systeem wordt opnieuw opgestart. Sun Aug 28 2016 20:28:22 Systeem: ReadyNASOS-achtergrondservice is gestart. Sun Aug 28 2016 20:27:45 Systeem: ReadyNASOS-service of -proces is opnieuw gestart. Mon Aug 22 2016 15:41:41 Systeem: ReadyNASOS-achtergrondservice is gestart. Mon Aug 22 2016 15:41:04 Systeem: ReadyNASOS-service of -proces is opnieuw gestart. Mon Aug 8 2016 21:22:20 Systeem: ReadyNASOS-achtergrondservice is gestart. Mon Aug 8 2016 21:21:45 Systeem: Firmware is geüpgraded naar 6.5.1.
Hans_Kusters wrote:
Guess I am correct I did skip the mandatory 6.5.2 version. Guess I have to do factory reset. Or is there other option?
First, I don't think upgrading from 6.5.1 to 6.6.0 caused this problem.
If you have a full backup, you could proceed with the factory reset. But if there's data on the NAS you'd like to back up, then wait for mdgm to get back to you. Or use paid support.
Still waiting for analysis of my log files. Meanwhile did some more digging. Ran diagnose utility from Raidar on my NAS.
Got long list of errors (see below) that seem to point at faulty drive. Anyone know what it means and what drive is affected.
Any clue if drive is defective or if reformating would restore/repair drive?
Hans
---copy of diagnostics result----
Successfully completed diagnostics System Logs
- 2017-01-02 09:10:03: BTRFS: error (device md127) in btrfs_commit_transaction:2083: errno=-5 IO failure (Error while writing out transaction)
- 2017-01-02 09:07:25: BTRFS critical (device md127): unable to find logical 1444213391360 len 4096
- 2017-01-02 09:07:24: BTRFS critical (device md127): unable to find logical 1444213391360 len 4096
- 2017-01-02 09:06:44: BTRFS critical (device md127): unable to find logical 1444213555200 len 4096
- 2017-01-02 09:06:43: BTRFS critical (device md127): unable to find logical 1444213555200 len 4096
- 2017-01-02 09:06:35: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 09:06:34: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 09:06:33: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 09:06:32: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 09:06:31: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 09:06:30: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 09:06:29: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 09:06:28: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
.......
list continues but deleted middle part, guess you get the idea
......
- 2017-01-02 07:59:13: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 07:59:12: BTRFS critical (device md127): unable to find logical 1444213563392 len 4096
- 2017-01-02 07:59:11: BTRFS critical (device md127): unable to find logical 1444213563392 len 4096
- 2017-01-02 07:59:10: BTRFS critical (device md127): unable to find logical 1444213563392 len 4096
- 2017-01-02 07:59:09: BTRFS critical (device md127): unable to find logical 1444213563392 len 4096
- 2017-01-02 07:59:08: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 07:59:07: BTRFS critical (device md127): unable to find logical 1444213571584 len 4096
- 2017-01-02 07:59:06: BTRFS critical (device md127): unable to find logical 1444213579776 len 4096
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
