cb47cce074
- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
1.9 KiB
Migration Status Update
Date: December 26, 2024
Status: In Progress - Storage Conversion Issue
Current Status
✅ Completed
-
Storage Pools Repaired
- pve: thin1-thin3 created and active
- pve2: thin1-thin3 repaired and active
-
Container Renaming
- All 8 containers renamed successfully on ml110
-
Migration Script
- Script updated to use API-based migration
- Containers are migrating but storage conversion needs manual adjustment
⚠️ Issue Identified
Problem: Proxmox migration API (pvesh) doesn't support --storage parameter for LXC container migrations. The containers are migrating but may end up on default storage instead of thin1.
Error: Unknown option: storage
🔧 Solutions
Option 1: Change Storage After Migration (Recommended) After containers migrate, move their storage to thin1:
# For each migrated container
ssh root@192.168.11.10
# Stop container
pct stop <VMID>
# Get current rootfs
pct config <VMID> | grep rootfs
# Move storage to thin1
pct set <VMID> --rootfs thin1:8,size=100G
# Start container
pct start <VMID>
Option 2: Use Proxmox Web UI
- Access Proxmox web UI
- Navigate to container
- Go to "Hardware" → "Hard Disk"
- Use "Disk Action" → "Move Storage"
- Select thin1 as target storage
Option 3: Backup/Restore with Storage Use vzdump/vzrestore with storage specification.
Migration Progress
Containers are currently migrating via API (without storage parameter). After migration completes, storage can be moved to thin1 using one of the methods above.
Next Steps
- Wait for migrations to complete
- Verify container locations (pve/pve2)
- Move container storage to thin1
- Verify hostnames
- Run ChainID 138 deployment script
Note: The migration API limitation means we need a two-step process: migrate first, then move storage.