TerraMaster Forum

Hello,

I am having an issue with my F6 424 NAS.

It started occurring when i upgraded to TOS 7.0

The NAS would hang up and become unresponsive after about 5 minutes, du to an OOM error.

I did a reset and downgraded to TOS6 thanks to a TOS backup i had.

My drives are 6xHDD in RAID6 on BTRFS and a SSD boot drive also BTRFS.

Now back on TOS 6, the NAS is inaccessible and unresponsive with the HDD's in, the boot sequence does not finish.

If i unplug the HDD's, i can enter TOS with no issue.

If i plug the HDD's after a shutdown => NAS inaccessible and unresponsive
If i hot plug the HDD's => the drives appear in the control panel but not the storage pool or the volume.
Here is the last system report

Can you help ?

Corrupted Btrfs filesystem metadata has been detected, preventing the mount from completing. Please try to recall if you experienced a system hang or power loss recently.

First, stop the process `mount /dev/vg0/lv1 /Volume2`, which has been failing repeatedly.

We recommend that you first try a read-only mount:
mount -o ro /dev/mapper/vg0-lv1 /Volume2

If the read-only mount also fails, please prepare sufficient space to attempt to export the data:
btrfs restore /dev/mapper/vg0-lv1 /target_directory

If you are unable to prepare sufficient space, and provided you are willing to accept the risk, you may consider referring to this guide on repairing the file system:
viewtopic.php?t=2575

Hello, i get an OOM at this step :
buche@TNAS:/# btrfs check /dev/mapper/vg0-lv1
Opening filesystem to check...
Checking filesystem on /dev/mapper/vg0-lv1
UUID: ef94fc0f-c381-4ba6-89c7-251e7bf83b46
[1/7] checking root items
[2/7] checking extents
Killed
buche@TNAS:/# dmesg | tail -50
[ 2012.667031] [ 3453] 0 3453 16600 2181 110592 1111 0 nginx
[ 2012.667051] [ 3459] 0 3459 3575 2737 69632 27 0 vmtouch
[ 2012.667054] [ 3460] 0 3460 628358 14136 847872 45152 0 TOSDaemon
[ 2012.667056] [ 3461] 0 3461 479880 0 249856 6485 0 nasips
[ 2012.667058] [ 3465] 0 3465 702 0 49152 27 0 vmtouch
[ 2012.667061] [ 3467] 0 3467 478593 5102 233472 3942 0 twm_authenticat
[ 2012.667063] [ 3468] 0 3468 460676 2083 233472 1152 0 msgcenter
[ 2012.667064] [ 3548] 107 3548 55329 736 163840 462 0 postgres
[ 2012.667067] [ 3604] 0 3604 493983 4690 217088 1377 0 ResourceCollect
[ 2012.667069] [ 3780] 0 3780 16690 1782 118784 1059 0 nginx
[ 2012.667071] [ 3781] 0 3781 16690 1782 118784 1059 0 nginx
[ 2012.667073] [ 3782] 0 3782 16690 1782 118784 1059 0 nginx
[ 2012.667075] [ 3783] 0 3783 16690 1782 118784 1059 0 nginx
[ 2012.667077] [ 3879] 0 3879 523140 2600 581632 8151 0 ncbd-hyperv
[ 2012.667078] [ 3946] 0 3946 497871 2057 262144 2792 0 ncbd-pc
[ 2012.667080] [ 3953] 0 3953 463299 5013 258048 4417 0 FileServer
[ 2012.667082] [ 4029] 0 4029 687938 5716 552960 8117 0 ncbd-vmware
[ 2012.667083] [ 4073] 0 4073 476645 2444 217088 4145 0 ter_vg_monitor
[ 2012.667085] [ 4154] 0 4154 461606 0 245760 5649 0 onlined
[ 2012.667087] [ 4222] 0 4222 54311 2505 176128 671 0 php-fpm7.4
[ 2012.667102] [ 4223] 0 4223 54311 1156 143360 677 0 php-fpm7.4
[ 2012.667104] [ 4224] 0 4224 54311 1145 143360 688 0 php-fpm7.4
[ 2012.667106] [ 4225] 0 4225 54311 1158 143360 675 0 php-fpm7.4
[ 2012.667108] [ 4226] 0 4226 54311 1157 143360 676 0 php-fpm7.4
[ 2012.667110] [ 4227] 0 4227 54311 1162 143360 671 0 php-fpm7.4
[ 2012.667112] [ 4545] 0 4545 1075 592 49152 18 0 cron
[ 2012.667114] [ 4620] 0 4620 479177 2735 241664 2284 0 dockermgr-api
[ 2012.667116] [ 4677] 0 4677 1205 387 45056 90 0 rpc.statd
[ 2012.667118] [ 4681] 0 4681 784 435 40960 16 0 rpc.idmapd
[ 2012.667119] [ 4684] 0 4684 1295 75 49152 34 0 rpc.mountd
[ 2012.667121] [ 4685] 0 4685 1364 371 49152 11 0 nfsdcld
[ 2012.667124] [ 4915] 0 4915 8179 3713 106496 1504 0 python3
[ 2012.667126] [ 4918] 0 4918 16416 1190 118784 11 0 nmbd
[ 2012.667128] [ 4919] 0 4919 20581 1408 155648 234 0 smbd
[ 2012.667130] [ 4922] 0 4922 20116 930 151552 254 0 smbd-notifyd
[ 2012.667132] [ 4923] 0 4923 20114 812 143360 247 0 cleanupd
[ 2012.667134] [ 4924] 0 4924 20198 1278 155648 21 0 samba-bgqd
[ 2012.667136] [ 4938] 0 4938 5137 1664 86016 196 -1000 sshd
[ 2012.667139] [ 4992] 0 4992 174500 207 159744 684 0 upnpd
[ 2012.667141] [ 5366] 10001 5366 11026 513 135168 2581 0 qbittorrent-nox
[ 2012.667142] [ 5385] 0 5385 321415 8172 548864 7528 0 python
[ 2012.667145] [ 7131] 0 7131 6676 2028 90112 29 0 sshd
[ 2012.667147] [ 7164] 0 7164 4366 1364 77824 49 0 systemd
[ 2012.667149] [ 7165] 0 7165 6943 250 81920 1132 0 (sd-pam)
[ 2012.667151] [ 7174] 0 7174 1456 472 45056 360 0 bash
[ 2012.667154] [ 8558] 0 8558 2103169 1733128 16908288 369236 0 btrfs
[ 2012.667159] [ 11333] 0 11333 1671 141 45056 0 0 smartctl
[ 2012.667161] [ 11334] 0 11334 461 34 32768 0 0 bash
[ 2012.667163] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-0.slice/session-c2.scope,task=btrfs,pid=8558,uid=0
[ 2012.667184] Out of memory: Killed process 8558 (btrfs) total-vm:8412676kB, anon-rss:6930840kB, file-rss:1672kB, shmem-rss:0kB, UID:0 pgtables:16512kB oom_score_adj:0
buche@TNAS:/#


