Red Light at Start-Up

[plusser]

Hello guys.
Is this normal (v2.3) - when I turn my box off at the back, it's difficult to restart. The red light comes on and that's it. I have to wait quite a bit of time to get it to go to "starting". Sometimes just 30 seconds, often longer.
Just wondering whether I should tolerate this or send it back before it fails completely.

Cheers,
+er

[Sicilian]

This does happen sometimes. Best thing to do is wait a few mins before powering on.

[pooface]

This does happen sometimes. Best thing to do is wait a few mins before powering on.

As Sic says ... linux boxes can be fiddly when turning off power. It's always best to turn off, leave for a minute or two, and then power on...

[Sicilian]

Another thing, when shutting down try to always use the power menu i.e. hold down standy button on remote and select Deep Standby, once fully off, turn off power.

[MalteseMick]

I get the same issue where sometimes it completely refuses to boot, I end up repeatedly turning it off and on until I get the 'Starting...' text.

[Sicilian]

I get the same issue where sometimes it completely refuses to boot, I end up repeatedly turning it off and on until I get the 'Starting...' text.

I wouldn't repeatedly turn it off, just leave unplugged for a minute or so.

[Larry-G]

I get the same issue where sometimes it completely refuses to boot, I end up repeatedly turning it off and on until I get the 'Starting...' text.

your receiver is basically a linux based pc and turning it on and off repeatedly in quick succession could easily lead it to the point where it will no longer boot at all

[MalteseMick]

I've left the box on the red light for half an hour with no boot, I've pulled the power out for 10 minutes and it still wouldn't boot. Whatever is going on in that BIOS it doesn't like being shut down unexpectedly, the only time I usually do this is when the box has frozen otherwise I always shut down/restart via menu. I understand turning it off and on isn't ideal but the randomness of when it decides to boot or not leaves me with little choice but trial and error.

[Hakon]

Had the same problem with my VU+ Duo , it didn't behave like this as new. I send it back and they put in new motherboard and powersupply, have been rebooting as aspected since this warranty repair. In sweden whe have the possibility to proclaim warranty for 3 years,so it was important for me to have this done as soon i find he fault.If it will happen again within 3 years i can proof that this fault has happend before,so it will again be a warranty repair.

[Stanman]

Lucky Swedes, here its 12 months or your fooked, can try under EU regs buts a lot of hassle.

[pooface]

Lucky Swedes, here its 12 months or your fooked, can try under EU regs buts a lot of hassle.

Have heard lots of people saying that realistically (and successfully in some cases), you have a case of getting it looked at up to 6 years after you bought it, as you have purchased it to do a job, and it should work for a realistic length of time ... Never tried it myself tho...

Sent from my HTC Desire

[fintannl]

personally, if something doesn't boot normally, i open it up and disconnect all extra hardware such as tuners hard disk etc.. then basically boot only the mainboard. If this works ok then it is one of the extra pieces of hardware that is causing the problem, so connect back in one at a time until you hit the problem. Then you have figured where the problem lies. If it still won't boot normally with all extras disconnected it can only be power or mainboard that can be at fault

[pooface]

personally, if something doesn't boot normally, i open it up and disconnect all extra hardware such as tuners hard disk etc.. then basically boot only the mainboard. If this works ok then it is one of the extra pieces of hardware that is causing the problem, so connect back in one at a time until you hit the problem. Then you have figured where the problem lies. If it still won't boot normally with all extras disconnected it can only be power or mainboard that can be at fault

If it was something I'd built myself, then yes, I agree with you... But, with something like this, I'd get on to the manufacturer/supplier, and let them deal with it. If they were prepared to send out the offending item if you took the trouble to diagnose it like that, then I would. Otherwise (since they likely would want you to send everything back), I'd save myself the hassle...

[plusser]

Thanks for the replies...but I'm still no nearer deciding whether I should send it back (ie. fault will eventually lead to a fail) or simply ignore it.

+er

[fintannl]

answer simple, inside warranty send back, outside warranty play as i suggest until you identify issue

[Sicilian]

Fintannl, does have a point. I've seen a unit do this, unplugged Ethernet cable and all booted fine. Swapped the cable for another and all carried on booting fine.

[Hakon]

