TerraMaster Forum

Applicable Versions:

All Versions

Applicable Models:

All TNAS Models

Issue:
The TOS message center indicates "RAID Degraded," and the NAS continues to emit a beeping sound.

Cause:
A hard drive in the array has failed, causing it to detach from the array and resulting in array degradation.



Solution:
1.According to the TOS Notification prompt, identify and note the failed hard drive. Short press the power button to turn off the NAS. Wait until the power indicator light is off, then remove the failed hard drive. Insert a new hard drive, ensuring that the capacity of the new hard drive is larger than or equal to the smallest drive in the array.

2.Short press the power button to turn on the NAS. Navigate to Control Panel > Storage Manager > Storage Pool, click the "Edit" button, and in the pop-up menu, select "Repair RAID." This process may take some time, so please be patient until it is completed. See the image below:



Note:
This solution is only applicable to array types including TRAID, TRAID+, RAID1, RAID5, RAID6, RAID10. If you encounter any issues or are unsure how to proceed, please consult the online customer service on the official website.

Ok but what if the system disk is not replicated? The data disc was synchronized but now the system is only in one of the two raid 1 drives

martingh wrote: ↑25 Jan 2025, 06:35

Please, what is the version of your TOS system? If it's TOS 5, it doesn't matter. For TOS 6, it depends on where the system disk is located. TOS 6 supports two system disks. If you have two system disks, replacing one of them won't be a problem because it will automatically synchronize another system disk.

TMnick wrote: ↑25 Jan 2025, 13:55

martingh wrote: ↑25 Jan 2025, 06:35

Please, what is the version of your TOS system? If it's TOS 5, it doesn't matter. For TOS 6, it depends on where the system disk is located. TOS 6 supports two system disks. If you have two system disks, replacing one of them won't be a problem because it will automatically synchronize another system disk.

I have TOS6 and this is exactly the problem. It synchronized the data volumes however md8 and md9 partitions were not synchronized.
I finally managed to make it work but I had to add manually the partitions to the md8 and md9 raids and had to create the EFI partition.

I expected this to be done automatically once you insert and synchronize a new nvme!

Now I'm going to replace the other nvme (the heatsink included is not compatible with the case so I have to return them and buy a nvme without heatsink and buy smaller ones).

As you can see the md1 is being synchronized however md8 and md9 will not:
:~# cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [multipath] [faulty]
md1 : active raid1 sdzb4[3] sdza4[2]
966137136 blocks super 1.2 [2/1] [_U]
[>....................] recovery = 3.8% (37205888/966137136) finish=37.2min speed=415777K/sec
bitmap: 2/8 pages [8KB], 65536KB chunk

md0 : active raid5 sdb4[0] sda4[3] sdd4[2] sdc4[1]
46843726848 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]

md8 : active raid1 sdza3[2]
1997824 blocks super 1.2 [2/1] [U_]
bitmap: 1/1 pages [4KB], 65536KB chunk

md9 : active raid1 sdza2[3]
7995392 blocks super 1.2 [2/1] [U_]
bitmap: 1/1 pages [4KB], 65536KB chunk

So this is what I had when it finished the synchronization:
martin_adm@TNAS4:~# mdadm --detail /dev/md9
/dev/md9:
Version : 1.2
Creation Time : Sun Jan 19 20:27:48 2025
Raid Level : raid1
Array Size : 7995392 (7.63 GiB 8.19 GB)
Used Dev Size : 7995392 (7.63 GiB 8.19 GB)
Raid Devices : 2
Total Devices : 1
Persistence : Superblock is persistent

Intent Bitmap : Internal

Update Time : Sat Jan 25 10:27:52 2025
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0

Name : TNAS:UTOSCORE-X86-S64
UUID : 5fde41d6:ff3bac6c:d4d4d565:e965fff0
Events : 712

Number Major Minor RaidDevice State
3 259 3 0 active sync /dev/sdza2
- 0 0 1 removed



So I had to manually add md8 and md9:
martin_adm@TNAS4:~# mdadm --add /dev/md9 /dev/sdzb2
mdadm: added /dev/sdzb2
martin_adm@TNAS4:~# mdadm --add /dev/md8 /dev/sdzb3
mdadm: added /dev/sdzb3
martin_adm@TNAS4:~# mdadm --assemble --force /dev/md8
martin_adm@TNAS4:~# mdadm --assemble --force /dev/md9
martin_adm@TNAS4:~# mdadm --detail --scan >> /etc/mdadm/mdadm.conf
martin_adm@TNAS4:~# update-initramfs -u

And with all of these, still missing the EFI partition... More steps...
So recovering a System Disk is everything but automatic, and I think it should when you replace a damaged disk.

Is this suitable for all RAID modes or some specific RAID modes?

CathyW wrote: ↑03 Apr 2025, 19:32 Is this suitable for all RAID modes or some specific RAID modes?

Array recovery is only applicable to protective RAID configurations such as RAID 1, RAID 5, RAID 10, etc.

F4-212, TOS 5.1.73, TRaid
Drives: 2x24TB, 1x20TB, 1x3TB

Yesterday I replaced a 512GB SSD with a 20TB HDD. I repaired the volume which took a little over a day. Once complete, I was able to expand the storage pool to 27TB. The TM Raid Calculator states I should have 47TB of available space.
I am a beginner user and am not comfortable using commands in a console. I spoke with a representative in chat and they suggested I recreate my storage pool. They said that would make me lose the data. I don't have a way to back all of this up. Any help is appreciated.