Welcome to Our Dreambox World - Japhar Sim - SuperSim
Forum Stats
12403 Members
237 Forums
7723 Topics
23804 Posts

Max Online: 4756 @ 02/20/20 11:12 PM
Newest Members
Mekaho, djmed, kiki21, nobles, Josef Novak
12402 Registered Users
Who's Online
10 registered (Toysoft, Admin, 1966, bitgames, Herrleon, d2mac, fabrizio77, misup, Mekaho, OMEGA), 1161 Guests and 312 Spiders online.
Key: Admin, Global Mod, Mod
Shout Box

Top Posters
Admin 9876
Toysoft 2634
satsedhu 1713
fairbird 765
ludo19 442
Top Posters (30 Days)
Admin 18
dmr 8
Rtm79 4
Toysoft 3
Sasillo 3
March
M Tu W Th F Sa Su
1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
Topic Options
#19755 - 10/27/19 11:11 AM DM900UHD Rescue mode problem
Pamiko Offline
stranger

Registered: 10/27/19
Posts: 5
Hello guys please help,
My DM900 after switch on remains in rescue mode regardless pushing the stand by button or normal boot.
IP address and Telnet control OK however when I try to open the webIF to flash the box, there is no "Dreambox start page" but this text "Content-Type: text/html;charset=utf-8" appears.
When I try to reflash the firmware I get this:
root@dm900:~# wget https://dreamboxupdate.com/opendreambox/2.5/stable/images/dm9
00/zImage-rescue-3.14-r0-dm900-20190911.bin
Connecting to dreamboxupdate.com (82.149.226.170:443)
wget: server returned error: HTTP/1.1 400 Bad Request
root@dm900:~#

I get this bootlog:

,/
,'/___, BOLT v1.18 v1.18 LOCAL BUILD
.'__ ,' (2016-12-01 16:24:31 cynric@cynric-VirtualBox)
/,' Copyright (C) 2016 Broadcom
/'

Board: BCM97252SSFF
SYS_CTRL: product=72521, family=7439b1, strap=000000b2,
otp @ 0xf0404030 = 0x822000e0: en_cr(0x00000060) en_testport(0x00000080) macrovision_disable(0x02000000) moca_disable(0x80000000) rv9_disable(0x00200000)
otp @ 0xf0404034 = 0x00000021: moca2_disable(0x00000001) rfm_disable(0x00000020)
CPU: 2x B15 [420f00f3] 1719 MHz
SCB: 432 MHz
DDR0 @ 1067MHz, DDR1 @ 1067MHz
RESET CAUSE: 0x000001 power_on (1 of 23 possible causes)
CS0: SFDP SPI, 32MB, 64kB blocks, 64kB erase block, 256B pages
EMMC1: transfer complete intr error, intr=0x608000
Command 8 failed
EMMC1: device failed to enter transfer mode
CS1: NAND: unrecognized ID: 0xfefefefe 0xfefefefe
RTS0: 0x1101004, 256 clients, ok
RTS1: 0x1181004, 256 clients, ok
BOX MODE: 5
card if inited
set pwm to 0/255
disp id 5420
load image
AVS: park check
AVS: temperature monitoring enabled
AVS: STB: V=0.890V, T=+52.582C, PV=0.830V, MV=0.890V, FW=30333278 [0.3.2.x]
USB otp=00000040
USB @ 0xf0470200: IPP is active low, IOC is negative polarity
init fp
found card in unknown state
ca valid!
set pwm to 200/255
Normal bootup
Default boot device not found!
Booting failed. Running recovery
Loader:zimg Filesys:raw Dev:flash0.recovery File: Options:(null)
usb: resetting device on bus 0 hub 1 port 1
USB: New high speed device connected to bus 0 hub 1 port 1
usb: found Mass-Storage Device 0951:1607
USBMASS: Unit 0 connected
...........
thanks in advance

Top
#19756 - 10/27/19 01:28 PM Re: DM900 rescue mode problem [Re: Pamiko]
Admin Online   content
Japhar Member
Carpal Tunnel

Registered: 10/19/10
Posts: 9876
The bin file is available, we tried to download it now successfully with a browser on our PC.

Code:
https://dreamboxupdate.com/opendreambox/2.5/stable/images/dm900/zImage-rescue-3.14-r0-dm900-20190911.bin


