Files
Sankofa/docs/ceph/PERC_CONTROLLER_CHECK.md
defiQUG 33d50fb91e
Some checks failed
API CI / API Lint (push) Successful in 47s
API CI / API Type Check (push) Failing after 47s
API CI / API Test (push) Successful in 1m0s
API CI / API Build (push) Failing after 50s
API CI / Build Docker Image (push) Has been skipped
Build Crossplane Provider / build (push) Failing after 5m51s
CD Pipeline / Deploy to Staging (push) Failing after 29s
CI Pipeline / Lint and Type Check (push) Failing after 36s
CI Pipeline / Build (push) Has been skipped
CI Pipeline / Test Backend (push) Failing after 1m33s
CI Pipeline / Test Frontend (push) Failing after 30s
CI Pipeline / Security Scan (push) Failing after 1m16s
Crossplane Provider CI / Go Test (push) Failing after 3m23s
Crossplane Provider CI / Go Lint (push) Failing after 7m27s
Crossplane Provider CI / Go Build (push) Failing after 3m27s
Deploy to Staging / Deploy to Staging (push) Failing after 30s
Portal CI / Portal Lint (push) Failing after 21s
Portal CI / Portal Type Check (push) Failing after 21s
Portal CI / Portal Test (push) Failing after 21s
Portal CI / Portal Build (push) Failing after 22s
Test Suite / frontend-tests (push) Failing after 30s
Test Suite / api-tests (push) Failing after 49s
Test Suite / blockchain-tests (push) Failing after 30s
Type Check / type-check (map[directory:. name:root]) (push) Failing after 23s
Type Check / type-check (map[directory:api name:api]) (push) Failing after 21s
Type Check / type-check (map[directory:portal name:portal]) (push) Failing after 19s
Validate Configuration Files / validate (push) Failing after 1m52s
CD Pipeline / Deploy to Production (push) Has been skipped
chore: consolidate local WIP (repo cleanup 20260707)
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-07 09:41:34 -07:00

3.9 KiB

Checking PERC Controller for 250GB Drives

Date: 2025-12-13
Issue: 6x 250GB drives not visible to OS, need to check PERC controller


Current Status

  • OS Detected: Only 2x 300GB drives (sda, sdb)
  • Expected: 6x 250GB drives should be visible
  • Likely Cause: Drives not configured in PERC controller or in RAID array

Check PERC Controller

Option 1: Install Dell OpenManage Tools

# Install Dell OpenManage Server Administrator
apt-get update
apt-get install -y srvadmin-all

# Start services
systemctl start dsm_sa_datamgrd
systemctl start dsm_sa_snmpd
systemctl start dsm_sa_eventmgrd

# Check physical disks
omreport storage pdisk controller=0

# Check virtual disks (RAID arrays)
omreport storage vdisk controller=0

Option 2: Use PERC CLI (if available)

# Check if perccli is installed
which perccli

# If not installed, download from Dell
# Then check physical disks
perccli /c0 show

# Check virtual disks
perccli /c0/vall show

Option 3: Check via /proc or /sys

# Check for PERC controller info
cat /proc/scsi/scsi

# Check block devices
ls -la /dev/sd*

# Check for additional controllers
lspci | grep -i raid
lspci | grep -i perc
lspci | grep -i lsi

Option 4: Check dmesg for disk detection

# Check kernel messages for disk detection
dmesg | grep -i "sd[a-z]"
dmesg | grep -i "disk"
dmesg | grep -i "perc"
dmesg | grep -i "raid"

# Check recent disk events
journalctl -k | grep -i disk | tail -50

What to Look For

If Drives Are in PERC Controller

You should see:

  • 8 physical disks total
  • 2x 300GB drives (already configured)
  • 6x 250GB drives (may be unconfigured or in RAID)

If Drives Are Unconfigured

They may show as:

  • "Unconfigured Good" or "Ready"
  • Not assigned to any virtual disk
  • Available for configuration

If Drives Are in RAID

They may be:

  • Part of a RAID array (virtual disk)
  • Not exposed as individual disks to OS
  • Need to be removed from RAID to use individually

Next Steps Based on Findings

Scenario 1: Drives Detected in PERC but Unconfigured

Action: Configure drives as individual disks (non-RAID) or create separate virtual disks

# Using perccli (example - adjust for your setup)
# Create individual virtual disks (one per physical disk)
# This exposes each drive to the OS

# Or configure PERC in HBA mode (if supported)
# This passes drives directly to OS without RAID

Scenario 2: Drives Not Detected in PERC

Possible causes:

  • Drives not physically installed
  • Drive backplane issue
  • Controller issue

Action:

  1. Check physical installation
  2. Check drive bay LEDs
  3. Check PERC controller status
  4. May need to reseat drives

Scenario 3: Drives in RAID Array

Action:

  1. Check RAID configuration
  2. Decide if RAID array can be broken up
  3. May need to backup data and reconfigure
  4. Create individual virtual disks for Ceph OSDs

For Ceph OSDs, you want:

  • Individual disks (not in RAID)
  • Direct access to each physical disk
  • PERC in HBA mode (if supported) or individual virtual disks

Why: Ceph handles redundancy, so RAID is not needed and can reduce performance.


Quick Check Commands

Run these on R630-01:

# 1. Check for PERC controller
lspci | grep -iE "raid|perc|lsi|megaraid"

# 2. Check kernel messages
dmesg | grep -iE "sd[a-z]|disk|perc" | tail -20

# 3. Check /proc for SCSI devices
cat /proc/scsi/scsi

# 4. Check for additional block devices
lsblk
fdisk -l

# 5. Check if OpenManage is available
which omreport
which perccli

Summary

The 6x 250GB drives are likely:

  1. In PERC controller but not configured/exposed
  2. In a RAID array that needs to be reconfigured
  3. Not physically installed (less likely if user confirmed they exist)

Next Step: Check PERC controller status to see where the drives are.


Last Updated: 2025-12-13