80 lines
1.9 KiB
Markdown
80 lines
1.9 KiB
Markdown
|
# Migration Status Update
|
||
|
|
|
||
|
|
**Date:** December 26, 2024
|
||
|
|
**Status:** In Progress - Storage Conversion Issue
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Current Status
|
||
|
|
|
||
|
|
### ✅ Completed
|
||
|
|
1. **Storage Pools Repaired**
|
||
|
|
- pve: thin1-thin3 created and active
|
||
|
|
- pve2: thin1-thin3 repaired and active
|
||
|
|
|
||
|
|
2. **Container Renaming**
|
||
|
|
- All 8 containers renamed successfully on ml110
|
||
|
|
|
||
|
|
3. **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:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
# 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**
|
||
|
|
1. Access Proxmox web UI
|
||
|
|
2. Navigate to container
|
||
|
|
3. Go to "Hardware" → "Hard Disk"
|
||
|
|
4. Use "Disk Action" → "Move Storage"
|
||
|
|
5. 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
|
||
|
|
|
||
|
|
1. Wait for migrations to complete
|
||
|
|
2. Verify container locations (pve/pve2)
|
||
|
|
3. Move container storage to thin1
|
||
|
|
4. Verify hostnames
|
||
|
|
5. Run ChainID 138 deployment script
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
**Note:** The migration API limitation means we need a two-step process: migrate first, then move storage.
|
||
|
|
|