Try again to reflash the rescue loader. Download it with your PC and upload it into your box in /tmp, then flash it with command below (don't do the wget if you downloaded it with the PC and uploaded it to /tmp).

Code:
cd /tmp
wget https://dreamboxupdate.com/opendreambox/2.5/stable/images/dm900/zImage-rescue-3.14-r0-dm900-20190911.bin
flash-rescue /tmp/zImage-rescue-3.14-r0-dm900-20190911.bin


To set to normal mode (boot) the DM900UHD you can also send the command below,

Code:
echo "normal" >> /proc/stb/fp/boot_mode


Your main error messages, show you have no image or partition with valid image or you boot into the corrupted CF. So you need to flash the rescue and then restore an image into the box (or defective Flash chip ? But the Rescue is also in Flash... and it works). You seems to have a USB Memory stick, try to remove it as well and if you have a HDD also remove it, like a CF Card.
Code:
EMMC1: transfer complete intr error, intr=0x608000
Command 8 failed
EMMC1: device failed to enter transfer mode
CS1: NAND: unrecognized ID: 0xfefefefe 0xfefefefe
...
Default boot device not found!
Booting failed. Running recovery

Admin
_________________________

Top
#19766 - 10/27/19 11:01 PM Re: DM900 rescue mode problem [Re: Pamiko]
Pamiko Offline
stranger

Registered: 10/27/19
Posts: 5
I get this: server returned error: HTTP/1.1 400 Bad Request

dm900 login: root
login[389]: root login on 'ttyS0'
root@dm900:~# cd /tmp
root@dm900:/tmp# wget https://dreamboxupdate.com/opendreambox/2.5/stable/images/dm900/zImage-re
scue-3.14-r0-dm900-20190911.bin
Connecting to dreamboxupdate.com (82.149.226.170:443)

wget: server returned error: HTTP/1.1 400 Bad Request

root@dm900:/tmp# flash-rescue /tmp/zImage-rescue-3.14-r0-dm900-20190911.bin
Fatal: Cannot access '/tmp/zImage-rescue-3.14-r0-dm900-20190911.bin'
root@dm900:/tmp#

do you have any other idea ?

Top
#19767 - 10/27/19 11:19 PM Re: DM900 rescue mode problem [Re: Pamiko]
Admin Online   content
Japhar Member
Carpal Tunnel

Registered: 10/19/10
Posts: 9876
Be careful, you need to send the full command here you ask for a wrong file name (in fact 2 filenames).
- zImage-re
- scue-3.14-r0-dm900-20190911.bin

It's 1 name, zImage-rescue-3.14-r0-dm900-20190911.bin

Click on the link, and you will get the file, if you break up the name it's normal you have a 400.

https://dreamboxupdate.com/opendreambox/...00-20190911.bin

I copied you the text properly... without the filename broken... I recopy you it.

Code:
cd /tmp
wget https://dreamboxupdate.com/opendreambox/2.5/stable/images/dm900/zImage-rescue-3.14-r0-dm900-20190911.bin
flash-rescue /tmp/zImage-rescue-3.14-r0-dm900-20190911.bin


Admin
_________________________

Top
#19774 - 10/28/19 05:55 PM Re: DM900 rescue mode problem [Re: Pamiko]
Pamiko Offline
stranger

Registered: 10/27/19
Posts: 5

dm900 login: root
login[389]: root login on 'ttyS0'
root@dm900:~# cd /tmp
root@dm900:/tmp# wget https://dreamboxupdate.com/opendreambox/...00-20190911.bin
Connecting to dreamboxupdate.com (82.149.226.170:443)
wget: server returned error: HTTP/1.1 400 Bad Request
root@dm900:/tmp#

I've downloaded "zImage-rescue-3.14-r0-dm900-20190911.bin" to my computer folder "C:"
Can I upload it to the "tmp" folder ?

Top
#19775 - 10/28/19 07:33 PM Re: DM900 rescue mode problem [Re: Pamiko]
Admin Online   content
Japhar Member
Carpal Tunnel

Registered: 10/19/10
Posts: 9876
Yes, you can upload it into the /tmp folder with WinSCP or any FTP tool (Remember it's binary and not ascii file, if you need to set the transfer mode do it in "binary").

The wget you put above is wrong as it's not the full file, there is ... then you should have the full link, https://dreamboxupdate.com/opendreambox/...00-20190911.bin

Code:
cd /tmp
wget https://dreamboxupdate.com/opendreambox/2.5/stable/images/dm900/zImage-rescue-3.14-r0-dm900-20190911.bin
flash-rescue /tmp/zImage-rescue-3.14-r0-dm900-20190911.bin


Once in the /tmp, or by FTP/transfer to box or using wget to download it, you can then use the flash-rescue tool to flash it to the box.

Admin
_________________________

Top
#19823 - 11/03/19 03:44 PM Re: DM900 rescue mode problem [Re: Admin]
bobyonekenobi86 Offline
stranger

Registered: 11/03/19
Posts: 2
Hi All,

I am technician helping out Pamiko.

The rescue image installed successfully:

Code:
root@dm900:/# cd /tmp/
root@dm900:/tmp# wget http://dreamboxupdate.com/opendreambox/2.5/stable/images/dm900/zImage-rescue-3.14-r0-dm900-20190911.bin
Connecting to dreamboxupdate.com (82.149.226.170:80)
zImage-rescue-3.14-r 100% |********************************************************************************| 11373k  0:00:00 ETA
root@dm900:/tmp# flash-rescue /tmp/zImage-rescue-3.14-r0-dm900-20190911.bin
Manufacturer ID: c2
Memory type    : 20
Memory density : 19
read id ok
comparing 2844 sectors...
nothing to do
root@dm900:/tmp#



But, as I see the main problem is the MMC NAND:

Code:
EMMC1: transfer complete intr error, intr=0x608000
Command 8 failed
EMMC1: device failed to enter transfer mode
CS1: NAND: unrecognized ID: 0xfefefefe 0xfefefefe


I can not locate it anywhere:

Code:
root@dm900:/dev# ls
autofs              mtd2                stderr              tty23               tty42               tty61
block               mtd2ro              stdin               tty24               tty43               tty62
brcm0               mtd3                stdout              tty25               tty44               tty63
bus                 mtd3ro              sw_sync             tty26               tty45               tty7
char                mtd4                tty                 tty27               tty46               tty8
console             mtd4ro              tty0                tty28               tty47               tty9
cpu_dma_latency     mtdblock0           tty1                tty29               tty48               ttyS0
dbox                mtdblock1           tty10               tty3                tty49               ttyS1
fd                  mtdblock2           tty11               tty30               tty5                ttyS2
full                mtdblock3           tty12               tty31               tty50               ttyS3
initctl             mtdblock4           tty13               tty32               tty51               urandom
kmsg                net                 tty14               tty33               tty52               vcs
loop-control        network_latency     tty15               tty34               tty53               vcs1
loop0               network_throughput  tty16               tty35               tty54               vcsa
loop1               null                tty17               tty36               tty55               vcsa1
mem                 port                tty18               tty37               tty56               zero
mtab                ptmx                tty19               tty38               tty57
mtd0                pts                 tty2                tty39               tty58
mtd0ro              random              tty20               tty4                tty59
mtd1                shm                 tty21               tty40               tty6
mtd1ro              snd                 tty22               tty41               tty60


FDISK
Quote:

root@dm900:/dev# fdisk -lu

Disk /dev/mtdblock0: 2 MB, 2097152 bytes
255 heads, 63 sectors/track, 0 cylinders, total 4096 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders, total 256 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/mtdblock2: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders, total 256 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock2 doesn't contain a valid partition table

Disk /dev/mtdblock3: 14 MB, 14417920 bytes
255 heads, 63 sectors/track, 1 cylinders, total 28160 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock3 doesn't contain a valid partition table

Disk /dev/mtdblock4: 33 MB, 33554432 bytes
255 heads, 63 sectors/track, 4 cylinders, total 65536 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock4 doesn't contain a valid partition table


FSTAB

Code:
rootfs  /               rootfs  rw,relatime                                     0 1
proc    /proc           proc    rw,nosuid,nodev,noexec,relatime                 0 0
sysfs   /sys            sysfs   rw,nosuid,nodev,noexec,relatime                 0 0
devpts  /dev/pts        devpts  rw,nosuid,noexec,relatime,gid=5,mode=620        0 0
tmpfs   /dev/shm        tmpfs   rw,nosuid,nodev,relatime                        0 0
tmpfs   /run            tmpfs   rw,nosuid,nodev,relatime,mode=755               0 0
tmpfs   /tmp            tmpfs   rw,relatime                                     0 0
tmpfs   /var/volatile   tmpfs   rw,relatime,mode=755                            0 0




Is it possible to somehow get it working and re-partition?
Also can we use external MMC or HDD for system partitions?

Thank you in advance!

Boby

PS.: Boot log in spoiler tag:

Click to reveal..

Code:
CPU 01
Dreambox DM900
AVS init...
AVS init OK
AVS load:select_image: addr_offset: 00051000 part_offset: 00000000 bootStatus: 2a252b25
AVS load_code offset =00051000
LOADED
AVS: overtemp mon ON

single board
select_image: addr_offset: 00055000 part_offset: 00000000 bootStatus: 3d2b2525
MEMSYS-STD
SHMOO 02010000 BLD:11138M HW:hpf0_b1p6 V:2.1.0.0
MCB: FLEX
AVS start:status=000000ff
STB: Current voltage=0000037e(894)
 temperature=0000d502(54530)
 PV=00000343(835)
 MV=00000381(897)
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 ON
CACHE FLUSH OK
_fbss  07080cd0
_ebss  0713dd70
_end   0713dd90
HEAP @ 07200000
STACK @ 09300000
ARCH: CONFIG OK
CLR BSS 07080cd0 to 0713dd70 OK
CLR SRAM  OK
CACHE FLUSH OK
CPU CLKSET OK
GO!

    ,/
  ,'/___, BOLT v1.18 v1.18 LOCAL BUILD
.'__  ,'  (2016-12-01 16:24:31 cynric@cynric-VirtualBox)
   /,'    Copyright (C) 2016 Broadcom
  /'

Board: BCM97252SSFF
SYS_CTRL: product=72521, family=7439b1, strap=000000b2,
otp @ 0xf0404030 = 0x822000e0: en_cr(0x00000060) en_testport(0x00000080) macrovision_disable(0x02000000) moca_disable(0x80000000) rv9_disable(0x00200000)
otp @ 0xf0404034 = 0x00000021: moca2_disable(0x00000001) rfm_disable(0x00000020)
CPU: 2x B15 [420f00f3] 1719 MHz
SCB: 432 MHz
DDR0 @ 1067MHz, DDR1 @ 1067MHz
RESET CAUSE: 0x000200 software_master (1 of 23 possible causes)
CS0: SFDP SPI, 32MB, 64kB blocks, 64kB erase block, 256B pages
EMMC1: transfer complete intr error, intr=0x608000
Command 8 failed
EMMC1: device failed to enter transfer mode
CS1: NAND: unrecognized ID: 0xfefefefe 0xfefefefe
RTS0: 0x1101004, 256 clients, ok
RTS1: 0x1181004, 256 clients, ok
BOX MODE: 5
card if inited
set pwm to 0/255
disp id 5420
load image
AVS: park check
AVS: temperature monitoring enabled
AVS: STB: V=0.892V, T=+55.017C, PV=0.835V, MV=0.897V, FW=30333278 [0.3.2.x]
USB otp=00000040
USB @ 0xf0470200: IPP is active low, IOC is negative polarity
init fp
found card in unknown state
ca valid!
set pwm to 200/255
Normal bootup
Default boot device not found!
Booting failed. Running recovery
Loader:zimg Filesys:raw Dev:flash0.recovery File: Options:(null)
Reading 11646952 bytes from zImage...........
Starting program at 0x8000 (DTB @ 0x7716000)

32 bit boot...
Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.14-1.17-dm900 (dm900@opendreambox.org) (gcc version 5.3.0 (GCC) ) #2 SMP Wed Sep 11 16:26:21 UTC 2019
[    0.000000] CPU: ARMv7 Processor [420f00f3] revision 3 (ARMv7), cr=30c7387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Machine model: BCM97252SSFF
[    0.000000] moving dtb from 0x0000000007716000 to 0x0000000000f4de70
[    0.000000] bmem: Reserved 640 MiB at 0x0000000018000000
[    0.000000] bmem: Reserved 384 MiB at 0x0000000080000000
[    0.000000] cma: Reserved 16 MiB at 0x000000000f000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] MCP: Enabling write pairing
[    0.000000] PERCPU: Embedded 8 pages/cpu @cdfc0000 s8384 r8192 d16192 u32768
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 523776
[    0.000000] Kernel command line: bmem=640M@384M bmem=384M@2048M console=ttyS0,1000000 root=/dev/mmcblk0p2 rootwait rootfstype=ext4 coherent_pool=2M
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 999648K/2097152K available (6114K kernel code, 214K rwdata, 1584K rodata, 7508K init, 208K bss, 1081120K reserved, 16384K cma-reserved, 786428K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc078ccec   (7700 kB)
[    0.000000]       .init : 0xc078d000 - 0xc0ee20c0   (7509 kB)
[    0.000000]       .data : 0xc0ee4000 - 0xc0f19b20   ( 215 kB)
[    0.000000]        .bss : 0xc0f19b28 - 0xc0f4de70   ( 209 kB)
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  Additional per-CPU info printed with stalls.
[    0.000000]  RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] irq_brcmstb_l2: registered L2 intc (mem: 0xfc403000, parent irq: 93)
[    0.000000] irq_brcmstb_l2: registered L2 intc (mem: 0xfc3e1000, parent irq: 64)
[    0.000000] irq_brcmstb_l2: registered L2 intc (mem: 0xfc410640, parent irq: 95)
[    0.000000] irq_brcmstb_l2: registered L2 intc (mem: 0xfc4d1200, parent irq: 58)
[    0.000000] Architected cp15 timer(s) running at 27.00MHz (virt).
[    0.000004] sched_clock: 56 bits at 27MHz, resolution 37ns, wraps every 2545165795328ns
[    0.000010] Switching to timer-based delay loop
[    0.000235] Console: colour dummy device 80x30
[    0.000255] Calibrating delay loop (skipped), value calculated using timer frequency.. 54.00 BogoMIPS (lpj=27000)
[    0.000264] pid_max: default: 32768 minimum: 301
[    0.000357] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000362] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.005894] Initializing cgroup subsys devices
[    0.005907] Initializing cgroup subsys freezer
[    0.005914] Initializing cgroup subsys net_cls
[    0.005941] CPU: Testing write buffer coherency: ok
[    0.006157] CPU0: update cpu_power 1024
[    0.006164] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.006214] Setting up static identity map for 0x5d5ab8 - 0x5d5b10
[    0.007444] CPU1: Booted secondary processor
[    0.007462] CPU1: update cpu_power 1024
[    0.007465] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.007538] Brought up 2 CPUs
[    0.007549] SMP: Total of 2 processors activated (108.00 BogoMIPS).
[    0.007553] CPU: All CPU(s) started in SVC mode.
[    0.007942] devtmpfs: initialized
[    0.011578] VFP support v0.3: implementor 42 architecture 4 part 00 variant 0 rev 0
[    0.012151] regulator-dummy: no parameters
[    0.012327] NET: Registered protocol family 16
[    0.013244] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[    0.013433] cpuidle: using governor ladder
[    0.013437] cpuidle: using governor menu
[    0.014584] irq: no irq domain found for /rdb/interrupt-controller@f040a700 !
[    0.014668] irq: no irq domain found for /rdb/interrupt-controller@f0417380 !
[    0.016357] syscon f0404000.syscon: regmap [mem 0xf0404000-0xf0404523] registered
[    0.016429] syscon f03e2400.syscon: regmap [mem 0xf03e2400-0xf03e27ff] registered
[    0.016496] syscon f0452000.syscon: regmap [mem 0xf0452000-0xf04520ff] registered
[    0.016560] syscon f0404100.syscon: regmap [mem 0xf0404100-0xf040415b] registered
[    0.016622] syscon f040415c.syscon: regmap [mem 0xf040415c-0xf040419b] registered
[    0.016689] syscon f0410700.syscon: regmap [mem 0xf0410700-0xf041070b] registered
[    0.016755] syscon f041070c.syscon: regmap [mem 0xf041070c-0xf0410713] registered
[    0.016817] syscon f1101004.syscon: regmap [mem 0xf1101004-0xf1101403] registered
[    0.016879] syscon f1181004.syscon: regmap [mem 0xf1181004-0xf1181403] registered
[    0.016948] syscon f0404080.syscon: regmap [mem 0xf0404080-0xf0404083] registered
[    0.017014] syscon f04040a4.syscon: regmap [mem 0xf04040a4-0xf04040a7] registered
[    0.017078] syscon f03e0154.syscon: regmap [mem 0xf03e0154-0xf03e0157] registered
[    0.017158] syscon f03e0354.syscon: regmap [mem 0xf03e0354-0xf03e0357] registered
[    0.017225] syscon f03e0400.syscon: regmap [mem 0xf03e0400-0xf03e0403] registered
[    0.017529] irq: no irq domain found for /rdb/interrupt-controller@f0417380 !
[    0.017755] Broadcom Brahma-B15 readahead cache at: 0xfc3e2478
[    0.022098] bio: create slab <bio-0> at 0
[    0.022406] brcmstb-gpio f040a600.gpio: Couldn't get IRQ. Enable CONFIG_BCM7120_L2_IRQ if you want GPIO interrupt support
[    0.022431] brcmstb-gpio f040a600.gpio: Registered 5 banks (GPIO(s): 0-159)
[    0.022458] brcmstb-gpio f0417400.gpio: Couldn't get IRQ. Enable CONFIG_BCM7120_L2_IRQ if you want GPIO interrupt support
[    0.022471] brcmstb-gpio f0417400.gpio: Registered 2 banks (GPIO(s): 160-223)
[    0.022819] SCSI subsystem initialized
[    0.023033] usbcore: registered new interface driver usbfs
[    0.023063] usbcore: registered new interface driver hub
[    0.023121] usbcore: registered new device driver usb
[    0.023141] media: Linux media interface: v0.10
[    0.023181] Linux video capture interface: v2.00
[    0.023217] pps_core: LinuxPPS API ver. 1 registered
[    0.023220] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.023231] PTP clock support registered
[    0.023449] Advanced Linux Sound Architecture Driver Initialized.
[    0.023735] Bluetooth: Core ver 2.18
[    0.023749] NET: Registered protocol family 31
[    0.023752] Bluetooth: HCI device and connection manager initialized
[    0.023760] Bluetooth: HCI socket layer initialized
[    0.023766] Bluetooth: L2CAP socket layer initialized
[    0.023773] Bluetooth: SCO socket layer initialized
[    0.024189] Switched to clocksource arch_sys_counter
[    0.024202] cfg80211: Calling CRDA to update world regulatory domain
[    0.028538] thermal thermal_zone0: failed to read out thermal zone 0
[    0.028623] NET: Registered protocol family 2
[    0.029024] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.029040] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.029062] TCP: Hash tables configured (established 2048 bind 2048)
[    0.029096] TCP: reno registered
[    0.029102] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.029115] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.029245] NET: Registered protocol family 1
[    0.029474] RPC: Registered named UNIX socket transport module.
[    0.029480] RPC: Registered udp transport module.
[    0.029483] RPC: Registered tcp transport module.
[    0.029487] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.246265] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.246589] bounce pool size: 64 pages
[    0.247118] NFS: Registering the id_resolver key type
[    0.247149] Key type id_resolver registered
[    0.247154] Key type id_legacy registered
[    0.247164] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.247322] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[    0.247610] msgmni has been set to 448
[    0.248434] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.248442] io scheduler noop registered
[    0.248461] io scheduler cfq registered (default)
[    0.248690] brcm-gisb-arb f0400000.gisb-arb: registered mem: fc400000, irqs: 258, 259
[    0.248979] brcm-usb-phy f0470200.usb-phy: USB3.0 clock not found in Device Tree
[    0.314488] brcmstb_memc f1102000.memc-ddr: registered
[    0.314516] brcmstb_memc f1182000.memc-ddr: registered
[    0.314724] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.315512] f040a900.serial: ttyS0 at MMIO 0xf040a900 (irq = 107, base_baud = 5062500) is a 16550A
[    0.412255] console [ttyS0] enabled
[    0.413484] loop: module loaded
[    0.414125] ahci brcmstb-ahci.0: can't get clock
[    0.414743] ahci brcmstb-ahci.0: SSS flag set, parallel bus scan disabled
[    0.426206] ahci brcmstb-ahci.0: AHCI 0001.0300 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[    0.427202] ahci brcmstb-ahci.0: flags: 64bit ncq sntf stag pm clo pmp slum part
[    0.429877] scsi0 : ahci_platform
[    0.430512] scsi1 : ahci_platform
[    0.431013] ata1: SATA max UDMA/133 mmio [mem 0xf045a000-0xf045aa9b] port 0x100 irq 91
[    0.431932] ata2: SATA max UDMA/133 mmio [mem 0xf045a000-0xf045aa9b] port 0x180 irq 91
[    0.433353] spi_brcmstb f03e3400.spi: 1-lane output, 3-byte address
[    0.434120] spi_brcmstb f03e3400.spi: master is unqueued, this is deprecated
[    0.437499] m25p80 spi32766.0: found mx25l25635e, expected m25p80
[    0.438227] spi_brcmstb f03e3400.spi: 1-lane output, 4-byte address
[    0.438959] m25p80 spi32766.0: mx25l25635e (32768 Kbytes)
[    0.439615] 5 ofpart partitions found on MTD device spi32766.0
[    0.440298] Creating 5 MTD partitions on "spi32766.0":
[    0.440891] 0x000000000000-0x000000200000 : "flash0.bolt"
[    0.442027] 0x000000200000-0x000000220000 : "flash0.nvram"
[    0.443068] 0x000000220000-0x000000240000 : "flash0.devtree"
[    0.444122] 0x000000240000-0x000001000000 : "flash0.recovery"
[    0.445175] 0x000000000000-0x000002000000 : "flash0"
[    0.446462] libphy: Fixed MDIO Bus: probed
[    0.447060] tun: Universal TUN/TAP device driver, 1.6
[    0.447662] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    0.448701] bcmgenet f0b00000.ethernet: GENET 4.5 EPHY: 0x1001
[    0.462192] libphy: bcmgenet MII bus: probed
[    0.485094] xhci-brcm: xHCI BRCM driver
[    0.485636] xhci-brcm f0471000.xhci_v2: xHCI Host Controller
[    0.486308] xhci-brcm f0471000.xhci_v2: new USB bus registered, assigned bus number 1
[    0.487500] xhci-brcm f0471000.xhci_v2: irq 149, io mem 0xf0471000
[    0.488347] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.489128] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.489965] usb usb1: Product: xHCI Host Controller
[    0.490532] usb usb1: Manufacturer: Linux 3.14-1.17-dm900 xhci-hcd
[    0.491246] usb usb1: SerialNumber: f0471000.xhci_v2
[    0.492138] hub 1-0:1.0: USB hub found
[    0.492601] hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
[    0.493531] xhci-brcm f0471000.xhci_v2: xHCI Host Controller
[    0.494194] xhci-brcm f0471000.xhci_v2: new USB bus registered, assigned bus number 2
[    0.495224] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    0.496003] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.496853] usb usb2: Product: xHCI Host Controller
[    0.497422] usb usb2: Manufacturer: Linux 3.14-1.17-dm900 xhci-hcd
[    0.498131] usb usb2: SerialNumber: f0471000.xhci_v2
[    0.498979] hub 2-0:1.0: USB hub found
[    0.499438] hub 2-0:1.0: 2 ports detected
[    0.500229] ehci-brcm: EHCI BRCM driver
[    0.500747] ehci-brcm f0470300.ehci_v2: EHCI Host Controller
[    0.501417] ehci-brcm f0470300.ehci_v2: new USB bus registered, assigned bus number 3
[    0.512428] ehci-brcm f0470300.ehci_v2: irq 145, io mem 0xf0470300
[    0.518197] ehci-brcm f0470300.ehci_v2: USB 2.0 started, EHCI 1.00
[    0.519013] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    0.519800] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.520635] usb usb3: Product: EHCI Host Controller
[    0.521202] usb usb3: Manufacturer: Linux 3.14-1.17-dm900 ehci_hcd
[    0.521911] usb usb3: SerialNumber: f0470300.ehci_v2
[    0.522748] hub 3-0:1.0: USB hub found
[    0.523213] hub 3-0:1.0: 1 port detected
[    0.523858] ehci-brcm f0470500.ehci_v2: EHCI Host Controller
[    0.524527] ehci-brcm f0470500.ehci_v2: new USB bus registered, assigned bus number 4
[    0.535527] ehci-brcm f0470500.ehci_v2: irq 146, io mem 0xf0470500
[    0.542193] ehci-brcm f0470500.ehci_v2: USB 2.0 started, EHCI 1.00
[    0.542995] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[    0.543782] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.544617] usb usb4: Product: EHCI Host Controller
[    0.545183] usb usb4: Manufacturer: Linux 3.14-1.17-dm900 ehci_hcd
[    0.545893] usb usb4: SerialNumber: f0470500.ehci_v2
[    0.546721] hub 4-0:1.0: USB hub found
[    0.547170] hub 4-0:1.0: 1 port detected
[    0.547880] ohci-brcm: OHCI BRCM driver
[    0.548390] ohci-brcm f0470400.ohci_v2: BRCM OHCI controller
[    0.549053] ohci-brcm f0470400.ohci_v2: new USB bus registered, assigned bus number 5
[    0.549977] ohci-brcm f0470400.ohci_v2: irq 147, io mem 0xf0470400
[    0.605301] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[    0.606080] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.606914] usb usb5: Product: BRCM OHCI controller
[    0.607480] usb usb5: Manufacturer: Linux 3.14-1.17-dm900 ohci_hcd
[    0.608195] usb usb5: SerialNumber: f0470400.ohci_v2
[    0.609027] hub 5-0:1.0: USB hub found
[    0.609494] hub 5-0:1.0: 1 port detected
[    0.610141] ohci-brcm f0470600.ohci_v2: BRCM OHCI controller
[    0.610811] ohci-brcm f0470600.ohci_v2: new USB bus registered, assigned bus number 6
[    0.611731] ohci-brcm f0470600.ohci_v2: irq 148, io mem 0xf0470600
[    0.667298] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[    0.668078] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.668913] usb usb6: Product: BRCM OHCI controller
[    0.669480] usb usb6: Manufacturer: Linux 3.14-1.17-dm900 ohci_hcd
[    0.670195] usb usb6: SerialNumber: f0470600.ohci_v2
[    0.671012] hub 6-0:1.0: USB hub found
[    0.671477] hub 6-0:1.0: 1 port detected
[    0.672161] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.672921] ehci-pci: EHCI PCI platform driver
[    0.673477] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.674194] ohci-pci: OHCI PCI platform driver
[    0.674824] usbcore: registered new interface driver usb-storage
[    0.675523] i2c /dev entries driver
[    0.675968] lirc_dev: IR Remote Control driver registered, major 250
[    0.677023] brcmstb_thermal f04d1500.thermal: registered AVS TMON of-sensor driver
[    0.678007] usbcore: registered new interface driver btusb
[    0.678698] cpufreq_cpu0: failed to get cpu0 regulator: -19
[    0.679520] brcmstb-cpufreq: probe of f03e257c.cpu-clk-div failed with error -17
[    0.680445] sdhci: Secure Digital Host Controller Interface driver
[    0.681154] sdhci: Copyright(c) Pierre Ossman
[    0.681662] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.683415] mmc0: no vqmmc regulator found
[    0.683888] mmc0: no vmmc regulator found
[    0.700207] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    0.701793] ata1.00: ATA-8: HGST HTS545050A7E680, GR2OA3B0, max UDMA/133
[    0.702573] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    0.704336] ata1.00: configured for UDMA/133
[    0.705058] scsi 0:0:0:0: Direct-Access     ATA      HGST HTS545050A7 GR2O PQ: 0 ANSI: 5
[    0.706419] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[    0.707298] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    0.708026] sd 0:0:0:0: [sda] Write Protect is off
[    0.708641] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    0.714199] mmc0: SDHCI controller on f03e0000.sdhci [f03e0000.sdhci] using ADMA
[    0.716149] mmc1: no vqmmc regulator found
[    0.716633] mmc1: no vmmc regulator found
[    0.747194] mmc1: SDHCI controller on f03e0200.sdhci [f03e0200.sdhci] using ADMA
[    0.748187] hidraw: raw HID events driver (C) Jiri Kosina
[    0.748905] usbcore: registered new interface driver usbhid
[    0.749551] usbhid: USB HID core driver
[    0.751939] TCP: cubic registered
[    0.752956] NET: Registered protocol family 10
[    0.753946] NET: Registered protocol family 17
[    0.754710] Bluetooth: RFCOMM TTY layer initialized
[    0.755294] Bluetooth: RFCOMM socket layer initialized
[    0.755460]  sda: sda1 sda2 sda3
[    0.756269] Bluetooth: RFCOMM ver 1.11
[    0.756704] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    0.757319] Bluetooth: BNEP filters: protocol multicast
[    0.757923] Bluetooth: BNEP socket layer initialized
[    0.758500] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    0.759188] Bluetooth: HIDP socket layer initialized
[    0.759821] l2tp_core: L2TP core driver, V2.0
[    0.760059] sd 0:0:0:0: [sda] Attached SCSI disk
[    0.760882] Key type dns_resolver registered
[    0.761451] Registering SWP/SWPB emulation handler
[    0.762307] regulator-dummy: disabling
[    0.764788] ALSA device list:
[    0.765135]   No soundcards found.
INIT: version 2.88 booting
[    0.819761] mmc1: error -84 whilst initialising MMC card
[    0.822230] ata2: SATA link down (SStatus 0 SControl 300)
Starting udev
starting version 230
[    0.864144] random: systemd-udevd: uninitialized urandom read (16 bytes read, 13 bits of entropy available)
[    0.865880] random: systemd-udevd: uninitialized urandom read (16 bytes read, 13 bits of entropy available)
[    0.867058] random: systemd-udevd: uninitialized urandom read (16 bytes read, 13 bits of entropy available)
[    0.868288] random: systemd-udevd: uninitialized urandom read (16 bytes read, 13 bits of entropy available)
[    0.889585] random: udevadm: uninitialized urandom read (16 bytes read, 14 bits of entropy available)
[    0.890843] random: udevadm: uninitialized urandom read (16 bytes read, 14 bits of entropy available)
[    0.891944] random: udevadm: uninitialized urandom read (16 bytes read, 14 bits of entropy available)
[    0.893266] random: udevadm: uninitialized urandom read (16 bytes read, 14 bits of entropy available)
[    0.894818] random: udevadm: uninitialized urandom read (16 bytes read, 14 bits of entropy available)
[    0.896126] random: udevadm: uninitialized urandom read (16 bytes read, 14 bits of entropy available)
[    0.928913] mmc1: error -84 whilst initialising MMC card
[    1.049336] mmc1: error -84 whilst initialising MMC card
[    1.200991] mmc1: error -84 whilst initialising MMC card
[    1.540053] bcmdriver: module license 'Proprietary' taints kernel.
[    1.540788] Disabling lock debugging due to kernel taint
[    1.541808] BCMDRV: Initializing bcmdriver version $ 8
[    1.542435] BCMDRV: Total intc words=4,Total Irqs=129
[    1.543643] BCMDRV: Initialization complete
bootlogd: cannot allocate pseudo tty: No such file or directory
Wed Sep 11 16:25:29 UTC 2019
INIT: Entering runlevel: 5
Configuring network interfaces... [    1.915198] f0b00000.etherne:01: Broadcom BCM7439 (2) PHY revision: 0x10, patch: 1
[    1.917828] f0b00000.ethernet: configuring instance for internal PHY
[    1.918630] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started
Sending discover...
[    3.483070] libphy: f0b00000.etherne:01 - Link is Up - 100/Full
[    3.483808] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending discover...
Sending select for 192.168.0.118...
Lease of 192.168.0.118 obtained, lease time 86400
/etc/udhcpc.d/50default: Adding DNS 192.168.0.1
done.
Starting Dropbear SSH server: Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCEqfRqCn9WKoN+JBAzzJRnc6GaQkYQ7mI9YY2eqJj/TCNfXOkVKCSEG4Spa7pMmiYtM+caOXHR+1GoQ41BxFM54wkqjA+qQMdrA0UXlABPZYilb2T4R5A2G0RyiYEnOO9osvBaRfIcU0qjb4xFOQqf8irmAMbiwMVQl51/Klivno0hIUxWYHykGAwThP/ir/bIpxH2vb+qJQ2wKj91hvudvyALMq0Zpf1aA/LV6c9QB/GgroqISJZXR3NV4Y86KOGt+MhouQrOFs1JrQiQH2cEvlsTSAlsM5wjtuqvHKyoCuHBCfI6MRJBosQ5qb2nEi2fiWu48qH1el2HLU6/x9Ej root@dm900
Fingerprint: md5 72:f5:04:fb:1d:75:4a:f6:8a:3b:46:da:3c:5e:24:ee
dropbear.
Starting autoflashd.
Starting recovery-ui.
Starting tpmd.
Starting internet superserver: xinetd.
Starting Lighttpd Web Server: lighttpd.
2019-09-11 16:25:36: (../../lighttpd-1.4.39/src/log.c.194) server started

