VU+ stuck at 'Starting...'

[Zartmy]

i dont think that PEB is your issue but i may be wrong
and here is your problem

a faulty tuner card

dvb_bcm7335: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint

Thats just the message you will get when using a close source licensed module under linux. It has nothing todo with a faulty tuner.

[danishdude]

Thats just the message you will get when using a close source licensed module under linux. It has nothing todo with a faulty tuner.

NOW i'm getting confused! (...and it has nothing to do with the whizzky in my glass )

[Zartmy]

16 months old - and the shop washes it's hands, and tells me i have to handle the problem myself, contacting the distributor directly (Digital Nordic Sweden) - as the warranty ran out four months ago. At the same time, they tell me i shouldnt get my hopes up, as i need to provide futher proof to the problem.(!!?) Apparently the serial-dump, showing the exact problem, is not enough - if you ask them.
What else do they want? What else can i do? Beats me...*sigh*

Your shop is talking bull, they have to make the service request from digital nordic. States so very clearly on there homepage -

http://www.digitalnordic.se/egensida/rma-service/501

[stick50jr]

Thats just the message you will get when using a close source licensed module under linux. It has nothing todo with a faulty tuner.

I agree, I get this same message even though my VuDuo is serviceable. The following command was used to check whether my usb tuner was being recognised, but I got the 'tainted' kernel message as well:

dmesg | grep dvb

dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb-usb: found a 'Avermedia TwinStar' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb: found a 'Avermedia TwinStar' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: Avermedia TwinStar successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9035

Your tuner may be stuffed, but this message doesn't provide any indication.

[danishdude]

I am all ears.
/learning-mode ON

[silverfox0786]

I agree, I get this same message even though my VuDuo is serviceable. The following command was used to check whether my usb tuner was being recognised, but I got the 'tainted' kernel message as well:

dmesg | grep dvb

dvb_bcm7335: module license 'Proprietary' taints kernel.
dvb-usb: found a 'Avermedia TwinStar' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9035-01.fw'
dvb-usb: found a 'Avermedia TwinStar' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: Avermedia TwinStar successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_af9035

Your tuner may be stuffed, but this message doesn't provide any indication.

agreed but you dont get this straight after

Disabling lock debugging due to kernel taint

[ashehzad]

Hi Guys,

I am new to this forum, i am having problem upgrading firmware on the VU+duo.
I am trying to upgrade BH 1.6.6 to any new 1.6.7,1.7.X but it failed.
It can only accept 1.6.6

I know, i have to upgrade updrade bootloader fthen i have to upgrade firmware but it fails.
Please see the log below. I can also see there are few bad sector on the Flash i see those errors even when i flash 1.6.6 but it runs OK

Any idea and help would be highly appreciated.


MEMC-00000000 RW=0000000F WW=00000045 G=00000001 R=00000008 W=00000018
MEMC-00000001 RW=00000010 WW=0000004D G=00000001 R=00000009 W=00000006 #$
3
COPY CODE
A567

BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Thu Sep 29 12:01:32 2011 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.

writing vfd

DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tech: 1Gb
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB

Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub

CFE initialized.

checking usb
Loader:elf Filesys:raw Dev:flash0.kernel File: Options:rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3
Loading: 0x80001000/7024928 0x806b4120/124048 Entry address is 0x80540b60
TP1 Entry Address at 0x80000ffc = 80540b60
Starting program at 0x80540b60

