New Image

[dazulrich]

If you know of other images where this works. maybe you can try and contact those trying to find out what they did to make this work better. or whether they use a particular version of the ntfs 3g driver. (which is a 3rd party opensource driver). Maybe the new version is incompatible, who knows. But you can try finding that info, and depending on what the answers are, Bonkel might be able to implement for you to test then.
Unless any other user with an AzboxHD and the same ntfs disk problem is interested in solving this, Zeini's recommendation to use ext3 or ext4 is the best alternativ suggestion at the moment.
Or you can try the user Fabry over on opensat4all forum , he once compiled a "kernel for powerusers" and he might have some insight into the ntfs quirks. (but as per his last post from July, he has no working Azbox or dev environment anymore)

---- some legwork ----
@Kapios: can you find out which image has stable ntfs support and what driver they are using. (maybe you can open the driver from your openspa image and see if you can find version info.

are you mounting the disk using the mount manager (via fstab), can you post the fstab entry?

@Bonkel, dein oe unterbau kommt von openpli? ich glaube die nutzen den ntfs treiber von meta-oe. (ntfs-3g-ntfsprogs_2013.1.13.bb)
openatv zb, hat eigenes bb und benutzt neueren treiber (ntfs-3g-ntfsprogs_2015.3.14.bb)
und laut Tuxera ist ntfs-3g_ntfsprogs-2016.2.22 aktuell.

[dazulrich]

Found some suggestions on ntfs use on openpli. Loading the kernel-ntfs-module.
http://forums.openpli.org/topic/2375...ce-kernel-33x/
and in this Azbox thread a comment about "-o ro " params when mounting
https://www.opensat4all.com/forums/t...nel-available/

[bonkel]

@Bonkel, dein oe unterbau kommt von openpli? ich glaube die nutzen den ntfs treiber von meta-oe. (ntfs-3g-ntfsprogs_2013.1.13.bb)
openatv zb, hat eigenes bb und benutzt neueren treiber (ntfs-3g-ntfsprogs_2015.3.14.bb)
und laut Tuxera ist ntfs-3g_ntfsprogs-2016.2.22 aktuell.

si, direkt aus dem meta oe , original unverfälscht ^^

[ingo]

Hello everybody.
Based on information from the resources provided by dazulrich, I made the following for stable operation ntfs:

opkg remove --force-depends ntfs-3g
opkg install kernel-module-ntfs

To start ntfs kernel module uses the contents of the script 'modprobe ntfs' when the system boots. File attached script S03ntfs.sh copied /etc/rcS.d (attribute 755). Then, reboot.
ntfs drives will be available in "read-only".

[dazulrich]

do you need to update /etc/filesystems to include ntfs as mentioned in one of the posts?

[ingo]

do you need to update /etc/filesystems to include ntfs as mentioned in one of the posts?

If in systems installed ntfs-3g, it must be removed.
Then install the kernel-module-ntfs. No need for any additional updates.

[dazulrich]

glad it works for you.. and thanks for working out a solution.
If proven stable and tested by kapios as well and other users, maybe this could be included in the image build.

[bonkel]

so instead of ntfs-3g, install kernel-module?
so i can delete ntfs-3g from oe build
and add modprob in initd as plugin with depend on kernel-modul?

and maybe # CONFIG_NTFS_RW is not set to CONFIG_NTFS_RW=y to have read and write access?

[ingo]

so instead of ntfs-3g, install kernel-module?
so i can delete ntfs-3g from oe build
and add modprob in initd as plugin with depend on kernel-modul?

I agree with you, for "read-only" ntfs, should do so.
ntfs-3g is not present in the original image (not the package). Since the full functionality ntfs not expected, there is no need to ntfs-3g.

and maybe # CONFIG_NTFS_RW is not set to CONFIG_NTFS_RW=y to have read and write access?

Sorry, I do not have in-depth knowledge on this issue.

For the image of users:
If ntfs-3g has been set by the user, only then it should be removed.

[dazulrich]

@Bonkel. Oatv hat das in oe-a 2.3 von not set auf RW umgestellt.
Nur wissen wir halt nicht ob es vorher oder nachher besser war.

die meisten Boxen haben "not set". RW macht aber eher Ärger würd ich mal sagen.