opendreambox 2.5.0 dm900 /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.




Top
#19824 - 11/03/19 04:03 PM Re: DM900 rescue mode problem [Re: Pamiko]
Admin Online   content
Japhar Member
Carpal Tunnel

Registered: 10/19/10
Posts: 9876
Try to post here,

https://dreambox.de/board/index.php?board/128-dreambox-dm900-ultrahd-dm920-ultrahd/

And let us know the answers you can get from the Dreambox Forum Support,

Admin
_________________________

Top
#19858 - 11/06/19 09:17 PM Re: DM900 rescue mode problem [Re: Pamiko]
Pamiko Offline
stranger

Registered: 10/27/19
Posts: 5
Hi all

I got an answer
Physically the "mmcblk0"  not visible and this is the  NAND EMMC.

The
mmcblk0p1 PARTLABEL="kernel"
mmcblk0p2 LABEL="dreambox-rootfs"
mmcblk0p2 LABEL="dreambox-data"

partitions shall be located here.
No physhical access at disposal, therefore the image can not be written with flush-tarbal
Can be flashed to a memory card however at restart the factory road-map comes back.
Due to HW failure motherboard replacement recommended!!!

Top
#19859 - 11/06/19 11:12 PM Re: DM900 rescue mode problem [Re: Pamiko]
Toysoft Online   content
Japhar Member
Carpal Tunnel

