Dreambox One Boot Problem

  • My dreambox One has stopped booting. I tried installing image dreambox-image-dreamone-20200724.tar.xz

    The rescue browser http://dreambox.home works - clicked booting. After some time - the tv only shows the dreambox boot logo.

    I can get internet connection to DCC. The telnet command 'systemctl start enigma2' log shows :-


    "Dependency failed for enigma2
    enigma2.service: Job enigma2.service/start failed with result 'dependency'"


    Any solution possible please ? Regards.


    Meine Dreambox One hat aufgehört zu booten. Ich habe versucht, image dreambox-image-dreamone-20200724.tar.xz zu installieren.

    Der Rettungsbrowser http: //dreambox.home funktioniert - geklicktes Booten. Nach einiger Zeit zeigt der Fernseher nur noch das Dreambox-Boot-Logo.

    Ich kann eine Internetverbindung zu DCC bekommen. Das Protokoll des Telnet-Befehls 'systemctl start enigma2' zeigt: -

    "Abhängigkeit für enigma2

    fehlgeschlagen enigma2.service: Job enigma2.service / start fehlgeschlagen mit Ergebnis 'Abhängigkeit' "


    Irgendeine mögliche Lösung bitte? Grüße.

  • Just simply put it back into rescue mode and do an online flash instead.

    Also remember to uncheck the boxes for restoring setting and uncheck backup settings

    Everything in life that's any fun is either immoral, illegal or fattening

  • Just simply put it back into rescue mode and do an online flash instead.

    Also remember to uncheck the boxes for restoring setting and uncheck backup settings

    I did that. Still no boot up. Now I do not get internet connection to DCC.

    Einmal editiert, zuletzt von pcd ()

  • Boot log

    I get following output from 'journalctl -xe >> /tmp/output.log 2>&1 &'.

    Can an expert please find what the problem is - and if it can be solved ?


    Jan 14 12:46:38 dreambox systemd[1]: Time has been changed

    -- Subject: Time change

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- The system clock has been changed to REALTIME microseconds after January 1st, 1970.

    Jan 14 12:46:38 dreambox systemd[1]: apt-daily.timer: Adding 5h 44min 28.510806s random time.

    Jan 14 12:46:38 dreambox systemd[1]: Starting Daily apt activities...

    -- Subject: Unit apt-daily.service has begun start-up

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit apt-daily.service has begun starting up.

    Jan 14 12:46:38 dreambox systemd[451]: apt-daily.service: Failed at step EXEC spawning /usr/lib/apt/apt.systemd.daily: Permission denied

    -- Subject: Process /usr/lib/apt/apt.systemd.daily could not be executed

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- The process /usr/lib/apt/apt.systemd.daily could not be executed and failed.

    --

    -- The error number returned by this process is 13.

    Jan 14 12:46:38 dreambox systemd[1]: apt-daily.service: Main process exited, code=exited, status=203/EXEC

    Jan 14 12:46:38 dreambox systemd[1]: Failed to start Daily apt activities.

    -- Subject: Unit apt-daily.service has failed

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit apt-daily.service has failed.

    --

    -- The result is failed.

    Jan 14 12:46:38 dreambox systemd[1]: apt-daily.timer: Adding 4h 31min 45.236413s random time.

    Jan 14 12:46:38 dreambox systemd[1]: apt-daily.service: Unit entered failed state.

    Jan 14 12:46:38 dreambox systemd[1]: apt-daily.timer: Adding 11h 41min 19.155898s random time.

    Jan 14 12:46:38 dreambox systemd[1]: apt-daily.service: Failed with result 'exit-code'.

    Jan 14 12:46:38 dreambox avahi-daemon[382]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::209:34ff:fe4a:ef89.

    Jan 14 12:46:38 dreambox avahi-daemon[382]: New relevant interface eth0.IPv6 for mDNS.

    Jan 14 12:46:38 dreambox avahi-daemon[382]: Registering new address record for fe80::209:34ff:fe4a:ef89 on eth0.*.

    Jan 14 12:46:39 dreambox dreamlpd[447]: Printer not found

    Jan 14 12:46:39 dreambox dreamlpd[447]: exiting program

    Jan 14 12:46:39 dreambox systemd[1]: dreamlpd.service: Service hold-off time over, scheduling restart.

    Jan 14 12:46:39 dreambox systemd[1]: Stopped LPD.

    -- Subject: Unit dreamlpd.service has finished shutting down

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit dreamlpd.service has finished shutting down.

    Jan 14 12:46:39 dreambox systemd[1]: Started LPD.

    -- Subject: Unit dreamlpd.service has finished start-up

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit dreamlpd.service has finished starting up.

    --

    -- The start-up result is done.

    Jan 14 12:46:39 dreambox dreamlpd[457]: starting ...

    Jan 14 12:46:39 dreambox connmand.real[373]: eth0 {add} route 212.227.81.55 gw 192.168.1.254 scope 0 <UNIVERSE>

    Jan 14 12:46:40 dreambox dreamlpd[457]: Printer not found

    Jan 14 12:46:40 dreambox dreamlpd[457]: exiting program

    Jan 14 12:46:40 dreambox systemd[1]: dreamlpd.service: Service hold-off time over, scheduling restart.

    Jan 14 12:46:40 dreambox systemd[1]: Stopped LPD.

    -- Subject: Unit dreamlpd.service has finished shutting down

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit dreamlpd.service has finished shutting down.

    Jan 14 12:46:40 dreambox systemd[1]: dreamlpd.service: Start request repeated too quickly.

    Jan 14 12:46:40 dreambox systemd[1]: Failed to start LPD.

    -- Subject: Unit dreamlpd.service has failed

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit dreamlpd.service has failed.

    --

    -- The result is failed.

    Jan 14 12:46:40 dreambox systemd[1]: dreamlpd.service: Unit entered failed state.

    Jan 14 12:46:40 dreambox systemd[1]: dreamlpd.service: Failed with result 'start-limit-hit'.

    Jan 14 12:47:01 dreambox nmbd[436]: [2021/01/14 12:47:01.990686, 0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)

    Jan 14 12:47:01 dreambox nmbd[436]: *****

    Jan 14 12:47:01 dreambox nmbd[436]:

    Jan 14 12:47:01 dreambox nmbd[436]: Samba name server DREAMBOX is now a local master browser for workgroup DREAMBOX on subnet 192.168.1.99

    Jan 14 12:47:01 dreambox nmbd[436]:

    Jan 14 12:47:01 dreambox nmbd[436]: *****

    Jan 14 12:47:10 dreambox connmand.real[373]: eth0 {del} route 212.227.81.55 gw 192.168.1.254 scope 0 <UNIVERSE>

    Jan 14 12:47:11 dreambox connmand.real[373]: ntp: time slew -0.119534 s

    Jan 14 12:48:04 dreambox systemd[1]: dev-disk-by\x2duuid-5F7E\x2dD106.device: Job dev-disk-by\x2duuid-5F7E\x2dD106.device/start timed out.

    Jan 14 12:48:04 dreambox systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-5F7E\x2dD106.device.

    -- Subject: Unit dev-disk-by\x2duuid-5F7E\x2dD106.device has failed

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit dev-disk-by\x2duuid-5F7E\x2dD106.device has failed.

    --

    -- The result is timeout.

    Jan 14 12:48:04 dreambox systemd[1]: Dependency failed for /media/hdd.

    -- Subject: Unit media-hdd.mount has failed

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit media-hdd.mount has failed.

    --

    -- The result is dependency.

    Jan 14 12:48:04 dreambox systemd[1]: media-hdd.mount: Job media-hdd.mount/start failed with result 'dependency'.

    Jan 14 12:48:04 dreambox systemd[1]: Startup finished in 1.569s (kernel) + 4min 57.996s (userspace) = 4min 59.566s.

    -- Subject: System start-up is now complete

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- All system services necessary queued for starting at boot have been

    -- successfully started. Note that this does not mean that the machine is

    -- now idle as services might still be busy with completing start-up.

    --

    -- Kernel start-up required 1569661 microseconds.

    --

    -- Initial RAM disk start-up required INITRD_USEC microseconds.

    --

    -- Userspace start-up required 297996985 microseconds.

    Jan 14 12:48:04 dreambox systemd[1]: dev-disk-by\x2duuid-5F7E\x2dD106.device: Job dev-disk-by\x2duuid-5F7E\x2dD106.device/start failed with result 'timeout'.

    Jan 14 12:55:36 dreambox systemd[1]: Created slice system-busybox\x2dtelnetd.slice.

    -- Subject: Unit system-busybox\x2dtelnetd.slice has finished start-up

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit system-busybox\x2dtelnetd.slice has finished starting up.

    --

    -- The start-up result is done.

    Jan 14 12:55:36 dreambox systemd[1]: Started 192.168.1.81:61979.

    -- Subject: Unit busybox-telnetd@0-192.168.1.99:23-192.168.1.81:61979.service has finished start-up

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit busybox-telnetd@0-192.168.1.99:23-192.168.1.81:61979.service has finished starting up.

    --

    -- The start-up result is done.

    Jan 14 12:55:36 dreambox systemd[1]: Created slice system-vsftpd.slice.

    -- Subject: Unit system-vsftpd.slice has finished start-up

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit system-vsftpd.slice has finished starting up.

    --

    -- The start-up result is done.

    Jan 14 12:55:36 dreambox systemd[1]: Started 192.168.1.81:61980.

    -- Subject: Unit vsftpd@0-192.168.1.99:21-192.168.1.81:61980.service has finished start-up

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit vsftpd@0-192.168.1.99:21-192.168.1.81:61980.service has finished starting up.

    --

    -- The start-up result is done.

    Jan 14 12:55:36 dreambox login[494]: ROOT LOGIN on '/dev/pts/0' from '[::ffff:192.168.1.81]:61979'

    Jan 14 12:55:36 dreambox systemd[1]: Started 192.168.1.81:61982.

    -- Subject: Unit vsftpd@1-192.168.1.99:21-192.168.1.81:61982.service has finished start-up

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit vsftpd@1-192.168.1.99:21-192.168.1.81:61982.service has finished starting up.

    --

    -- The start-up result is done.

    Jan 14 12:57:06 dreambox systemd[1]: dev-disk-by\x2duuid-5F7E\x2dD106.device: Job dev-disk-by\x2duuid-5F7E\x2dD106.device/start timed out.

    Jan 14 12:57:06 dreambox systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-5F7E\x2dD106.device.

    -- Subject: Unit dev-disk-by\x2duuid-5F7E\x2dD106.device has failed

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit dev-disk-by\x2duuid-5F7E\x2dD106.device has failed.

    --

    -- The result is timeout.

    Jan 14 12:57:06 dreambox systemd[1]: Dependency failed for /media/hdd.

    -- Subject: Unit media-hdd.mount has failed

    -- Defined-By: systemd

    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel

    --

    -- Unit media-hdd.mount has failed.

    --

    -- The result is dependency.

    Jan 14 12:57:06 dreambox systemd[1]: media-hdd.mount: Job media-hdd.mount/start failed with result 'dependency'.

    Jan 14 12:57:06 dreambox systemd[1]: dev-disk-by\x2duuid-5F7E\x2dD106.device: Job dev-disk-by\x2duuid-5F7E\x2dD106.device/start failed with result 'timeout'.


    Regards, pcd.

  • Of cause you should be able and flash a DMM image.

    As long as you get the box back into Rescue Mode?


    If so when you are doing the new flash, and i strongly recommend "Online Rescue" Make sure you have uncheck the boxes for Backup and restore settings.

    This is very important special if you have try one of the public OE-A builds for Dreambox One. Otherwise you mix the both images and cant boot.

    Everything in life that's any fun is either immoral, illegal or fattening

  • Of cause you should be able and flash a DMM image.

    As long as you get the box back into Rescue Mode?


    If so when you are doing the new flash, and i strongly recommend "Online Rescue" Make sure you have uncheck the boxes for Backup and restore settings.

    This is very important special if you have try one of the public OE-A builds for Dreambox One. Otherwise you mix the both images and cant boot.

    I did that. Now only blue skin and no connection to DCC.

    The rescue output is :-

    [*] Remounting '/dev/dreambox-data' to '/data'

    [*] Downloading 'http://dreamboxupdate.com/download/recovery/one/release/recovery.sig'

    % Total % Received % Xferd Average Speed Time Time Time Current

    Dload Upload Total Spent Left Speed


    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0

    100 438 100 438 0 0 4522 0 --:--:-- --:--:-- --:--:-- 8111

    [*] Copying 'recovery' from local storage

    [*] Verifying signature of 'recovery'

    gpgv: Signature made Wed May 22 22:30:55 2019 UTC

    gpgv: using RSA key B80355A90FEB3DE6938E7B700A963A18CBA77E11

    gpgv: Good signature from "Dreambox One Recovery <one@recovery.dreambox.de>"

    [*] Verifying signature of '/data/.recovery/recovery'

    [*] Unmounting '/data'

    [*] Running './recovery'

    [*] Options '-v'

    [*] Mounting '/dev/dreambox-data' to '/data'

    [*] Downloading 'http://dreamboxupdate.com/download/recovery/one/release/dreambox-image-one.tar.xz.sig'

    % Total % Received % Xferd Average Speed Time Time Time Current

    Dload Upload Total Spent Left Speed


    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0

    100 438 100 438 0 0 3783 0 --:--:-- --:--:-- --:--:-- 8588

    [*] Copying 'dreambox-image-one.tar.xz' from local storage

    [*] Verifying signature of 'dreambox-image-one.tar.xz'

    gpgv: Signature made Fri Nov 6 16:58:14 2020 UTC

    gpgv: using RSA key B80355A90FEB3DE6938E7B700A963A18CBA77E11

    gpgv: Good signature from "Dreambox One Recovery <one@recovery.dreambox.de>"

    [*] Creating ext4 filesystem 'dreambox-rootfs' on /dev/dreambox-rootfs

    mke2fs 1.43.4 (31-Jan-2017)

    Discarding device blocks: 4096/1048576 528384/1048576 done

    Creating filesystem with 1048576 4k blocks and 262144 inodes

    Filesystem UUID: 975b9d32-043a-4477-aac1-e9bdbd60b373

    Superblock backups stored on blocks:

    32768, 98304, 163840, 229376, 294912, 819200, 884736


    Allocating group tables: 0/32 done

    Writing inode tables: 0/32 done

    Creating journal (16384 blocks): done

    Writing superblocks and filesystem accounting information: 0/32 done


    [*] Mounting '/dev/dreambox-rootfs' to '/mnt'

    [*] Extracting 'dreambox-image-one.tar.xz' to '/mnt'

    [*] Mounting '/dev' to '/mnt/dev'

    [*] Mounting '/proc' to '/mnt/proc'

    [*] Mounting '/run' to '/mnt/run'

    [*] Mounting '/sys' to '/mnt/sys'

    [*] Mounting '/tmp' to '/mnt/tmp'

    Image Name: autoexec

    Created: Thu Jan 14 17:53:19 2021

    Image Type: AArch64 Linux Script (uncompressed)

    Data Size: 621 Bytes = 0.61 kB = 0.00 MB

    Load Address: 00000000

    Entry Point: 00000000

    Contents:

    Image 0: 613 Bytes = 0.60 kB = 0.00 MB

    [*] Creating boot image

    [*] Writing bootblob.bin to /dev/boot

    162+1 records in

    162+1 records out

    10670080 bytes (10.2MB) copied, 0.224876 seconds, 45.3MB/s

    [*] Unmounting '/mnt/dev'

    [*] Unmounting '/mnt/proc'

    [*] Unmounting '/mnt/run'

    [*] Unmounting '/mnt/sys'

    [*] Unmounting '/mnt/tmp'

    [*] Unmounting '/mnt'

    [*] Verifying signature of '/data/.recovery/dreambox-image-one.tar.xz'

    [*] Unmounting '/data'

    [*] Finished successfully. You may reboot now.

    [*] Initiating reboot

  • I am in no way an expert but looks like the flash when through correct and you now have booted into the DM Image?

    To connect with ftp ot dcc you must first create a password. Menu>>Setup>>System>>password>>Enter Password.


    Now create your own password and save. After us that password to connect with dcc.

    Username is as always root

    Everything in life that's any fun is either immoral, illegal or fattening

  • I am in no way an expert but looks like the flash when through correct and you now have booted into the DM Image?

    To connect with ftp ot dcc you must first create a password. Menu>>Setup>>System>>password>>Enter Password.


    Now create your own password and save. After us that password to connect with dcc.

    Username is as always root

    The receiver did not boot. Only blue screen on the TV. I do not see Menu.

  • Lets see


    When you power up the box you go straight to this blue screen? Or does the dreambox logo show up first?

    (1) When I do online restore - on box power up no change in tv blue screen (hdmi no signal).

    (2) When I flash a backup DMM image - on box power up the dreambox logo shows but nothing more happens.

  • Have you made any progress on this issue??


    Maybe give a more detailed description, And maybe see if you can post a bootlog??

    Everything in life that's any fun is either immoral, illegal or fattening

  • Have you made any progress on this issue??


    Maybe give a more detailed description, And maybe see if you can post a bootlog??

    Thank you for your interest.

    To summarise - I got the DreamOne from Germany. It worked ok for many months - then it stopped booting. The current situation is :-

    (1) If I flash a DM image - blue screen - no internet.

    (2) If I flash a DM image backup - the dream logo shows and no more. But internet

    connection works. If I run enigma2 with telnet - the image starts and works normally.

    I can use the receiver but have to start enigma2 by telnet after every restart. The

    Genuinedreambox plugin fails. I attach the enigma2 log which shows the Genuinedreambox error.


    The supplier wants the receiver back - but with covid lockdown it not possible

    for me to go to the post office. So I will be very grateful if someone can suggest a solution to the enigma2 start issue.


    Regards, pcd.