Android Dual Boot Patcher: exFAT driver issue?

[webmaster33]

Dual Boot Patcher (Android) is using exFAT driver 1.2.6 and I have some issues with using Samsung EVO 64GB external sdcard. Might be possible, that the write issues are related to exFAT driver problems? I have no issue, if I format the card with FAT32 format. Did format to exFAT filesystem under Windows 7.

Including the kmsg.log relevant part here, if you see any signs related to the exFAT driver:

[   12.334167] mblog: 1 fstab entries for the external SD
[   12.334350] mblog: [Attempt 1/10] Finding and mounting external SD
[   12.334472] mblog: Matching devices against pattern: /devices/platform/msm_sdcc.2/mmc_host/mmc2*
[   12.338012] mblog: /default.prop contains fuse-exfat override: true
[   12.428955] mblog: Using fuse-exfat: 1
[   12.462677] mblog: Running executable: /sbin/fsck.exfat
[   12.464721] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   12.464904] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   12.465087] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   12.465179] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   12.465332] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   12.465484] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   12.465576] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   12.465698] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   12.465850] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   12.466003] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   13.065521] [SSP] Updated 88487 bytes / 107440 bytes
[   13.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   13.758789] max77693-muic max77693-muic: func:max77693_muic_usb_detect info->muic_data->sw_path:0
[   14.104248] [SSP] Updated 103374 bytes / 107440 bytes
[   14.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   14.863281] [SSP] Firmware download is success.(107440 bytes)
[   15.078796] [SSP]: debug_work_func(0) - Sensor state: 0x0, RC: 0, MS: 0
[   15.078887] [SSP] : debug_work_func firmware downloading state = 3
[   15.148773] msm_thermal: Max frequency reset for cpu0
[   15.149139] msm_thermal: Max frequency reset for cpu1
[   15.149536] msm_thermal: Max frequency reset for cpu2
[   15.149902] msm_thermal: Max frequency reset for cpu3
[   15.158782] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   16.158843] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   17.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   17.868804] [SSP] forced_to_download_binary, DL state = 4
[   17.871063] [SSP] MCU device ID = 85, reading ID = 85
[   17.871276] [SSP] Sensor Posision A : 3, G : 3, M: 5, P: 0
[   17.871948] ssp_enable, enable = 1, old enable = 1
[   17.872833] [SSP]: Proximity Threshold - 0, 0
[   17.873291] [SSP]: set_hw_offset: x: 0, y: 0, z: 0
[   17.873443] ssp_sensorhub_report_notice: reset
[   17.873504] [SSP] forced_to_download_binary, DL state = 5
[   17.874084] [SSP] MCU Firm Rev : New = 14111200
[   18.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   19.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   20.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   21.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   22.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   23.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   24.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   25.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   25.758819] max77693-muic max77693-muic: func:max77693_muic_dock_usb_detect info->muic_data->sw_path:0
[   26.078826] [SSP]: debug_work_func(0) - Sensor state: 0x3fff, RC: 0, MS: 0
[   26.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   27.158782] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   27.905670] [SSP]: MSG From MCU - Init
[   27.905670] Gyro Temp Init
[   27.905670] CheckLightLux Init
[   27.905670] AD 6 1 0 1
[   28.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   28.798797] max77693-muic max77693-muic: func:max77693_muic_mhl_detect cable_type:0
[   29.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   30.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   31.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   32.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   33.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   34.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   35.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   36.158782] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   37.078796] [SSP]: debug_work_func(1) - Sensor state: 0x3fff, RC: 0, MS: 0
[   37.158782] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   38.158782] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   39.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   39.881530] mblog: Command output: exfatfsck 1.2.6
[   39.881622] mblog: Command output: Checking file system on /dev/block/mmcblk1.
[   39.881774] mblog: Command output: File system version           1.0
[   39.881896] mblog: Command output: Sector size                 512 bytes
[   39.881988] mblog: Command output: Cluster size                128 KB
[   39.882110] mblog: Command output: Volume size                  60 GB
[   39.882202] mblog: Command output: Used space                   36 GB
[   39.882324] mblog: Command output: Available space              24 GB
[   39.882415] mblog: Command output: Totally 1589 directories and 16564 files.
[   39.882568] mblog: Command output: File system checking finished. No errors found.
[   39.883026] mblog: Running executable: /sbin/mount.exfat
[   39.884948] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   39.885101] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   39.885253] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   39.885345] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   39.885498] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   39.885620] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   39.885711] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   39.885864] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   39.885986] mblog: Command output: __bionic_open_tzdata_path: ANDROID_DATA not set!
[   39.886077] mblog: Command output: __bionic_open_tzdata_path: ANDROID_ROOT not set!
[   39.962768] mblog: mount.exfat returned: 0
[   39.962860] mblog: Successfully mounted /dev/block/mmcblk1 (fuse-exfat) at /raw/extsd
[   39.963073] mblog: Successfully mounted partitions
[   39.963378] mblog: Successfully mounted fstab (excluding /data)
[   39.963653] mblog: fstab: /dev/block/platform/msm_sdcc.1/by-name/boot      /boot          emmc    defaults                                                                                      recoveryonly
[   39.963897] mblog: fstab: /dev/block/platform/msm_sdcc.1/by-name/recovery  /recovery      emmc    defaults                                                                                      recoveryonly
[   39.964050] mblog: fstab: /dev/block/platform/msm_sdcc.1/by-name/apnhlos   /firmware      vfat    ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0  wait
[   39.964263] mblog: fstab: /dev/block/platform/msm_sdcc.1/by-name/mdm       /firmware-mdm  vfat    ro,shortname=lower,uid=1000,gid=1000,dmask=227,fmask=337,context=u:object_r:firmware_file:s0  wait
[   39.964447] mblog: fstab: /dev/block/platform/msm_sdcc.1/by-name/efs       /efs           ext4    nosuid,nodev,noatime,noauto_da_alloc,journal_async_commit,errors=panic                        wait,check,notrim
[   39.964660] mblog: fstab: /dev/block/platform/msm_sdcc.1/by-name/userdata  /data          f2fs    nosuid,nodev,noatime,rw,inline_xattr                                                          wait,check,formattable,encryptable=footer
[   39.964874] mblog: -> /data entry
[   39.964965] mblog: fstab: /dev/block/platform/msm_sdcc.1/by-name/userdata  /data          ext4    nosuid,nodev,noatime,noauto_da_alloc,journal_async_commit,errors=panic                        wait,check,formattable,encryptable=footer
[   39.965179] mblog: -> /data entry
[   39.965240] mblog: fstab: /devices/platform/msm_sdcc.2/mmc_host/mmc2*      auto           auto    defaults                                                                                      voldmanaged=sdcard1:auto,encryptable=userdata
[   39.965484] mblog: fstab: /devices/platform/msm_hsusb_host/usb*            auto           auto    defaults                                                                                      voldmanaged=usb:auto
[   39.965698] mblog: /raw/data: Has 2 fstab entries
[   39.965820] mblog: Attempting to mount(/dev/block/platform/msm_sdcc.1/by-name/userdata, /raw/data, f2fs, 1030, inline_xattr)
[   39.965942] mblog: /dev/block/platform/msm_sdcc.1/by-name/userdata: Waiting up to 20 seconds for block device
[   39.972137] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x94890)
[   39.972259] F2FS-fs (mmcblk0p29): Can't find valid F2FS filesystem in 1th superblock
[   39.972717] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x100000)
[   39.972778] F2FS-fs (mmcblk0p29): Can't find valid F2FS filesystem in 2th superblock
[   39.972930] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x94890)
[   39.973052] F2FS-fs (mmcblk0p29): Can't find valid F2FS filesystem in 1th superblock
[   39.973114] F2FS-fs (mmcblk0p29): Magic Mismatch, valid(0xf2f52010) - read(0x100000)
[   39.973266] F2FS-fs (mmcblk0p29): Can't find valid F2FS filesystem in 2th superblock
[   39.973571] mblog: Failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (f2fs) at /raw/data: Invalid argument
[   39.973693] mblog: Attempting to mount(/dev/block/platform/msm_sdcc.1/by-name/userdata, /raw/data, ext4, 1030, noauto_da_alloc,journal_async_commit,errors=panic)
[   39.973846] mblog: /dev/block/platform/msm_sdcc.1/by-name/userdata: Waiting up to 20 seconds for block device
[   39.987640] EXT4-fs (mmcblk0p29): 4 orphan inodes deleted
[   39.987731] EXT4-fs (mmcblk0p29): recovery complete
[   39.994873] EXT4-fs (mmcblk0p29): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,journal_async_commit,errors=panic
[   39.995025] mblog: Successfully mounted /dev/block/platform/msm_sdcc.1/by-name/userdata (ext4) at /raw/data
[   39.995178] mblog: Successfully mounted partitions
[   39.998687] mblog: Boot UI is missing. Skipping...
[   40.012573] mblog: Policy version: 30
[   40.043334] SELinux:  Android master kernel running Android M policy in compatibility mode.
[   40.158782] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   40.231262] mblog: Assigning /raw/extsd/multiboot/extsd-slot-rr574/system.img to loop device /dev/block/loop1
[   40.272338] EXT4-fs (loop1): mounted filesystem with ordered data mode. Opts: 
[   40.512237] mblog: Assigning /raw/extsd/multiboot/extsd-slot-rr574/system.img to loop device /dev/block/loop2
[   40.513977] EXT4-fs (loop2): recovery complete
[   40.514068] EXT4-fs (loop2): mounted filesystem with ordered data mode. Opts: 
[   40.560974] mblog: /system/bin/fsck_msdos: SELinux label is: u:object_r:fsck_exec:s0
[   40.561157] mblog: Failed to bind mount /wrapped/fsck_msdos to /system/bin/fsck_msdos: Invalid argument
[   40.563171] mblog: /system/bin/fsck_msdos_mtk: Failed to stat: No such file or directory
[   40.565216] mblog: /system/bin/fsck.exfat: SELinux label is: u:object_r:fsck_exec:s0
[   40.565429] mblog: Failed to bind mount /wrapped/fsck.exfat to /system/bin/fsck.exfat: Invalid argument
[   40.566711] mblog: /system/bin/mount.exfat: SELinux label is: u:object_r:system_file:s0
[   40.566894] mblog: Failed to bind mount /wrapped/mount.exfat to /system/bin/mount.exfat: Invalid argument
[   40.567077] mblog: /wrapped: Failed to remount read-only: Invalid argument
[   40.567291] mblog: JSON error on line -1: unable to open /raw/data/media/0/MultiBoot/extsd-slot-rr574/config.json: No such file or directory
[   40.567443] mblog: /raw/data/media/0/MultiBoot/extsd-slot-rr574/config.json: Failed to load config for ROM extsd-slot-rr574
[   40.567565] mblog: Enable appsync: 0
[   40.583160] mblog: /data/security/spota: Mounted read-only tmpfs over spota directory
[   40.597381] mblog: Policy version: 30
[   40.634063] mblog: Received notification to stop uevent thread
[   40.634368] mblog: Received notification to stop property service
[   40.711242] mblog: Launching real init ...
[   40.713409] init: init started!
[   40.859283] init: (Initializing SELinux enforcing took 0.15s.)
[   40.874023] init: init second stage started!
[   40.874511] init: property_set("ro.boot.warranty_bit", "1") failed
[   41.024291] init: (Loading properties from /default.prop took 0.00s.)
[   41.025939] init: (Parsing /init.multiboot.rc took 0.00s.)
[   41.026092] init: (Parsing /init.environ.rc took 0.00s.)
[   41.026489] init: (Parsing /init.usb.rc took 0.00s.)
[   41.027435] init: (Parsing init.qcom.power.rc took 0.00s.)
[   41.028533] init: (Parsing init.qcom.usb.rc took 0.00s.)
[   41.028656] init: (Parsing /init.qcom.rc took 0.00s.)
[   41.029174] init: (Parsing /init.usb.configfs.rc took 0.00s.)
[   41.029327] init: (Parsing /init.zygote32.rc took 0.00s.)
[   41.029541] init: (Parsing /init.trace.rc took 0.00s.)
[   41.030029] init: (Parsing /init.superuser.rc took 0.00s.)
[   41.030181] init: (Parsing /init.cm.rc took 0.00s.)
[   41.030273] init: (Parsing /init.rc took 0.01s.)
[   41.030487] init: SELinux: Could not get canonical path /adb_keys restorecon: No such file or directory.
[   41.030792] init: Starting service 'ueventd'...
[   41.031555] init: Waiting for /dev/.coldboot_done...
[   41.033111] ueventd: ueventd started!
[   41.158813] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   41.542388] power_supply sec-fuelgauge: driver failed to report `status' property: 4294967274
[   41.545745] max77693_get_charger_state: CHG_DTLS : 0x 8
[   41.546325] max77693_get_health_state: reg_data(0x3)
[   41.546966] max77693_get_vbus_state: VBUS is invalid. CHGIN < CHGIN_UVLO
[   41.548034] max77693_get_health_state: vbus_state : 0x0, chg_dtls : 0x8
[   41.548156] max77693_get_health_state: vbus is under
[   41.549835] max77693_get_input_current: CHG_CNFG_09(0x17)
[   41.549987] power_supply sec-charger: driver failed to report `power_now' property: 4294967274
[   41.575622] ueventd: Coldboot took 0.53s.
[   41.577148] init: Waiting for /dev/.coldboot_done took 0.55s.
[   41.660522] keychord: using input dev pmic8xxx_pwrkey for fevent
[   41.660614] keychord: using input dev max77693-muic for fevent
[   41.660736] keychord: using input dev gpio-keys for fevent
[   41.666534] init: write_file: Unable to open '/proc/sys/kernel/hung_task_timeout_secs': No such file or directory
[   41.666778] init: write_file: Unable to open '/proc/sys/kernel/sched_tunable_scaling': No such file or directory
[   41.666931] init: write_file: Unable to open '/proc/sys/kernel/sched_latency_ns': No such file or directory
[   41.667114] init: write_file: Unable to open '/proc/sys/kernel/sched_wakeup_granularity_ns': No such file or directory
[   41.667266] init: write_file: Unable to open '/proc/sys/kernel/sched_compat_yield': No such file or directory
[   41.668914] init: write_file: Unable to write to '/dev/cpuctl/cpu.shares': Invalid argument
[   41.671630] init: write_file: Unable to open '/proc/sys/abi/swp': No such file or directory
[   41.687652] fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/apnhlos,target=/firmware,type=vfat)=0
[   41.695129] fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/mdm,target=/firmware-mdm,type=vfat)=0
[   41.696228] loop: Write error at byte offset 0, length 4096.
[   41.696319] Buffer I/O error on device loop1, logical block 0
[   41.696441] lost page write due to I/O error on loop1
[   41.696533] EXT4-fs error (device loop1): ext4_find_entry:941: inode #486: comm init: reading directory lblock 0
[   41.696685] Aborting journal on device loop1-8.
[   41.696807] loop: Write error at byte offset 1075802112, length 4096.
[   41.696899] Buffer I/O error on device loop1, logical block 262647
[   41.697021] lost page write due to I/O error on loop1
[   41.697113] JBD2: Error -5 detected when updating journal superblock for loop1-8.
[   41.697235] EXT4-fs (loop1): Remounting filesystem read-only
[   41.699707] sec-fuelgauge 11-0036: 0x02(0xb4), 0x03(0x20), 0x04(0x3f), 0x05(0x77), 0x06(0x00), 0x07(0x00), 0x08(0x00), 0x09(0x12), 0x0a(0x00), 0x0b(0x00), 0x0c(0x6c), 0x0d(0x1e), 
[   41.703247] sec-fuelgauge 11-0036: 0x14(0x00), 0x15(0xff), 0x16(0xfe), 0x17(0xda), 0x18(0x7d), 0x19(0x00), 0x1a(0x01), 0x1b(0xff), 
[   41.703399] sec-fuelgauge 11-0036: sec_fg_get_atomic_capacity: old : 31, current : 31
[   41.703979] max77693_get_input_current: CHG_CNFG_09(0x17)
[   41.706115] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
[   41.706329] fs_mgr: check_fs(): mount(/dev/block/platform/msm_sdcc.1/by-name/efs,/efs,ext4)=0: Success
[   41.713043] sec-battery sec-battery: sec_bat_get_battery_info:Vnow(3602mV),Inow(460mA),SOC(31%),Tbat(358)
[   41.713195] sec-battery sec-battery: sec_bat_monitor_work: Status(Discharging), mode(None), Health(Good), Cable(1), siop_level(100)
[   41.713958] max77693-muic max77693-muic: func:max77693_muic_monitor_status, ST1:0x3f, ST2:0x0 CABLE:0
[   41.768859] fs_mgr: check_fs(): unmount(/efs) succeeded
[   41.769012] fs_mgr: Running /system/bin/e2fsck on /dev/block/platform/msm_sdcc.1/by-name/efs
[   41.770507] e2fsck: executing /system/bin/e2fsck failed: I/O error
[   41.770538] 
[   41.770690] e2fsck: e2fsck terminated by exit(255)
[   41.770690] 
[   41.775634] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,journal_async_commit,errors=panic
[   41.775817] fs_mgr: __mount(source=/dev/block/platform/msm_sdcc.1/by-name/efs,target=/efs,type=ext4)=0
[   41.776458] init: Untracked pid 204 killed by signal 6
[   41.778106] init: Starting service 'logd'...
[   41.780456] init: cannot execve('/system/bin/logd'): I/O error
[   41.780883] init: Service 'logd' (pid 221) exited with status 127
[   41.781036] init: Service 'logd' (pid 221) killing any children in process group
[   41.783905] init: property_set("ro.product.name", "jfltexx") failed
[   41.794708] init: (Loading properties from /system/build.prop took 0.01s.)
[   41.795166] EXT4-fs (loop1): previous I/O error to superblock detected
[   41.795257] loop: Write error at byte offset 0, length 4096.
[   41.795410] Buffer I/O error on device loop1, logical block 0
[   41.795471] lost page write due to I/O error on loop1
[   41.795623] EXT4-fs error (device loop1): ext4_find_entry:941: inode #1957: comm init: reading directory lblock 0
[   41.795745] init: (Loading properties from /vendor/build.prop took 0.00s.)
[   41.795898] init: (Loading properties from /factory/factory.prop took 0.00s.)
[   41.797546] init: Starting service 'logd'...
[   41.798309] init: Starting service 'vold'...
[   41.799652] init: cannot execve('/system/bin/logd'): I/O error
[   41.799957] init: Not bootcharting.
[   41.800048] init: cannot execve('/system/bin/vold'): I/O error
[   41.800811] init: Service 'logd' (pid 222) exited with status 127
[   41.800903] init: Service 'logd' (pid 222) killing any children in process group
[   41.801300] init: Service 'vold' (pid 223) exited with status 127
[   41.801452] init: Service 'vold' (pid 223) killing any children in process group
[   42.158996] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
[   42.555084] init: SELinux: Could not set context for /data/security/spota:  Read-only file system
[   42.563323] init: SELinux: Could not get canonical path /data/user/0 restorecon: No such file or directory.
[   42.563751] init: Starting service 'exec 0 (/system/bin/tzdatacheck)'...
[   42.564605] init: cannot execve('/system/bin/tzdatacheck'): I/O error
[   42.564971] init: Service 'exec 0 (/system/bin/tzdatacheck)' (pid 224) exited with status 127
[   42.590393] SELinux:  Context u:object_r:cpk_efs_file:s0 is not valid (left unmapped).
[   42.595306] EXT4-fs (loop1): previous I/O error to superblock detected
[   42.595489] loop: Write error at byte offset 0, length 4096.
[   42.595550] Buffer I/O error on device loop1, logical block 0
[   42.595703] lost page write due to I/O error on loop1
[   42.595794] EXT4-fs error (device loop1): ext4_find_entry:941: inode #486: comm init: reading directory lblock 0
[   42.600250] init: Starting service 'sysinit'...
[   42.600952] init: (Loading properties from /data/local.prop took 0.00s.)
[   42.601074] init: cannot execve('/system/bin/sysinit'): I/O error
[   42.601287] init: Starting service 'logd'...
[   42.602020] init: Service 'sysinit' (pid 225) exited with status 127
[   42.602508] init: Starting service 'logd-reinit'...
[   42.603240] init: cannot execve('/system/bin/logd'): I/O error
[   42.603820] init: Service 'logd-reinit' (pid 228) exited with status 127
[   42.604553] init: cannot execve('/system/bin/logd'): I/O error
[   42.605010] init: Service 'logd' (pid 227) exited with status 127
[   42.605102] init: Service 'logd' (pid 227) killing any children in process group

