1/2
error/alert keeps triggered the ip threshold on HCI for vdc server

Newbie869533 Lv1  Posted 2026-Aug-10 11:10

hi..can anyone help me to bring the solution for my problem??? an error captured at hci(vdc server) shown when the node accesses the datastore(VS)'s disk(sdb), the read/write latency exceeds the threshold(50ms) for a period of time. I've already replace new hdd into my vdc server(disk 1 & disk 2), but the error keeps appear.

Muhammad Abid has solved this question and earned 10 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Yes. Replacing Disk 1 and Disk 2 does not necessarily resolve this error, because the alert specifically says that the HCI/VDC node is experiencing high read/write latency while accessing datastore disk /dev/sdb. The problem can be caused by the datastore/storage layer, controller, disk workload, or another node—not only by a failed HDD.

Sangfor's documentation confirms that datastore latency reflects I/O requests waiting in queue; increasing latency indicates poorer storage performance.

What I recommend checking
Confirm which physical disk is /dev/sdb
Go to HCI → Storage → Disks.
Identify /dev/sdb.
Don't assume it is the HDD you replaced. Verify the serial number/model.
Check datastore latency
Go to Storage → Virtual Storage/Datastore → select the datastore.

Check:
IOPS
Read latency
Write latency
Read/write throughput
Node hit rate
Compare the affected node with other nodes. Sangfor provides historical views for these metrics.

Check whether another disk/node is causing the bottleneck

This is very important in HCI. A single slow disk or overloaded node can affect datastore performance even if you replaced the disks on one VDC server.

Check HDD/SSD health
Look for:

Bad sectors
SMART warnings
High disk utilization
Disk read/write errors
Rebuild/synchronization activity

Sangfor's storage view specifically provides information about disks with bad sectors.

Check RAID/HBA/controller configuration

If the disks are behind a RAID controller rather than proper HBA/JBOD/pass-through, this can affect how HCI accesses and monitors the disks. Sangfor recommends homogeneous storage configurations and notes that mixed disk performance can create a bottleneck.

Check whether the datastore is under heavy I/O

Look at VMs using this datastore. A database, backup, antivirus scan, CDP, or VM generating high random I/O can push latency above the threshold. Sangfor also provides disk I/O limits for controlling excessive VM disk I/O.

Most important point

Since you already replaced Disk 1 and Disk 2 but /dev/sdb latency errors continue, I would not replace more HDDs yet.

First determine:

/dev/sdb → physical disk serial/model → which node → which datastore → current IOPS/latency → disk health/controller status.

If you send me a screenshot of the HCI error and the Storage → Virtual Storage → datastore performance page, I can tell you exactly what to check next and whether the problem is likely the HDD, HBA/RAID controller, datastore, or a high-IO VM.
Is this answer helpful?
Muhammad Abid Lv3  Posted 2026-Aug-11 12:41
  
Yes. Replacing Disk 1 and Disk 2 does not necessarily resolve this error, because the alert specifically says that the HCI/VDC node is experiencing high read/write latency while accessing datastore disk /dev/sdb. The problem can be caused by the datastore/storage layer, controller, disk workload, or another node—not only by a failed HDD.

Sangfor's documentation confirms that datastore latency reflects I/O requests waiting in queue; increasing latency indicates poorer storage performance.

What I recommend checking
Confirm which physical disk is /dev/sdb
Go to HCI → Storage → Disks.
Identify /dev/sdb.
Don't assume it is the HDD you replaced. Verify the serial number/model.
Check datastore latency
Go to Storage → Virtual Storage/Datastore → select the datastore.

Check:
IOPS
Read latency
Write latency
Read/write throughput
Node hit rate
Compare the affected node with other nodes. Sangfor provides historical views for these metrics.

Check whether another disk/node is causing the bottleneck

This is very important in HCI. A single slow disk or overloaded node can affect datastore performance even if you replaced the disks on one VDC server.

Check HDD/SSD health
Look for:

Bad sectors
SMART warnings
High disk utilization
Disk read/write errors
Rebuild/synchronization activity

Sangfor's storage view specifically provides information about disks with bad sectors.

Check RAID/HBA/controller configuration

If the disks are behind a RAID controller rather than proper HBA/JBOD/pass-through, this can affect how HCI accesses and monitors the disks. Sangfor recommends homogeneous storage configurations and notes that mixed disk performance can create a bottleneck.

Check whether the datastore is under heavy I/O

Look at VMs using this datastore. A database, backup, antivirus scan, CDP, or VM generating high random I/O can push latency above the threshold. Sangfor also provides disk I/O limits for controlling excessive VM disk I/O.

Most important point

Since you already replaced Disk 1 and Disk 2 but /dev/sdb latency errors continue, I would not replace more HDDs yet.

First determine:

/dev/sdb → physical disk serial/model → which node → which datastore → current IOPS/latency → disk health/controller status.

If you send me a screenshot of the HCI error and the Storage → Virtual Storage → datastore performance page, I can tell you exactly what to check next and whether the problem is likely the HDD, HBA/RAID controller, datastore, or a high-IO VM.
Prosi Lv4  Posted 2026-Aug-11 18:51
  
Yes—if Disk 1 and Disk 2 have already been replaced but the same warning persists for sdb, I wouldn't immediately assume the new HDDs are faulty.
The key point of the warning is that read/write latency exceeded 50 ms for a certain period.
Do not keep replacing disks simply because the warning mentions "disk latency." If two newly replaced disks exhibit the exact same symptoms, there is a strong case for examining the controller/storage path and the workload, rather than the HDDs themselves.
Korchai Lv2  Posted 2026-Aug-14 00:48
  
Yes, I wouldn't assume the new HDDs are defective right away if Disk 1 and Disk 2 have previously been changed but the sdb warning still exists.
The warning's main point is that read/write latency was more than 50 ms for a specific amount of time.
Don't keep swapping out drives just because the alert says "disk latency." Examining the controller/storage path and the workload instead of the HDDs itself is strongly recommended if two recently replaced disks show exactly the same symptoms.

I Can Help:

Change

Board Leaders

George ...

Weekly Sharers

George ...

Weekly Questioners