X96 Max+ and ceemmc -x failure

Hello, I reinstall the stable version and now I have this: https://paste.debian.net/1141156/

It does not finish the process, I need to Ctrl+C to stop.

Ask me if need any info.

Regards.

What device you are using? It can not copy data to internal emmc as it’s read only.
And when you upgrade CE by tar file when booted from eMMC? Is the update working?

The information I found about this error:

The messages to me suggest either
a) a faulty piece of hardware
or
b) a low-level driver at fault
or
c) a USB disconnect caused by the HDD itself ...

So I guess it’s answer a).

@boot2k3 Can it be the eMMC sdio speed?

Also please remember your devices aren’t official supported:

Today downloaded and installed stable version 9.2.2 on Android box H96 MAX X3 4/64 1Gbit Lan (S905X3)

Unfortunately, it works only from the card and can not install on eMMC, android do not need, switching from the box Tanix TX3 mini where Coreelec works great, but the box is slower and can not handle everything.

And one more small thing, it seems to me as if the driver jammed even if I uploaded the correct rc_config, so the reaction is quite slow.

I attach the log here:

/$ ls -l /dev/ | paste
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100 15526    0     0  100 15526      0  12410  0:00:01  0:00:01 --:--:-- 12410100 15526    0     0  100 15526      0   6894  0:00:02  0:00:02 --:--:--  6894100 15544  100    18  100 15526      7   6168  0:00:02  0:00:02 --:--:--  6178
http://ix.io/2ixr
/$ ls -l /sys/block/
total 0
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx    1 root     root             0 Jan  1  2015 mmcblk0 -> ../devices/platform/ffe07000.emmc/mmc_host/emmc/emmc:0001/block/mmcblk0
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 mmcblk0boot0 -> ../devices/platform/ffe07000.emmc/mmc_host/emmc/emmc:0001/block/mmcblk0/mmcblk0boot0
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 mmcblk0boot1 -> ../devices/platform/ffe07000.emmc/mmc_host/emmc/emmc:0001/block/mmcblk0/mmcblk0boot1
lrwxrwxrwx    1 root     root             0 Apr 18 16:06 mmcblk0rpmb -> ../devices/platform/ffe07000.emmc/mmc_host/emmc/emmc:0001/block/mmcblk0/mmcblk0rpmb
lrwxrwxrwx    1 root     root             0 Jan  1  2015 mmcblk1 -> ../devices/platform/ffe05000.sd/mmc_host/sd/sd:59b4/block/mmcblk1
/$ mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=1958708k,nr_inodes=489677,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/mmcblk1p1 on /flash type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/loop0 on / type squashfs (ro,relatime)
/dev/mmcblk1p2 on /storage type ext4 (rw,noatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/debug type cgroup (rw,nosuid,nodev,noexec,relatime,debug)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /var type tmpfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
/$ dmesg|paste
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100 97578    0     0  100 97578      0  77875  0:00:01  0:00:01 --:--:-- 77937100 97578    0     0  100 97578      0  43291  0:00:02  0:00:02 --:--:-- 43291100 97596  100    18  100 97578      6  37257  0:00:03  0:00:02  0:00:01 37250100 97596  100    18  100 97578      6  37243  0:00:03  0:00:02  0:00:01 37250
http://ix.io/2ixw

and what is the error? any log? run ceemmc -vx and post all console output.

And it’s recomended to install first in dual boot mode if something is not working. Then you should be still able to remove it from internal. On single install it’s only way back by burncardmaker or USB burn tool.

Don’t know if slow emmc could be the reason… but it possible to try this dtb file and check
But it’s possible that need to wait some more time…
I remember long time syncthing when I had slow usb stick

Thanks Portisch,

My device is X96Max (sm1_s905x3_2g.dtb). When I upgrade by tar, it boot from USB. I test to power off the device and boot without the USB, it doesn’t boot, it stop in the X96Max+ logo (I have no Android, I had install to internall weeks ago but in a upgrade it doesn’t boot. So am again in USB boot).

The last upgrade work well.

Is there any test I could perform to confirm that my hardware is broken? something like badblocks?

Thanks for your great help.

Best regards.

Currently I have no idea, only a UART log of the bootloader will show what is going wrong.
I guess this X96 Max+ device is really not supported. Nobody of us do have such device so we can not tell you what is wrong.

Recover your device by an vendor Android ROM (image) and run CE from uSD/USB.

Thanks Portisch for your help.

I recover the device from Android image, and it run perfect installed in internal.

Then I installed stable CE and install to internal again: https://paste.debian.net/1141279/

It stay lot of time in 95% in this stage:

Copy all data from ‘/flash’ to ‘/media/CE_FLASH’
212.83M 100% 1017.96kB/s 0:03:24 (xfr#30, to-chk=0/32)

The I remove the USB stick and reboot, but it doesn’t boot, there es no X96max logo (yesterday was there).

I boot from USB and it start OK. Try to install to internal again: https://paste.debian.net/1141281/

Actually I have running with the USB stick and it works well, but I prefer to get it in internal.

Hope someone could debug it with UART log, I don’t know how to take this logs.

Best regards.

For some reason your eMMC is remounted to read-only mode in the middle of using ceemc tool. This is first problem needs to be solved. But the reason is unknown.

Thanks vpeter.

But the first install to internall from Android works well.

Weeks ago I had the nightlys images in the internall working well, but after a upgrade (maybe a month ago) it doesn’t boot anymore and I need to boot from USB.

I want to try a nightly from one or two month ago just to test, but there are not in relkai.coreelec.org.

Regards.

But why u run ceemmc again? Just update system by common tar method. ceemmc renewal option is only for “recovery”.

Because it doesn’t work in the first try. I just want to test if the second try will install correctly.

I can’t help you further, it just does not work on your device because the CE_STORAGE partition is read only. I have no idea why and without hardware I have no idea how to solve it. The storage partition get created and formated but then it’s read only. :roll_eyes:

But you should be able to use dual boot, isn’t it? (Please recover the device first by an Android image)

Maybe you want do try it again - for sure it will fail again.

But please run:

dmesg | paste

right after ceemmc is finished.
Maybe there is some info why the mount changed from RW to RO.

1 Like

Thanks for your help.

There are lots of mmc lines between one dmesg and other.

Hope this will help.

Regards.

At least it shows the error:

[11061.546244@1] meson-mmc: >>>>>>>>>>>>>>scan command window>>>>>>>>>>>>>>>
[11061.546246@1] meson-mmc: >>cmd delay [ 0x0 -- 0x3 ] is ok
[11061.546248@1] meson-mmc: >>cmd delay [ 0x4 -- 0x7 ] is nok
[11061.546251@1] meson-mmc: >>cmd delay [ 0x8 -- 0x39 ] is ok
[11061.546252@1] meson-mmc: >>cmd delay [ 0x3a -- 0x3e ] is nok
[11061.546254@1] meson-mmc: >>cmd delay [ 0x3f ] is ok
[11061.546256@1] meson-mmc: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[11061.547417@0] meson-mmc: emmc: warning... data crc, vstat:0xa1ff2100, virqc:3fff
[11061.547423@0] meson-mmc: @ cmd 25 arg 17fcd0 with ffffffc044783388; stop 0, status 4
[11061.547426@0] meson-mmc: emmc: err: wait for irq service, bus_fsm:0x8
[11061.547432@0] meson-mmc: emmc: cmd 25, arg 0x17fcd0, operation is in [CE_STORAGE] disk!
[11061.547454@0] meson-mmc: meson_mmc_irq_thread_v3() 653: set 1st retry!
[11061.547457@0] meson-mmc: retry cmd 25 the 3-th time(s)
[11061.548027@1] emmc: req failed (CMD25): -84, retrying...
[11061.548846@0] meson-mmc: emmc: warning... data crc, vstat:0xa1ff2100, virqc:3fff
[11061.548852@0] meson-mmc: @ cmd 25 arg 17fcd0 with ffffffc044783388; stop 0, status 4
[11061.548855@0] meson-mmc: emmc: err: wait for irq service, bus_fsm:0x8
[11061.548860@0] meson-mmc: emmc: cmd 25, arg 0x17fcd0, operation is in [CE_STORAGE] disk!
[11061.548879@0] meson-mmc: retry cmd 25 the 2-th time(s)
[11061.549305@1] emmc: req failed (CMD25): -84, retrying...
[11061.550132@0] meson-mmc: emmc: warning... data crc, vstat:0xa1ff2100, virqc:3fff
[11061.550135@0] meson-mmc: @ cmd 25 arg 17fcd0 with ffffffc044783388; stop 0, status 4
[11061.550138@0] meson-mmc: emmc: err: wait for irq service, bus_fsm:0x8
[11061.550140@0] meson-mmc: emmc: cmd 25, arg 0x17fcd0, operation is in [CE_STORAGE] disk!
[11061.550148@0] meson-mmc: retry cmd 25 the 1-th time(s)
[11061.550572@1] emmc: req failed (CMD25): -84, retrying...
[11061.551396@0] meson-mmc: emmc: warning... data crc, vstat:0xa1ff2100, virqc:3fff
[11061.551400@0] meson-mmc: @ cmd 25 arg 17fcd0 with ffffffc044783388; stop 0, status 4
[11061.551402@0] meson-mmc: emmc: err: wait for irq service, bus_fsm:0x8
[11061.551404@0] meson-mmc: emmc: cmd 25, arg 0x17fcd0, operation is in [CE_STORAGE] disk!
[11061.551415@0] meson-mmc: Command retried failed line:675, cmd:25
[11061.551888@1] mmcblk0: response CRC error sending r/w cmd command, card status 0x900
[11061.554070@0] meson-mmc: emmc: warning... data crc, vstat:0xa1ff2100, virqc:3fff
[11061.554075@0] meson-mmc: @ cmd 25 arg 17ffd0 with ffffffc0447831a8; stop 0, status 4
[11061.554080@0] meson-mmc: emmc: err: wait for irq service, bus_fsm:0x8
[11061.554083@0] meson-mmc: emmc: cmd 25, arg 0x17ffd0, operation is in [CE_STORAGE] disk!
[11061.554100@0] meson-mmc: meson_mmc_irq_thread_v3() 653: set 1st retry!
[11061.554103@0] meson-mmc: retry cmd 25 the 3-th time(s)
[11061.554342@1] emmc: req failed (CMD25): -84, retrying...
[11061.554601@3] EXT4-fs error (device loop2): ext4_journal_check_start:56: Detected aborted journal
[11061.554605@3] EXT4-fs (loop2): Remounting filesystem read-only
[11061.554616@3] EXT4-fs (loop2): previous I/O error to superblock detected
[11061.555290@3] EXT4-fs (loop2): ext4_writepages: jbd2_start: 1024 pages, ino 525122; err -30

Can u please run this command:
dd if=/dev/dtb | gzip > /storage/downloads/dtb.img.gz

Then upload this dtb.img.gz.
What box you have excactly? H96 Max or H96 Max+?

Hello,

here is the file: dtb.img.gz (255.3 KB)

Un the back of the box:

VONTAR
ANDROID PLAYER
Model: X96Max
RAM: 2G
ROM: 16G

When the device boot, it show a logo that say “X96Max+”.

Kind regards.

So what you bought then? A Max or Max+? :face_with_hand_over_mouth:
Thx for the dtb, I will check it later.

1 Like

Also if it’s a Max device it looks like u use a wrong dtb! H96 Max is a S905x2 device H96 Max+ S905x3.
This may the reason ceemmc fails on your device.

What does Kodi - Settings - Systeminfo - Hardware - CPU say? S905x2 or S905x3?