personally, if something doesn't boot normally, i open it up and disconnect all extra hardware such as tuners hard disk etc.. then basically boot only the mainboard. If this works ok then it is one of the extra pieces of hardware that is causing the problem, so connect back in one at a time until you hit the problem. Then you have figured where the problem lies. If it still won't boot normally with all extras disconnected it can only be power or mainboard that can be at fault
I disconnected all from my box, no HDD, no USB ,no cables to LNB/network, nothing connected just powercable and original image.It was not a software problem that i could do something about.The dealer tested to and the solution was new hardware inside. But i made a intresting test when it was faulty, a freezeblock in a plasticbag and this tight to the CPU so it was really cooled, now the reboot worked properly. So my idea was that the CPU was overheated in some way.

[fintannl]

now i haven't had issue to yet open my vu+ thank god but I would expect that if I did open it that there would be pins to allow the insertion of an extra 5V or 12V fan if such was required. however i'm a bit surprised that the vu+ would have cpu heating issues considering the amount of internal free space in the box. as said previously if this box is within warranty then send it back

[MalteseMick]

I'm having about one crash every two or three days with the VIX rotating image just staying on the screen and nothing responding until you do a hard reboot - this doesn't leave a crash log as it doesn't green screen. I've figured out that instead of turning it off and on via the switch on the back if I do a reboot via telnet it prevents any of the booting issues.

Simply telnet into your box and use the 'reboot' command when the remote is unresponsive.

[Likvid]

This is normal with the red light if you power on the receiver too fast, it's a safety procedure to protect the PSU from overloading, the DM800 has the same principle that you have to wait when you switch the power at the back, wait 5-10 seconds and then switch it on and it will work.

[plusser]

UPDATE: I no longer use an external USB hard drive, but rather an internal SATA. Since making this change, I do not have the "red light at stat-up" problem - box boots first time, every time.

+er

[HeRmAN]

I have now a similar annoying problem.

It started this morning when we had a thunder storm so I turned the Vu+Duo off by the remote (long press on the remote and then select turn off)
I waited longer than normal but it didn't shut down so I pulled the plug anyway.

