DM920 lässt sich flashen geht aber trotzdem in Rescue Mode

Oli_K76 · 5. August 2020

Hallo Zusammen,

leider bootet meine DM920 seit heute in den Rescue Mode. Es hat sich bereits abgezeichnet weil z.B. EPG nicht mehr gespeichert wurde, etc.

Laut Log wird sie auch geflashed, meine Erachtens auch alles sauber auf die richtigen Partitionen, aber sie geht trotzdem wieder in den Rescue Mode. Habe auch verschiedene Images und normales Recovery versucht:

Code

[*] Remounting '/dev/mmcblk0p3' to '/data'
[*] Downloading 'http://dreamboxupdate.com/download/recovery/dm920/release/recovery.sig'
[*] Copying 'recovery' from local storage
[*] Verifying signature of 'recovery'
gpgv: Signature made Mon Dec 11 21:41:43 2017 UTC using RSA key ID B3C5B1A3
gpgv: Good signature from "Dreambox DM920 Recovery <dm920@recovery.dreambox.de>"
[*] Unmounting '/data'
[*] Running './recovery'
[*] Options '-v'
[*] Mounting '/dev/mmcblk0p3' to '/data'
[*] Downloading 'http://dreamboxupdate.com/download/recovery/dm920/release/dreambox-image-dm920.tar.xz.sig'
[*] Copying 'dreambox-image-dm920.tar.xz' from local storage
[*] Verifying signature of 'dreambox-image-dm920.tar.xz'
gpgv: Signature made Thu Nov 14 16:42:13 2019 UTC using RSA key ID B3C5B1A3
gpgv: Good signature from "Dreambox DM920 Recovery <dm920@recovery.dreambox.de>"
[*] Creating ext4 filesystem 'dreambox-rootfs' on /dev/mmcblk0p2
mke2fs 1.43-WIP (18-May-2015)
Discarding device blocks:   4096/253952             done                            
Creating filesystem with 253952 4k blocks and 63488 inodes
Filesystem UUID: 44ce5a99-e9f5-4fa0-b8d7-ab6f30adddf1
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376


Allocating group tables: 0/8   done                            
Writing inode tables: 0/8   done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/8   done


[*] Mounting '/dev/mmcblk0p2' to '/mnt'
[*] Extracting 'dreambox-image-dm920.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'
update-alternatives: error: cannot append to '/var/log/alternatives.log': No such file or directory
[*] Writing /boot/zImage-3.14-1.17-dm920 to /dev/mmcblk0p1
64+1 records in
64+1 records out
4248912 bytes (4.1MB) copied, 1.942312 seconds, 2.1MB/s
[*] Unmounting '/mnt/dev'
[*] Unmounting '/mnt/proc'
[*] Unmounting '/mnt/run'
[*] Unmounting '/mnt/sys'
[*] Unmounting '/mnt/tmp'
[*] Unmounting '/mnt'
[*] Unmounting '/data'
[*] Finished successfully. You may reboot now.
[*] Initiating reboot

Alles anzeigen

Das sieht eigentlich alles gut aus, dies irritiert ein wenig, habe ich so unter Linux noch nicht wahrgenommen "Discarding device blocks: 4096/253952"

Dass kein /var/log/alternatives.log vorhanden ist, sollte eigentlich auch kein Problem sein, habe es aber auch mal angelegt ohne Unterschied.

Code

root@dm920:~# blkid
/dev/mmcblk0: PTUUID="88250523-0901-4fe5-96ea-e2a7b9cc409c" PTTYPE="gpt"
/dev/mmcblk0p1: PARTLABEL="kernel" PARTUUID="ed288b57-3a2a-48ac-9fd8-af839664b4cf"
/dev/mmcblk0p2: LABEL="dreambox-rootfs" UUID="5fd2e976-36ba-4934-8b48-054a4032dd65" TYPE="ext4" PARTLABEL="rootfs" PARTUUID="7e4551e2-1959-4d0d-8902-fd2e690e74c3"
/dev/mmcblk0p3: LABEL="dreambox-data" UUID="4659a3e8-c50b-4660-9165-8704436cc5a6" TYPE="ext4" PARTLABEL="data" PARTUUID="6b06369f-e834-4cd1-a83c-a54e821c3e86"