Can you help further ?

buche wrote: ↑02 Sep 2026, 16:18

Looking at your dmesg output, btrfs check was terminated by the Linux OOM (Out of Memory) killer after consuming around 8 GB of RAM during the [2/7] checking extents phase. Checking and repairing a large Btrfs filesystem (especially across a 6-drive RAID6 pool) requires a substantial amount of memory to build and verify metadata trees.

Based on this, if possible, we strongly recommend adding more RAM to the NAS before attempting the filesystem check and repair again.

The system hang on this command and got another issue

Out of memory: Killed proces 8558(btrfs)

buche@TNAS:/# /etc/tos/scripts/mntdata
[DEBUG /usr/sbin/mdadm -E /dev/sda2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sda2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sda3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sda3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdb2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdb2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdb3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdb3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdc2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdc2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdc3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdc3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdd2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdd2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdd3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdd3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sde2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sde2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sde3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sde3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdf2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdf2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdf3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdf3.
: exit status 1
2026-09-02 17:38:21.900 [INFO] /usr/sbin/mdadm --grow --bitmap=internal /dev/md9
2026-09-02 17:38:21.901 [INFO] [mntdata-initCore]set internal bitmap for core raid(active).Err:mdadm: bitmap already present on /dev/md9

[DEBUG /usr/sbin/mdadm --re-add /dev/md9 /dev/sdza2]
2026-09-02 17:38:21.902 [INFO] [mntdata-initCore]get Cores:[{2026-09-02 17:38:10 +0000 UTC /dev/sdza2 Active device 0 false e1881073:0bf7f6a6:f915237f:e82a2368 /dev/sdza}]
2026-09-02 17:38:21.902 [INFO] [mntdata-initSwap]get init SwapMember:[{2026-09-02 17:13:13 +0000 UTC /dev/sdza3 Active device 0 false b1710ae2:000c7a66:b8951196:dd1a51e9 /dev/sdza}]
[DEBUG /usr/sbin/mdadm -A /dev/md8 /dev/sdza3 -f]
2026-09-02 17:38:21.904 [INFO] /usr/sbin/mdadm --grow --bitmap=internal /dev/md8
2026-09-02 17:38:21.905 [INFO] [mntdata-initSwap]set internal bitmap for swap raid(active).Err:mdadm: bitmap already present on /dev/md8

[DEBUG /usr/sbin/mdadm --re-add /dev/md8 /dev/sdza3]
2026-09-02 17:38:21.922 [INFO] getCacheRaidInfo Failed::already exists data raid(/dev/md0), can`t continue
[DEBUG /usr/sbin/mdadm --re-add /dev/md0 /dev/sdza4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sda4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sdb4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sdc4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sdd4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sde4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sdf4]
[DEBUG /usr/sbin/iniparse -a -f /etc/volume/volume.conf -s 00000002-2412-1113-5327-6cbfb50427d2 -system]
mountPath = /Volume2
check filesystem on /dev/mapper/vg0-lv1
2026-09-02 17:42:25.818 [INFO] changeBtrfsSubvol::/dev/mapper/vg0-lv1 btrfs subvolume @ is Exists.
/etc/tos/scripts/mntVolume /dev/mapper/vg0-lv1
[DEBUG /bin/bash -c /etc/tos/scripts/mntVolume /dev/mapper/vg0-lv1]
[DEBUG 2026/09/02 17:42:26 can't found flashCache block device!
]
[DEBUG /usr/sbin/iniparse -a -f /etc/volume/volume.conf -s 00000001-2505-0703-2257-6cbfb50427d2 -system]
mountPath = /Volume1
2026-09-02 17:42:27.371 [INFO] /.eraseAcl not exist

Have you set up Hyper Cache before? Based on the error message you provided, this may be related to abnormal cache metadata. Please visit the link below and schedule a remote assistance session with our online support team:
https://salesiq.zohopublic.com/signatur ... 97d0be8892

Hello,
After a sheduled remote assistance meeting with support, we ran this comand :
buche@TNAS:/# btrfs check /dev/mapper/vg0-lv1 Opening filesystem to check...
Checking filesystem on /dev/mapper/vg0-lv1 UUID: ef94fc0f-c381-4ba6-89c7-251e7bf83b46
[1/7] checking root items
[2/7] checking extents
[3/7] checking free space tree
[4/7] checking fs roots
[5/7] checking only csums items (without verifying data)
[6/7] checking root refs
[7/7] checking quota groups found
29461121978368 bytes used, no error found
total csum bytes: 28729530100
total tree bytes: 42083155968
total fs tree bytes: 4853596160
total extent tree bytes: 4195155968
btree space waste bytes: 5293167300
file data blocks allocated: 1044670393643008
referenced 30969966440448
buche@TNAS:/#

Hovever when executing script /etc/tos/scripts/mntdata
OOM error started appearing and the NAS became unresponsive.

buche@TNAS:~# /etc/tos/scripts/mntdata
[DEBUG /usr/sbin/mdadm -E /dev/sda2]
2026/09/09 12:47:54 mdadm: No md superblock detected on /dev/sda2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sda3]
2026/09/09 12:47:56 mdadm: No md superblock detected on /dev/sda3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdc2]
2026/09/09 12:47:57 mdadm: No md superblock detected on /dev/sdc2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdc3]
2026/09/09 12:47:57 mdadm: No md superblock detected on /dev/sdc3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdd2]
2026/09/09 12:47:58 mdadm: No md superblock detected on /dev/sdd2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdd3]
2026/09/09 12:47:58 mdadm: No md superblock detected on /dev/sdd3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sde2]
2026/09/09 12:47:59 mdadm: No md superblock detected on /dev/sde2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sde3]
2026/09/09 12:47:59 mdadm: No md superblock detected on /dev/sde3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdf2]
2026/09/09 12:47:59 mdadm: No md superblock detected on /dev/sdf2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdf3]
2026/09/09 12:47:59 mdadm: No md superblock detected on /dev/sdf3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdg2]
2026/09/09 12:48:00 mdadm: No md superblock detected on /dev/sdg2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdg3]
2026/09/09 12:48:00 mdadm: No md superblock detected on /dev/sdg3.
: exit status 1

2026/09/09 12:52:00 /buildAgent/work/b4988470bd41b41d/core/sqlitedb/sqlitedb_model.go:60 SLOW SQL >= 1s
[147411.391ms] [rows:1] SELECT count(*) FROM INFORMATION_SCHEMA.columns WHERE table_schema = CURRENT_SCHEMA() AND table_name = 'share_config' AND column_name = 'close_status'

2026/09/09 12:57:13 /buildAgent/work/b4988470bd41b41d/core/sqlitedb/sqlitedb_model.go:60 SLOW SQL >= 1s
[296713.567ms] [rows:1] SELECT count(*) FROM INFORMATION_SCHEMA.columns WHERE table_schema = CURRENT_SCHEMA() AND table_name = 'share_config' AND column_name = 'share_link'

2026/09/09 13:02:10 /buildAgent/work/b4988470bd41b41d/core/sqlitedb/sqlitedb_model.go:63 SLOW SQL >= 1s
[281086.190ms] [rows:1] SELECT count(*) FROM information_schema.tables WHERE table_schema = CURRENT_SCHEMA() AND table_name = 'share_config' AND table_type = 'BASE TABLE'


2026/09/09 13:05:55 /buildAgent/work/b4988470bd41b41d/core/sqlitedb/sqlitedb_model.go:63 SLOW SQL >= 1s
[208856.472ms] [rows:1] SELECT CURRENT_DATABASE()
Killed
buche@TNAS:~#

Can you help further ?

Hello again,

unfortunately, after another session with tech support, the issue is not resolved.

- I added a 128gb USB drive as SWAP.
- Tech support ran this command :
buche@TNAS:/# /etc/tos/scripts/mntdata

Which again caused an OOM error after this :
[DEBUG /usr/sbin/mdadm -E /dev/sda2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sda2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sda3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sda3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdb2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdb2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdb3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdb3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdc2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdc2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdc3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdc3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdd2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdd2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdd3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdd3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sde2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sde2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sde3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sde3.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdf2]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdf2.
: exit status 1
[DEBUG /usr/sbin/mdadm -E /dev/sdf3]
2026/09/02 17:38:21 mdadm: No md superblock detected on /dev/sdf3.
: exit status 1
2026-09-02 17:38:21.900 [INFO] /usr/sbin/mdadm --grow --bitmap=internal /dev/md9
2026-09-02 17:38:21.901 [INFO] [mntdata-initCore]set internal bitmap for core raid(active).Err:mdadm: bitmap already present on /dev/md9

[DEBUG /usr/sbin/mdadm --re-add /dev/md9 /dev/sdza2]
2026-09-02 17:38:21.902 [INFO] [mntdata-initCore]get Cores:[{2026-09-02 17:38:10 +0000 UTC /dev/sdza2 Active device 0 false e1881073:0bf7f6a6:f915237f:e82a2368 /dev/sdza}]
2026-09-02 17:38:21.902 [INFO] [mntdata-initSwap]get init SwapMember:[{2026-09-02 17:13:13 +0000 UTC /dev/sdza3 Active device 0 false b1710ae2:000c7a66:b8951196:dd1a51e9 /dev/sdza}]
[DEBUG /usr/sbin/mdadm -A /dev/md8 /dev/sdza3 -f]
2026-09-02 17:38:21.904 [INFO] /usr/sbin/mdadm --grow --bitmap=internal /dev/md8
2026-09-02 17:38:21.905 [INFO] [mntdata-initSwap]set internal bitmap for swap raid(active).Err:mdadm: bitmap already present on /dev/md8

[DEBUG /usr/sbin/mdadm --re-add /dev/md8 /dev/sdza3]
2026-09-02 17:38:21.922 [INFO] getCacheRaidInfo Failed::already exists data raid(/dev/md0), can`t continue
[DEBUG /usr/sbin/mdadm --re-add /dev/md0 /dev/sdza4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sda4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sdb4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sdc4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sdd4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sde4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md1 /dev/sdf4]
[DEBUG /usr/sbin/iniparse -a -f /etc/volume/volume.conf -s 00000002-2412-1113-5327-6cbfb50427d2 -system]
mountPath = /Volume2
check filesystem on /dev/mapper/vg0-lv1
2026-09-02 17:42:25.818 [INFO] changeBtrfsSubvol::/dev/mapper/vg0-lv1 btrfs subvolume @ is Exists.
/etc/tos/scripts/mntVolume /dev/mapper/vg0-lv1
[DEBUG /bin/bash -c /etc/tos/scripts/mntVolume /dev/mapper/vg0-lv1]
[DEBUG 2026/09/02 17:42:26 can't found flashCache block device!
]
[DEBUG /usr/sbin/iniparse -a -f /etc/volume/volume.conf -s 00000001-2505-0703-2257-6cbfb50427d2 -system]
mountPath = /Volume1
2026-09-02 17:42:27.371 [INFO] /.eraseAcl not exist

I have been advised to upgrade from 8GB RAM to 16 RAM.

My questions are :

1. Would a 128GB usb thumb drive work in this use case ?
2. How confident are we this would fix the issue ?

Thanks

An external USB drive can only be used as external hard drive storage; this is a different concept from memory (RAM). The current issue is that running mount and repair commands fails due to OOM, so we recommend adding more memory.