Registered: 10/22/10
Posts: 2634
Argh... that's not a good news, then probably the Flash chip is defective ?

Missing this, perhaps a corrupted/missing partition table...

Quote:
Found valid GPT with protective MBR; using GPT

Disk /dev/mmcblk0: 7634944 sectors, 3728M
Logical sector size: 512
Disk identifier (GUID): 30f082cc-2877-4689-9b2b-e1812454a613
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7634910

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

Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot1 doesn't contain a valid partition table

Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot0 doesn't contain a valid partition table


TS
_________________________
DM8000, DM800se, DM500HD, DM800HD, DM7025, DM7020s, DM7000, DM500s
VU+ Solo, VU+ Uno, VU+ Duo, Kathrein UFS910
Tivusat, TNTSat, Fransat, SSR/TSR, BBC1-2-3/ITV
DE-OpenBlackHole 1.4 image : http://www.openblackhole.com/

Top
#19890 - 11/09/19 04:13 PM Re: DM900 rescue mode problem [Re: Pamiko]
Admin Online   content
Japhar Member
Carpal Tunnel

Registered: 10/19/10
Posts: 9876
Perhaps you should recreate by hand the missing partitions ?

Go to rescue mode, if you are not already in rescue mode most probably.

Code:
echo "rescue" >> /proc/stb/fp/boot_mode && reboot