Ich werde mich aber auch mal seriel verbinden um mir die Ausgabe mal auf die Konsole zu holen.

Hat jemand gerade einen Ansatzpunkt bevor ich an ein USB recovery gehe?
https://board.newnigma2.to/wbb…M920-DM7080-USB-Recovery/

Besten Dank

Grüße
Oli_K76

netman · 5. August 2020

Hast du schon mal ein Original-Image geflashed zum Testen?

Joey99 · 5. August 2020

Laut Log ja - online Recovery.
Ein Bootlog wäre aufschlussreich.

Oli_K76 · 5. August 2020

Also Images zu flashen versucht habe ich oZZooN, Gemini und Original.

bootlog ist leider leer:

Code

root@dm920:~# ls -laF /var/log/
drwxr-xr-x    2 root     root           100 Jan  1  1970 ./
drwxr-xr-x    5 root     root           100 Jan  1  1970 ../
-rw-r--r--    1 root     root             0    Jan  1  1970 boot
-rw-r--r--    1 root     root         20963 Jan  1  1970 dmesg
-rw-rw-r--    1 root     root          3072 Nov  7 20:12 wtmp

Aber in dmesg habe ich was gefunden:

Code

[    0.586039] ALSA device list:
[    0.586044]   No soundcards found.
[    0.586091] Warning: unable to open an initial console.
[    0.647141] mmc1: BKOPS_EN bit is not set
[    0.656966] mmc1: new high speed MMC card at address 0001
[    0.657337] mmcblk0: mmc1:0001 8GME4R 7.28 GiB
[    0.657460] mmcblk0boot0: mmc1:0001 8GME4R partition 1 4.00 MiB
[    0.657558] mmcblk0boot1: mmc1:0001 8GME4R partition 2 4.00 MiB
[    0.657671] mmcblk0rpmb: mmc1:0001 8GME4R partition 3 512 KiB
[    0.662331]  mmcblk0: p1 p2 p3
[    0.665653]  mmcblk0boot1: unknown partition table
[    0.666395]  mmcblk0boot0: unknown partition table
[    0.687569] systemd-udevd[95]: starting version 230
[    0.689505] random: systemd-udevd: uninitialized urandom read (16 bytes read, 28 bits of entropy available)
[    0.689855] random: systemd-udevd: uninitialized urandom read (16 bytes read, 28 bits of entropy available)
[    0.689903] random: systemd-udevd: uninitialized urandom read (16 bytes read, 28 bits of ent...18]: failed to execute '/lib/systemd/systemd-sysctl' '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/eth0 --prefix=/net/ipv4/neigh/eth0 --prefix=/net/ipv6/conf/eth0 --prefix=/net/ipv6/neigh/eth0': No su
ch file or directory
[    0.860530] systemd-udevd[106]: Process '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/eth0 --prefix=/net/ipv4/neigh/eth0 --prefix=/net/ipv6/conf/eth0 --prefix=/net/ipv6/neigh/eth0' failed with exit code 2.
[    0.915965] systemd-udevd[119]: failed to execute '/lib/systemd/systemd-vconsole-setup' '/lib/systemd/systemd-vconsole-setup': No such file or directory
[    0.916581] systemd-udevd[106]: Process '/lib/systemd/systemd-vconsole-setup' failed with exit code 2.
[    1.020712] bcmdriver: module license 'Proprietary' taints kernel.
[    1.020722] Disabling lock debugging due to kernel taint
[    1.021125] BCMDRV: Initializing bcmdriver version $ 8
[    1.021137] BCMDRV: Total intc words=4,Total Irqs=129
[    1.021815] BCMDRV: Initialization complete

