Fixes to EXT4 mounting failure
Posted: 30 Sep 2020, 14:52
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…
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…