initrd-magisk loop in "Initialize system environment....." about initrd-magisk HOT 12 CLOSED

I'm trying cm14.1-r5 with initrd-magisk v1.6, not looping but I still can see this from DEBUG=3

EXT4-fs (sda4) couldn't mount as ext3 due to feature incompatibilities
 found at /dev/sda4
EXT4-fs (loop0) couldn't mount as ext3 due to feature incompatibilities

Magisk installed and su prompt from Magisk. su version same with apk

EDIT: I forgot to unsu cmsu. I manually unsu because I run unsu in DEBUG=1 initrd-magisk v1.6 unsu command not found
EDIT 2: BTW I using initrd from iso same I see ☝️ message and not looping

from initrd-magisk.

Can you send your original initrd.img, thanks

from initrd-magisk.

cm-x86_64-14.1-r5.zip
Same from iso

from initrd-magisk.

@HuskyDG
Sorry I found the problem. in the end function check_root() if boot-magisk.img not found zcat raised errorlevel. I not know why and I run zcat boot.img.gz with path completion in DEBUG boot $? return 0, but the size is 0 after I boot in linux. in linux I run zcat and I get this file

# sha512sum
5590b1c34105cf61f9fd05acc35e60c53c1268512a60b5829d7cc7ba11297500e1136bad824e2616bb70d57e97a167b25b9a13f894e087e4857a58a452bde94c  boot-magisk.img

for the message it's probably due to mount without adding type
init_debug.diff.txt
and there are similarities v1.6 with the original initrd.img

from initrd-magisk.

if you can fix, you can fork repo and make pull request

from initrd-magisk.

you can test your changes immediately in GitHub's Actions tab

from initrd-magisk.

can initrd-magisk work without boot-magisk.img even after boot.img.gz is used it still doesn't exist
Is there any impact if I ignore boot-magisk.img

from initrd-magisk.

can initrd-magisk work without boot-magisk.img even after boot.img.gz is used it still doesn't exist Is there any impact if I ignore boot-magisk.img

you boot android from iso (live mode)?

from initrd-magisk.

you boot android from iso (live mode)?

No. I extract in harddisk sda4 and unsquash system.sfs also uses data.img

I run zcat boot.img.gz with path completion in DEBUG boot $? return 0, but the size is 0

maybe the cause is zcat trying to write boot.img.gz in read only mnt SRC

from initrd-magisk.

sorry for let you wait,
try 7f9f172

from initrd-magisk.

https://github.com/HuskyDG/initrd-magisk/actions/runs/2391222999

from initrd-magisk.

are you still there?

from initrd-magisk.