Aliendalvik not starting - errors in journalctl bad extra_isize

alien-dalvik

asked 2020-06-21 16:11:18 +0200

daywalker

1570 ●31 ●46 ●43

updated 2020-06-22 09:57:04 +0200

jiit

2678 ●32 ●58 ●59

admin

After a reboot aliendalvik is not starting anymore. In journalctl i am getting these errors over and over:

kernel: EXT4-fs error (device dm-2): ext4_iget:4330: inode #915773: comm start-aliendalv: bad extra_isize (44871 != 256)

Any clue how to fix this?

Device is an XA2 SFOS 3.3.0.16 Device is encrypted, + encrypted microsd is uded.

dm-2 should be /home regarding info on dmsetup info /dev/dm-2

Everything was working fine until the battery went empty, i recharged it and turned it on a few minutes ago. Since then android apps are not starting and above error is in the log.

edit retag flag offensive close delete

Comments

did you try to start it maunally or just by trggering an android app ?

pawel ( 2020-06-21 16:38:06 +0200 )edit

@pawel i have configured aliendalvik to start on system boot. but it does not apparently

daywalker ( 2020-06-21 18:11:53 +0200 )edit

Comments

@lethe had a bit of struggle due to usb3 bug on linux fastboot and fastboot driver bug on windows 10 (latest build 2004) but eventually got an old usb2 hub and could flash hybris-recovery.img with linux. Filecheck could repair it and aliendalvik is starting up. Crossing fingers everything will work the next few days so i do not have to reinstall aliendalvik. Thanks so far!

daywalker ( 2020-06-24 00:20:15 +0200 )edit

Aliendalvik not starting - errors in journalctl bad extra_isize

Comments

1 Answer

Comments

Question tools

Stats

Related questions

Aliendalvik not starting - errors in journalctl bad extra_isize

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions