Failed to remove '/.new_rootfs/': Directory not empty
Hey, so I'm getting the error in the title when doing akshara update. I'm trying to track down if this is because of my custom track or because of something else/ you can find my tracks here:
https://github.com/s-20/owlbear-tracks/tree/main
It's a spinoff of the regular Gnome track,. streamlined, with some stuff swapped around. Currently trying to refresh on gnomeish-owlbear.yaml and it worked until my last couple changes.
Edit: a Gist with my system.yaml and the output of the akshara update command:
https://gist.github.com/s-20/8c6868b537e5f5164b87ed0e05fd5e09
Solution:Jump to solution
this was fixed in https://git.blendos.co/blendOS/system-tools/akshara/-/commit/825e6c8516fced88d79a424cd108ff0ec1b4f1d7
GitLab
Fix
/.new_rootfs/ not being deleted on error (was not empty) (825...A modern take on managing and updating operating systems.
11 Replies
When the update is running try running
systemctl daemon-reload in a terminalDoesn't seem to do anything unfortunately. The systemctl command runs fine, but the update ends with:
and it happens really quick. The system lock aquires, the Arch tarball downloads, checksum verifies, and then it goes to generate the system. Then it aborts with the above output.
If I rm -r the /.new_rootfs/ directory, I get the same results.
Gist
Output of sudo akshara update command and my System.yaml
Output of sudo akshara update command and my System.yaml - output of akshara update
Solution
this was fixed in https://git.blendos.co/blendOS/system-tools/akshara/-/commit/825e6c8516fced88d79a424cd108ff0ec1b4f1d7
GitLab
Fix
/.new_rootfs/ not being deleted on error (was not empty) (825...A modern take on managing and updating operating systems.
the copy of akshara in the repo is out of date
@rudra has to fix that
Well, this seems to have partially solved the problem; but it's still not working after replacing the modified file. Now I get this:
Sorry it took so long to post feedback on this. I just got home.
oops i forgor about this
uhhhhh should have it fixed later hopefully
Once it gets fixed, do I have to do anything or just update again?
Youβll have to manually use the new one like you did before
Just once
That's what I thought. Thanks!
Out of curiosity, will reinstalling the OS also fix the problem? I didn't do the install that long ago, and I could start over fairly easily.
Not trying to rush you, just curious if you got to it.
the problem is twofold, that's just the error handling, a symptom of the problem
i'm pretty sure systemctl daemon-reload, if done at the right time/put in akshara, would work
not yet