Alles anzeigen

So wie es aussieht ist das Boot Device dahin.

Code

root@dm920:~# fsck.ext4 /dev/mmcblk0p2
e2fsck 1.43-WIP (18-May-2015)
dreambox-rootfs: clean, 14795/63488 files, 100416/253952 blocks


root@dm920:~# fsck.ext4 /dev/mmcblk0p3
e2fsck 1.43-WIP (18-May-2015)
dreambox-data: clean, 17/412080 files, 82298/1646587 blocks


root@dm920:~# mount /dev/mmcblk0p2 /data/


root@dm920:~# ls -alF /data/
drwxr-xr-x   19 root     root          4096 Nov  7  2017 ./
drwxr-xr-x   19 root     root             0 Nov  7 20:13 ../
drwxr-xr-x    2 root     root          4096 Nov  7  2017 bin/
drwxr-xr-x    2 root     root          4096 Nov  7  2017 boot/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 dev/
drwxr-xr-x   45 root     root          4096 Nov  7  2017 etc/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 home/
drwxr-xr-x    8 root     root          4096 Nov  7  2017 lib/
drwx------    2 root     root         16384 Nov  7  2017 lost+found/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 media/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 mnt/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 proc/
drwx------    2 root     root          4096 Apr 20  2018 root/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 run/
drwxr-xr-x    2 root     root          4096 Nov  7  2017 sbin/
drwxr-xr-x    2 root     root          4096 Apr 20  2018 sys/
drwxrwxrwt    2 root     root          4096 Apr 20  2018 tmp/
drwxr-xr-x   10 root     root          4096 Nov  7  2017 usr/
drwxr-xr-x    8 root     root          4096 Nov  7  2017 var/


root@dm920:~# ls -alF /data/boot/
drwxr-xr-x    2 root     root          4096 Nov  7  2017 ./
drwxr-xr-x   19 root     root          4096 Nov  7  2017 ../
-rw-r--r--    1 root     root         48398 Apr 20  2018 devicetree-zImage-dreambox-dm900.dtb
lrwxrwxrwx    1 root     root            36 Nov  7  2017 dreambox-dm900.dtb -> /etc/alternatives/dreambox-dm900.dtb
lrwxrwxrwx    1 root     root            24 Nov  7  2017 zImage -> /etc/alternatives/zImage
-rw-r--r--    1 root     root       4248912 Apr 20  2018 zImage-3.14-1.17-dm920

Alles anzeigen

Code

root@dm920:~# fdisk /dev/mmcblk0
Found valid GPT with protective MBR; using GPT




Command (m for help): p
Disk /dev/mmcblk0: 15269888 sectors, 3360M
Logical sector size: 512
Disk identifier (GUID): 88250523-0901-4fe5-96ea-e2a7b9cc409c
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 15269854


Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048           65535       31.0M   0700  kernel
   2           65536         2097151        992M   0700  rootfs
   3         2097152        15269854       6431M   0700  data


Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy


root@dm920:~# fdisk /dev/mmcblk0boot0
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.




Command (m for help): q


root@dm920:~# fdisk /dev/mmcblk0boot1
Device contains neither a valid DOS partition table, nor Sun, SGI, OSF or GPT disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that the previous content
won't be recoverable.




Command (m for help): q




root@dm920:~# mount /dev/mmcblk0boot0 /data/
mount: /dev/mmcblk0boot0 is write-protected, mounting read-only
mount: unknown filesystem type


root@dm920:~# mount /dev/mmcblk0boot1 /data/
mount: /dev/mmcblk0boot1 is write-protected, mounting read-only
mount: unknown filesystem type

Alles anzeigen

Ich denke, dass der bootloader das boot Device nicht mounten kann. Wahrscheinlich muss ich doch mit der Console ran um zu sehen was passiert.
Das Rescue System schreibt ja nur in die Datenpartitionen, Partitionstabellen erstellt er dabei nicht. Gibt es hierzu ein Workaround oder kann mir jemand sagen wie die Bootpartitionen aussehen müssen?