Later today when I was going to start it up it was stuck at showing the one of the startup sceens on the TV (I may have been the loading Enigma II but I don't remember) and the VIX icon was spinning.
I re.booted the unit by turning of at the back, wait for 10s and powered it back on again.

Now the LED is red and the display shows "Starting ..."
then it switches over to showing "VuDuo" at the display, the red LED goes off and the tv shows the "Starting..." image
then shortly after it switches to show the blurred image "Shutting down" and then the device switches off !!

If I try to start it by either the remote or by re-booting with the power is does the same all over and I can't start it at all.
Very annoying :mad:

I guess that it has "Shut down" on it's to do list....
Any tip on what I can do to solve the issue except to reinstall the firmware and all other stuff.
I'm using VIX 2.0 in it now.
Edit> (both card slots are empty when I tried this but the HD is still in)

[punisher]

remove any usb devices you may have connected, leave it off for a bit and try switching it back on (see if you can access ftp or telnet) and if all else fails then i guess you might need to reflash

[HeRmAN]

Don't use any USB devices and I also un-plugged the eth cable, Nothing works.
I will try to log what comes out on the console port before I reflash it to see if there are any clues of this behaviour.
just trying to find the serial port settings, speed etc.

[HeRmAN]

115200, 8/1/N no flow control seams to be used on the RS232 port

This is what comes out at start-up while the Display shows "Starting..."

BCM73350010
012
Shmoo Version=1.9

MEMC-00000000 RW=00000011 WW=0000004B G=00000001 R=00000008 W=00000017
MEMC-00000001 RW=0000000F WW=00000053 G=00000001 R=00000007 W=00000005 #$
3
COPY CODE
A567

BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Wed Dec 9 17:23:18 2009 (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/3800452 0x803a0d84/176784 Entry address is 0x8037e000
TP1 Entry Address at 0x80000ffc = 8037e000
Starting program at 0x8037e000

<5>Linux version 2.6.18-7.3 (andyblac@MacPro) (gcc version 4.4.4 (GCC) ) #1 SMP Wed Feb 9 01:16:37 GMT 2011
Fetching vars from bootloader... OK (E,D,B,C)
Detected 256 MB on MEMC0 (strap 0xe5430060)
CFE EnvVar: LINUX_FFS_STARTAD: 00000000, LINUX_FFS_SIZE: 07600000
CFE EnvVar: LINUX_PART_STARTAD: 07600000, LINUX_PART_SIZE: 00200000
g_board_RAM_size=256MB
Options: sata=1 enet=1 emac_1=1 no_mdio=0 docsis=0 ebi_war=0 pci=1 smp=1
CPU revision is: 0002a044
FPU revision is: 00130001
Determined physical RAM map:
memory: 10000000 @ 00000000 (usable)
User-defined physical RAM map:
node [00000000, 09000000: RAM]
node [09000000, 07000000: RSVD]
<5>Reserving 112 MB upper memory starting at 09000000
<7>On node 0 totalpages: 65536
<7> DMA zone: 65536 pages, LIFO batch:15
Built 1 zonelists. Total pages: 65536
<5>Kernel command line: rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3 console=ttyS0,115200
Primary instruction cache 32kB, physically tagged, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, linesize 64 bytes.
Synthesized TLB refill handler (23 instructions).
Synthesized TLB load handler fastpath (37 instructions).
Synthesized TLB store handler fastpath (37 instructions).
Synthesized TLB modify handler fastpath (36 instructions).
PID hash table entries: 2048 (order: 11, 8192 bytes)
Found MIPS counter frequency: 203 Mhz
Using 202.502 MHz high precision timer.
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 141056k/262144k available (3020k kernel code, 120900k reserved, 548k data, 140k init, 0k highmem)
Mount-cache hash table entries: 512
Checking for 'wait' instruction... available.
plat_prepare_cpus: ENABLING 2nd Thread...
TP0: prom_boot_secondary: Kick off 2nd CPU...
CPU revision is: 0002a044
FPU revision is: 00130001
Primary instruction cache 32kB, physically tagged, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, linesize 64 bytes.
Synthesized TLB refill handler (23 instructions).
Brought up 2 CPUs
migration_cost=1000
NET: Registered protocol family 16
registering PCI controller with io_map_base unset
registering PCI controller with io_map_base unset
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
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: 4096 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 4096)
TCP reno registered
brcm-pm: disabling power to USB block
brcm-pm: disabling power to ENET block
brcm-pm: disabling power to SATA block
audit: initializing netlink socket (disabled)
audit(946684800.330:1): initialized
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc.
yaffs Feb 9 2011 01:16:35 Installing.
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 22) is a 16550A
loop: loaded (max 8 devices)
brcm-pm: enabling power to ENET block
Broadcom BCM7335 P20 Ethernet Network Device v2.0 Feb 9 2011 01:16:15
Config Internal PHY Through MDIO: 100 MB Full-Duplex (auto-neg)
Broadcom STB NAND controller (BrcmNand Controller)
i=0, CS[0] = 0
brcmnand_probe: CS0: dev_id=ecf10095
NAND Config: Reg=55042200, chipSize=128 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
timing1 not adjusted: 5363444f
timing2 not adjusted: 00000fc6
BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB

Found NAND: ACC=d3000000, cfg=55042200, flashId=ecf10095, tim1=5363444f, tim2=00000fc6
BrcmNAND version = 0x0201 128MB @00000000
brcmnand_probe: CS0: dev_id=ecf10095
Found NAND chip on Chip Select 0, chipSize=128MB, usable size=128MB, base=0x
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
mtd->oobsize=64, mtd->eccOobSize=16
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: bbt_td = bbt_main_descr
brcmnandCET: Status -> Deferred
numchips=1, size=8000000
Creating 7 MTD partitions on "bcm7xxx-nand.0":
0x0000000000000000-0x0000000007600000 : "rootfs"
0x0000000007600000-0x0000000007800000 : "kernel"
0x0000000007800000-0x0000000007c00000 : "boot"
0x0000000007c00000-0x0000000007d00000 : "cfe"
0x0000000007d00000-0x0000000007d80000 : "mac"
0x0000000007d80000-0x0000000007e00000 : "env"
0x0000000007e00000-0x0000000007f00000 : "nvm"
usbmon: debugfs is not available
ehci_hcd_brcm_init: Initializing 2 EHCI controller(s)
brcm-pm: enabling power to USB block
10 Dec 2004 USB 2.0 'Enhanced' Host Controller (EHCI) Driver (EHCI-brcm-0)
drivers/usb/host/ehci-brcm.c: starting brcm EHCI USB Controller
- USB h/w setup mode <B>
- USB power enable set for active HIGH mode
brcm-ehci brcm-ehci.0: BRCM EHCI
brcm-ehci brcm-ehci.0: new USB bus registered, assigned bus number 1
brcm-ehci brcm-ehci.0: irq 62, io mem 0x10480300
brcm-ehci brcm-ehci.0: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
10 Dec 2004 USB 2.0 'Enhanced' Host Controller (EHCI) Driver (EHCI-brcm-1)
drivers/usb/host/ehci-brcm.c: starting brcm EHCI USB Controller
brcm-ehci-1 brcm-ehci-1.1: BRCM EHCI
brcm-ehci-1 brcm-ehci-1.1: new USB bus registered, assigned bus number 2
brcm-ehci-1 brcm-ehci-1.1: irq 57, io mem 0x10480500
brcm-ehci-1 brcm-ehci-1.1: USB 0.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd_brcm_init: Initializing 2 OHCI controller(s)
2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (OHCI-brcm-0)
drivers/usb/host/ohci-brcm.c: starting brcm OHCI USB Controller
- Resetting at b0480408
<-- brcm_start_hc
brcm-ohci-0 brcm-ohci-0.0: BRCM OHCI
brcm-ohci-0 brcm-ohci-0.0: new USB bus registered, assigned bus number 3
brcm-ohci-0 brcm-ohci-0.0: irq 63, io mem 0x10480400
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (OHCI-brcm-1)
drivers/usb/host/ohci-brcm.c: starting brcm OHCI USB Controller
- Resetting at b0480608
<-- brcm_start_hc
brcm-ohci-1 brcm-ohci-1.1: BRCM OHCI
brcm-ohci-1 brcm-ohci-1.1: new USB bus registered, assigned bus number 4
brcm-ohci-1 brcm-ohci-1.1: irq 64, io mem 0x10480600
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
pegasus: v0.6.13 (2005/11/13), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new driver pegasus
drivers/usb/net/rtl8150.c: rtl8150 based usb-ethernet driver v0.6.2 (2004/08/27)
usbcore: registered new driver rtl8150
usbcore: registered new driver asix
usbcore: registered new driver cdc_ether
usbcore: registered new driver net1080
usbcore: registered new driver zaurus
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
VFS: Mounted root (jffs2 filesystem).
Freeing unused kernel memory: 140k freed

After this the display on the front panel switches to VuDuo and the following appear on the console port

INIT: version 2.86 booting
Please wait: booting...
mount: sysfs already mounted or /sys busy
mount: according to mtab, sysfs is already mounted on /sys
Root filesystem already rw, not remounting
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for Belkin / Peracom / GoHubs USB Serial Adapter
usbcore: registered new driver belkin
drivers/usb/serial/belkin_sa.c: USB Belkin Serial converter driver v1.2
dvb_bcm7335: module license 'Proprietary' taints kernel.
$Id: bcm7335_init.c Ver. 0.1$
DVB: registering new adapter (BM750S)
bcm7335: hotplug_callback():
Hotplug - status.connected 1
bcm7335: hotplug_callback():
Hotplug - connecting HDMI to display 0xe
brcm_demux_init: $Id: bcm7335_demux.c,v 0.6 $
[VID]: <6>bcm7335_video_init
[AUD]: <6>bcm7335_audio_init
[AUD]: Open sync channel for decode
DVB: registering adapter 0 frontend 0 (BCM7335 FE)...
DVB: registering adapter 0 frontend 0 (BCM7335 FE)...
[MPVR]: >> misc_pvr_init
input: dreambox remote control (native) as /class/input/input0
[LCD]: registered
[CI]:-BM750_PCB_2_1

[CI]: registered ci0
[CI]: registered ci1
[DFP]: registered dbox fp
[DFP]: bcm7335_i2c_write: Error 1114113

