[VU+ Solo2] External USB Hard Disk with NTFS is not seen after Mount Point Set

[sigpark]

I have a New Samsung 1TB M3 external USB hard disk. I would like to use it as NTFS for ease of use between my W7 systems. I understand there are ext readers for W7. When I insert the disk with factory build there is a small (200Mb) EISA partition and an NTFS partition. My VU Solo 2 will see the EISA partition, but the NTFS partition is "unknown" size, the same is true for exFAT- please see image
EISA (200Mb usable) but NTFS or exFAT and is not usable.

However Mac OS files system HFS is fine, please see this image
Formatted on Mac OS

Next I tried flattening the disk to a single NTFS or exFAT partition - same problem
NTFS or exFAT on its own

You can set the mount point as you can see above but it does not take. The only way I have been able to use my disk is by initialising it to ext4. To do that it must be viewable in the storage manager as you can imagine. The disk can only be seen by storage manager if it has a "recognisable" partition, i.e. the one with two partitions above or the HFS. NTFS or exFAT on its own is not seen, so cannot be initialised by Storage Manager (even though above there is an "unknown" mount point).

Finally just to show the initialised disk is fine, so the problem issue I have is with NTFS or exFAT - but it is NTFS I want.


Please note that I took the images at different times to show the problem. If anyone can shed any light on this matter it would be great. Thanks!

 

[abu baniaz]

Have you installed the ntfs drivers?

There is an issue with ex-fat one, but that issue is in the to do list.

 

[abu baniaz]

I stand corrected.

Using TM Twin build 808, I installed ntfs-3g drivers. Hot plugging the usb device reults in a lockup.

HOTPLUG connection!
hotplug: ACTION=add
complete ACTION=add
HOTPLUG connection lost!
hotplug: {'ACTION': 'add', 'PHYSDEVPATH': '/block/sdb/device', 'DEVPATH': '/dev/sdb1'}
main thread is non-idle! display spinner!

Rebooting the receiver with the ntfs device connected results in receiver not booting fully, it gets stuck at 41%

Perhaps this is related to this
http://www.world-of-satellite.com/showthread.php?35547-USB-using-exfat

 

[sigpark]

Have you installed the ntfs drivers?

There is an issue with ex-fat one, but that issue is in the to do list.

No! And I Have done so now. All good, how foolish of me. When I read through the posts, I thought that NTFS-3G was to support RW, and the RO would be good.

Thanks abu baniaz

 

[sigpark]

Just one to be aware of. The transfer speed performance over the network (Gb) are inferior with the NTFS file system - must be overhead of the driver (no criticism). I can only write at about 8MB/s and read at about 18MB/s with NTFS. The write speeds with ext4 to same disk are about 22MB/s and read is 30MB/s.

Also, for anybody that reads this thread - the driver referred to by abu baniaz is downloadable via the plug-in feeds (driver section)

 

[Rob van der Does]

I have no issues with an USB-HDD in NTFS-format, using the drivers from the feeds.
It is very well possible that the obtainable speeds are low; after all it's not a native Linux format.

 

[sigpark]

I have no issues with an USB-HDD in NTFS-format, using the drivers from the feeds.
It is very well possible that the obtainable speeds are low; after all it's not a native Linux format.

Hi Rob, I have no issues either. It is as you say the obtainable speeds are low @ 8MB/s with NTFS driver (write) relative to the same disk formatted in ext4 which yields about 31MB/s on a Gb network. I have tested this with VU+ Solo 2. Clearly on 100Mb network, I don't believe you would see any difference.