How to repair a corrupted file system?

[TMlinda]

{L_BUTTON_AT}user222333

You can plug in all the hard disk to install 5.1.29 system, please refer to this link: viewtopic.php?f=76&t=423 if the installation interface appear in the process of "create the storage pool" or "formatting" word, Please do not proceed and contact us.

[GJ86]

Hello
I have a problem with the file system.
After losing power, Volume1 BTRFS became courrapted

Server: F5-221 TOS 4 -> TOS 5.0.176-00227
2 hard drives :3 and 4 TB combined in RAID0, both shown as good.
After executing all the commands, I finally received this message.

Code: Select all

[grzegorz@Serwerek /]# /etc/tos/scripts/mntdata

2024/11/16 21:37:01 /work/PKGS/Assembly/tosdeamon/core/sqlitedb/sqlitedb_model.go:76 ERROR: could not find tuple for trigger 66750 (SQLSTATE XX000)
[1.638ms] [rows:0] ALTER TABLE "external_acl" DROP CONSTRAINT "fk_external_acl_user_table"
[DEBUG /usr/sbin/mdadm --re-add /dev/md9 /dev/sda2]
[DEBUG /usr/sbin/mdadm --re-add /dev/md9 /dev/sdb2]
[DEBUG /usr/sbin/mdadm -A /dev/md8 /dev/sda3 -f]
[DEBUG /usr/sbin/mdadm --re-add /dev/md8 /dev/sda3]
[DEBUG /usr/sbin/mdadm --re-add /dev/md8 /dev/sdb3]
[DEBUG /usr/sbin/mdadm --re-add /dev/md0 /dev/sda4]
[DEBUG /usr/sbin/mdadm --re-add /dev/md0 /dev/sdb4]
[DEBUG /usr/sbin/iniparse -a -f /etc/volume/volume.conf -s 00000001-2408-2020-2037-6cbfb501cf26 -system]
mountPath =  /Volume1
check filesystem on /dev/mapper/vg0-lv0 
/etc/tos/scripts/flashcache start /dev/mapper/vg0-lv0
[DEBUG /etc/tos/scripts/flashcache start /dev/mapper/vg0-lv0]
[DEBUG 2024/11/16 21:37:07 can't found flashCache block device!
mount: /Volume1: wrong fs type, bad option, bad superblock on /dev/mapper/vg0-lv0, missing codepage or helper program, or other error.
Mount Failed: /dev/mapper/vg0-lv0 to /Volume1
]
[DEBUG /bin/bash -c /etc/init.d/nas/mkbase]

File system not returned
Can anyone help PLS

[GJ86]

Referring to the fact that no one could help restore the file system, I found another, but more time-consuming and requiring additional disk space method to recover data.

I bought a new disk and made Volume2 (I had free disk bays)
I followed the guide: https://archive.kernel.org/oldwiki/btrf ... store.html
The simplest version, unfortunately did not help, so I used the more difficult one with the command:

Code: Select all

btrfs restore -mi t [block number] /dev/mapper/vg0-lg0 /Volume2/public/copy

– change it with your folder
For a large dataset, I suggest combining this with

Code: Select all

nohup &

https://phpunixman.sourceforge.net/index.php/man/nohup
Probably should looks like :

Code: Select all

nohup btrfs restore -mi t [numer bloku] /dev/mapper/vg0-lg0 /Volume2/public/copy &

I haven't used it and have currently recovered about 600GB from 7TB after 3 hours and i can't close my SSH conection
Recovered data seems to be fine – I'll let you know when I'm done
Good luck

[Ikaru]

Hello,

After a power outage and not having an UPS, I ended up with my volume being corrupted. From what I’ve gathered by searching on the web, it seems to be a corrupted metadata issue with my LVM. Currently, I have a RAID 0 setup consisting of 3x6TB and 1x4TB. I tried the method suggested in this forum section, but every time I attempt to run a btrfs check --repair, I get the following error:

Code: Select all

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 11483596980224 wanted 505698 found 505099
parent transid verify failed on 11483596980224 wanted 505698 found 505099
parent transid verify failed on 11483596980224 wanted 505698 found 505099
Ignoring transid failure
WARNING: could not setup extent tree, skipping it
Couldn't setup device tree
ERROR: cannot open file system

I really need your help, and this is the first time I’m facing this type of issue, so I’m a bit lost.

If you need more details, feel free to ask, especially if it helps me recover my data.

[TMtina]

Hello,

