Problem creating virtualstor - SSD and HDD errors

Szymon Domanski Lv1Posted Apr-16-2026 22:19

Last edited by Szymon Domanski Apr-16-2026 22:24.

Last edited by Szymon Domanski Apr-16-2026 22:24.

Hello,
I've got problem with creating virtual datastor on Sangfor HCI.

Firstly on hosts there are AVAGO RAID cards, that dont support JBOD. I've put every disk into separate RAID 0, so each virtual disk for every physical disk

Unfortunately, when creating a virtualdatastor, and choosing disks, every one of them is showing error - different error for SSD:

And different for HDD:

For SSD I've opened aDeploy and used "Allow SSD" function, but after I get confirmation that SSD whitelist is updated, nothing really happens.

How can I solve that issue?

Muhammad Abid has solved this question and earned 20 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

In Sangfor HCI, disks must be presented in JBOD / HBA (passthrough mode). Your current setup (each disk in RAID 0) is still treated as RAID-managed storage, so HCI blocks it.

Why you’re seeing these errors:
SSD error (not in compatibility list)
RAID controller hides the real SSD details (model/firmware), so even after “Allow SSD” via aDeploy, it doesn’t fully apply.
HDD error (disk health failed)
HCI cannot read SMART/health data through RAID → required for datastore.
aDeploy not fixing
Because the RAID layer is still in between, not true passthrough.

Correct Solution:
Change RAID card to HBA / IT mode (JBOD)
If your AVAGO card doesn’t support it → use a supported HBA controller
Re-add disks and create datastore again

Summary:

RAID 0 ≠ JBOD

Sangfor requires direct disk access, otherwise datastore creation will fail.
Is this answer helpful?
Muhammad Abid Lv2Posted Apr-17-2026 15:18
  
In Sangfor HCI, disks must be presented in JBOD / HBA (passthrough mode). Your current setup (each disk in RAID 0) is still treated as RAID-managed storage, so HCI blocks it.

Why you’re seeing these errors:
SSD error (not in compatibility list)
RAID controller hides the real SSD details (model/firmware), so even after “Allow SSD” via aDeploy, it doesn’t fully apply.
HDD error (disk health failed)
HCI cannot read SMART/health data through RAID → required for datastore.
aDeploy not fixing
Because the RAID layer is still in between, not true passthrough.

Correct Solution:
Change RAID card to HBA / IT mode (JBOD)
If your AVAGO card doesn’t support it → use a supported HBA controller
Re-add disks and create datastore again

Summary:

RAID 0 ≠ JBOD

Sangfor requires direct disk access, otherwise datastore creation will fail.

I Can Help:

Change

Board Leaders

NyxZale...

Weekly Sharers

Newbie5...

Weekly Questioners