root/backup_to_external_m.2
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
a8bc889e470adab29b6aeb7ca1556fc41ec1b3ab
backup_to_external_m.2/old_scripts/DRIVE_SELECTION_REFERENCE.md
root 72f9838f55 cleanup: Archive old complex scripts and documentation 
- Move all old complex backup scripts to old_scripts/
- Archive previous documentation versions
- Clean up temporary files and debian packages
- Update README to focus on new simple system
- Keep only the enhanced simple backup system in main directory

Main directory now contains only:
- simple_backup_gui.py (GUI interface)
- enhanced_simple_backup.sh (CLI interface)
- list_drives.sh (helper)
- simple_backup.sh (basic CLI)
- SIMPLE_BACKUP_README.md (detailed docs)
- README.md (project overview)
2025-10-09 00:30:03 +02:00

1.7 KiB
Raw Blame History

Drive Selection Reference

Based on your system screenshots, here's the correct drive mapping:

Current System Layout (from screenshots):

Available Drives:

  • /dev/nvme0n1 - 476.9G KXG6AZNV512G TOSHIBA

    • ✅ INTERNAL DRIVE (source)
    • This is your current system with:
      • nvme0n1p1: 58GB Linux filesystem (root)
      • nvme0n1p2: 512MB EFI system
      • nvme0n1p3: 417GB Linux filesystem (home)

  • /dev/sda - 476.9G Tech JMicron

    • ✅ EXTERNAL M.2 SSD (target)
    • This should be selected as migration TARGET
    • Will be completely wiped and converted to LVM

  • /dev/sdb - 119.3G Extreme Pro SanDisk

    • 🔧 USB STICK (migration tools)
    • This USB stick with the migration tools
    • Should NOT be selected for migration

Correct Migration Configuration:

Source (Internal): /dev/nvme0n1 → Target (External): /dev/sda

What the Enhanced Script Now Does:

  1. Excludes USB stick - Won't offer /dev/sdb as an option
  2. Shows drive details - Displays size, model, USB detection
  3. Suggests configuration:
    • Internal: /dev/nvme0n1 (NVMe drives are typically internal)
    • External: /dev/sda (USB-connected drives are typically external)
  4. User confirmation - Asks you to confirm before proceeding
  5. Final safety check - Shows exactly what will be wiped
  6. Type 'YES' confirmation - Prevents accidental data loss

Migration Process:

  1. Boot from USB (/dev/sdb)
  2. Run migration script
  3. Script will suggest:
    • Internal: /dev/nvme0n1 (476.9G TOSHIBA)
    • External: /dev/sda (476.9G JMicron)
  4. Confirm selection
  5. Type 'YES' to proceed

This should prevent the wrong drive selection issue you encountered!

Reference in New Issue View Git Blame Copy Permalink