Re: BTRFS critical (device md0): corrupt leaf, unaligned key offset for file ...

bartw · ‎2019-06-13

Hi all,

I have a very recent system installed at a customer and the RN424 was running fine (backup-NAS).

Today I visited the customer and saw that Radiator reported "Management Service offline", and I could also not access the system anymore via Frontview.

# df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 4.0G 804M 2.9G 22% / (so ample free space)
tmpfs 981M 0 981M 0% /dev/shm
tmpfs 981M 388K 980M 1% /run
tmpfs 491M 1.5M 489M 1% /run/lock
tmpfs 981M 0 981M 0% /sys/fs/cgroup
/dev/md127 5.5T 4.7T 813G 86% /data
/dev/md127 5.5T 4.7T 813G 86% /home
/dev/md127 5.5T 4.7T 813G 86% /apps

ssh still works, but it is clear that there is something wrong with /dev/md0. (see output of Diagnose)

dmesg =>

[ 65.743537] BTRFS critical (device md0): corrupt leaf, unaligned key offset for file extent: block=60571648, root=1, slot=11
[ 65.784533] BTRFS critical (device md0): corrupt leaf, unaligned key offset for file extent: block=60571648, root=1, slot=11

The data volume seems to be fine though. Running 6.10.1

Diagnose info via Radiator gives me the following :

Successfully completed diagnostics
System
Volume 0 is inactive
Volume data-0 is inactive
Volume data-1 is inactive
Volume data-2 is inactive
Logs
2019-06-13 19:58:19: BTRFS critical (device md0): corrupt leaf, unaligned key offset for file extent: block=60571648, root=1, slot=11
2019-06-13 19:50:49: BTRFS critical (device md0): corrupt leaf, unaligned key offset for file extent: block=60571648, root=1, slot=11
2019-06-13 19:43:11: BTRFS critical (device md0): corrupt leaf, unaligned key offset for file extent: block=60571648, root=1, slot=11
2019-06-13 19:43:10: BTRFS critical (device md0): corrupt leaf, unaligned key offset for file extent: block=60571648, root=1, slot=11
2019-06-13 19:39:36: BTRFS critical (device md0): corrupt leaf, unaligned key offset for file extent: block=60571648, root=1, slot=11
2019-06-13 19:39:36: readynasd[3538]: segfault at 1f8 ip 00000000004d4196 sp 00007ffe93ac7490 error 6 in readynasd[400000+178000]
2019-06-13 19:39:36: readynasd[3544]: segfault at 1f8 ip 00000000004d4196 sp 00007ffd717602c0 error 6 in readynasd[400000+178000]

What is the right procedure to repair /dev/md0 without destroying the data?

Thanks for your help.

JohnCM_S · ‎2019-06-13

Hi bartw,

'Management Service offline' means that readynasd is not running. The reason it is not running is because md0 has a corrupt operating system. md0 needs to run for readynasd to run.

You will need to get some assistance in fixing the operating system. You may contact NETGEAR support so they can assist you on that.

Alternatively, you can boot the NAS in Read-Only to make your data accessible. You can then backup your data and reset the NAS to factory default afterward.

Regards,

JohnCM_S · ‎2019-06-18

Hi bartw,

We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance.

If your issue is now resolved, we encourage you to mark the appropriate reply as the “Accept as Solution” or post what resolved it and mark it as a solution so others can be confident in benefiting from the solution.

The NETGEAR community looks forward to hearing from you and being a helpful resource in the future!

Regards,