[DFP]: bcm7335_max_i2c_write: Error 1114113

[DFP]: Scart 4707 is found 4

[SC]: registered sci0
[SC]: registered sci1
bm750_system_time_set wakeup mode get
bm750_system_time_set wakeup mode get 0xc4
procmk_init
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Serial Device
usbcore: registered new driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
drivers/usb/serial/usb-serial.c: USB Serial support registered for Keyspan - (without firmware)
drivers/usb/serial/usb-serial.c: USB Serial support registered for Keyspan 1 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for Keyspan 2 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for Keyspan 4 port adapter
usbcore: registered new driver keyspan
drivers/usb/serial/keyspan.c: v1.1.4:Keyspan USB to Serial Converter Driver
NTFS driver 2.1.27 [Flags: R/W MODULE].
drivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
usbcore: registered new driver pl2303
drivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
usbcore: registered new driver rt73
brcm-pm: enabling power to SATA block
ata1: SATA max UDMA/133 cmd 0xB0510000 ctl 0xB0510020 bmdma 0xB0510030 irq 42
ata2: SATA max UDMA/133 cmd 0xB0510100 ctl 0xB0510120 bmdma 0xB0510130 irq 42
scsi0 : sata_svw
ata1: SATA link down (SStatus 4 SControl 300)
ATA: abnormal status 0x7F on port 0xb051001c
scsi1 : sata_svw
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl F0000)
ata2.00: ATA-8, max UDMA/133, 3907029168 sectors: LBA48 NCQ (depth 0/32)
ata2.00: ata2: dev 0 multi count 0
ata2.00: configured for UDMA/133
Vendor: ATA Model: Hitachi HDS72202 Rev: JKAO
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 3907029168 512-byte hdwr sectors (2000399 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
SCSI device sda: 3907029168 512-byte hdwr sectors (2000399 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write back
sda: sda1
sd 1:0:0:0: Attached scsi disk sda
sd 1:0:0:0: Attached scsi generic sg0 type 0
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is recommended
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
SGI XFS with no debug enabled
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_SELECT_SOURCE 1
[VID]: VIDEO_PLAY 1 2 0
[VID]: VIDEO_CONTINUE 1 1
[VID]: VIDEO_CLEAR_BUFFER 1 1 0
logger: mount: mount point /media/sdb1 does not exist
[VID]: VIDEO_STOP 0 1
[VID]: VIDEO_SELECT_SOURCE 0
ALSA: Restoring mixer settings...
Configuring network interfaces... done.
Starting portmap daemon: portmap.
Mounting remote filesystems...
vm.dirty_writeback_centisecs = 300
vm.dirty_background_ratio = 1
vm.dirty_ratio = 60
hwclock: can't open '/dev/misc/rtc': No such file or directory
INIT: Entering runlevel: 3
Starting system message bus: dbus.
Starting Dropbear SSH server: dropbear.
starting Busybox Periodic Command Scheduler: crond... done.
crond[445]: crond (busybox 1.15.3) started, log level 8

Starting internet superserver: inetd.
creating NFS state directory: /etc/rc3.d/S20nfsserver: line 149: can't create sm/state: No space left on device
done
starting 8 nfsd kernel threads: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
done
starting mountd: done
starting statd: done
exportfs: Warning: /media/hdd2/ does not exist
exportfs: Warning: /media/usb does not support NFS export.
exportfs: can't open /var/lib/nfs/etab.tmp for writing
exportfs: can't open /var/lib/nfs/xtab.tmp for writing
Starting Samba: smbd nmbd.
Starting syslogd/klogd: done
* starting FTP Server: vsftpd... done.
* Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
...fail!
/usr/bin/enigma2.sh: line 14: can't create /home/root/Enigma2-01-01-2000_00-01-48.log: No space left on device
INIT: Sending processes the TERM signal
Stopping Dropbear SSH server: stopped /usr/sbin/dropbear (pid 438)
dropbear.
* Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon
...fail!
stopping Busybox Periodic Command Scheduler: crond... stopped crond (pid 445)
done.
Stopping system message bus: stopped process in pidfile '/var/run/dbus/pid' (pid 425)
dbus.
Stopping internet superserver: inetd.
exportfs: can't open /var/lib/nfs/etab.tmp for writing
exportfs: can't open /var/lib/nfs/xtab.tmp for writing
stopping statd: done
stopping mountd: done
stopping nfsd: nfsd: last server has exited
nfsd: unexporting all filesystems
done
removing nfsd kernel module: done
Stopping Samba: smbd nmbd.
* stopping FTP Server: vsftpd... no /usr/sbin/vsftpd found; none killed
ALSA: Storing mixer settings...
Unmounting remote filesystems...
Deconfiguring network interfaces... done.
Stopping syslogd/klogd: stopped syslogd (pid 500)
stopped klogd (pid 502)
done
Sending all processes the TERM signal...
!!!BKNI_WaitForEvent exit
Sending all processes the KILL signal...
hwclock: can't open '/dev/misc/rtc': No such file or directory
/etc/rc0.d/S25save-rtc.sh: line 5: can't create /etc/timestamp: No space left on device
Stopping portmap daemon: portmap.
Deactivating swap...
Unmounting local filesystems...
[VID]: VIDEO_SET_STREAMTYPE 0
[VID]: VIDEO_SELECT_SOURCE 1
[VID]: VIDEO_PLAY 1 2 0
[VID]: VIDEO_CONTINUE 1 1
[VID]: VIDEO_CLEAR_BUFFER 1 1 0
[VID]: VIDEO_STOP 0 1
[VID]: VIDEO_SELECT_SOURCE 0
And then it switches off leaving the red LED on and no text in the display on the front panel.

Any clues of what may be wrong?
I guess my next step is to upgrade to an official FW to see if I can wake it up unless anyone has some other bright idea?!

[HeRmAN]

The upgrade to official fw 5.9 via USB went well so I guees that part of the previous image was corrupt :-(
and since the box is working I will try to get back to the nice VIX image (current version)

[pooface]

Looking through your log, I saw the following:


/usr/bin/enigma2.sh: line 14: can't create /home/root/Enigma2-01-01-2000_00-01-48.log: No space left on device
INIT: Sending processes the TERM signal

Looks like it's ran out of space... Before there, I noticed something about not being able to find hdd or something... So looks like the hdd didn't mount, and it couldn't write to it at some point, so wrote to the flash, and then ran out space... Had a problem like that once before, and iirc, the box just stopped loading (not shutting down tho, ust stopped)...

[Alias1]

Hence we learn the value of doing backups :)

[HeRmAN]

Well, I'm back with a working unit again.
I didn't have any backup but I have made notes of how to configure most things the way I want so it wasn't that bad and I also got my notes updated.
The tricky part for a newbie in Linus was to get CCcam and install it even I had the files from the last time I did it (but I hadn't made any notes of how and it wasn't a ipk package then)
The time time consuming part was to do a new service scan....
The picions isn't working even I did downloaded them again for but they don't appear anyway
So now (When I get the time for it) I will try to learn how to do a backup of the configuration and my settings to my server.
The good with the bad is that I now have 2.2 instead of 2.0 :-)

The confusing part is why it showed "No space left on device". Can it happen again, Is there any hardware issues?
(I bought the unit 1st of July last Year...)
But that's anyway for the hints.

[pooface]

Well, I'm back with a working unit again.
I didn't have any backup but I have made notes of how to configure most things the way I want so it wasn't that bad and I also got my notes updated.
The tricky part for a newbie in Linus was to get CCcam and install it even I had the files from the last time I did it (but I hadn't made any notes of how and it wasn't a ipk package then)
The time time consuming part was to do a new service scan....
The picions isn't working even I did downloaded them again for but they don't appear anyway
So now (When I get the time for it) I will try to learn how to do a backup of the configuration and my settings to my server.
The good with the bad is that I now have 2.2 instead of 2.0 :-)

