How can I repair filesystem for /dev/md9 ?

SMB, NFS, AFP, FTP, web file manager and Rsync server.
Locked
User avatar
antocara
Posts: 14
Joined: 08 Aug 2020, 12:29

How can I repair filesystem for /dev/md9 ?

Post by antocara »

Hi, I have F4-210 with 4 HDD formatted as ext4 and each HDD as a single volume. I'm experincing a lot of issue and mulfuncions, apparently even with a clean Filesystem.
I then tried to boot the system with only one HDD at time detaching the other three. This time I 've found filesystem errors that I have repaired.

But the last drive tgive me file system errors on /dev/md9 and I do not know I to repair this.
Any help for that ?

Here is the output for blkid:
root@TNAS-01573E:/home/admin# blkid
/dev/sda1: LABEL="UTOSBOOT-X86-S64" UUID="3a4f3362-b26e-4661-9a77-9185f193e480" TYPE="ext4" PARTLABEL="primary" PARTUUID="43f846d7-a7a5-42d1-b609-cf763d791d00"
/dev/sdb1: LABEL="UTOSDISK-X86-S64" UUID="b0579d70-089d-4773-910d-f0361f9e6e25" TYPE="ext4" PARTLABEL="primary" PARTUUID="0b1f8e79-0cc0-429f-8990-a030fd0db859"
/dev/sdb2: UUID="bfa942a5-71fa-b070-6db2-cb989c0d3127" UUID_SUB="e154a692-99b4-b3e3-eeda-8a22fb115f9e" LABEL="TNAS:UTOSCORE-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="5e6ddd65-5749-44e8-a8c6-da0917278549"
/dev/sdb3: UUID="c79b3fc3-5a24-7cee-08a5-f8cd347b820c" UUID_SUB="413490b2-9d6a-2dfb-de5a-0e76c50ca718" LABEL="TNAS-01573E:UTOSSWAP-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="304e51c8-212d-480b-a055-d2e7d01e354b"
/dev/sdb4: UUID="84818ed6-8897-40bd-a915-cf593fdea79a" UUID_SUB="08f21b1e-3409-c784-b368-e3f376b41924" LABEL="TNAS-01573E:UTOSUSER-X86-S64" TYPE="linux_raid_member" PARTLABEL="primary" PARTUUID="f2c68b2f-e565-4550-9984-c40f3065ed49"
/dev/md9: UUID="6affff87-a1ac-4f86-a979-3dd8b1ca0d59" TYPE="ext4"
/dev/md1: UUID="w38S8k-MbeZ-dQc7-WVJX-m5Rz-eI60-66uE1G" TYPE="LVM2_member"
/dev/vg1/lv1: UUID="340a3030-ce87-456e-b7c8-6855b22ddf5e" TYPE="ext4"
/dev/md8: TYPE="swap"
/dev/mapper/vg1-lv1: UUID="340a3030-ce87-456e-b7c8-6855b22ddf5e" TYPE="ext4"

Here is the output for dmesg |grep err:
root@TNAS-01573E:/home/admin# dmesg |grep err
[ 0.000000] CPU features: enabling workaround for ARM erratum 845719
[ 7.512498] ***WARNING***: Unable to find /var/lib/scst/vdev_mode_pages (err -2), saved mode pages disabled. You should create this directory manually or reinstall SCST
[ 10.221588] hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
[ 18.009883] ata1: COMRESET failed (errno=-16)
[ 32.990974] EXT4-fs (md9): warning: mounting fs with errors, running e2fsck is recommended
[ 36.920375] EXT4-fs error (device md9): ext4_mb_generate_buddy:758: group 1, block bitmap and bg descriptor inconsistent: 19516 vs 19517 free clusters
[ 37.038819] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm rm: deleted inode referenced: 427
[ 37.057863] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm ln: deleted inode referenced: 427
[ 37.074821] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm ln: deleted inode referenced: 427
[ 37.091870] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm ln: deleted inode referenced: 427
[ 39.072279] xt_ipvs: Unknown symbol ip_vs_proto_get (err 0)
[ 39.108585] xt_ipvs: Unknown symbol ip_vs_proto_get (err 0)
[ 39.130574] xt_ipvs: Unknown symbol ip_vs_proto_get (err 0)
[ 39.170032] xt_ipvs: Unknown symbol ip_vs_proto_get (err 0)
[ 43.370603] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm nasips: deleted inode referenced: 427
[ 43.392912] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm nasips: deleted inode referenced: 427
[ 43.409362] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm nasips: deleted inode referenced: 427
[ 45.122187] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 45.139942] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 45.159966] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 45.192999] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 45.207921] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 45.223169] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 45.247386] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.660841] EXT4-fs error: 34 callbacks suppressed
[ 49.665774] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.686825] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.713952] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.734445] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.756423] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.783108] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.827130] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.859581] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.898557] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm regcloud: deleted inode referenced: 427
[ 49.923980] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm role: deleted inode referenced: 427
[ 55.143911] EXT4-fs error: 43 callbacks suppressed
[ 55.148829] EXT4-fs error (device md9): ext4_lookup:1584: inode #80: comm role: deleted inode referenced: 427
[ 55.669390] EXT4-fs error (device md9): ext4_lookup:1584: inode #7149: comm cp: deleted inode referenced: 7072
[ 55.705649] EXT4-fs error (device md9): ext4_lookup:1584: inode #7149: comm cp: deleted inode referenced: 7072
[ 55.742731] EXT4-fs error (device md9): ext4_lookup:1584: inode #7149: comm cp: deleted inode referenced: 7072
[ 55.776622] EXT4-fs error (device md9): ext4_lookup:1584: inode #7149: comm cp: deleted inode referenced: 7072
[ 55.808294] EXT4-fs error (device md9): ext4_lookup:1584: inode #7149: comm cp: deleted inode referenced: 7072
[ 55.842165] EXT4-fs error (device md9): ext4_lookup:1584: inode #7149: comm cp: deleted inode referenced: 7073
[ 55.888134] EXT4-fs error (device md9): ext4_lookup:1584: inode #7149: comm cp: deleted inode referenced: 7073
[ 55.918688] EXT4-fs error (device md9): ext4_lookup:1584: inode #7149: comm cp: deleted inode referenced: 7073
[ 55.948507] EXT4-fs error (device md9): ext4_lookup:1584: inode #7149: comm cp: deleted inode referenced: 7073
[ 65.165493] EXT4-fs error: 23 callbacks suppressed .
.. Trunkated
User avatar
TMSupport
TerraMaster Team
Posts: 2314
Joined: 13 Dec 2019, 15:15

Re: How can I repair filesystem for /dev/md9 ?

Post by TMSupport »

The md9 partition is a system partition, please try to reinstall the system to fix it.
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
antocara
Posts: 14
Joined: 08 Aug 2020, 12:29

Re: How can I repair filesystem for /dev/md9 ?

Post by antocara »

Ok,
Thanks. I'm going to follow the procedure.
Thanks
Locked