Betatester: Do you have dual boot with Android? I think the issue happens only in this case.
Can you check /proc/cmdline if you have disk=FOLDER=/dev/CE_STORAGE.
Yes, dual boot.
Created full system and Kodi backup to external USB with CE backup tool.
Performed soft reset. System restarted and went through its soft reset cycle. System restarted again and I was greeted with the red Welcome to CoreELEC screen. My media were untouched.
Restored from backup, rebooted and found my previous configuration restored.
Performed hard reset. System restarted and went through its hard reset cycle. System restarted again and I was greeted with the red Welcome to CoreELEC screen. My media were gone.
Restored from backup, rebooted and found my previous configuration and media restored.
System: NexBox A95X-B7N 1/8 running CoreELEC-ng 9.2.4.2 stable in dual boot with Android 7.1 (Nougat) from eMMC.
Unable to replicate following error during 5 consecutive attempts:
Conclusion: CoreELEC-ng 9.2.4.2 Stable works as intended on a NexBox A95X-B7N (S905X) 1/8 when performing a hard and/or soft reset via the CoreELEC configuration addon.
Iām using single boot configuration and installed CE-ng via ceemmc -x on top of Android 7.1 rom on A95X 2/16 box.
The /proc/cmdline generated for booting from eMMC used disk=FOLDER=/dev/CE_STORAGE vs the one for booting from USB / SD disk=LABEL=STORAGE ( there is special case in the cfgload script for this )
The script that perform soft/hard reset does not handle the FOLDER case so it is just restarting the box without performing the reset operation as it does not find the reset target.
Check with file explorer if you have CE_STORAGE mounted. If yes, unmount. See if that makes a difference.
Anyway, the fix is send: https://github.com/CoreELEC/CoreELEC/pull/263
Tested on Beelink GT King Pro.
1 Like
@vpeter, just tested a local build with your fix on my A95X box and confirm fixing the issue.
Thank you!
1 Like
I presume this issue only affects some boxes then?
From what i know about dual boot installation it is done in same way on all boxes. Thatās why I canāt understand why it would work on some boxes and not on others.
When folder is used for storage it is subfolder from Android data partition. In this case partition canāt be recreated but files must be manually removed. And this case was not covered in factory reset. This is for hard reset: soft reset was not affected.
Thatās what I am trying to figure out myself. Right now I am leaning towards file permissions.
Then try this:
mkdir mount_storage1
mkdir mount_storage2
mount /dev/CE_STORAGE mount_storage1
mount /dev/data mount_storage2
You should see same content inside like
drwx------ 2 root root 4096 May 25 17:13 adb
drwxrwxr-x 2 1000 1000 4096 May 26 12:06 anr
drwxrwx--x 6 1000 1000 4096 May 26 12:06 app
drwx------ 2 root root 4096 May 25 17:13 app-asec
drwxrwx--x 2 1000 1000 4096 May 25 17:13 app-ephemeral
drwxrwx--x 2 1000 1000 4096 May 25 17:13 app-lib
drwxrwx--x 2 1000 1000 4096 May 25 17:13 app-private
drwx------ 6 1000 1000 4096 Oct 3 15:40 backup
drwxr-xr-x 2 2000 2000 4096 May 25 17:13 bootchart
drwxrwx--- 5 1000 2001 4096 May 25 17:13 cache
drwxr-xr-x 19 root root 4096 Oct 18 16:16 coreelec_storage
drwxrwx--x 3 root root 4096 May 25 17:13 dalvik-cache
drwxrwx--x 87 1000 1000 4096 May 25 17:14 data
drwxrwx--- 3 1019 1019 4096 May 25 17:13 drm
drwxrwx--x 2 1000 1000 4096 May 25 17:13 droidota
drwxr-x--x 4 root root 4096 May 25 17:14 local
drwxrwx--x 3 1007 1007 4096 May 25 17:13 log
drwxrwx--- 2 root root 16384 May 25 17:13 lost+found
drwxrwx--- 4 1023 1023 4096 May 25 17:13 media
drwxrwx--- 2 1031 1031 4096 May 25 17:13 mediadrm
drwxrwx--t 42 1000 9998 4096 May 25 17:13 misc
drwxrwx--t 3 1000 9998 4096 May 25 17:13 misc_ce
drwxrwx--t 3 1000 9998 4096 May 25 17:13 misc_de
drwxrwx--- 3 1027 1027 4096 May 25 17:13 nfc
drwxrwx--x 2 root root 4096 May 25 17:13 ota
drwxrwx--- 2 1000 2001 4096 May 25 17:13 ota_package
drwx------ 2 root root 4096 Oct 3 15:40 property
drwxrwx--x 2 1000 1000 4096 May 25 17:13 resource-cache
drwx------ 2 1000 1000 4096 May 25 17:13 ss
drwxrwxr-x 19 1000 1000 4096 Oct 3 15:40 system
drwxrwx--- 3 1000 1000 4096 May 25 17:13 system_ce
drwxrwx--- 3 1000 1000 4096 May 25 17:13 system_de
drwxrwx--x 2 1000 1000 4096 May 25 17:13 tombstones
drwx--x--x 2 1000 1000 4096 May 25 17:13 user
drwx--x--x 3 1000 1000 4096 May 25 17:13 user_de
drwxrwx--x 6 root root 4096 May 25 17:13 vendor
drwxrwx--x 3 root root 4096 May 25 17:13 vendor_ce
drwxrwx--x 3 root root 4096 May 25 17:13 vendor_de
and the most important is folder coreelec_storage which is mounted to /storage.
I try this from where? Android Terminal, Secure Shell? Can you please elaborate? Thank you.
Model: Mecool M8S Plus DVB
CoreELEC-Amlogic-ng.arm-9.2-nightly_20201019
GXL p231
Is running with black screen and with this error in dmesg:
failed to allocate memory for node linux,meson-fb, size:8 MB
dmesg.txt (71.9 KB)
I keep having network related problems with playback, particularly easy to reproduce using the music playerās Party mode. Enable party mode and skip to the next song until the player goes all wonky and refuses to play anything. It just keeps scrolling through the list until I use the X key to stop it.
This is what repeats in the log in that situation:
2020-10-23 20:43:20.330 T:3918496640 WARNING: PAPlayer::QueueNextFileEx - Failed to create the decoder
2020-10-23 20:43:20.376 T:3578037120 ERROR: Open - Unhandled exception
2020-10-23 20:43:20.376 T:3578037120 ERROR: Open - Error opening nfs://192.168.0.75/volume2/Music/Faith No More/The Real Thing/06 The Real Thing.ogg
2020-10-23 20:43:20.376 T:3578037120 ERROR: Init: Error opening file musicdb://songs/11973.ogg
2020-10-23 20:43:20.376 T:3578037120 ERROR: CAudioDecoder: Unable to Init Codec while loading file nfs://192.168.0.75/volume2/Music/Faith No More/The Real Thing/06 The Real Thing.ogg
The NAS is online and no problems accessing it. I switched to NFS shares today to test, but itās as bad as SMB.
Is there anything I could do to make it work better? I have a big library and it would be nice to be able to skip songs as needed. The same issues are probably causing problems with playback of videos over the network, Iāve reported those in this thread a few times I think.
Known dtb issue. S902 dtbās are faulty.
I got a debug log here, couldnāt use pastebin as the file is too big.
https://drive.google.com/file/d/1HNPX0Xc_2VRMBDi7Kplmf_TKtoM3sRfV/view?usp=sharing
20201011 was latest build that wifi was working for me. I have EVOLVEO MultiMedia Box C4, any suggestions? tested all builds till 20201023 and that 1011 is latest build with wifi for me 
Please upload dmesg log for last working and not working builds
And also output of command:
udevadm info /sys/bus/sdio/devices/* | paste
20201011 -
logs - http://ix.io/2BWt
udevadm - http://ix.io/2cNl
20201024 -
logs - http://ix.io/2BWz
udevadm - http://ix.io/2cdd
Moderator note: issue identified and fixed with https://github.com/CoreELEC/CoreELEC/commit/b61c70bb471b080f1747fc19abc03f992522b02e
Did latest -NG nightly fail to build?
All good here.