Then check the partitions, below you have correct partitions from a working DM900UHD,

Quote:
opendreambox 2.5.0 dm900

>>> Your Dreambox has booted into RESCUE MODE.
>>> Please log in as user 'root' (no password required),
>>> then run 'help' to get further information.

dm900 login: root
root@dm900:~# fdisk -lu

Disk /dev/mtdblock0: 2 MB, 2097152 bytes
255 heads, 63 sectors/track, 0 cylinders, total 4096 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders, total 256 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/mtdblock2: 0 MB, 131072 bytes
255 heads, 63 sectors/track, 0 cylinders, total 256 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock2 doesn't contain a valid partition table

Disk /dev/mtdblock3: 14 MB, 14417920 bytes
255 heads, 63 sectors/track, 1 cylinders, total 28160 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock3 doesn't contain a valid partition table

Disk /dev/mtdblock4: 33 MB, 33554432 bytes
255 heads, 63 sectors/track, 4 cylinders, total 65536 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mtdblock4 doesn't contain a valid partition table
Found valid GPT with protective MBR; using GPT

Disk /dev/mmcblk0: 7634944 sectors, 3728M
Logical sector size: 512
Disk identifier (GUID): 30f082cc-2877-4689-9b2b-e1812454a613
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7634910

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

