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>
3.6 KiB
3.6 KiB
R630-01 Disk Layout Reference
Overview
This document describes the disk layout for the R630-01 Proxmox VE host based on lsblk output.
Disk Inventory
System Disk: /dev/sda (279.4G)
- Type: System/OS disk with LVM
- Partitions:
sda1: 1007K (BIOS boot partition)sda2: 1G (EFI boot partition, mounted at/boot/efi)sda3: 278G (LVM physical volume)
- LVM Volumes:
pve-swap: 8G (swap)pve-root: 79.5G (root filesystem, mounted at/)pve-data: 171G (Proxmox data storage)
- Status: ✅ Active system disk
- Usage: Proxmox VE host OS and base storage
Secondary Disk: /dev/sdb (279.4G)
- Type: Standalone LVM physical volume (not in volume group)
- Partitions: None (has LVM2_member signature)
- Status: ✅ Available for use (needs LVM signature removal for Ceph)
- Model: HUC106030CSS600
- Recommendations:
- Ceph OSD (wipe LVM signature first)
- Proxmox storage pool
- Backup storage
Ceph Candidate Disks: /dev/sdc through /dev/sdh (6x 232.9G)
- Type: SSDs - Ready for Ceph OSDs
- Model: CT250MX500SSD1 (Crucial MX500)
- Size: ~232.9G each
- Total Capacity: ~1.4TB
- Status: ✅ All 6 disks available (no partitions, unmounted)
- Typical Usage: Ceph OSD nodes for distributed storage
Disk Layout Summary
sda (279.4G) - System Disk
├─ sda1 (1007K) - BIOS boot
├─ sda2 (1G) - EFI boot [/boot/efi]
└─ sda3 (278G) - LVM PV
├─ pve-swap (8G)
├─ pve-root (79.5G) [/]
└─ pve-data (171G)
sdb (279.4G) - Available
sdc-sdh (6x 232.9G) - Storage/Ceph candidates
Storage Recommendations
For Ceph OSD Setup (Recommended)
Quick Setup (Automated):
# Run on r630-01 directly
./scripts/setup-ceph-osds-r630.sh
# Or run remotely
./scripts/run-ceph-osd-setup-remote.sh L@kers2010
# To include sdb disk as well
./scripts/run-ceph-osd-setup-remote.sh L@kers2010 --include-sdb
Manual Setup:
- Verify disk status: Run
analyze-r630-disk-layout.sh - Wipe disks (if needed):
wipefs -a /dev/sdX - Create OSDs:
ceph-volume lvm create --data /dev/sdX - Verify:
ceph osd tree
What the automated script does:
- Checks prerequisites (Ceph installed, cluster accessible)
- Verifies all 6 SSDs (sdc-sdh) are available
- Optionally prepares sdb (removes LVM signature)
- Creates OSDs on all available disks
- Enables and starts OSD services
- Verifies Ceph health and OSD status
For Proxmox Storage
- Format disks: Use
format-ssds-and-check-proxmox.sh - Add to Proxmox: Datacenter > Storage > Add
- Choose type: Directory, LVM, or ZFS
For Mixed Use
- Use
sdbfor Proxmox storage - Use
sdc-sdhfor Ceph OSDs - Keep
sdaas system disk
Related Scripts
Analysis & Verification
scripts/analyze-r630-disk-layout.sh- Comprehensive disk analysisscripts/check-proxmox-storage.sh- Quick Proxmox storage checkscripts/verify-r630-disks.sh- Disk verification for Ceph
Ceph OSD Setup
scripts/setup-ceph-osds-r630.sh- Main setup script (run on r630-01)scripts/run-ceph-osd-setup-remote.sh- Remote execution helperscripts/create-ceph-osds-all-drives.sh- Alternative OSD creation scriptscripts/create-all-osds-efficient.sh- Efficient OSD creation
Proxmox Storage
scripts/format-ssds-and-check-proxmox.sh- Format disks for Proxmox
Notes
- All disk sizes are approximate (decimal vs binary)
- Check actual status with
lsblkor analysis script - Always verify before making changes to disk layout
- Backup important data before repartitioning