Attaching full last_kmsg.txt file for full reference. last_kmsg.txt

[relan]

To be honest, I have no idea what is Dual Boot Patcher. How exactly does it use fuse-exfat?

Could you get the log from fuse-exfat? It prints errors into syslog, but it seems that Android does not have it. Hint: make logging functions in libexfat/log.c use __android_log_vprint.

[webmaster33]

Here you can read about Dual Boot Patcher: https://dbp.noobdev.io It makes possible to install multiple ROMs onto the same Android phone.

One solution is to flash the ROM external sdcard. Since my sdcard is 64GB, it should use exFAT. Well, if it is formatted to exFAT, then gives the errors above. However, if I format to FAT32, then boots without problems. This is why I thought, that exFAT driver may cause the problem.

Personally I don't develop in C++, so I don't know how to implement your suggestion.

But if I get exact code, I will implement into the Dual Boot Patcher code and compile it.

I know that I should place the debugging code into mount_fstab.cpp, under method mount_fstab(): https://github.com/chenxiaolong/DualBootPatcher/blob/e3366791f3ff06aa46a26f354e298fe43fc99ecb/mbtool/mount_fstab.cpp

[webmaster33]

The following issue is discussing the problem: https://github.com/chenxiaolong/DualBootPatcher/issues/375

