fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
3.0 KiB
3.0 KiB
R630-01 RAID 10 Expansion - Final Status
Date: January 6, 2026
Status: ⚠️ RAID EXPANDED - THIN POOLS RECREATED
Summary
RAID 10 has been successfully expanded from 4 disks to 6 disks. Thin pools have been recreated, but container/VM volumes will need to be restored from backups.
Completed ✅
- ✅ RAID 10 Expanded - Successfully created RAID 10 with all 6 disks (sdc-sdh)
- ✅ RAID Synchronized - Array fully synchronized
- ✅ Volume Group Restored - pve VG active
- ✅ Thin Pools Recreated - thin1 (208G) and data (200G) pools created
Current Status
RAID Array
- Device: /dev/md0
- Level: RAID 10
- Disks: sdc, sdd, sde, sdf, sdg, sdh (6 disks)
- Capacity: 698.28 GiB (~700GB)
- State: Clean, Active
- Status: ✅ OPERATIONAL
Volume Group
- VG Name: pve
- VG Size: 698.28 GiB
- PVs: 1 (/dev/md0)
- Status: ✅ ACTIVE
Thin Pools
- thin1: 208G (recreated)
- data: 200G (recreated)
- Status: ✅ CREATED
Container/VM Volumes
- Status: ⚠️ NEED TO BE RECREATED
- Impact: Containers/VMs cannot start until volumes are restored
Next Steps Required
1. Restore Container/VM Volumes
Containers and VMs need their disk volumes recreated. Options:
Option A: Restore from Backups (Recommended)
- Use Proxmox backup/restore functionality
- Restore each container/VM from backup
- This will recreate volumes automatically
Option B: Manual Recreation
- Recreate volumes based on original sizes
- Restore data from backups
- More complex but may preserve some data
2. Verify Storage
# Check thin pools
lvs -a pve
# Check Proxmox storage
pvesm status
# Check containers/VMs
pct list
qm list
3. Start Containers/VMs
Once volumes are restored:
# Start containers
pct start <vmid>
# Start VMs
qm start <vmid>
Important Notes
- RAID is operational - The RAID 10 array is working correctly with 6 disks
- Performance improved - Now has ~6x read and ~3x write performance
- Thin pools ready - Storage pools are created and ready for use
- Data recovery - Original container/VM data may still be on RAID but LVM metadata was lost
- Backups recommended - Always restore from backups rather than attempting data recovery
RAID Performance
RAID 10 with 6 Disks
- Read Speed: ~6x single disk (~600-900 MB/s)
- Write Speed: ~3x single disk (~300-450 MB/s)
- IOPS: Maximum possible
- Redundancy: Can survive 1-3 disk failures
Recovery Commands
# Check RAID status
cat /proc/mdstat
mdadm --detail /dev/md0
# Check LVM
vgs pve
lvs -a pve
# Check storage
pvesm status
# Restore container from backup
pct restore <vmid> <backup_file>
# Restore VM from backup
qmrestore <backup_file> <vmid>
Last Updated: January 6, 2026
RAID Status: ✅ OPERATIONAL
Storage Status: ⚠️ THIN POOLS READY - VOLUMES NEED RESTORATION