I tried to load a bootlogo .mvi and bootlogo.wait file , then it crashed. Renard pointed out to me that the 920 only has a bootlogo.mvi. Maybe the file didn't suit the image or it was corrupt , I just don't know as I normally check these things. One good thing tho, I am always trying to learn more about my dreamboxes and I certainly learned lots from people like yourself ,who have great knowledge on file systems.
Beiträge von scotty28
-
-
Fred Bogus Trumper ,Binsche, gutemine , Hilfsbereit and Renard . WOW!!!! Between you , you have brought my dead box back to life, I am currently loading channels on a NEW image.
I will give you the details when I can upload it, I am unable to copy it from telnet . Basically I put in the CODE:sgdisk /dev/mmcblk0 -z -n 1:2048:65535 -c 1:kernel -t 1:8301 -n 2:65536:4194303 -c 2:rootfs -t 2:8307 -n 3:4194304: -c 3:data -t 3:8300 in then tried the CODE: fdisk -lu / dev / mmcblk0 , a couple of times then it reacted and I was able to use the rescue loader online recovery and loaded a new image. Thank you all for your input, your knowledge is BRILLIANT .
THANKS !!!
-
And thank you gutemine for your help
-
I copied and pasted both the command directly from Binsche and copied and pasted the results in telnet as they were written.
I have copied your command Fred and here is the result.
root@dm920:~# sgdisk /dev/mmcblk0 -z -n 1:2048:65535 -c 1:kernel -t 1:8301 -n 2
65536:4194303 -c 2:rootfs -t 2:8307 -n 3:4194304: -c 3:data -t 3:8300
Caution: invalid main GPT header, but valid backup; regenerating main header
from backup!
Caution! After loading partitions, the CRC doesn't check out
Warning! Main partition table CRC mismatch! Loaded backup partition tableinstead of main partition table!
Warning! One or more CRCs don't match. You should repair the disk!
Invalid partition data
GPT data structures destroyed! You may now partition the disk using fdisk orother utilities.
Hope this makes some sense
-
it also says.
root@dm920:~# sgdisk / dev / mmcblk0 -z -n 1: 2048: 65535 -c 1: kernel -t 1: 8
01 -n 2: 65536: 4194303 -c 2: rootfs -t 2: 8307 -n 3: 4194304: -c 3 : data -t 3
8300
The specified path is a directory!
Problem opening '' for writing! Program will now terminate.
root@dm920:~#
-
Hi Binsche, Thank you for your help. I have tried both of your codes and here are the results.
root@dm920:~# fdisk -lu / dev / mmcblk0
fdisk: can't open '/': Is a directory
fdisk: can't open 'dev': No such file or directory
fdisk: can't open '/': Is a directory
fdisk: can't open 'mmcblk0': No such file or directory
root@dm920:~# sgdisk / dev / mmcblk0 -z -n 1: 2048: 65535 -c 1: kernel -t 1: 8
01 -n 2: 65536: 4194303 -
-
Ok Fred thanks I will try and contact one of the team.
-
Thanks so much Fred for your help I will contact them later as I have to go out now
THANK YOU
-
root@dm920:~# fdisk -lu /dev/mmcblk0
Disk /dev/mmcblk0: 7818 MB, 7818182656 bytes
4 heads, 16 sectors/track, 238592 cylinders, total 15269888 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk /dev/mmcblk0 doesn't contain a valid partition table
root@dm920:~# blkid|grep mmcblk0
-
I take it the file system is corrupted? can it be formatted in any way?
-
-
I would like to recover it by any means, my knowledge is limited so any help is very welcome,. I understand it may be a hardware problem that I can't fix , but I will try all options and thanks for your help
-
there is a spelling mistake in enigma, tried it again with enigma , but the same result, it's not responding to systemctl
-
here's the message
root@dm920:~# systemctl restart einigma2.service-bash: systemctl: not found
root@dm920:~#
-
on pressing enter it came up
rootfs / rootfs rw,relatime 0 0
-
Thanks Fred Bogus Trumper, I will try now.
-
As you can see from my previous post whenever I send certain commands by telnet , it comes up -bash (*****) not found. so trying to get a log isn't easy. It does however respond to dmesg and here is where in that message there seem to be errors [ 0.586097] Warning: unable to open an initial console.
[ 0.646988] mmc1: BKOPS_EN bit is not set
[ 0.653567] mmc1: new high speed MMC card at address 0001
[ 0.653867] mmcblk0: mmc1:0001 8GME4R 7.28 GiB
[ 0.653993] mmcblk0boot0: mmc1:0001 8GME4R partition 1 4.00 MiB
[ 0.654110] mmcblk0boot1: mmc1:0001 8GME4R partition 2 4.00 MiB
[ 0.654249] mmcblk0rpmb: mmc1:0001 8GME4R partition 3 512 KiB
[ 0.655471] mmcblk0: unknown partition table
[ 0.656505] mmcblk0boot1: unknown partition table
[ 0.657158] mmcblk0boot0: unknown partition table
[ 0.683827] systemd-udevd[95]: starting version 230
[ 0.685874] random: systemd-udevd: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.686380] random: systemd-udevd: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.686440] random: systemd-udevd: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.686500] random: systemd-udevd: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.695979] random: udevadm: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.696153] random: udevadm: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.696188] random: udevadm: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.696438] random: udevadm: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.697125] random: udevadm: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.697423] random: udevadm: uninitialized urandom read (16 bytes read, 27 bits of entropy available)
[ 0.853129] systemd-udevd[118]: 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 such file or directory
[ 0.856616] systemd-udevd[102]: 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.892680] systemd-udevd[119]: failed to execute '/lib/systemd/systemd-vconsole-setup' '/lib/systemd/systemd-vconsole-setup': No such file or directory
[ 0.893079] systemd-udevd[101]: Process '/lib/systemd/systemd-vconsole-setup' failed with exit code 2.
[ 0.909157] bcmdriver: module license 'Proprietary' taints kernel.
[ 0.909167] Disabling lock debugging due to kernel taint
[ 0.909593] BCMDRV: Initializing bcmdriver version $ 8
[ 0.909601] BCMDRV: Total intc words=4,Total Irqs=129
[ 0.910388] BCMDRV: Initialization complete
[ 1.273218] f0b00000.etherne:01: Broadcom BCM7439 (2) PHY revision: 0x10, patch: 1
[ 1.274891] f0b00000.ethernet: configuring instance for internal PHY
[ 1.274960] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3.277327] libphy: f0b00000.etherne:01 - Link is Down
[ 4.144897] libphy: f0b00000.etherne:01 - Link is Up - 1000/Full
[ 4.144919] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 15.897558] random: nonblocking pool is initialized
root@dm920:~#Also something has changed in telnet when I link to the box it comes up now as
opendreambox 2.5.0 dm 920
>>> your dreambox has booted into RESCUE MODE.
>>>Please log in as user 'root' (no password is required)
>>>then run 'help' to get further information.
I was running the pure2 image when in crashed and tried online recovery with a opendreambox 2.5.0 image just before writing this post so it's strange as telnet is recognising it as opendreambox as it says this below when trying to load it.
Code[*] Downloading 'http://dreamboxupdate.com/download/recovery/dm920/release/recovery.sig' [*] Downloading 'http://dreamboxupdate.com/download/recovery/dm920/release/recovery' [*] 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>" [*] Running './recovery' [*] Options '-v' Fatal: Target device '/dev/mmcblk0p2' is not writable Fatal: Failed to execute './recovery'
Anyway I sent the commands that I got from the 'Help, notification on telnet and the first line came up with bash not found but not with the other three lines.
root@dm920:~# . : [ [[ alias bg break cd chdir continue echo eval exec exit
-bash: .: :: not found
root@dm920:~# export false fg getopts hash help history jobs kill let local
root@dm920:~# printf pwd read readonly return set shift source test times trap
pwdroot@dm920:~# true type ulimit umask unalias unset waitplease help
-
Hi , I downloaded VCP and did what it said , but no port was visible. I also tried the telnet method and this is a copy of the telnet window
root@dm920:~# journalctl -fu enigma2
-bash: journalctl: not found
root@dm920:~# journalctl -f -u enigma2 > /tmp/enigma2.log
-bash: journalctl: not found
root@dm920:~#
-
Hi Hilfsbereit,
here is the log from telnet
Link encap:Ethernet HWaddr 00:09:34:48:B0:4E
inet addr:192.168.1.116 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::209:34ff:fe48:b04e%lo/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:491 errors:0 dropped:0 overruns:0 frame:0
TX packets:148 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:34340 (33.5 KiB) TX bytes:16588 (16.1 KiB)
Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1%1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
-
THANKS Hilfsbereit ,I will try. Much appreciated