[relan]

Here you can read about Dual Boot Patcher: https://dbp.noobdev.io

There's zero info about its internals.

But if I get exact code, I will implement into the Dual Boot Patcher code and compile it.

Good time for you to start learning C. :) In libexfat/log.c:

• replace vsyslog(LOG_ERR, format, aq); with __android_log_vprint(ANDROID_LOG_ERROR, "exfat", fmt, aq);
• add #include <android/log.h>

[webmaster33]

@relan: I saw the android branch. Is it finished? Will it be merged into next release?

[webmaster33]

The external 64Gb sdcard now was formatted using TWRP v3.0.2 to exFAT.

Attaching logs about kernel booting process.

I see the following in /multiboot/sdcard/logs/kmsg.log:

<3>[    9.297454] mblog: 1 fstab entries for the external SD
<3>[    9.297576] mblog: [Attempt 1/10] Finding and mounting external SD
<3>[    9.297790] mblog: Matching devices against pattern: /devices/platform/msm_sdcc.2/mmc_host/mmc2*
<3>[    9.301574] mblog: /default.prop contains fuse-exfat override: false
<6>[    9.312347] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
<3>[    9.391937] mblog: Using fuse-exfat: 0
<3>[    9.392089] mblog: Failed to mount /dev/block/mmcblk1p1 (exfat) at /raw/extsd: No such device
<3>[    9.395996] mblog: /default.prop contains fuse-exfat override: false
<3>[    9.482238] FAT-fs (mmcblk1): invalid media value (0x01)
<6>[    9.482330] FAT-fs (mmcblk1): Can't find a valid FAT filesystem
<3>[    9.482757] mblog: Failed to mount /dev/block/mmcblk1 (vfat) at /raw/extsd: Invalid argument
<6>[   10.312316] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on.
<3>[   10.483032] mblog: [Attempt 2/10] Finding and mounting external SD
<3>[   10.483215] mblog: Matching devices against pattern: /devices/platform/msm_sdcc.2/mmc_host/mmc2*
<3>[   10.486938] mblog: /default.prop contains fuse-exfat override: false
<3>[   10.577423] mblog: Using fuse-exfat: 0
<3>[   10.577606] mblog: Failed to mount /dev/block/mmcblk1p1 (exfat) at /raw/extsd: No such device
<3>[   10.581420] mblog: /default.prop contains fuse-exfat override: false
<3>[   10.667724] FAT-fs (mmcblk1): invalid media value (0x01)
<6>[   10.667816] FAT-fs (mmcblk1): Can't find a valid FAT filesystem
<3>[   10.668151] mblog: Failed to mount /dev/block/mmcblk1 (vfat) at /raw/extsd: Invalid argument
<6>[   10.912353] max77693-muic max77693-muic: func:max77693_muic_usb_detect info->muic_data->sw_path:0
<6>[   11.312316] synaptics_rmi4_i2c 3-0020: synaptics_init_power_on: until lcd does not turn on. 

Does it help you? kmsg.log.txt 20170328.084614.tar.gz

[relan]

I saw the android branch. Is it finished?

It's a work-in-progress.

Will it be merged into next release?

It depends. I need to test those changes before I merge them.

Does it help you?

I'm afraid no. I don't see any error messages from fuse-exfat here.

[relan]

No new info for over a year, closing.

[webmaster33]

I will reopen the issue if I will have time to test exFAT again.