The confusing part is why it showed "No space left on device". Can it happen again, Is there any hardware issues?
(I bought the unit 1st of July last Year...)
But that's anyway for the hints.

Only time you will get the "No space left on device" is when you store too much on the flash on the box. It could be that your log files were taking up all of the nand flash space, so no storage left...

From what I remember, there will usually be around 60-65mb free after you've installed channels etc and set up the box (no plugins installed). When you install plugins, it uses your flash. If you store you picons on the internal flash, that consumes space too. The log files you create consume space (hence why it's suggested to only turn them on if we ask you to for debugging purposes).

I had a problem with my box, when I changed things over and disconnected my hdd. I found that instead of my usb being mounted as /media/usb (since /dev/sdb1 -> /media/usb & /dev/sda1 -> /media/hdd in fstab), the usb stick became /dev/sda1 instead of /dev/sdb1. So, /media/hdd was my usb stick, and /media/usb was internal flash. I was using the image manager to take backups to /media/usb, and so when it created the backup, it filled the flash memory, not the usb memory. Another reason why mount manager should be used to create your mounts, not fstab (I was testing summat at the time :p)

In most situations, you will not fill up flash, but that's how it happened to me, and it can be easily possible when messing with things.

Hope this helps

[HeRmAN]

The logs are limited to maximum 4MB (default I think) so that should not be the reason.

