chore: consolidate local WIP (repo cleanup 20260707)
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
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>
This commit is contained in:
146
docs/ceph/FORMAT_SSDS_FOR_PROXMOX.md
Normal file
146
docs/ceph/FORMAT_SSDS_FOR_PROXMOX.md
Normal file
@@ -0,0 +1,146 @@
|
||||
# Format 250GB SSDs and Check Proxmox Recognition
|
||||
|
||||
**Date**: 2025-12-13
|
||||
**Purpose**: Format the 6x 250GB SSDs and verify Proxmox can see them
|
||||
|
||||
---
|
||||
|
||||
## Quick Start
|
||||
|
||||
On R630-01:
|
||||
|
||||
```bash
|
||||
# Copy script
|
||||
scp scripts/format-ssds-and-check-proxmox.sh root@192.168.11.11:/tmp/
|
||||
|
||||
# SSH and run
|
||||
ssh root@192.168.11.11
|
||||
bash /tmp/format-ssds-and-check-proxmox.sh
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## What the Script Does
|
||||
|
||||
1. **Checks current drive status** - Shows what's on each drive
|
||||
2. **Formats drives** - Creates GPT partition table on each
|
||||
3. **Creates partitions** - Single partition on each drive (unformatted)
|
||||
4. **Checks block devices** - Shows what the system sees
|
||||
5. **Checks Proxmox storage** - Shows Proxmox's view
|
||||
6. **Provides summary** - What to check next
|
||||
|
||||
---
|
||||
|
||||
## Manual Method
|
||||
|
||||
If you prefer to do it manually:
|
||||
|
||||
```bash
|
||||
# For each drive (sdc, sdd, sde, sdf, sdg, sdh)
|
||||
for drive in sdc sdd sde sdf sdg sdh; do
|
||||
# Unmount any partitions
|
||||
umount /dev/${drive}* 2>/dev/null || true
|
||||
|
||||
# Create GPT partition table
|
||||
parted -s /dev/$drive mklabel gpt
|
||||
|
||||
# Create single partition
|
||||
parted -s /dev/$drive mkpart primary 0% 100%
|
||||
|
||||
# Re-read partition table
|
||||
partprobe /dev/$drive
|
||||
done
|
||||
|
||||
# Check results
|
||||
lsblk
|
||||
pvesm status
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Check in Proxmox Web UI
|
||||
|
||||
1. **Login**: https://192.168.11.11:8006
|
||||
2. **Navigate**: Datacenter > Storage
|
||||
3. **Click**: "Add" button
|
||||
4. **Check**: Available disks should be listed
|
||||
|
||||
---
|
||||
|
||||
## Expected Results
|
||||
|
||||
### After Formatting
|
||||
|
||||
Each drive should show:
|
||||
- GPT partition table
|
||||
- One partition (unformatted)
|
||||
- Visible to `lsblk`
|
||||
- Potentially visible to Proxmox storage manager
|
||||
|
||||
### What Proxmox Should See
|
||||
|
||||
- 6x drives around 250GB
|
||||
- Available for storage creation
|
||||
- Can be used for:
|
||||
- Directory storage
|
||||
- LVM storage
|
||||
- Ceph OSD (after further setup)
|
||||
|
||||
---
|
||||
|
||||
## Next Steps After Formatting
|
||||
|
||||
Once Proxmox recognizes the drives:
|
||||
|
||||
1. **Option 1: Use for Ceph OSDs**
|
||||
- Create OSDs on formatted drives
|
||||
- Add to Ceph cluster
|
||||
|
||||
2. **Option 2: Use as Proxmox Storage**
|
||||
- Add as Directory storage
|
||||
- Add as LVM storage
|
||||
- Use for VM disks
|
||||
|
||||
3. **Option 3: Leave for Later**
|
||||
- Drives are ready
|
||||
- Can be configured when needed
|
||||
|
||||
---
|
||||
|
||||
## Verification Commands
|
||||
|
||||
```bash
|
||||
# Check block devices
|
||||
lsblk -o NAME,SIZE,TYPE,MOUNTPOINT,FSTYPE
|
||||
|
||||
# Check Proxmox storage
|
||||
pvesm status
|
||||
|
||||
# Check partitions
|
||||
fdisk -l | grep -E "^Disk /dev/sd[c-h]"
|
||||
|
||||
# Check if Proxmox can see them
|
||||
pvesm scan local
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## Summary
|
||||
|
||||
### Current State
|
||||
- 6x 250GB SSDs wiped
|
||||
- Need to format and check Proxmox recognition
|
||||
|
||||
### Action
|
||||
- Format drives with GPT partition tables
|
||||
- Check if Proxmox recognizes them
|
||||
|
||||
### Expected Result
|
||||
- Drives formatted and visible
|
||||
- Proxmox can see them
|
||||
- Ready for storage configuration
|
||||
|
||||
---
|
||||
|
||||
**Last Updated**: 2025-12-13
|
||||
|
||||
Reference in New Issue
Block a user