Why does my system not detect the self-encrypting drive (SED) during Cigent PBA installation?

In most cases, the SED is not detected because of incorrect BIOS/UEFI configuration—particularly AHCI mode or Block SID settings.

Most common causes

1. Storage controller is set to RAID instead of AHCI

Cigent PBA requires the storage controller to be in AHCI mode.

What to check:

• BIOS → Storage settings
• Ensure SATA/NVMe Operation = AHCI
• Disable RAID mode if enabled

If RAID mode is active, the PBA software may not recognize the SED.

2. Block SID Authentication is enabled

Many platforms ship with this protection enabled by default.

What to check:

• Set Block SID Authentication = OFF
• Save BIOS settings
• Proceed immediately with installation (some systems revert the setting)

This setting must be disabled so PBA can provision the drive correctly.

3. BIOS changes were not saved or reverted

Some platforms silently revert storage security settings.

Verify:

• BIOS settings were saved
• System was fully rebooted
• Settings remained after reboot

This is especially common on certain enterprise laptops.

4. Unsupported or improperly connected drive

Less common, but possible.

Check:

• Drive is a supported Cigent Secure SSD or compatible SED
• Drive is properly seated
• Correct NVMe/SATA slot is used
• No unsupported controller in the path

5. Using the wrong installation mode or environment

In some advanced configurations:

• RAID controllers may require special handling
• Controller-based locking environments may need advanced flags

If you are using RAID or advanced storage controllers, consult Cigent Support.

Quick troubleshooting checklist

Before retrying installation:

• ✔ AHCI mode enabled
• ✔ Block SID Authentication OFF
• ✔ BIOS settings saved and persistent
• ✔ Drive properly installed
• ✔ Supported SED model confirmed
• ✔ System fully power-cycled

When to contact support

Contact Cigent Support if:

• The drive still does not appear after BIOS corrections
• You are using RAID or controller-based locking
• The system previously worked and stopped detecting the drive