Applicable Products
- QuTS hero h5.3.0 or later
- High Availability Manager
Background
QNAP NAS devices support disk roaming, which allows users to move disks to different slots while the system is powered off. After restarting, the system can still detect and mount the storage pool that the moved disks belong to, even though their locations have changed.
However, if your NAS devices are in a high-availability (HA) cluster, performing disk roaming only on one node device may cause High Availability Manager to detect disk slot inconsistencies between the two nodes. These inconsistencies may affect cluster health and stability.
Scenarios
The effect of disk roaming on the HA cluster depends on where you moved your disks on one node relative to the other node.
There are two major disk roaming scenarios. Let’s assume you powered off the passive node and moved two disks that belong to the same storage pool to different disk slots:
| Scenario | Active Node | Passive Node | Description |
|---|
| Swapped slots | Slot 1: Disk A (400 GB)
Slot 2: Disk B (200 GB) | Slot 1: Disk B (200 GB)
Slot 2: Disk A (400 GB) | The two disks on the passive node swapped slots compared to the corresponding disks on the active node, but the same two slots are still occupied. |
| Different slots | Slot 1: Disk A (400 GB)
Slot 2: Disk B (200 GB) | Slot 3: Disk A (400 GB)
Slot 4: Disk B (200 GB) | The two disks on the passive node were moved to different slots than the corresponding disks on the active node. |
The effects of each scenario on the HA status are as follows:
| Scenario | HA Status | Details |
|---|
| Swapped slots | Good | The storage pool and data synchronization still work as expected.
However, future actions involving the disk slots may be affected (see important note in next section). |
| Different slots | Warning | Disk slot mismatch is detected.
The storage pool and data synchronization still work as expected.
However, cluster health is affected, and future actions involving the disk slots may be affected (see important note in next section). |
Solution
In both scenarios above, the HA cluster will continue to operate and sync data between the two nodes normally.
However, we highly recommend that the corresponding disks are always installed in matching disk slots between the two nodes. This ensures the long-term health and stability of the HA cluster.
You can resolve the disk slot inconsistency by doing one of the following:
- Perform a switchover, shut down the passive node, and then move the corresponding disks on the original active node to the same slots as those on the original passive node.
- Move the disks on the passive node back to their original disk slots.
Important
If you leave the disk slot inconsistency in place, you may fail to perform future storage actions involving those disks and disk slots.
For example, if you remove the storage pool and try to create a new one using the same disks while a scenario of swapped slots or different slots is still present between the two nodes, High Availability Manager will recheck the hardware configuration of both nodes and detect the inconsistency, preventing the system from creating the new storage pool.
Further Reading
How do I replace a hard drive with a larger capacity in an HA cluster?
适用产品
- QuTS hero h5.3.0 or later
- High Availability Manager
背景
QNAP NAS 设备支持磁盘漫游，允许用户在系统关闭时将磁盘移动到不同的插槽。重新启动后，系统仍然可以检测并挂载移动磁盘所属的存储池，即使它们的位置已更改。
然而，如果您的 NAS 设备处于高可用性 (HA) 群集中，仅在一个节点设备上执行磁盘漫游可能会导致High Availability Manager检测到两个节点之间的磁盘插槽不一致。这些不一致可能会影响群集的健康和稳定性。
场景
磁盘漫游对 HA 群集的影响取决于您在一个节点上移动磁盘相对于另一个节点的位置。
有两种主要的磁盘漫游场景。假设您关闭了被动节点，并将属于同一存储池的两个磁盘移动到不同的磁盘插槽：
| 场景 | 主动节点 | 被动节点 | 描述 |
|---|
| 交换插槽 | 插槽 1：磁盘 A (400 GB)
插槽 2：磁盘 B (200 GB) | 插槽 1：磁盘 B (200 GB)
插槽 2：磁盘 A (400 GB) | 被动节点上的两个磁盘与主动节点上的相应磁盘交换了插槽，但仍然占据相同的两个插槽。 |
| 不同插槽 | 插槽 1：磁盘 A (400 GB)
插槽 2：磁盘 B (200 GB) | 插槽 3： 磁盘 A (400 GB)
插槽 4： 磁盘 B (200 GB) | 被动节点上的两个磁盘被移动到与主动节点上的相应磁盘不同的插槽。 |
每种场景对 HA 状态的影响如下：
| 场景 | HA 状态 | 详情 |
|---|
| 交换插槽 | 良好 | 存储 池和数据同步仍然按预期工作。
然而，涉及磁盘插槽的未来操作可能会受到影响（请参阅下一节的重要说明）。 |
| 不同插槽 | 警告 | 检测到磁盘插槽不匹配。
存储 池和数据同步仍然按预期工作。
然而，群集 健康受到影响，涉及磁盘插槽的未来操作可能会受到影响（请参阅下一节的重要说明）。 |
解决方案
在上述两种情况下，HA 群集 将继续正常操作并在两个节点之间同步数据。
然而，我们强烈建议始终在两个节点之间将相应的磁盘安装在匹配的磁盘插槽中。这确保了 HA 群集 的长期健康和稳定性。
您可以通过以下方法之一解决磁盘插槽不一致的问题：
- 执行切换，关闭被动节点，然后将原始主动节点上的相应磁盘移动到与原始被动节点相同的插槽中。
- 将被动节点上的磁盘移回其原始磁盘插槽。
重要
如果您保持磁盘插槽不一致，您可能无法执行涉及这些磁盘和磁盘插槽的未来 存储 操作。
例如，如果您移除 存储 池并尝试使用相同的磁盘创建一个新的池，而两个节点之间仍然存在交换插槽或不同插槽的情况，High Availability Manager 将重新检查两个节点的硬件配置并检测到不一致，阻止系统创建新的 存储 池。
进一步阅读
如何在 HA 群集 中用更大容量的硬盘替换？
