GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — data.img preventing Migration Assistant transfers · Issue #1511 · orbstack/orbstack

data.img preventing Migration Assistant transfers #1511

New issue
Copy link
New issue
Copy link
Closed
Closed
data.img preventing Migration Assistant transfers#1511
Copy link
Labels
t/improvementMinor improvementMinor improvement

Description

@DarthNerdus
DarthNerdus
opened on Oct 13, 2024
Issue body actions

Describe the bug

The data.img sparse bundle size (8.8TB reported on my Mac) prevented me from using Migration Assistant, which does not provide helpful errors. Understanding the context with #29, I am opening this ticket anyways. I appreciate the forward-thinking adoption of this image format, but clearly even Apple's backup and recovery tools are not yet ready to adopt this.

It was only after failing multiple times to migrate, even thinking of recursive disk space traps, that I identified data.img as the culprit. During use of Carbon Copy Cloner, which reported that it "Discovered" 9.2TB of files but then successfully saved ~400GB that I was able to use CCC's audit function to identify that it registered data.img as being 8.8TB in size.

Apple's migration tool provides notoriously little feedback, and I am opening (yet another) Radar about this. But OrbStack is claiming the juice is worth the squeeze to move forward with Apple's modern tools... when Apple's tools clearly aren't expecting this yet either.

To Reproduce

  1. Use OrbStack as you normally would.
  2. Attempt to migrate to a new Mac using Migration Assistant
  3. Observe that Migration Assistant will calculate a total space requirement that fits on the new Mac
  4. During file migration, the process will stop stating there is "not enough space" every time
  5. Delete data.img from the source drive
  6. Reattempt migration
  7. Migration succeeds.

Expected behavior

I would be able to migrate from my old Mac, to my new (which has larger storage, not less), without finding and deleting data.img.

Diagnostic report (REQUIRED)

OrbStack info:
Version: 1.7.5
Commit: 82ec89be256fec62e3236f71eea94263bfcffe17 (v1.7.5)

System info:
macOS: 15.0.1 (24A348)
CPU: arm64, 11 cores
CPU model: Apple M3 Pro
Model: Mac15,6
Memory: 36 GiB

Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-10-13T22-55-23.815864Z.zip

Screenshots and additional context (optional)

No response

Reacted by Tom Atkins, Matthew Davidson and Shivan

Activity

  1. DarthNerdus
    added
    t/bugSomething isn't workingSomething isn't working
    on Oct 13, 2024
  2. winterqt commented on Oct 15, 2024

    @winterqt
    winterqt
    on Oct 15, 2024
    More actions

    We exclude the data image from Time Machine since Apple lets us. It doesn't look like there's a way to do similar for Migration Assistant. Going to keep this open in case we come up with anything, but for now, the ball's in Apple's court.

  3. winterqt
    added
    t/improvementMinor improvementMinor improvement
    and removed
    t/bugSomething isn't workingSomething isn't working
    on Oct 15, 2024
  4. DarthNerdus commented on Oct 15, 2024

    @DarthNerdus
    DarthNerdus
    on Oct 15, 2024
    Author
    More actions

    Should this at least be better documented/FAQ'd? I'm not expecting an alert in the application, obviously, but this only came to my attention because another tool pointed to the OrbStack file and then I found the legacy issue here on Github. In addition to this, it required non-standard tooling in order to actually backup data.img and restore it. I didn't find any solution to enable Migration Assistant besides deleting the file from the source machine.

    If I had moved forward with just starting the second laptop from scratch and attempted to move the file, I would have been hit by similar messaging/failures in Finder that the file is too big for the destination. This is not just a Migration Assistant issue, really, the file is completely non-portable via the standard available tooling today.

    image
  5. winterqt commented on Oct 16, 2024

    @winterqt
    winterqt
    on Oct 16, 2024
    More actions

    Should this at least be better documented/FAQ'd?

    Absolutely.

  6. janspants11 commented on Nov 9, 2024

    @janspants11
    janspants11
    on Nov 9, 2024
    More actions

    I did not error on migration assistant to my new machine but now I am having the exact same error trying to boot orbstack on the new device.

    I was able to boot by completely removing the .orbstack/ folder

    Reacted by Esteban Serrano and Sugus
  7. dongjiancom commented on Nov 12, 2024

    @dongjiancom
    dongjiancom
    on Nov 12, 2024
    More actions

    orbstack使用了自己的ssh,存储在:/.orbstack/ssh
    我删除了
    /.orbstack/ 并重新安装, 解决了这个报错

    Reacted by September999999999 and Sugus
  8. kdrag0n commented on Nov 18, 2024

    @kdrag0n
    kdrag0n
    on Nov 18, 2024
    Member
    More actions

    We've added a warning to the docs: https://docs.orbstack.dev/faq#data-img

  9. kdrag0n
    closed this as completedon Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    t/improvementMinor improvementMinor improvement

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.