F5-221 NAS Failed Volume

[ScottHenderson]

I have a F5-221 NAS with 5 volumes across 5 drives of storage inserted in it. 4 of the volumes are operating Normal, but one is showing Volume Corrupted. It looks like one of the volumes has failed with a BTRFS error. When I try to follow the "How to repair a corrupted file system?", and use PuTTY to access the volume and check what is broken with the command dmesg, searching the result returns the following error:


BTRFS info (device dm-4): flagging fs with big metadata feature
[ 128.067104] BTRFS info (device dm-4): setting nodatasum
[ 128.067232] BTRFS info (device dm-4): setting nodatacow, compression disabled
[ 128.067328] BTRFS info (device dm-4): turning off barriers
[ 128.067426] BTRFS info (device dm-4): enabling auto defrag
[ 128.067518] BTRFS info (device dm-4): using free space tree
[ 128.067607] BTRFS info (device dm-4): has skinny extents
[ 128.148850] BTRFS error (device dm-4): parent transid verify failed on 739002 9283328 wanted 827226 found 827134
[ 128.152902] BTRFS error (device dm-4): parent transid verify failed on 739002 9283328 wanted 827226 found 827134
[ 128.153056] BTRFS warning (device dm-4): couldn't read tree root
[ 128.164445] BTRFS error (device dm-4): open_ctree failed
[ 132.014784] BTRFS: device label TOS_VOL_20230615 devid 1 transid 115329 /dev/ mapper/vg4-lv4 scanned by mount (2982)

When I tried to continue to follow the instructions to repair the file system, it immediately kicked me out of PuTTY and the NAS was unresponsive until I rebooted it. I didn't want to risk damaging it farther, so I did not try anything else.

Is there a way to repair the file system on the volume or is everything on the storage lost?

[TMzethar]

This can be seen as an error related to the BTRFS file system.
This might help you fix the errors:
viewtopic.php?t=2575

[ScottHenderson]

When I follow the steps listed on the help page, chaning the commands to refer to the correct volume, i get an error that says that I can't setup etent tree or open the file system and then the process fails.The error is listed below.

I split up the fuser -mk command into fuser -m and fuser -k because when I run it as fuser -mk i get a "PuTTY Fatal Error" that claims "Remote side unexpectedly closed network connection" and the unit becomes unresponsive until I reboot it.

--------------------------------------------------------------------------------------------------------
[Conduit@TNAS-143D /]# fuser -m /Volume4
1 2 3 4 5 6 7 9 10 11 12 13 14 15 16 17 18 19 20 22 23 25 26 27 32 62 63 64 65 6
6 68 69 70 71 72 73 74 75 76 78 79 80 81 82 83 84 85 86 87 89 90 91 92 93 94 95
96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116
117 118 120 121 122 123 125 127 128 129 132 134 135 136 137 138 140 141 142 143
144 145 146 147 148 158 159 160 196 204 205 409 412 428 451 1307 1321 1436 1660
1661 1662 1663 1664 1749 1751 1752 1753 1754 1755 1786 1801 1807 1813 1819 1825
1879 1950 1951 1952 1953 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509
2510 2511 2512 2513 2514 2515 2516 2664 2665 2666 2667 2668 2669 2670 2671 2672
2673 2674 2675 2676 2677 2678 2679 2680 2681 2982 2983 2984 2985 2986 2987 2988
2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3461 3487 3514 3749 3769
3771 3773 3795 3953 3954 4561 4615 4661 4699 4705 4735 4847 5274 5280 5448 5460
5678 8554 12222 12223 12224 12225 12226 12227 12228 12229 12230 12231 12232 1223
3 12234 12235 12236 12237 12240 12241 18163 18594 18828 18830 18831 18832 18882
22145 22277
[Conduit@TNAS-143D /]# fuser -k /Volume4
[Conduit@TNAS-143D /]# btrfs check /dev/mapper/vg3-lv3
Opening filesystem to check...
parent transid verify failed on 7390029283328 wanted 827226 found 827134
parent transid verify failed on 7390029283328 wanted 827226 found 827134
parent transid verify failed on 7390029283328 wanted 827226 found 827134
Ignoring transid failure
ERROR: could not setup extent tree
ERROR: cannot open file system
[Conduit@TNAS-143D /]# btrfs check --repair /dev/mapper/vg3-lv3
enabling repair mode
WARNING:

Do not use --repair unless you are advised to do so by a developer
or an experienced user, and then only after having accepted that no
fsck can successfully repair all types of filesystem corruption. Eg.
some software or hardware bugs can fatally damage a volume.
The operation will start in 10 seconds.
Use Ctrl-C to stop it.
10 9 8 7 6 5 4 3 2 1
Starting repair.
Opening filesystem to check...
parent transid verify failed on 7390029283328 wanted 827226 found 827134
parent transid verify failed on 7390029283328 wanted 827226 found 827134
parent transid verify failed on 7390029283328 wanted 827226 found 827134
Ignoring transid failure
WARNING: could not setup extent tree, skipping it
Couldn't setup device tree
ERROR: cannot open file system
[Conduit@TNAS-143D /]#
--------------------------------------------------------------------------------------------------------