[TOS4] I Can't Click the “Edit” Button to Repair RAID 10 after It Is Corrupted?
Posted: 06 Nov 2024, 18:39
Applicable models
220, 420, 221, 421, 422 series models
Applicable Versions
TOS4
Problem phenomenon
The RAID 10 disk is damaged, pull out the bad disk and put in the new disk, but the “Edit” button is still grayed out. Cannot add the new disk to RAID 10 to repair it.
Solution
1. Create the new disk as a Single pool, and then immediately delete the newly created Single pool. This is to allow the disk to be automatically partitioned and formatted as a TOS4-only disk.
2. Login to the terminal via SSH/Telnet/HDMI monitor.
(SSH connection method: viewtopic.php?t=2350)
3. Enter the following command to confirm the constituent members of your RAID 10:
3. Enter the following command to add your new disk to RAID 10. (Assuming that sda, sdc, and sdd are RAID 10 member disks and sdb is the new disk)
4. Go back to the TOS control panel page and you should see RAID 10 being recovered. You can also check the recovery progress in real time by typing the following command in a terminal window:
Note.
If the new disk fails to join RAID 10 or if you notice that the synchronization keeps stopping after joining for a while, it is highly likely that there are other damaged disks. In this case, it is recommended that you back up your data to another device at the first opportunity.
220, 420, 221, 421, 422 series models
Applicable Versions
TOS4
Problem phenomenon
The RAID 10 disk is damaged, pull out the bad disk and put in the new disk, but the “Edit” button is still grayed out. Cannot add the new disk to RAID 10 to repair it.
Solution
1. Create the new disk as a Single pool, and then immediately delete the newly created Single pool. This is to allow the disk to be automatically partitioned and formatted as a TOS4-only disk.
2. Login to the terminal via SSH/Telnet/HDMI monitor.
(SSH connection method: viewtopic.php?t=2350)
3. Enter the following command to confirm the constituent members of your RAID 10:
Code: Select all
ls /dev/sd*
cat /proc/mdstat
lsblk
mdadm -D /dev/md0Code: Select all
mdadm -a /dev/md0 /dev/sdb4 Code: Select all
watch -n 1 'cat /proc/mdstat | grep “recovery”' If the new disk fails to join RAID 10 or if you notice that the synchronization keeps stopping after joining for a while, it is highly likely that there are other damaged disks. In this case, it is recommended that you back up your data to another device at the first opportunity.