Linux version 3.1.1 (vix@buildpc) (gcc version 4.6.4 20120303 (prerelease) (GCC) ) #1 SMP Sat Oct 20 05:45:24 BST 2012
Fetching vars from bootloader... found 11 vars.
Options: sata=1 enet=1 emac_1=1 no_mdio=0 docsis=0 pci=1 smp=1 moca=0 usb=1
Using 256 MB + 128 MB RAM (from CFE)
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Determined physical RAM map:
memory: 10000000 @ 00000000 (usable)
bmem: adding 112 MB RESERVED region at 144 MB (0x07000000@0x09000000)
Zone PFN ranges:
Normal 0x00000000 -> 0x00010000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00010000
PERCPU: Embedded 7 pages/cpu @81203000 s4384 r8192 d16096 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: bmem=112M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw console=ttyS0,115200n8 rootflags=sync
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
Memory: 138144k/262144k available (5436k kernel code, 124000k reserved, 1189k data, 236k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Detected MIPS clock frequency: 404 MHz (202.497 MHz counter)
Console: colour dummy device 80x25
Calibrating delay loop... 403.45 BogoMIPS (lpj=201728)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
SMP: Booting CPU1...
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
SMP: CPU1 is running
Brought up 2 CPUs
devtmpfs: initialized
NET: Registered protocol family 16
PCI2.3->SDRAM window: 512 MB
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.24.
PCI: found device 14e4:8602 on SATA bus, slot 0 (irq 42)
pci 0000:01:00.0: BAR 5: assigned [mem 0x10510000-0x10510fff]
pci 0000:01:00.0: BAR 5: set to [mem 0x10510000-0x10510fff] (PCI address [0x10510000-0x10510fff])
pci 0000:01:00.0: BAR 6: assigned [mem 0x10511000-0x105117ff pref]
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Switching to clocksource upg
cfg80211: Calling CRDA to update world regulatory domain
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 128 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
fuse init (API version 7.17)
msgmni has been set to 269
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
loop: module loaded
brcm-pm: enabling sata clocks
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
scsi0 : sata_brcmstb
scsi1 : sata_brcmstb
ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
Broadcom STB NAND controller (BrcmNand Controller)
bcmemac: Broadcom STB 10/100 EMAC driver v3.0
bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:1d:ec:cb:96:39)
bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
usbcore: registered new interface driver zd1201
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
brcm-pm: enabling usb clocks
ehci-brcm ehci-brcm.0: Broadcom STB EHCI
ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci-brcm ehci-brcm.1: Broadcom STB EHCI
ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-brcm ohci-brcm.0: Broadcom STB OHCI
ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
ata1: SATA link down (SStatus 4 SControl 300)
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
lirc_dev: IR Remote Control driver registered, major 254
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR LIRC bridge handler initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
EBI CS0: setting up NAND flash (primary)
mtd->oobsize=0, mtd->eccOobSize=0
NAND_CS_NAND_XOR=00000001
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Block size=00020000, erase shift=17
NAND Config: Reg=55042200, chipSize=128 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS0

