Revision history [back]

Updated yesterday to 3.0.3.8 and now my Xperia X hangs on the sony logo.

I went into recovery mode and tried to repair the file system with no avail. I can mount the /dev/mapper/sailfish-home and /dev/mapper/sailfish-root devices and access the files.

Can i try anything else without factory reset or reflash?

I have searched with the usual tags but did not find a solution in other threads.

Are there any interesting logs? I seem to cannot find useful logs in /var/logs ...

Updated yesterday to 3.0.3.8 and now my Xperia X hangs on the sony logo.

I went into recovery mode and tried to repair the file system with no avail. I can mount the /dev/mapper/sailfish-home and /dev/mapper/sailfish-root devices and access the files.

Can i try anything else without factory reset or reflash?

I have searched with the usual tags but did not find a solution in other threads.

Are there any interesting logs? I seem to cannot find useful logs in /var/logs ...

[   21.213583] EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
[   21.213893] EXT4-fs (dm-0): couldn't mount as ext2 due to feature incompatibilities
[   21.300509] EXT4-fs (dm-0): recovery complete
[   21.300872] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[  393.214398] EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
[  393.214725] EXT4-fs (dm-0): couldn't mount as ext2 due to feature incompatibilities
[  393.219959] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[  646.574092] incell_state_sp_on: In-Cell I/F state no update
[  969.281530] EXT4-fs (mmcblk0p28): couldn't mount as ext3 due to feature incompatibilities
[  969.281896] EXT4-fs (mmcblk0p28): couldn't mount as ext2 due to feature incompatibilities
[  969.286957] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: (null)
[ 1046.476242] isofs_fill_super: bread failed, dev=mmcblk0p29, iso_blknum=16, block=32
[ 1046.476406] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=256, location=256
[ 1046.476767] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=512, location=512
[ 1046.476812] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=256, location=256
[ 1046.477182] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=512, location=512
[ 1046.477192] UDF-fs: warning (device mmcblk0p29): udf_fill_super: No partition found (1)
[ 1046.477507] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 1046.477515] F2FS-fs (mmcblk0p29): Can't find a valid F2FS filesystem in first superblock
[ 1046.477647] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 1046.477654] F2FS-fs (mmcblk0p29): Can't find a valid F2FS filesystem in second superblock
[ 1139.434516] EXT4-fs (dm-1): couldn't mount as ext3 due to feature incompatibilities
[ 1139.434885] EXT4-fs (dm-1): couldn't mount as ext2 due to feature incompatibilities
[ 1139.448822] EXT4-fs (dm-1): 1 orphan inode deleted
[ 1139.448837] EXT4-fs (dm-1): recovery complete
[ 1139.455606] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)

Updated yesterday to 3.0.3.8 and now my Xperia X hangs on the sony logo.

I went into recovery mode and tried to repair the file system with no avail. I can mount the /dev/mapper/sailfish-home and /dev/mapper/sailfish-root devices and access the files.

Can i try anything else without factory reset or reflash?

I have searched with the usual tags but did not find a solution in other threads.

Are there any interesting logs? I seem to cannot find useful logs in /var/logs ...

I found something in dmesg via chroot - seems like something is wrong with mmcblk0p29

[   21.213583] EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
[   21.213893] EXT4-fs (dm-0): couldn't mount as ext2 due to feature incompatibilities
[   21.300509] EXT4-fs (dm-0): recovery complete
[   21.300872] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[  393.214398] EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
[  393.214725] EXT4-fs (dm-0): couldn't mount as ext2 due to feature incompatibilities
[  393.219959] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[  646.574092] incell_state_sp_on: In-Cell I/F state no update
[  969.281530] EXT4-fs (mmcblk0p28): couldn't mount as ext3 due to feature incompatibilities
[  969.281896] EXT4-fs (mmcblk0p28): couldn't mount as ext2 due to feature incompatibilities
[  969.286957] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: (null)
[ 1046.476242] isofs_fill_super: bread failed, dev=mmcblk0p29, iso_blknum=16, block=32
[ 1046.476406] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=256, location=256
[ 1046.476767] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=512, location=512
[ 1046.476812] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=256, location=256
[ 1046.477182] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=512, location=512
[ 1046.477192] UDF-fs: warning (device mmcblk0p29): udf_fill_super: No partition found (1)
[ 1046.477507] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 1046.477515] F2FS-fs (mmcblk0p29): Can't find a valid F2FS filesystem in first superblock
[ 1046.477647] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 1046.477654] F2FS-fs (mmcblk0p29): Can't find a valid F2FS filesystem in second superblock
[ 1139.434516] EXT4-fs (dm-1): couldn't mount as ext3 due to feature incompatibilities
[ 1139.434885] EXT4-fs (dm-1): couldn't mount as ext2 due to feature incompatibilities
[ 1139.448822] EXT4-fs (dm-1): 1 orphan inode deleted
[ 1139.448837] EXT4-fs (dm-1): recovery complete
[ 1139.455606] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)

Updated yesterday to 3.0.3.8 and now my Xperia X hangs on the sony logo.

I went into recovery mode and tried to repair the file system with no avail. I can mount the /dev/mapper/sailfish-home and /dev/mapper/sailfish-root devices and access the files.files in recovery mode. Also chroot is working...

Can i try anything else without factory reset or reflash?

I have searched with the usual tags but did not find a solution in other threads.

Are there any interesting logs? I seem to cannot find useful logs in /var/logs ...

I found something in dmesg via chroot - seems like something is wrong with mmcblk0p29

[   21.213583] EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
[   21.213893] EXT4-fs (dm-0): couldn't mount as ext2 due to feature incompatibilities
[   21.300509] EXT4-fs (dm-0): recovery complete
[   21.300872] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[  393.214398] EXT4-fs (dm-0): couldn't mount as ext3 due to feature incompatibilities
[  393.214725] EXT4-fs (dm-0): couldn't mount as ext2 due to feature incompatibilities
[  393.219959] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
[  646.574092] incell_state_sp_on: In-Cell I/F state no update
[  969.281530] EXT4-fs (mmcblk0p28): couldn't mount as ext3 due to feature incompatibilities
[  969.281896] EXT4-fs (mmcblk0p28): couldn't mount as ext2 due to feature incompatibilities
[  969.286957] EXT4-fs (mmcblk0p28): mounted filesystem with ordered data mode. Opts: (null)
[ 1046.476242] isofs_fill_super: bread failed, dev=mmcblk0p29, iso_blknum=16, block=32
[ 1046.476406] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=256, location=256
[ 1046.476767] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=512, location=512
[ 1046.476812] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=256, location=256
[ 1046.477182] UDF-fs: error (device mmcblk0p29): udf_read_tagged: read failed, block=512, location=512
[ 1046.477192] UDF-fs: warning (device mmcblk0p29): udf_fill_super: No partition found (1)
[ 1046.477507] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 1046.477515] F2FS-fs (mmcblk0p29): Can't find a valid F2FS filesystem in first superblock
[ 1046.477647] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[ 1046.477654] F2FS-fs (mmcblk0p29): Can't find a valid F2FS filesystem in second superblock
[ 1139.434516] EXT4-fs (dm-1): couldn't mount as ext3 due to feature incompatibilities
[ 1139.434885] EXT4-fs (dm-1): couldn't mount as ext2 due to feature incompatibilities
[ 1139.448822] EXT4-fs (dm-1): 1 orphan inode deleted
[ 1139.448837] EXT4-fs (dm-1): recovery complete
[ 1139.455606] EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)