Volume Corrupted After Update

RAID, Volume, storage pool, hard drive, USB, SSD cache and iSCSI LUN
Locked
User avatar
yordan
Posts: 4
Joined: 28 Jan 2023, 02:36

Volume Corrupted After Update

Post by yordan »

Hi folks!
I did the update to TOS5 but I am having the following issue now.
My Volume2 is not mounting here are some logs and errors:

dmsg

Code: Select all

[ 3390.496651] BTRFS info (device md0): trying to use backup root at mount time
[ 3390.496666] BTRFS info (device md0): using free space tree
[ 3390.496672] BTRFS info (device md0): has skinny extents
[ 3390.520039] BTRFS critical (device md0): corrupt leaf: root=456 block=1410992898048 slot=4 ino=43546, invalid inode transid: has 204220 expect [0, 204192]
[ 3390.520247] BTRFS critical (device md0): corrupt leaf: root=456 block=1410992898048 slot=4 ino=43546, invalid inode transid: has 204220 expect [0, 204192]
[ 3390.520272] BTRFS warning (device md0): failed to read tree root
[ 3390.520477] BTRFS critical (device md0): corrupt leaf: root=456 block=1410992898048 slot=4 ino=43546, invalid inode transid: has 204220 expect [0, 204192]
[ 3390.520861] BTRFS critical (device md0): corrupt leaf: root=456 block=1410992898048 slot=4 ino=43546, invalid inode transid: has 204220 expect [0, 204192]
[ 3390.520886] BTRFS warning (device md0): failed to read tree root
[ 3398.819232] BTRFS error (device md0): parent transid verify failed on 2749613850624 wanted 203663 found 204272
[ 3398.824081] BTRFS error (device md0): parent transid verify failed on 2749613850624 wanted 203663 found 204272
[ 3398.824105] BTRFS error (device md0): failed to read block groups: -5
[ 3398.839741] BTRFS error (device md0): open_ctree failed
[ 3648.187866] BTRFS info (device md0): setting nodatasum
[ 3648.187877] BTRFS info (device md0): setting nodatacow, compression disabled
[ 3648.187882] BTRFS info (device md0): turning off barriers
[ 3648.187888] BTRFS info (device md0): enabling auto defrag
[ 3648.187891] BTRFS info (device md0): using free space tree
[ 3648.187895] BTRFS info (device md0): has skinny extents
[ 3648.220841] BTRFS critical (device md0): corrupt leaf: root=456 block=1410992898048 slot=4 ino=43546, invalid inode transid: has 204220 expect [0, 204192]
[ 3648.221019] BTRFS critical (device md0): corrupt leaf: root=456 block=1410992898048 slot=4 ino=43546, invalid inode transid: has 204220 expect [0, 204192]
[ 3648.221037] BTRFS warning (device md0): failed to read tree root
[ 3648.227035] BTRFS error (device md0): open_ctree failed

Code: Select all

Starting repair.
Opening filesystem to check...
parent transid verify failed on 1410992898048 wanted 204191 found 204221
parent transid verify failed on 1410992898048 wanted 204191 found 204221
parent transid verify failed on 1410992898048 wanted 204191 found 204221
Ignoring transid failure
WARNING: could not setup extent tree, skipping it
Couldn't setup device tree
ERROR: cannot open file system

Code: Select all

[yordan@TNAS ~]# blkid
/dev/sda1: LABEL="UTOSDISK-X86-S64" UUID="5ab33a2d-76c0-4894-9b9d-0c96c1796e51" BLOCK_SIZE="1024" TYPE="ext4" PARTLABEL="primary" PARTUUID="de902fb0-f5d5-4abf-a5fb-65e1ab1eaea4"
/dev/sdb1: LABEL="UTOSDISK-X86-S64" UUID="19f2d26a-4c2f-494a-a2ee-c7f367f44629" BLOCK_SIZE="1024" TYPE="ext4" PARTLABEL="primary" PARTUUID="3a459d09-023a-4e9a-abc4-3824f013abb9"
/dev/sdc1: LABEL="UTOSDISK-X86-S64" UUID="d081c960-8260-4af8-8759-295eb5fb7765" BLOCK_SIZE="1024" TYPE="ext4" PARTLABEL="primary" PARTUUID="a2f11ed5-a2b0-4b22-8292-e807a3714945"
/dev/sdd1: LABEL="UTOSDISK-X86-S64" UUID="f5517649-3c13-4c86-92ac-fc535258b939" BLOCK_SIZE="1024" TYPE="ext4" PARTLABEL="primary" PARTUUID="56019887-8563-4075-94b5-7134f18f1fba"
/dev/sde1: LABEL="UTOSDISK-X86-S64" UUID="95ed91bc-d69d-49a1-849a-be864882e101" BLOCK_SIZE="1024" TYPE="ext4" PARTLABEL="primary" PARTUUID="78af920c-f6eb-4fc6-a616-9512fd87bea9"
/dev/mapper/vg0-lv0: LABEL="TOS_VOL_20230127" UUID="00000001-2301-2723-4330-6cbfb500850a" UUID_SUB="97a4645e-39ca-4ede-b149-0267e88221f2" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/md1: UUID="s64ulR-sPf1-RZdl-y4mS-OknT-jOjC-HtN2AL" TYPE="LVM2_member"
/dev/md0: UUID="18b8031b-9763-4bf5-8a94-d35292ef6a48" UUID_SUB="b4edc5fd-b875-441a-905e-4ced31658c3f" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sda2: UUID="9b6c87fa-86cd-bdcb-fabf-930ae3a4fc33" UUID_SUB="a1ab15f2-6998-f04e-100c-a5af595cdfed" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="71830061-b927-4698-9682-4b19d97737dd"
/dev/sda3: UUID="a8882b6b-375f-7fc5-a645-7c738a2c293c" UUID_SUB="d08624b5-6d86-1b26-9d0e-1406ad084c3c" LABEL="TNAS:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="e85c0758-db24-4f26-b757-c354eae44054"
/dev/sda4: UUID="55658a80-a80b-d3a8-8708-c10bf4da8753" UUID_SUB="010e1754-e660-2235-5439-3ea15cccb1b9" LABEL="TNAS-00724F:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="05fe5028-4ea2-4a6e-b835-2195f3f557eb"
/dev/sdb2: UUID="9b6c87fa-86cd-bdcb-fabf-930ae3a4fc33" UUID_SUB="87b14ce6-7508-7e08-1a86-2eac5fe3d072" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="6ec17177-fda8-4462-ba75-2bdef815ec56"
/dev/sdb3: UUID="a8882b6b-375f-7fc5-a645-7c738a2c293c" UUID_SUB="4d882e6d-1c37-6c3f-e8d8-be9353905bd5" LABEL="TNAS:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="56cdd86f-22ef-46c6-9bc3-24529a361c27"
/dev/sdb4: UUID="55658a80-a80b-d3a8-8708-c10bf4da8753" UUID_SUB="e213193e-597e-1fdd-f031-29aa8fe15636" LABEL="TNAS-00724F:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="25fa256a-7fa4-4b23-bf9e-07cddefd8dca"
/dev/sdc2: UUID="9b6c87fa-86cd-bdcb-fabf-930ae3a4fc33" UUID_SUB="672892bd-1400-fc97-d757-296b7461152b" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="e9aca9f9-f0b9-41b0-a84b-e9b837ba2b26"
/dev/sdc3: UUID="a8882b6b-375f-7fc5-a645-7c738a2c293c" UUID_SUB="bf64b2ff-640b-f517-3c42-d7430ed005f1" LABEL="TNAS:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="cfcfee50-b8a2-470f-9f94-d5afe7ef8a6b"
/dev/sdc4: UUID="55658a80-a80b-d3a8-8708-c10bf4da8753" UUID_SUB="3d427088-d390-d6c1-0258-2a9fa0655b52" LABEL="TNAS-00724F:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="34260279-467e-4e32-8410-cce0a0644cee"
/dev/sdd2: UUID="9b6c87fa-86cd-bdcb-fabf-930ae3a4fc33" UUID_SUB="1926493f-dc9c-abb4-d0ad-4a56e3d24d43" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="4f8b06cc-c9dc-4797-aea9-e3ae334f3115"
/dev/sdd3: UUID="a8882b6b-375f-7fc5-a645-7c738a2c293c" UUID_SUB="92a3321f-f6c2-f8de-8fdb-22a0112df24d" LABEL="TNAS:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="9290a04a-5dc7-4883-bca6-8e8bd0da65d0"
/dev/sdd4: UUID="55658a80-a80b-d3a8-8708-c10bf4da8753" UUID_SUB="c5860e4e-3103-cc2f-f3b7-e11ee5529717" LABEL="TNAS-00724F:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="0f79c068-28f2-4b84-901f-4ca9ca840c43"
/dev/sde2: UUID="9b6c87fa-86cd-bdcb-fabf-930ae3a4fc33" UUID_SUB="ab0f7b9a-ca47-fd53-0922-4cd1561e1ab2" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="d9501896-09d5-4d0b-921b-a6ae76603f66"
/dev/sde3: UUID="a8882b6b-375f-7fc5-a645-7c738a2c293c" UUID_SUB="c12f7111-a572-1300-0277-c0850fc7483d" LABEL="TNAS:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="fa794382-609a-4ac0-bb28-461a87d82204"
/dev/sde4: UUID="98b81179-8b15-f4d5-a466-49e0d13dc2d0" UUID_SUB="5a5b8772-1f75-58ed-9e23-4e0bb3b808f8" LABEL="TNAS:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="126cb10d-b890-415d-8667-def9489a2551"
/dev/md9: UUID="e0a13c04-8328-4b1c-84ae-181df29036d1" BLOCK_SIZE="4096" TYPE="ext4"
/dev/md8: UUID="1e8b338e-10a4-4ff7-aacd-49c2ae105e09" TYPE="swap"
User avatar
yordan
Posts: 4
Joined: 28 Jan 2023, 02:36

