run the git lfs pull until that directory has some megabytes per folder. Either via repo forall or navigate into the prebuilt lfs directory and do a git lfs pull on the tag your checking out
during doing this i was thinking as well : it is not a real solution in the long term.
you are right, and when read your comment, i throught he is right i am a too “punk”, harvey186 was used to say (about himself) i am partisant of "quick and dirty"
Copy and paste is good and is what I do, because it is guaranteed and I often make typos !
Ron said that it was change of apostrophe made a difference for him.
From your ncdu, I speculate that you might have started pulling and the remote connection dropped. I think I have experience of this, but the terminal gives no response if anything fails the prompt just returns silently.
forum posts are also put into a editor and many systems to sanitising on user input written to databases, so they don’t turn into SQL-injections.
Different locale settings, language packages… can have an impact, which is why using a English default Ubuntu and Using Docker unifies things and makes trouble shooting easier.
My last build was ~10 years ago, as a sysadmin I never used Docker, but for getting back into building, I have accepted, this is the common ground these days.
So we need a fix, perhaps not >repo_foral – we have no idea if it is capable of feedback !?
I have an idea that following straight on form a successful repo sync, helps to ensure you have a line to the server, just a guess.
Last of my "quick and dirty" ideas – delete one random folder prebuilts/prebuiltapks/Apps now repo sync has definitely got some work to do ! now follow on lfs pull.
If I copy and paste the correct command in the forum in the terminal its replaced by the incorrect apostrophes…so better no copy & paste
Please see screenshot for clarification which apostrophes works for me (German keyboard)