So I think Paride is more or less right in #10: One of the subiquities starts the install. One of the subiquities then segfaults (doesn't matter which one). Systemd restarts this subiquity, which then unmounts /target, so the subiquity running the install just copies filesystem.squashfs to RAM and eventually runs out of space. One obvious thing to do would be to only unmount /target just before starting the install, so lets do that.
The 'block probing crashed with CancelledError' things are also bugs (would you believe there are two CancelledErrors??) but I don't think we are logging enough of them to fill up RAM. I've fixed these in https://github.com/CanonicalLtd/subiquity/pull/675 Now, as to why subiquity is segfaulting: I have no idea :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865027 Title: focal-arm64 install fails. No space left on device on /target To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1865027/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
