[Help] What to do when a few bad sectors on one of the 4 HDD in a TRAID 5
Posted: 29 Jul 2025, 18:02
Hi,
I read this thread here viewtopic.php?t=7780, which advises users to replace the HDD, when they get a warning for bad sectors on one of the hdd in a RAID.
My system is:
Device: F4-220
OS: 5.1.67-00214
4 HDD x 2 TB formatted as EXT4
type: TRAID 5
All HDD are reported "in good state" and the RAID array is also showing as not damaged.
A few days ago I got a report that /dev/sdc (3rd HDD in the TRAID5) has 8 bad sectors:
"error_description": "Error: UNC 8 sectors at LBA = 0x01aaab80 = 27962240",
"previous_commands": [
{
"registers": {
"command": 200,
"features": 0,
"count": 8,
"lba": 11185024,
"device": 225,
"device_control": 8
},
The questions for Tech Support are:
- Is there a way to repair the HDD in the TRAID?
I would not like to replace the HDD just because of those bad sectors. After all, this is why we have RAID, to make sure that the failure of a single hdd does not damaged the entire system.
- Should I try to replace the HDD? Was the bug mentioned in the post I linked above fixed?
Can I do this myself?
Thanks
Sorin
I read this thread here viewtopic.php?t=7780, which advises users to replace the HDD, when they get a warning for bad sectors on one of the hdd in a RAID.
My system is:
Device: F4-220
OS: 5.1.67-00214
4 HDD x 2 TB formatted as EXT4
type: TRAID 5
All HDD are reported "in good state" and the RAID array is also showing as not damaged.
A few days ago I got a report that /dev/sdc (3rd HDD in the TRAID5) has 8 bad sectors:
"error_description": "Error: UNC 8 sectors at LBA = 0x01aaab80 = 27962240",
"previous_commands": [
{
"registers": {
"command": 200,
"features": 0,
"count": 8,
"lba": 11185024,
"device": 225,
"device_control": 8
},
The questions for Tech Support are:
- Is there a way to repair the HDD in the TRAID?
I would not like to replace the HDD just because of those bad sectors. After all, this is why we have RAID, to make sure that the failure of a single hdd does not damaged the entire system.
- Should I try to replace the HDD? Was the bug mentioned in the post I linked above fixed?
Can I do this myself?
Thanks
Sorin