We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2020-05-18 17:27:58 +0200

[XA2] [bug] I/O error doing file system check on working device

Hi. When booting into Jolla recovery on my Xperia XA2 and performing a file system check I get these I/O errors:

/dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error
/dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4186112: Input/output error /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4096: Input/output error
2 logical volume(s) in volume group "sailfish" now active e2fsck 1.45.4 (23-Sep-2019) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information root: 37390/184320 files (0.2% non-contiguous), 603974/785408 blocks e2fsck 1.45.4 (23-Sep-2019) Pass 1: Checking inodes, blocks, and sizes Inode 706861 extent tree (at level 1) could be shorter. Optimize? yes

Pass 1E: Optimizing extent trees Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information

home: FILE SYSTEM WAS MODIFIED home: 72432/996608 files (2.9% non-contiguous), 3068826/4456448 blocks /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error 0 logical volume(s) in volume group "sailfish" now active Done Press [Enter] to return to recovery menu...

I'm able to boot into Sailfish and use it without any issues. I tried reinstalling Android and Sailfish again but ended up with the same errors. I'm currently on SailfishOS 3.3.0.16.

After reaching out to Jolla Care they confirmed that they get the same output on a perfectly working XA2 with SailfishOS. I thereby assume this is a bug in the filesystem layout.

[XA2] [bug] I/O error doing file system check on working device

Hi. When booting into Jolla recovery on my Xperia XA2 and performing a file system check I get these I/O errors:

/dev/mmcblk0rpmb: read failed after

  /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error 
/dev/mmcblk0rpmb: read failed after 0
error /dev/mmcblk0rpmb: read failed after 0 of 4096 at 4128768: Input/output error /dev/mmcblk0rpmb: read failed after 0 0 of 4096 at 4186112: Input/output error /dev/mmcblk0rpmb: read failed after 0 0 of 4096 at 4096: Input/output error
error 2 logical volume(s) in volume group group "sailfish" now active active e2fsck 1.45.4 (23-Sep-2019) 1.45.4 (23-Sep-2019) Pass 1: Checking inodes, inodes, blocks, and sizes sizes Pass 2: Checking Checking directory structure structure Pass 3: Checking Checking directory connectivity Pass 4: connectivity Pass 4: Checking reference counts Pass 5: counts Pass 5: Checking group summary information root: 37390/184320 files (0.2% (0.2% non-contiguous), 603974/785408 blocks e2fsck 1.45.4 (23-Sep-2019) Pass 1: (23-Sep-2019) Pass 1: Checking inodes, blocks, and sizes Inode 706861 extent tree (at level 1) 1) could be shorter. Optimize? yes

yes Pass 1E: Optimizing extent trees Pass trees Pass 2: Checking directory structure Pass structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass counts Pass 5: Checking group summary information

information home: ***** FILE SYSTEM WAS MODIFIED MODIFIED ***** home: 72432/996608 files (2.9% non-contiguous), 3068826/4456448 blocks /dev/mmcblk0rpmb: read failed 3068826/4456448 blocks /dev/mmcblk0rpmb: read failed after 0 of 4096 at 0: Input/output error Input/output error 0 logical volume(s) in volume volume group "sailfish" now active Done Press [Enter] to return to recovery menu...

menu...

I'm able to boot into Sailfish and use it without any issues. I tried reinstalling Android and Sailfish again but ended up with the same errors. I'm currently on SailfishOS 3.3.0.16.

After reaching out to Jolla Care they confirmed that they get the same output on a perfectly working XA2 with SailfishOS. I thereby assume this is a bug in the filesystem layout.