TerraMaster Official Forum

After a couple of restarts, everything came back to normality and no issues were found during the weekend with no errors.. [ 47.589224] BTRFS: device fsid 4c70363f-977c-430c-9f86-27e962112093 devid 1 transid 37582 /dev/mapper/vg0-lv0 [ 47.591332] BTRFS info (device dm-0): metadata ratio 50 [ 47.5923...

Hello, it may be that the kernel has not been upgraded completely after upgrading the system, causing the root mismatch. You can remount the file system or reinstall the system to update the kernel to the latest I have not upgraded the system (same kernel) Remounting the file system happens on ever...

Hello, I managed to stop all services and unmount the unit executing fuser -km /mnt/md0 Then I followed the guide and btrfs check /dev/mapper/vg0-lv0 Opening filesystem to check... Checking filesystem on /dev/dm-0 UUID: 4c70363f-977c-430c-9f86-27e962112093 [1/7] checking root items root item for roo...

Thank for your reply. I can access the shares and the web. This is a F5-221 v4.2.08P1.10 This guide is useless because, as I said before, the main problem is that running the command "umount /mnt/md0" gives this result umount: /mnt/md0: target is busy. Using a external keyboard and monitor...

I have run btrfs scrub as read only.... no errors

Hello, I have 14 instances of the following error when I run dmesg BTRFS error (device dm-0): parent transid verify failed on 811548672 wanted 37188 found 37194 I do not know any way of starting the system with the device dm-0 unmounted, so I do not dare to run btrfs-zero-log because I do not know i...

Hi,
Thanks for the info. It would be nice if the forum had a "like" or "thanks" function for posts like this. Keeps threads tidy and provides feedback without making dozens of boring "+1" lines.

Thanks for the response. And what about these others? Mar 24 18:22:02 nas smbd[15050]: [2021/03/24 18:22:02.072965, 0] ../source3/lib/sysquotas.c:461(sys_get_quota) Mar 24 18:22:02 nas smbd[15050]: sys_path_to_bdev() failed for path [.]! I have read it has something to do with smbd quotas are incomp...

I have no problems logging into TOS. The hard disks are brand new and were fully scanned for bad sectors before formatting. Iron wolf recommended by you. Everything reported as healthy status. Haven't seen the error anymore. I'll keep an eye on it, as basically you have no more idea than me about it...

Hello, I found this message in /var/logs/messages Mar 21 00:39:38 nas kernel: [39424.722003] ------------[ cut here ]------------ Mar 21 00:39:38 nas kernel: [39424.724034] WARNING: CPU: 1 PID: 10300 at fs/btrfs/transaction.c:322 record_root_in_trans+0xd1/0xe0 Mar 21 00:39:38 nas kernel: [39424.7261...