Found NAND on CS0: ACC=d3000000, cfg=55042200, flashId=ecf10095, tim1=4232222d, tim2=00000d94
BrcmNAND version = 0x0201 128MB @00000000
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Found NAND flash on Chip Select 0, chipSize=128MB, usable size=128MB, base=0
brcmnand_scan: B4 nand_select = 40000101
brcmnand_scan: After nand_select = 40000101
page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
Brcm NAND controller version = 2.1 NAND flash size 128MB @18000000
ECC layout=brcmnand_oob_bch4_4k
brcmnand_scan: mtd->oobsize=64
brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
-->brcmnand_default_bbt
brcmnand_default_bbt: bbt_td = bbt_main_descr
Creating 7 MTD partitions on "brcmnand.0":
0x000000000000-0x000007600000 : "rootfs"
0x000007600000-0x000007a00000 : "kernel"
0x000007a00000-0x000007c00000 : "boot"
0x000007c00000-0x000007d00000 : "cfe"
0x000007d00000-0x000007d80000 : "mac"
0x000007d80000-0x000007e00000 : "env"
0x000007e00000-0x000007f00000 : "nvm"
UBI: attaching mtd0 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-8: ST3500312CS, SC13, max UDMA/133
ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 0/32)
ata2.00: configured for UDMA/133
scsi 1:0:0:0: Direct-Access ATA ST3500312CS SC13 PQ: 0 ANSI: 5
sd 1:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sda: sda1
sd 1:0:0:0: [sda] Attached SCSI disk
UBI: max. sequence number: 93
UBI: attached mtd0 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 118 MiB
UBI: number of good PEBs: 941
UBI: number of bad PEBs: 3
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 941
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 1615474374
UBI: background thread "ubi_bgt0d" started, PID 45
UBIFS: parse sync
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 116436992 bytes (113708 KiB, 111 MiB, 917 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:13.
devtmpfs: mounted
Freeing unused kernel memory: 236k freed
INIT: version 2.88 booting
EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sda1): recovery complete
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
procmk_init
dvb_bcm7335: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
DVB: registering new adapter (bm750)
bcm7335: hotplug_callback():
Hotplug - status.connected 0
CPU 0 Unable to handle kernel paging request at virtual address c06c7790, epc == c06c7790, ra == 80074244
Oops[#1]:
Cpu 0
$ 0 : 00000000 10008700 c06c7790 00060000
$ 4 : 0000000d c0abe9e4 00000000 00000048
$ 8 : 10008700 1000001f 00000000 00000800
$12 : 00000000 80678398 0000000a 7faa4718
$16 : 88496400 00010000 00000000 00000000
$20 : 0000000d 8063ed80 80640000 806c0000
$24 : 0000004f 779fce28
$28 : 884d2000 884d3778 805d1f64 80074244
Hi : 00000000
Lo : 00004e84
epc : c06c7790 0xc06c7790
Tainted: P
ra : 80074244 handle_irq_event_percpu+0x78/0x310
Status: 10008302 KERNEL EXL
Cause : 00800008
BadVA : c06c7790
PrId : 0002a044 (Brcm4380)
Modules linked in: procmk
Process modprobe (pid: 96, threadinfo=884d2000, task=88de5218, tls=77b79490)
Stack : 380754db 0000000a 10008700 00000000 81203580 80648160 8063ed80 00010000
00000001 00000020 00001400 fffff7ff 88ec8480 806d0000 88eb4400 8007452c
81203508 806480a0 00000100 8007b07c 00000100 8063e640 8063ed80 800773d0
00000000 8063e664 00000100 8063e640 0000000a 00000000 0000000d 80073964
88eb4400 80077f48 806b3b40 8002523c 00000000 80006854 00000009 00000000
...
Call Trace:
[<8007452c>] handle_irq_event+0x50/0x84
[<8007b07c>] __rcu_process_callbacks+0x60/0x478
[<800773d0>] handle_level_irq+0xd8/0x188
[<80073964>] generic_handle_irq+0x34/0x54
[<80077f48>] handle_percpu_irq+0x8c/0xc0
[<8002523c>] task_tick_fair+0x58/0x170
[<80006854>] do_IRQ+0x18/0x24
[<80002324>] brcm_intc_dispatch+0x90/0x220
[<8003a070>] do_softirq+0xa4/0xac
[<80002710>] plat_irq_dispatch+0xc8/0x104
[<8002adbc>] find_busiest_group+0x208/0xa64
[<80004a84>] ret_from_irq+0x0/0x4
[<80358b60>] brcmnand_cache_is_valid.constprop.11+0x74/0x268
[<8029daf0>] __udelay+0x40/0x50
[<803579b8>] brcmnand_ctrl_writeAddr+0xa4/0xe8
[<8035abbc>] brcmnand_ctrl_posted_read_cache+0xd8/0x8fc
[<803577f0>] brcmnand_read_page+0x110/0x234
[<80357dbc>] brcmnand_release_device+0x38/0x60
[<80359920>] brcmnand_do_read_ops+0xfc/0x2c0
[<80359bac>] brcmnand_read+0xc8/0x13c
[<80335558>] part_read+0x8c/0x138
[<80367cc4>] ubi_eba_read_leb+0x194/0x320
[<80369d48>] ubi_io_read+0x98/0x1bc
[<80367c60>] ubi_eba_read_leb+0x130/0x320
[<80367088>] ubi_leb_read+0xdc/0x164
[<802199b0>] ubifs_leb_read+0x34/0xa4
[<80004358>] brcmstb_send_ipi_mask+0x30/0x70
[<8007b07c>] __rcu_process_callbacks+0x60/0x478
[<8021c68c>] fallible_read_node+0x64/0x1b8
[<8021dc64>] ubifs_lookup_level0+0xd4/0x1f8
[<80550000>] __kprobes_text_end+0x13b8/0x1670
[<80012890>] local_r4k_flush_data_cache_page+0x0/0x10
[<8021dea4>] ubifs_tnc_locate+0x11c/0x244
[<80210500>] do_readpage+0x2d8/0x604
[<800870e8>] __alloc_pages_nodemask+0xec/0x630
[<80212a90>] ubifs_readpage+0x60/0x430
[<8007fd50>] add_to_page_cache_locked+0x9c/0x1cc
[<800825c4>] filemap_fault+0x434/0x5c0
[<800a04ac>] __do_fault+0x8c/0x708
[<800a439c>] handle_pte_fault+0x128/0xa7c
[<800a0c28>] tlb_flush_mmu+0x78/0xa4
[<800a1100>] free_pgtables+0xd0/0x110
[<800a4db4>] handle_mm_fault+0xc4/0x120
[<80010838>] do_page_fault+0x128/0x330
[<80022f2c>] set_next_entity+0x40/0x8c
[<800253e8>] pick_next_task_fair+0x94/0x110
[<800a75a0>] remove_vma+0x64/0xac
[<8054ae58>] __schedule+0x118/0x9cc
[<800a87c4>] do_munmap+0x1cc/0x344
[<800a9ec4>] sys_munmap+0x4c/0x68
[<80004a60>] ret_from_exception+0x0/0x24


Code: (Bad address in epc)

---[ end trace e65f297c518e5117 ]---
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 180 seconds..

[judge]

original box or clone?

[srprizze]

How to flash / Upgrade Vu+ Uno via USB memory stick
How to flash a VU+ Uno using a USB stick
Quick guide how to flash a VU+ Uno receiver with a USB stick. Tools required are just your favourite image and at least a 128mb memory stick formatted FAT32.

1. Format you memory stick on you PC FAT32.
2. Create a directory in called vuplus.
3. Within the the vuplus directory create another folder called uno.
4. Unzip the USB upgrade files (4) into that directory.
The 4 files are :
boot_cfe_auto.jffs2
kernel_cfe_auto.bin
root_cfe_auto.jffs2
splash_cfe_auto.bin
5. Power off your VU+ Uno.
6. Insert memory stick into front USB slot.
7. Power on your VU+ Uno and follow the on screen instructions.

On Screen Instructions will include press ch- on the Uno [not remote] to initiate flash
This must be done within 10 seconds as i have found or it will boot box as normal
once done it will advise you to remove USB Stick and reboot

Thats it your done.

[finbarr]

Hi guys,

I have a similar issue to the OP when using my Vu Duo running Vix 808. I've re flashed a couple of times, but still see the issue.

Problem: i have a power timer set to reboot the box during the night, but once or twice a week, the box is stuck with the 'Starting...' Message on the front panel. (no red right though)

Box details:
- Genuine duo bought from world of sat.
- I have a USB key in the back, formatted by Vix. With an active 64MG swap, and holds EPG data from XMLTV for 28,2E + picons.
- I have a Sony PlayTV DVB-T dual tuner plugged in.

Plugins installed:
- MyMatrix active skin
- Ondemand
- ocram shd picons
- dib0700 drivers from feeds.

I don't have logs from a time when it happened, but I do have logs from a good startup which might help. I will post those in a minute. Some interesting things I see in the logs (are these bad??)

root@vuduo:~# cat /var/log/messages | grep -i peb
Jan 1 01:00:31 vuduo user.notice kernel: UBI: number of good PEBs: 939
Jan 1 01:00:31 vuduo user.notice kernel: UBI: number of bad PEBs: 5
Jan 1 01:00:31 vuduo user.notice kernel: UBI: number of corrupted PEBs: 0
Jan 1 01:00:31 vuduo user.notice kernel: UBI: available PEBs: 0
Jan 1 01:00:31 vuduo user.notice kernel: UBI: total number of reserved PEBs: 939
Jan 1 01:00:31 vuduo user.notice kernel: UBI: number of PEBs reserved for bad PEB handling: 9
root@vuduo:~#



cat /var/log/messages | grep -i "kernel t"
Jan 1 01:00:31 vuduo user.warn kernel: Disabling lock debugging due to kernel taint
root@vuduo:~#

[finbarr]

Log

message.log

[judge]

Could be off track here, but last lines of that log read:

Mar  5 22:09:31 vuduo daemon.notice automount[655]: >> mount: mounting /dev/logs on /autofs/logs failed: No such file or directory
Mar  5 22:09:31 vuduo daemon.err automount[655]: mount(generic): failed to mount /dev/logs (type auto) on /autofs/logs
Mar  5 22:09:31 vuduo daemon.err automount[655]: failed to mount /autofs/logs

Have you now or ever had network mounts set-up on the Duo?

[finbarr]

Nope, never set up shares or mounts.

[mickyblueys]

I had this issue on both my duo's, it is quite common, to get around the issue, I cancelled my reboot power timer and set it to just restart the gui instead, this resets the boxes clock so that my epg and autobouquets still do there daily updates. ......So now I haven't had the ...starting....problem since!

Hope this helps.

Sent from my GT-I9195 using Tapatalk

[finbarr]

Just to report that your fix has worked beautifully after more than a week or testing. Not a single Starting... message staying put. Cheers MickyB