Disk /dev/mmcblk0boot1: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot1 doesn't contain a valid partition table

Disk /dev/mmcblk0boot0: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders, total 8192 sectors
Units = sectors of 1 * 512 = 512 bytes

Disk /dev/mmcblk0boot0 doesn't contain a valid partition table


And try to recreate the same partitions, that seems to be lost.

Let us know if you get something working,

Admin

DM920UHD :

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

Disk /dev/mmcblk0: 15269888 sectors, 3360M
Logical sector size: 512
Disk identifier (GUID): a157dc9b-d004-44e6-a25a-9c0d96d709f6
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 4194303 2016M 0700 rootfs
3 4194304 15269854 5407M 0700 data


Perhaps you could restore your GPT partitions this way... from rescue partition.

Quote:
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


DM900UHD :

Quote:
opendreambox 2.5.0 dm900

>>> Your Dreambox has booted into RESCUE MODE.
>>> Please log in as user 'root' (no password required),
>>> then run 'help' to get further information.

dm900 login: root
root@dm900:~# fdisk -lu /dev/mmcblk0
Found valid GPT with protective MBR; using GPT

Disk /dev/mmcblk0: 7634944 sectors, 3728M
Logical sector size: 512
Disk identifier (GUID): 30f082cc-2877-4689-9b2b-e1812454a613
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7634910

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