Vielleicht liege ich auch falsch und es gibt noch einen anderen Ansatz?

Danke

nokia2 · 5. August 2020

Ohne Bootlog ist das echt schwierig.

Hast Du mal geschaut, ob zufällig eine Taste am Frontpanel festhängt?

Sowas ist auch schon passiert. Dann wurde halt laufend wieder ins recovery gebootet.

cu

Oli_K76 · 6. August 2020

Hallo nokia2,

die Box hat keine tasten mehr, nur touch.
Anbei der Output der Konsole:

Code

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2020.08.06 17:20:20 =~=~=~=~=~=~=~=~=~=~=~=
CPU 01
Dreambox DM920


AVS init...
AVS init OK
AVS load:select_image: addr_offset: 00051000 part_offset: 00000000 bootStatus: 2a002b00
AVS load_code offset =00051000
LOADED
AVS: overtemp mon ON


single board
select_image: addr_offset: 00055000 part_offset: 00000000 bootStatus: 3d2b2500
MEMSYS-STD
SHMOO 02010000 BLD:11138M HW:hpf0_b1p6 V:2.1.0.0
MCB: FLEX
AVS start:status=000000ff
STB: Current voltage=00000390(912)
 temperature=0000d502(54530)
 PV=0000034e(846)
 MV=00000390(912)
AVS FW rev=30333278 [0.3.2.x]
OK
DDR0: !@ ffe0e780 <= ffe0df10 MEMSYS-0 @ f1100000 OK
DDR1: =@ ffe0e780 <= ffe0df10 MEMSYS-1 @ f1180000 OK
Sdram Scramble OTP = 0x00000001 
Sdram Scramble OK
select_image: addr_offset: 00020000 part_offset: 00000000 bootStatus: 1b25252b
BFW load mode OTP = 0x0000000f 
bfw_hash_locked = 0x00000000 
BFW key3 OK, BFW load OK
BFW v2.1.0
COPY CODE... DONE
MICH: disable success
SSBL
PINMUX
CACHE FLUSH OK
MMU ...key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHCGGlHWmO+15JfrcdP4CsV92UT1oQduCmYM1VeLM4uNFvSrX1cwXkVA96j5fRqS6gZ7eL6V527Wf4M2GV5xNtJdgPi7nDl/zVHv5FvJmFnNUY8yjJdNVIQuDD8h1qOwyBrsfAqZigIkHrP1V/Wp77Yut1W0CIvT+6lsyIXWnev14EovlM8Es1GFLi04vVcLS569ry18i50Z4PqKNsyMvkivDxMFP2GMUOFiYLQW1E29jXn64Dzb/anAguANjBKMiX9XyeClx5rpd0I/u1GS5NhHW4Rt8qAqqsT8tfWta2RxTTqraOVn/VMb6GIL9HB60bMmnxjdklTF8bF60kGIvH root@dm920
Fingerprint: md5 54:5c:c1:1f:9e:a2:45:22:d7:bc:4f:63:31:60:f9:32
dropbear.
Starting autoflashd.
Starting recovery-ui.
Starting tpmd.
Starting internet superserver: xinetd.
[   13.196052] random: nonblocking pool is initialized
Starting Lighttpd Web Server: lighttpd.
2017-11-07 20:06:34: (../../lighttpd-1.4.39/src/log.c.194) server started 




opendreambox 2.5.0 dm920 /dev/ttyS0






>>> Your Dreambox has booted into RESCUE MODE.


>>> Please log in as user 'root' (no password required),


>>> then run 'help' to get further information.


dm920 login:

Alles anzeigen

So wie ich vermutet habe:
Normal bootup
Default boot device not found!
Booting failed. Running recovery

Kann jemand helfen?

Besten Dank

Grüße
Olli

DM920 lässt sich flashen geht aber trotzdem in Rescue Mode

Wer ist / war online ?

Benutzer online 26

Wer war online 227