root@vuduo:~# free
total used free shared buffers
Mem: 141412 130688 10724 0 512
Swap: 0 0 0
Total: 141412 130688 10724
the above will show the ram usage in the box, how about the flash usage? Any similar command available?

[pooface]

The logs are limited to maximum 4MB (default I think) so that should not be the reason.

root@vuduo:~# free
total used free shared buffers
Mem: 141412 130688 10724 0 512
Swap: 0 0 0
Total: 141412 130688 10724
the above will show the ram usage in the box, how about the flash usage? Any similar command available?

Try running "df -h":


Filesystem Size Used Available Use% Mounted on
/dev/root 122.0M 51.2M 70.8M 42% /
tmpfs 64.0K 12.0K 52.0K 19% /dev
/dev/sdb1 29.3G 3.1G 25.6G 11% /media/usb
/dev/sda1 1.8T 248.5G 1.6T 13% /media/hdd
tmpfs 155.4M 3.9M 151.5M 3% /var/volatile
tmpfs 155.4M 0 155.4M 0% /dev/shm

It's the dev/root

[HeRmAN]

Thanks, good to have in mind if it happens again to me or if someone with similar symptoms are reading this post.
I don't expect to see a low memory on my box now since I flashed it with a new 2.2 image from usb.

But it looks good at the moment.

root@vuduo:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 118.0M 47.8M 70.2M 40% /
tmpfs 64.0K 8.0K 56.0K 13% /dev
/dev/sda1 1.8T 191.6G 1.6T 10% /media/hdd
tmpfs 69.0M 848.0K 68.2M 1% /var/volatile
tmpfs 69.0M 0 69.0M 0% /dev/shm

[kingo]

Only time you will get the "No space left on device" is when you store too much on the flash on the box. It could be that your log files were taking up all of the nand flash space, so no storage left...

From what I remember, there will usually be around 60-65mb free after you've installed channels etc and set up the box (no plugins installed). When you install plugins, it uses your flash. If you store you picons on the internal flash, that consumes space too. The log files you create consume space (hence why it's suggested to only turn them on if we ask you to for debugging purposes).

I had a problem with my box, when I changed things over and disconnected my hdd. I found that instead of my usb being mounted as /media/usb (since /dev/sdb1 -> /media/usb & /dev/sda1 -> /media/hdd in fstab), the usb stick became /dev/sda1 instead of /dev/sdb1. So, /media/hdd was my usb stick, and /media/usb was internal flash. I was using the image manager to take backups to /media/usb, and so when it created the backup, it filled the flash memory, not the usb memory. Another reason why mount manager should be used to create your mounts, not fstab (I was testing summat at the time :p)

In most situations, you will not fill up flash, but that's how it happened to me, and it can be easily possible when messing with things.

Hope this helps

I have done by accident what pooface has said above now I cannot boot my Vu+duo just says shutting down and cant access via ftp is there anyway of getting the box back up ????

[Larry-G]

if you cant even get in bu FTP then try re-flashing the image as that should wipe the flash area as well.

[kingo]

Right I have now done that but now when i set up my fixed dish and installed cats eys enigma 2 setting says tuning failed and no signal

[kingo]

and the setup config does not give me the option of single only advance loopthrough and simple

[kingo]

sorted that forget that i need to go into simple then change