Hello,
I looked through all topics but did not find anything applicable go me. Looks like a serious issue.
I use an original kickstarter purchased eBlocker family with lifetime update. It is online since I received it.
Banana Pi M2+
eBlockerOS Version 2.3.7
eBlocker Blockierlisten Version 2019-06-04-04-00-07
The eBlocker connects every night to the update server and does not update the filter list. I know, that it is because updates were discontinued.
I could not get it using free filter lists.
Do I need to update the OS using an image on a SD card? If so, will I loose my list of trusted websites and apps?
Or do I just need to wait until the new software is available and the device updates itself?
Does anyone else have similar issues?
Sounds odd. All eBlocker Lifetime users should get updates automatically.
Try to use the new license code:
Settings > License & Updates > Activate New License (at bottom of page)
Enter following license code:
FAMLFT-DEMO
Shutdown device (System > Reboot > Shutdown) and disconnect power for 1min. Then reconnect...
Ok, thank you for your effort.
I tried it as described, but without success.
It says, "No updates available" when I click on "check now" for manual updates.
Still the same versions, unfortunately.
eBlockerOS Version 2.3.7
eBlocker Blocker Lists Version 2019-06-04-04-00-07
I ran the diagnostics report and looked through the files.
I do not know much about linux, but I found this in the install-eblocker-updates.log
Hit https://apt.eblocker.com jessie InRelease
Hit https://apt.eblocker.com jessie InRelease
Hit https://apt.eblocker.com jessie InRelease
Hit https://apt.eblocker.com jessie/main armhf Packages
Get:1 https://apt.eblocker.com jessie/main Translation-en [162 B]
Hit https://apt.eblocker.com jessie/main armhf Packages
Get:2 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:3 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:4 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:5 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:6 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:7 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:8 https://apt.eblocker.com jessie/main Translation-en [162 B]
Hit https://apt.eblocker.com jessie/main armhf Packages
Get:9 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:10 https://apt.eblocker.com jessie/main Translation-en [162 B]
Ign https://apt.eblocker.com jessie/main Translation-en
Get:11 https://apt.eblocker.com jessie/main Translation-en [162 B]
Ign https://apt.eblocker.com jessie/main Translation-en
Get:12 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:13 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:14 https://apt.eblocker.com jessie/main Translation-en [162 B]
Get:15 https://apt.eblocker.com jessie/main Translation-en [162 B]
Ign https://apt.eblocker.com jessie/main Translation-en
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
It seems that a previous update was interrupted.
We had a repair skript for this (see below), but there is no guarantee that it works.
The safest thing would be to download the M2+ image from https://eblocker.org/en/eblockeros-download/ and write it to a micro SD card with Balena Etcher. If you take the M2+ board out of the case, you can plug in the SD card. If it is present, the M2+ will boot from this instead of the internal storage. You would lose your settings, however. You might be able to backup some of them in eBlocker's settings under System / Reset / Save Settings.
Alternatively, you could try the attached repair script:
- Unpack the ZIP file and copy the two included files to the root directory of a USB thumb drive (USB 2.0 / FAT16 or FAT32 formatted).
- Shut down the eBlocker, remove the power cable and plug in the USB thumb drive
- Attach the power cable
- eBlocker will boot up, run the repair skript and will shut down again
- If you are not sure, please wait at least 10 minutes
- Remove the power cable
- Remove the USB thumb drive
- Attach the power cable again.
Now you can try to update eBlocker again from the settings.
I ran the repair skript. It worked and the eBlocker it is up to date now.
Many thanks for your help.
Sorry to bump that thread.
I cannot update my orginal eBlocker with a Banana Pi M2+ on eBlockerOS Version 2.3.7. Trying to "run" the script "eblocker-repair" doesnt help. There is no update found.
Booting and running the Banana Pi M2+ from sdcard with the image "eBlocker-2.5.2-banana-pi-m2plus.img" works fine.
Is there a possibility to use the console to copy "eBlocker-2.5.2-banana-pi-m2plus.img" from an USB tumb drive to the emmc?
E.g. sudo dd if= xxx.img of=/dev/mmcblk1 bs=10MB
@peschwar I don't have the answer but a question for you: Have you tried running eOS 2.5.x on M2+ (via SD) and downloaded some GB (i.e. a game or such) or left it running over a loooong period?
Background: We are experiencing issues (as you might have read) with sudden halts and reboots if booted from eMMC (although it's probably not related to that)
So unless we have a stable eOS version - I guess it makes no sense to copy it to eMMC. But I'll check back with the developer team about your question.
THX!
If you want to be on the safe side
- Create an sdcard with armbian os (at least 16GB sdcard, or use usb stick)
- Boot the sdcard and log on armbian (with monitor/keyboard/mouse)
- go to the location, where you want to put the backup of the emmc -> cd ./home for example
- dd if=/dev/mmcblk2 | gzip > ./image_mmcblk2.gz status=progress
When this has finished, you are on the safe side. You can restore the system to this state whenever needed.
To restore the gz image just do this
gzip -dc image_mmcblk2.gz |sudo dd of=/dev/mmcblk2 status=progress
AND
as there is no console in eBlockerOS enabled, you can use the armbian os sdcard to dd the image as I wrote before to the internal emmc 🙂
Regards
Sven
@peschwar see here for the current state: https://eblocker.org/community/announcements/white-cube-eos-2-5-upgrade-development-status/#post-1768
As you are obviously a tech geek we‘d be happy if you‘d join the volunteers team for alpha testing. Just let me know and I open doors to the internal development forum for you...