Then finally do what I've requested, disable tuner 2 AND disconnect power of your box and then reboot it and do a scan ON tuner 1.
I did this.
1618 services found
1874 services found
So now I did a comparison between Dreambox One (Si2166D) and Dreambox 7080 (Si2166D) on 7°W (which is a extremely weak position for me), both found 26 transponders on blindscan.
Dreambox One = 296 services
Dreambox 7080 = 304 services
The only Transponder missing has only a SNR of 5.00dB (on both boxes) which means it's not even watchable (I don't even get picture, on both boxes). And yes it can be found by scanning the TP manually, but I still don't see any issue, except that a non-working transponder is missing.
So now I did a comparison between Dreambox One and Vu+ Solo4k on 13°E
Dreambox One = 1865 services
Vu+ Solo4k = 1869 services
Dreambox One (blindscan) = 1896 services
Nahezu die gleiche Formulierung hatten wir erst gestern in dem Tuner Thread...
Ich werde das Gefühl nicht los das unser Kollege hier und die zwei in dem anderen Thread alle zusammengehören...
Das sind doch alles beratungsresistente User aus dem Tunisia Sat Forum...
Your Feeling is wrong. i don't know those two.
I think this was part of one of the last updates:
added trickmodes (ffw/rwd/slowmo) for amlogic platforms (kernel/driver update required)
By the latest update its been a little bit better but it hasnt been completely ok yet.
if you have dreamONE, you only have to try with it and you can find out what the problem is.
I used a EXT4 formatted drive.
The problem is still not resolved. 👇👇🏻
third bad idea ...
In some cases NTFS will not work as expected. NTFS is a proprietary filesystem for linux with all its limitations.
Have you ever tried ext4 instead of NTFS? Everything is better than this desaster. I have been using linux receivers with ext4 formated drives a in a windows environment for years and I never had such problems.
Do you also ask the Microsoft support for ext4 or btrfs support? There are also proprietary Windows drivers for ext filesystems available. But you will never get support for this ...
Now I’m using dm900 and dm520 models except dreamone, and I have’nt any problem with external hard NTFS formated.
Anyways, this is a serious problem with the dreambox one model that is not typical in other models like dm920, dm900, dm520, dm820, dm7080, dm7020...
However, it is working perfectly on other models like dm920, dm520 and dm7020.
ntfs disk formated working here.
When it’s being play from hard, there is no problem, but when i forward or backward the video like twenty times or more, the image will be constant or the receiver doesn’t work at all and i have to turn it off from the back button and again turn it on.
The problem is still not resolved. 👇👇🏻
OK, you are using the minimal (!) 4k Blocksize which is optimal for storing lots of small files., but this is totally idiotic for doing PVR recordings.
Format it with at least 64k, or up to the maximum 2048kB and you will see the difference.
Seems also like you have not permanently mounted the stick, which means it will be mounted also from autofs - which then is a sync mount instdead of async - which is another nightmare for a PVR recording.
Which means there is nothing to fix, except your understanding what you are actually doing
How to mount it correctly?
1. Please post the output of the follwing command executed on the Dream One via ssh or telnet:
2. what blocksize did you use when formatting the NTFS - keep in mind that this is now a 64 Bit Linux and NOT 32 Bit anymore and recordings are BIG files, which means you should use the biggest possible blocksize and NOT the default one your PC might have proposed.
opendreambox 2.6.0 dreambox
dreambox login: root
root@dreambox:~# cat /proc/mounts
/dev/root / ext4 rw,relatime,data=ordered 0 0
devtmpfs /dev devtmpfs rw,relatime,size=285884k,nr_inodes=71471,mode=755 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
/dev/mmcblk1p1 /media/ba ext4 rw,noatime,nodiratime,nodelalloc,data=journal 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/debug cgroup rw,nosuid,nodev,noexec,relatime,debug 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/schedtune cgroup rw,nosuid,nodev,noexec,relatime,schedtune 0 0
systemd-1 /data autofs rw,relatime,fd=11,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=544 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
tmpfs /var/volatile tmpfs rw,relatime,mode=755 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
/etc/auto.misc /misc autofs rw,relatime,fd=6,pgrp=454,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18947 0 0
-hosts /net autofs rw,relatime,fd=12,pgrp=454,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18204 0 0
/etc/auto.hotplug /autofs autofs rw,relatime,fd=18,pgrp=454,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=4519 0 0
/etc/auto.network /media/net autofs rw,relatime,fd=24,pgrp=454,timeout=300,minproto=5,maxproto=5,indirect,pipe_ino=18953 0 0
/dev/dreambox-data /data ext4 rw,relatime,data=ordered 0 0
did you install the ntfs-3g driver, standard ntfs driver can only read any may have poor performance
yeah, I install it. Now I’m using dm900 and dm520 models except dreamone, and I have’nt any problem with external hard NTFS formated.
Poor NTFS performance isn't a Drembox One only Problem!
This problem is a known problem and exist over years.
Linux developers (not Dream Property!!!) not interested on NTFS.
They all use Linux Filesystem.
You have to learn, your request is for this Devs irrelevant.
If you want a fix, then your counterpart is this man: https://en.wikipedia.org/wiki/Linus_Torvalds
Why users of other Dreambox models haven’t had any problems with external hard drives NTFS formatted?
As a customer I thought I’m responsible to report the problem. I believe Dreambox also is responsible to fix that problem for the customers.
I was wondering why users of other Dreambox models haven’t had any problems with NTFS formatted external drives!!
thanks a lot
You can't compare the NTFS performance under windows with the NTFS performance under Linux. As the posters above already tried to tell you: NTFS under Linux ist a performance killer, anyway you use it local or over ftp.
I think our discussion is going off the topic.
My main concern is why the NTFS formatted external drives have not been working correctly in the dream one models. However, it is working perfectly on other models like dm920, dm520 and dm7020.