After a power outage and not having an UPS, I ended up with my volume being corrupted. From what I’ve gathered by searching on the web, it seems to be a corrupted metadata issue with my LVM. Currently, I have a RAID 0 setup consisting of 3x6TB and 1x4TB. I tried the method suggested in this forum section, but every time I attempt to run a btrfs check --repair, I get the following error:

Code: Select all

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 11483596980224 wanted 505698 found 505099
parent transid verify failed on 11483596980224 wanted 505698 found 505099
parent transid verify failed on 11483596980224 wanted 505698 found 505099
Ignoring transid failure
WARNING: could not setup extent tree, skipping it
Couldn't setup device tree
ERROR: cannot open file system

I really need your help, and this is the first time I’m facing this type of issue, so I’m a bit lost.

If you need more details, feel free to ask, especially if it helps me recover my data.

The error message indicates that the file system cannot be opened, we recommend that you seek the help of a professional data recovery service company.

[GJ86]

Hello,

After a power outage and not having an UPS, I ended up with my volume being corrupted. From what I’ve gathered by searching on the web, it seems to be a corrupted metadata issue with my LVM. Currently, I have a RAID 0 setup consisting of 3x6TB and 1x4TB. I tried the method suggested in this forum section, but every time I attempt to run a btrfs check --repair, I get the following error:

Code: Select all

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 11483596980224 wanted 505698 found 505099
parent transid verify failed on 11483596980224 wanted 505698 found 505099
parent transid verify failed on 11483596980224 wanted 505698 found 505099
Ignoring transid failure
WARNING: could not setup extent tree, skipping it
Couldn't setup device tree
ERROR: cannot open file system

I really need your help, and this is the first time I’m facing this type of issue, so I’m a bit lost.

If you need more details, feel free to ask, especially if it helps me recover my data.

You can try my method. I rocovered most of my data

[Mayhem]

I lost the ability to connect to my F2-221 earlier today. No TNAS desktop access, no Portainer access, can't get to my web interfaces for a couple of apps running in Portainer, no ability to mount it as a network drive..

So I am attempting to repair my installation using this guide but after step 2, I could not get back in so I rebooted the NAS.

Now at Step 3, it tells me that /dev/mapper/vg0-lv0 is in use and aborts. Repeating Step 1 shows neither /mnt/Volume1 nor /home are mounted.

e2fsck -b 32768 /dev/mapper/vg0-lv0 -y tells me the same thing.

[EthanLiu]

I lost the ability to connect to my F2-221 earlier today. No TNAS desktop access, no Portainer access, can't get to my web interfaces for a couple of apps running in Portainer, no ability to mount it as a network drive..

So I am attempting to repair my installation using this guide but after step 2, I could not get back in so I rebooted the NAS.

Now at Step 3, it tells me that /dev/mapper/vg0-lv0 is in use and aborts. Repeating Step 1 shows neither /mnt/Volume1 nor /home are mounted.

e2fsck -b 32768 /dev/mapper/vg0-lv0 -y tells me the same thing.

We can't provide a direct solution to your situation, so we recommend you schedule an appointment with an engineer for remote service. To schedule an appointment promptly, please contact our online customer service team through our official website.

[goombakid]

I'm not sure if this is the right place to ask this, but here it goes.

I've had an F2-210 with a 4TB and 3TB drive in it for a while now. All drives are all single disk. I'm trying to upgrade to a 20TB drive that I recently got (one that is listed as "recommended" for this NAS). My plan was to install the drive and move files from the 4TB drive (mainly video files, I use the NAS mainly for streaming at home) to this 20TB drive (formatted for single disk use). However, midway through transferring files over, my drive keeps getting a "RAID error" flag on the drive. I've already removed the drive and formatted it twice.

I've been bulk moving the files to the new drive. Could the overworking of the drive moving the files over be an issue? I just recently been getting an overheating notification.

What other reason could my drive be giving me a RAID error?

[TMtina]

Hello, regarding stability issues under high-intensity read/write operations, please prioritize troubleshooting the following three points:

Heat Dissipation Optimization: We recommend adjusting the settings in [Control Panel > Hardware > Fan Mode] to “Full Speed Mode” to ensure effective heat dissipation during sustained hard drive operation.

Power Supply Verification: Confirm you are using the original TNAS power adapter or a compatible one. An underpowered supply cannot deliver stable electricity to the hard drive under heavy load.

Connection Integrity: Inspect the SATA cable connections to ensure they are securely seated at both the motherboard and hard drive interfaces.

After completing these checks, attempt data transfer again and observe if the issue improves.