When Fuji is used in macOS Recovery to acquire a FileVault-encrypted Mac, the target Data volume shows up in the device list but can't be selected or acquired. It has no mount point because the volume is locked. There's currently no method in the GUI to unlock it, and the auto-discovery in shared/environment.py falls back to SOURCE_PATH = "/" when no .fseventsd canary is found (because the volume was never mounted).
In practice, any Mac with FileVault enabled can't be acquired from Recovery without manual command-line intervention before launching Fuji. That adds steps, increases the risk of error, and moves work outside of the GUI flow.
When Fuji is used in macOS Recovery to acquire a FileVault-encrypted Mac, the target Data volume shows up in the device list but can't be selected or acquired. It has no mount point because the volume is locked. There's currently no method in the GUI to unlock it, and the auto-discovery in
shared/environment.pyfalls back toSOURCE_PATH = "/"when no.fseventsdcanary is found (because the volume was never mounted).In practice, any Mac with FileVault enabled can't be acquired from Recovery without manual command-line intervention before launching Fuji. That adds steps, increases the risk of error, and moves work outside of the GUI flow.