Should be...
Quote:
sgdisk /dev/mmcblk0 -z -n 1:2048:65535 -c 1:kernel -t 1:8301 -n 2:65536:2097151 -c 2:rootfs -t 2:8307 -n 3:2097152: -c 3:data -t 3:8300
_________________________

Top
#19930 - 11/17/19 03:23 PM Re: DM900 rescue mode problem [Re: Admin]
bobyonekenobi86 Offline
stranger

Registered: 11/03/19
Posts: 2
Thanks for brainstorming! smile

The issue is that I am unable to create partitions on a disk what is not present. Unfortunately mmcblk0 is not present in /dev. The OS is not seeing the drive.

My idea was to modify the rescue scripts (luckily it is working with variables). It was successfully created the partitions on a HDD (/dev/sda). The problem is that on a restary it re-reads the ROM and wants to boot from mmcblk0 not sda.

My idea is to extract the rescue image file. modify the scripts, and re program ROM with the modified one, to work from sda instead.

Basically the mmcblk0 drive seems defective.

Top
#19934 - 11/18/19 01:08 AM Re: DM900 rescue mode problem [Re: Pamiko]
Admin Online   content
Japhar Member
Carpal Tunnel

Registered: 10/19/10
Posts: 9876
Good luck, keep us informed. Thank you for the update,

