Try to install TSPanel - 'No Space On Device"

you have filled your flash. which is not good for the health of the image.

i would personally just reflash the receiver than trying to empty the flash, then start again. also make sure your EPG is not set to the flash as this can easily go wrong and cause this problem.

In the EPG options there is a "configure" menu,in this you can change where the epg is stored too,i.e Flash/HDD etc

the EPG it self once running is held in live memory and only written to storage or read from on bootup or shutdown. i recommend either USB or HDD as perfect locations for EPG but dont use flash because EPG data can easily corrupt and grow huge filling up the flash very rapidly.

these are my stats with the vix 3.0-262 image

Welcome to OpenViX for vuuno
openvix 3.0 vuuno

vuuno login: root
root@vuuno:~# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 98.6M 51.1M 47.4M 52% /
devtmpfs 134.3M 4.0K 134.3M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
/dev/sda1 298.0G 57.3G 240.7G 19% /media/hdd
/dev/sdb1 3.7G 131.7M 3.6G 3% /media/usb
tmpfs 134.4M 80.0K 134.4M 0% /var/volatile
root@vuuno:~#

i got my info via a telnet session using the df -h command. and yes the uno does have the stated 512MB ram but part of that is reserved for core functions of the receiver in the same way that the ultimo has 1GB of ram but half is reserved for core functions and later use.

the uno has more than adequate ram but images such as BH and VTI that are based on the OI firmware are very large and in some cases almost double that of other pli / pli based images.

i forget the exact technical specs at present but the receiver does have the stated 512MB ram and as i said part of this is withheld from the user for core functions.

with the cat /proc/meminfo command via telnet.

root@vuuno:~# cat /proc/meminfo
MemTotal: 275352 kB
MemFree: 174868 kB
Buffers: 4212 kB
Cached: 41620 kB
SwapCached: 0 kB
Active: 43148 kB
Inactive: 31636 kB
Active(anon): 28980 kB
Inactive(anon): 52 kB
Active(file): 14168 kB
Inactive(file): 31584 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 8 kB
Writeback: 0 kB
AnonPages: 28948 kB
Mapped: 10500 kB
Shmem: 84 kB
Slab: 12568 kB
SReclaimable: 4304 kB
SUnreclaim: 8264 kB
KernelStack: 560 kB
PageTables: 244 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 137676 kB
Committed_AS: 55308 kB
VmallocTotal: 524084 kB
VmallocUsed: 11764 kB
VmallocChunk: 502660 kB
root@vuuno:~#

because its partitioned off and not accessible to the user, why report memory that is not accessible ?.

for example here are the same commands run on my ultimo which has 1GB of ram but not all of that is accessible to the user.

Welcome to OpenViX for vuultimo
openvix 3.0 vuultimo

vuultimo login: root
root@vuultimo:~# df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 438.9M 59.2M 379.7M 13% /
devtmpfs 134.3M 4.0K 134.3M 0% /dev
tmpfs 64.0K 0 64.0K 0% /media
/dev/sda1 931.4G 232.6G 698.8G 25% /media/hdd
/dev/sdb1 3.7G 359.5M 3.4G 9% /media/usb
tmpfs 134.4M 156.0K 134.3M 0% /var/volatile
root@vuultimo:~#

===

root@vuultimo:~# cat /proc/meminfo
MemTotal: 275352 kB
MemFree: 65440 kB
Buffers: 3740 kB
Cached: 110752 kB
SwapCached: 0 kB
Active: 103580 kB
Inactive: 66212 kB
Active(anon): 55396 kB
Inactive(anon): 64 kB
Active(file): 48184 kB
Inactive(file): 66148 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 4 kB
Writeback: 0 kB
AnonPages: 55304 kB
Mapped: 12132 kB
Shmem: 160 kB
Slab: 25636 kB
SReclaimable: 16220 kB
SUnreclaim: 9416 kB
KernelStack: 728 kB
PageTables: 328 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 137676 kB
Committed_AS: 77428 kB
VmallocTotal: 524084 kB
VmallocUsed: 12860 kB
VmallocChunk: 470892 kB
root@vuultimo:~#