Re: Volume Corrupted After Update

Post by yordan »

ALSO LITTLE BIT MORE DEBUG INFO

Code: Select all

mdadm -D /dev/md0
/dev/md0:
        Version : 1.2
  Creation Time : Mon Apr 15 03:20:32 2019
     Raid Level : raid5
     Array Size : 11710780416 (11168.27 GiB 11991.84 GB)
  Used Dev Size : 3903593472 (3722.76 GiB 3997.28 GB)
   Raid Devices : 4
  Total Devices : 4
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Sat Jan 28 02:49:52 2023
          State : clean 
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 512K

           Name : TNAS-00724F:UTOSUSER-X86-S64
           UUID : 55658a80:a80bd3a8:8708c10b:f4da8753
         Events : 6800

    Number   Major   Minor   RaidDevice State
       0       8       52        0      active sync   /dev/sdd4
       1       8       36        1      active sync   /dev/sdc4
       2       8        4        2      active sync   /dev/sda4
       3       8       20        3      active sync   /dev/sdb4
[yordan@TNAS ~]# mdadm -D /dev/md1
/dev/md1:
        Version : 1.2
  Creation Time : Fri Jan 27 08:43:31 2023
     Raid Level : raid1
     Array Size : 224006144 (213.63 GiB 229.38 GB)
  Used Dev Size : 224006144 (213.63 GiB 229.38 GB)
   Raid Devices : 1
  Total Devices : 1
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Fri Jan 27 12:08:23 2023
          State : clean 
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           Name : TNAS:UTOSUSER-X86-S64  (local to host TNAS)
           UUID : 98b81179:8b15f4d5:a46649e0:d13dc2d0
         Events : 6

    Number   Major   Minor   RaidDevice State
       0       8       68        0      active sync   /dev/sde4
User avatar
TMnorah
TerraMaster Team
Posts: 117
Joined: 17 Aug 2021, 09:51

Re: Volume Corrupted After Update

Post by TMnorah »

Please contact our technical support through our support email and tell them your situation. It is suggested to attach a screenshot.
To contact our team, please send email to following addresses, remember to replace (at) with @
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
User avatar
yordan
Posts: 4
Joined: 28 Jan 2023, 02:36

Re: Volume Corrupted After Update

Post by yordan »

No worries, I had most of the important data on another hard drive. Also I bought Synology since they don't ask me to backup 12TB before I do update of the OS.
User avatar
matt_30
Posts: 67
Joined: 02 Jan 2021, 23:22

Re: Volume Corrupted After Update

Post by matt_30 »

I believe I have the same problem.

Since around this time I have been seeing corruption which I have repaired only for it to return.

Has this become a known problem.

I have also noticed that journaling is not available on ext4 partitions. Is this by design?

```
[matt@TNAS-7702 pihole]# tune2fs -l /dev/mapper/vg0-lv2
tune2fs 1.46.5 (30-Dec-2021)
Filesystem volume name: <none>
Last mounted on: /Volume3
Filesystem UUID: 00000003-2206-2514-2705-6cbfb5017702
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: ext_attr resize_inode dir_index filetype extent 64bit flex_bg ea_inode sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
```
User avatar
yordan
Posts: 4
Joined: 28 Jan 2023, 02:36

Re: Volume Corrupted After Update

Post by yordan »

If I were you I will just get another device, I know how you feel - paying more but you should understand that the software is everything ... TerraMaster offers good hardware for the price but the software has always been the weak point. And at the end it is all about time .... the time you will need to recover (if you can recover)... think of this time as money you are loosing ... so pay in advance and don't rely the mercy of TM.
Locked