Admin
_________________________

Top
#22192 - 11/01/20 01:03 AM Re: DM900 rescue mode problem [Re: Pamiko]
Johnny_B Offline
VIPF Japhar
enthusiast

Registered: 03/09/15
Posts: 218
Loc: Netherlands
Since I seems to have the same issue as you seems to have,
Same issue as if the nand flash chip has been damaged.
And noticed after (allot of) searching to the fault figured out that in my case the box just worked when I disconnect the front panel.
And thus, as it may seems that there is some issue with the front panel which I still need to find out..

In any case, see in the picture snap to see if you have the same errors before trying it,

It may also be the front panel in your case.
So, see if it also helps you..
Disconnect the flat cable from the front panel.
See with the usb serial mode if the box starts up and which ip it gets.
And test the box by the webif browser.

I'm not claiming that it is, buy may.
It's at least worth to try/


Attachments
Snap1.jpg (24 downloads)

_________________________
Doing nothing leads to nothing.

------------- Please note, for technical support -------------
Will be given here, or on the jb8a8f8 forum and I prefer it in English.
Johnny B.

Click on the banner if you like to go there..

Top
#24838 - 03/12/23 12:56 PM Re: DM900UHD Rescue mode problem [Re: Pamiko]
Toysoft Online   content
Japhar Member
Carpal Tunnel

Registered: 10/22/10
Posts: 2634
I got this, what do you think ?

TS


Attachments
error.jpg


_________________________
DM8000, DM800se, DM500HD, DM800HD, DM7025, DM7020s, DM7000, DM500s
VU+ Solo, VU+ Uno, VU+ Duo, Kathrein UFS910
Tivusat, TNTSat, Fransat, SSR/TSR, BBC1-2-3/ITV
DE-OpenBlackHole 1.4 image : http://www.openblackhole.com/

Top



Moderator:  Emosim 
New Topics
ERROR after flashing OpenPLi 8.X star 20230624
by Sasillo
03/25/24 06:27 PM
Fatal: Target device '/dev/dreambox-rootf
s' is not

by Admin
03/22/24 02:45 PM
EchoStar wins DoD extensions for private 5G
by Admin
03/19/24 02:56 PM
DM900 red light
by slavekpl
03/17/24 03:42 PM
openpli-enigma2-8xst
ar-dm820 epgimport not install

by dmr
03/13/24 09:09 AM
openpli-20240306-GCC
-13.2-dm820

by dmr
03/12/24 01:01 PM
Build your own OSCam... Ubuntu 18 and 22 svn11737
by Admin
03/04/24 10:37 PM
EchoStar bleeds Boost Mobile subscribers
by Admin
03/04/24 04:35 PM
Old DM800HDpvr
by Rtm79
03/03/24 06:32 PM
Saluti
by Rtm79
03/03/24 06:19 PM
DM7020HD : OpenPLi 8.xStar 20240303 GSt 1.20.5
by Admin
03/03/24 12:57 PM
DM7020HD : OpenPLi 8.xStar 20240303 GSt 1.20.5
by Admin
03/03/24 12:57 PM