I have builded PMOS for samsung galaxy tab 2 7 " but i have error while flashing it via recovery
/tmp/postmarketos/pmos.log here https://pastebin.com/XNZZPiUW
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
I have no idea what causes this error since I don't know how the recovery-zip internals work, but there was the same error when flashing to the Samsung S5 mini.
For that device this error went away by running the installer a second time, but that also has some other errors (see #1635 (closed)), There devices probably have the same installation failures.
Am not so sure about your /tmp theory, my /tmp is 600MB+ and it doesn't seem to be even touched much if at all during the attempted install (watched df -h while flashing a few times)
It's not a problem to flash 300MB+ LineageOS ROM to this phone so I'd be surprised if storage was an issue with 100MB+ PMOS ROM
@K3V3L TWRP version? PMOS does not appear to be supporting TWRP 3.2.0+ at the moment, I'll make an issue about it.
however the umount .log problem might be not related to that, it's my problem with not being able to copy recovery.fstab that's the issue with that.
EDIT:
Writeup on that issue here - #1636 (closed) - as for your original issue I'd try the install process again until it throws a different error or goes through, as that worked for me.
EDIT2:
I need to attempt to flash (.log error), then I need to go to TWRP mount settings and unmount SYSTEM (otherwise next attempt is a umount error) and only after that it can proceed to semi-correctly flash the system.
I ran into this about two weeks ago, and the fix appears to be merged a month ago, so I think it doesn't fix it.
Also am pretty sure that mounting /SYSTEM (which is done if you format partitions in TWRP) and then flashing the recovery.zip is a 100% failure of similar/same nature as OP's problem (as it relates to umounting).
(it at least failed on my samsung-kminilte when I tried about a week-two ago)
Uh, what I meant was #1636 (closed) (hash instead of exclamation mark), the fstab issue
you have fixed in !1673 (merged). As I understood, this should fix the following error
found in @K3V3L's log:
umount: can't umount /tmp/postmarketos/chroot/pmos.log: No such file or
directory
Really unsure if my MR fixed that particular issue, but it's true I've been unable to reproduce it since then. Maybe it has something to do with having an Android ROM previously installed or I inadvertently fixed that one too.