Forum Discussion

Aspirant

Dec 27, 2016

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 ...

btrfs search forward error

NAS inaccesable

Other Discussions

StephenB

Guru - Experienced User

Dec 31, 2016

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.

Hans_Kusters

Aspirant

Jan 02, 2017

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

FramerV
NETGEAR Employee Retired
Jan 02, 2017
Hi Hans_Kusters,

The error seems to be pointing to your data volume.

On the logs the got, can you look at the mdstat and disk_info?

On the mdstat look for something similar like:

md127 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]

2915732352 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]

On the disk_info, look out for:

1. ATA Error.

2. Reallocated Sectors.

3. Current Pending Sector Count.

4. Uncorrectable Sector Count.

You could also PM mdgm regarding the system logs update.

Regards,
- Hans_Kusters
  Aspirant
  Jan 03, 2017
  FramerV
  Thanks for helping. No reply from mdgm on my logs. No clue how to reach him by PM.
  Yes as you suspected there is these lines in mdstat log
  =====
  md127 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
  17567012352 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
  
  md1 : active raid6 sda2[0] sdd2[3] sdc2[2] sdb2[1]
  1047424 blocks super 1.2 level 6, 64k chunk, algorithm 2 [4/4] [UUUU]
  =====
  But no clue what this means or how to repair it.
  
  In diskinfo.log there is noting with regard to (S)ATA errors or Sector problems
  So unlikely the problem lies in errors on disk.
  
  As said before send logs to mdgm a week ago and waiting for mdgm to contact me as I have no clue on how to contact him.
  
  Hans
- Hans_Kusters
  Aspirant
  Jan 03, 2017
  FramerV
  Thanks for helping. No reply from mdgm on my logs. No clue how to reach him by PM.
  And yes, as you suspected there is similar lines in mdstat log
  They read:
  md127 : active raid5 sda3[0] sdd3[3] sdc3[2] sdb3[1]
  17567012352 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
  
  md1 : active raid6 sda2[0] sdd2[3] sdc2[2] sdb2[1]
  1047424 blocks super 1.2 level 6, 64k chunk, algorithm 2 [4/4] [UUUU]
  
  But no clue what this means or how to repair it.
  
  In diskinfo.log there is noting with regard to (S)ATA errors or Sector problems
  So unlikely the problem lies in errors on disk.
  
  As said before send logs to mdgm a week ago and waiting for mdgm to contact me as I have no clue on how to contact him.
  
  Hans
  - StephenB
    Guru - Experienced User
    Jan 03, 2017
    Hans_Kusters wrote:
    
    No clue how to reach him by PM.
    
    PM - "private message" Use the messages link in the upper right corner of the forum, addressing the message to mdgm.