Fixes to EXT4 mounting failure

Hard Drive, volume, storage pool, RAID
Post Reply
User avatar
TMSupport
TerraMaster Team
Posts: 2314
Joined: 13 Dec 2019, 15:15

Fixes to EXT4 mounting failure

Post by TMSupport »

Fixes to EXT4 mounting failure

Applicable models: all NAS models.

Failures:
1. TOS prompts for initialization and asks to format hard drives.
2. TNAS freezes.
3. TNAS loses connections.
4. Unable to upload files or having “input/output error” while copying data via SMB.

Root cause:
Some partitions of the hard drives are damaged and causes the failure to mount the array. md9 and md0 need to be fixed.

Fixes:
1. Mount ext4 file system
cmd:
mount /dev/md9 /
mount /dev/md0 /mnt/md0

Go to step 2 if it comes to the “input/output error”.

2. Input the cmd:
e2fsck -p /dev/mdx
and hit Enter to wait for the fix result, once done, go back to Step 1 to run the commands again.

Note: If the fix fails, please turn off TNAS, remove the hard drive, put them back, reboot TNAS, and execute the commands again.

3. If the above fails multiply times, please consider to do a bad block san for the hard drives.
Note:
The bad blocks will be marked after scanning, and will be skipped in the next reading. Please operate with caution as it may cause data loss when bad blocks are large. It’s suggested to operate with the presence of a professional data recovery company to avoid possible data loss.

cmd’s to scan bad blocks:
badblocks -b 4096 /dev/mdx -o /tmp/mdx.bacblock 2>/dev/null

and then execute the repair commands:
e2fsck -l /tmp/mdx.bacblock /dev/mdx

Once completed, please execute the mount commands:
mount /dev/md9 /
mount /dev/md0 /mnt/md0

Note:
1. /tmp/mdx.bacblock: means the array that needs to be executed with the commands, like md9, md0…

2. /dev/mdx: means the bad block, like md9, md0…
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
sts41
Posts: 20
Joined: 26 May 2022, 21:29

Re: Fixes to EXT4 mounting failure

Post by sts41 »

I upgraded my F5-221 from 4.2.40 to TOS 5.1.67.
In preperation for TRAID I added a 12 TB drive in slot 5, created a volume with ext4 filesystem and copied over all my files. (backup)
I rebuild the system with TOS 5.1.67 and built a TRAID with the 4X4TB disks.
I then plugged in my 12 TB drive and I am unable to get TOS 5 to read it.

Disk /dev/sde: 10.9 TiB, 12000138625024 bytes, 23437770752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: B4B3EF71-A327-4B1C-8533-5F90484C3FE1

Device Start End Sectors Size Type
/dev/sde1 2048 585727 583680 285M Linux filesystem
/dev/sde2 585728 4585471 3999744 1.9G Linux filesystem
/dev/sde3 4585472 6586367 2000896 977M Linux filesystem
/dev/sde4 6586368 23437768703 23431182336 10.9T Linux filesystem



fsck returns:
[user@TNAS-6384 /]# e2fsck /dev/sdd4
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdd4

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>

/dev/sdd4 contains a linux_raid_member file system labelled 'TNAS-016384:UTOSUSER-X86-S64'

Is there any way to get this to mount on TOS 5.1.67?

Thanks Steve
User avatar
sts41
Posts: 20
Joined: 26 May 2022, 21:29

Re: Fixes to EXT4 mounting failure

Post by sts41 »

OK... so I rebooted the TNAS with the drive in and it fixed and mounted it....

Thanks Steve
Post Reply