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
Co-authored-by: Cursor <cursoragent@cursor.com>
102 lines
2.3 KiB
Markdown
102 lines
2.3 KiB
Markdown
# 250GB SSDs Status - Visible and Ready
|
|
|
|
**Date**: 2025-12-13
|
|
**Status**: ✅ **ALL 6 DRIVES VISIBLE AND READY**
|
|
|
|
---
|
|
|
|
## Current Status
|
|
|
|
### ✅ All 6x 250GB SSDs Detected
|
|
|
|
| Drive | Size | Model | Partition | Status |
|
|
|-------|------|-------|-----------|--------|
|
|
| **sdc** | 232.9G | CT250MX500SSD1 | sdc1 (232.9G) | ✅ Ready |
|
|
| **sdd** | 232.9G | CT250MX500SSD1 | sdd1 (232.9G) | ✅ Ready |
|
|
| **sde** | 232.9G | CT250MX500SSD1 | sde1 (232.9G) | ✅ Ready |
|
|
| **sdf** | 232.9G | CT250MX500SSD1 | sdf1 (232.9G) | ✅ Ready |
|
|
| **sdg** | 232.9G | CT250MX500SSD1 | sdg1 (232.9G) | ✅ Ready |
|
|
| **sdh** | 232.9G | CT250MX500SSD1 | sdh1 (232.9G) | ✅ Ready |
|
|
|
|
### Key Observations
|
|
|
|
- ✅ **All drives visible** to the system
|
|
- ✅ **Partitions created** (sdc1, sdd1, etc.)
|
|
- ✅ **No filesystem** (FSTYPE empty) - clean and ready
|
|
- ✅ **Not mounted** - available for use
|
|
- ✅ **Proxmox can see them** - ready for storage configuration
|
|
|
|
---
|
|
|
|
## Proxmox Storage Status
|
|
|
|
Current storage pools:
|
|
- **ceph-fs**: inactive (mount error - needs fixing)
|
|
- **ceph-rbd**: inactive
|
|
- **local**: active (81.5 GB)
|
|
- **local-lvm**: active (179.6 GB)
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
### Option 1: Create Ceph OSDs (Recommended)
|
|
|
|
Use these drives for Ceph OSDs to fix the TOO_FEW_OSDS error:
|
|
|
|
```bash
|
|
# Remove partitions first (Ceph needs raw devices)
|
|
for drive in sdc sdd sde sdf sdg sdh; do
|
|
wipefs -a /dev/$drive
|
|
ceph-volume lvm create --data /dev/$drive
|
|
done
|
|
```
|
|
|
|
### Option 2: Add as Proxmox Storage
|
|
|
|
Add them as Directory or LVM storage in Proxmox:
|
|
|
|
1. **Via Web UI**: Datacenter > Storage > Add
|
|
2. **Via CLI**: Use `pvesm` commands
|
|
|
|
### Option 3: Use for Ceph OSD (One at a Time)
|
|
|
|
Start with one drive to fix the immediate issue:
|
|
|
|
```bash
|
|
# Use sdc for third OSD
|
|
wipefs -a /dev/sdc
|
|
ceph-volume lvm create --data /dev/sdc
|
|
|
|
# Verify
|
|
ceph osd tree
|
|
ceph health
|
|
```
|
|
|
|
---
|
|
|
|
## Summary
|
|
|
|
### Current State
|
|
- ✅ 6x 250GB SSDs formatted and visible
|
|
- ✅ Partitions created (ready for use)
|
|
- ✅ No filesystem (clean slate)
|
|
- ✅ Proxmox can see them
|
|
|
|
### Ready For
|
|
- ✅ Ceph OSD creation
|
|
- ✅ Proxmox storage configuration
|
|
- ✅ Any storage use case
|
|
|
|
### Next Action
|
|
Choose how to use the drives:
|
|
1. **Ceph OSDs** (fixes TOO_FEW_OSDS error)
|
|
2. **Proxmox storage** (for VMs)
|
|
3. **Both** (some for Ceph, some for storage)
|
|
|
|
---
|
|
|
|
**Last Updated**: 2025-12-13
|
|
**Status**: ✅ **DRIVES READY - CHOOSE USE CASE**
|
|
|