TerraMaster Forum

I forced my way through the repair process that worked with the second command "e2fsck -b 32768 /dev/md0 -y"

BTW a few remarks on the procedure as it doesn't work exactly like scripted.

umount commands only works once you kill all processes including your bash sessions (especially for /home), so I advise to use the lazy option

umount -l /home

then disconnect, and it will get unmounted finally, now you can proceed with the following repair commands after reconnecting as root user..

attaching here the outpout of "dmesg | grep error" command, can you tell if anything is indicating an issue?
"
[root@TNAS-002C6C ~]# dmesg |grep error
[ 1.018436] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 7.790691] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168e-3.fw failed with error -2
[ 50.007136] ata1.00: error: { UNC }
[ 50.009620] sd 1:0:0:0: [sda] tag#10 Add. Sense: Unrecovered read error - auto reallocate failed
[ 50.009647] print_req_error: I/O error, dev sda, sector 2659856
[ 5725.503809] ata2.00: error: { UNC }
[ 5725.505521] sd 2:0:0:0: [sdb] tag#17 Add. Sense: Unrecovered read error - auto reallocate failed
[ 5725.505547] print_req_error: I/O error, dev sdb, sector 2468905528
[30717.623139] ata2.00: error: { UNC }
[30717.624618] sd 2:0:0:0: [sdb] tag#7 Add. Sense: Unrecovered read error - auto reallocate failed
[30717.624645] print_req_error: I/O error, dev sdb, sector 2330494512
[61461.313177] ata2.00: error: { UNC }
[61461.314801] sd 2:0:0:0: [sdb] tag#15 Add. Sense: Unrecovered read error - auto reallocate failed
[61461.314828] print_req_error: I/O error, dev sdb, sector 1365852432
[81824.200877] ata2.00: error: { UNC }
[81824.202725] sd 2:0:0:0: [sdb] tag#8 Add. Sense: Unrecovered read error - auto reallocate failed
[81824.202752] print_req_error: I/O error, dev sdb, sector 4276650552
[82844.361171] ata2.00: error: { UNC }
[82844.363241] sd 2:0:0:0: [sdb] tag#14 Add. Sense: Unrecovered read error - auto reallocate failed
[82844.363268] print_req_error: I/O error, dev sdb, sector 2716369200
[root@TNAS-002C6C ~]#
"

I am attempting to repair some errors found by dmesg

When running the command

btrfs check /dev/mapper/vg0-lv0

I get

Opening filesystem to check...
ERROR: cannot open device '/dev/mapper/vg0-lv0': Device or resource busy
ERROR: cannot open file system

whats the next step please ?

Please follow the first and second steps of the article. viewtopic.php?f=79&t=2575

TMSupport wrote: > > > Please follow the first and second steps of the article. > viewtopic.php?f=79&t=2575 I have done, the error occurs at step 2: btrfs check /dev/mapper/vg0-lv0

The file system cannot be opened and cannot be repaired. Please find a data recovery company for data recovery.

TMSupport wrote:
>


I do not understand, I can access my files. I am following your instruction here viewtopic.php?p=18080#p18080 due to the randomly not been able to access TNAS....sometimes and only since the last TOS update. If I switch off the device on and off, I can access and remap the network drive

Are you suggesting i am going to lose access to my files, are you suggesting i should stop using the device or what ???

The btrfs file system is unstable on arm models.
It is recommended that you copy the data first, format the hard disk and reinstall the TOS and use the ext4 file system.

TMSupport wrote:
> The btrfs file system is unstable on arm models.
> It is recommended that you copy the data first, format the hard disk and
> reinstall the TOS and use the ext4 file system.


So, what is the best method for me to do this ?

my current setup is a 4TB HDD in RAID 0 configuration, is my best solution to BUY another 4TB and backup all my data on that then format the drives in the TNAS to EXT4 ?