NSLU2-Linux
view · edit · print · history
FAQ »

FAQ.NTFS History

Hide minor edits - Show changes to markup

July 28, 2008, at 12:16 AM by mkurtz -- added link to HowTo/BuildNTFS3G
Added lines 27-30:

Building the NTFS-3G driver for Unslung

View BuildNTFS3G for instructions on how to build the FUSE kernel drive and user-space NTFS-3G tools. The NTFS-3G driver is much more reliable and faster than the Paragon driver. It is, however, difficult to build until we get an optware package.

January 03, 2008, at 10:42 PM by mwester -- clarifications
Changed lines 11-12 from:

Finaly the ntfs driver isn't as stable as it should be. Test shows that the slug will hang when writing to ntfs under high io load.

to:

WARNING: The NTFS driver isn't as stable as it should be. Tests show that the slug will hang when writing to NTFS under moderate to high I/O load. This problem is in the Linksys-provided driver, and occurs in both the native Linksys firmware as well as with Unslung. There's nothing that can be done to fix this, since the source code for this driver is proprietary.

Changed lines 17-18 from:
Captive - http://www.jankratochvil.net/project/captive/: This driver has full read/write support for NTFS because it uses a wrapper around the Windows ntfs.sys binary driver. Porting this to the NSLU2 would require finding a ntfs.sys compiled for ARM and then trying to port the Captive wrapper. Finding a ARM compatible ntfs.sys from Microsoft is basically impossible unless Microsoft decide to port Windows to ARM. Using something like QEMU to emulate a x86 platform to run the ntfs.sys driver is in theory possible but it is not an ideal solution and would entail a large amount of work. You could for example boot a full i386 linux installation in qemu. This installation could access the NTFS via a network block device from the ARM side of things. The i386 qemu could then export the accessed file system via NFS or other means back to the ARM. Short answer is still no. Plus it would be rather slow.
to:
Captive - http://www.jankratochvil.net/project/captive/: This driver has full read/write support for NTFS because it uses a wrapper around the Windows ntfs.sys binary driver. Porting this to the NSLU2 would require finding a ntfs.sys compiled for ARM and then trying to port the Captive wrapper. Finding a ARM compatible ntfs.sys from Microsoft is basically impossible unless Microsoft decide to port Windows to ARM. Using something like QEMU to emulate a x86 platform to run the ntfs.sys driver is in theory possible but it is not an ideal solution and would entail a large amount of work. You could for example boot a full i386 linux installation in qemu. This installation could access the NTFS via a network block device from the ARM side of things. The i386 qemu could then export the accessed file system via NFS or other means back to the ARM. Short answer is still no. Plus it would be rather slow. So this project is not practical or possible for the NSLU2.
Changed lines 23-30 from:

The project is a fork of Linux-NTFS having major functional, performance and reliability improvements. NTFS read/write success confirmed (though reliability to be established) when using Debian\NSLU2 with ntfs-3g version 1.0 (currently in experimental, 2-Mar-07) with fuse-utils 0.6.2.

Commercial Paragon NTFS for Linux - http://www.ntfs-linux.com/: This is a commercial package which fully supports NTFS read and write. Linksys has included a copy of the driver in 2.3R63 and above.

Using the Paragon driver with Unslung 5.5 and 6.8

The Paragon driver is already available in Unslung as a ipkg. Install it (ipkg install ufsd) and the ipkg will download the Linksys firmware, extract the kernel module and install it. We can not distribute the module itself and must do it via this method.

to:

The project is a fork of Linux-NTFS having major functional, performance and reliability improvements. NTFS read/write success confirmed (though reliability to be established) when using Debian\NSLU2 with ntfs-3g version 1.0 (currently in experimental, 2-Mar-07) with fuse-utils 0.6.2.n This driver has also been tested with SlugOS 6.8, and found to work.

Commercial Paragon NTFS for Linux - http://www.ntfs-linux.com/: This is a commercial package which fully supports NTFS read and write. This is the driver that Linksys has included in 2.3R63 and above -- and is the one that has the bugs mentioned above.

Using the Paragon driver with Unslung 6.x

For Unslung 6.8 and 6.10, the Paragon driver (supplied by Linksys) is already installed; there is nothing necessary to do.

Using the Paragon driver with Unslung 5.5

For Unslung 5.5, the Paragon driver is available in Unslung as a ipkg. Install it (ipkg install ufsd) and the ipkg will download the Linksys firmware, extract the kernel module and install it. We can not distribute the module itself and must do it via this method.

March 02, 2007, at 01:22 PM by emm_is -- ntfs-3g with Debian/NSLU2 now working
Changed lines 23-24 from:

The project is a fork of Linux-NTFS having major functional, performance and reliability improvements. NTFS read/write success confirmed (though reliability to be established) when using NSLU2 with ntfs-3g version 1.0 (currently in experimental, 2-Mar-07) with fuse-utils 0.6.2.

to:

The project is a fork of Linux-NTFS having major functional, performance and reliability improvements. NTFS read/write success confirmed (though reliability to be established) when using Debian\NSLU2 with ntfs-3g version 1.0 (currently in experimental, 2-Mar-07) with fuse-utils 0.6.2.

March 02, 2007, at 01:20 PM by emm_is -- ntfs-3g with Debian/NSLU2 now working
Changed lines 23-24 from:

The project is a fork of Linux-NTFS having major functional, performance and reliability improvements.

to:

The project is a fork of Linux-NTFS having major functional, performance and reliability improvements. NTFS read/write success confirmed (though reliability to be established) when using NSLU2 with ntfs-3g version 1.0 (currently in experimental, 2-Mar-07) with fuse-utils 0.6.2.

February 16, 2007, at 08:42 PM by foobar -- add ntfs-3g
Changed lines 15-16 from:

There are three NTFS drivers for Linux in existance:

to:

There are four NTFS drivers for Linux in existance:

Added lines 22-24:
NTFS-3G - http://www.ntfs-3g.org: Open source, free, reliable, full read-write NTFS driver.

The project is a fork of Linux-NTFS having major functional, performance and reliability improvements.

February 02, 2007, at 09:37 AM by slw --
Changed lines 43-45 from:
to:

Feb 1 2007 -- actually, I just tried this and the current ufsd ipkg choked when it found the busybox unzip

January 23, 2007, at 08:38 PM by os -- typo After that, run @@ipkg configure usfd@@ should be ...ufsd
Changed lines 30-31 from:

Notice (by J With): if the automatic download of the firmare fails you should download it manually from the Linksys support site (you can use this link) and save it as NSLU2_V23R63.zip in /tmp. After that, run ipkg configure usfd to proceed with the install.

to:

Notice (by J With): if the automatic download of the firmare fails you should download it manually from the Linksys support site (you can use this link) and save it as NSLU2_V23R63.zip in /tmp. After that, run ipkg configure ufsd to proceed with the install.

December 18, 2006, at 03:47 PM by gna --
Changed lines 52-53 from:

just upload an up-to-date linksys firmware (currently V23RA5?) to the /temp directory and do the following:

to:

just upload an up-to-date linksys firmware (currently V23RA5?) to the /tmp directory and do the following:

December 18, 2006, at 03:47 PM by gna -- ---newer linksys firmware---
Changed lines 52-58 from:

just upload an up-to-date linksys firmware (currently V23RA5?) to the /tem directory and do the following: dd if=NAME_OF_FIRMWARE.bin of=ramdisk.gz bs=16 skip=90113 <br> gunzip ramdisk.gz<br> /opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /lib/modules/ufsd.o<br> /opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /initrd/lib/modules/ufsd.o<br>

to:

just upload an up-to-date linksys firmware (currently V23RA5?) to the /temp directory and do the following:

dd if=NAME_OF_FIRMWARE.bin of=ramdisk.gz bs=16 skip=90113

gunzip ramdisk.gz

/opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /lib/modules/ufsd.o

/opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /initrd/lib/modules/ufsd.o

/gna!arf!argn!

December 18, 2006, at 03:45 PM by gna --
Changed lines 53-58 from:

dd if=NAME_OF_FIRMWARE.bin of=ramdisk.gz bs=16 skip=90113 gunzip ramdisk.gz /opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /lib/modules/ufsd.o /opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /initrd/lib/modules/ufsd.o

to:

dd if=NAME_OF_FIRMWARE.bin of=ramdisk.gz bs=16 skip=90113 <br> gunzip ramdisk.gz<br> /opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /lib/modules/ufsd.o<br> /opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /initrd/lib/modules/ufsd.o<br>

December 18, 2006, at 03:44 PM by gna -- Get ufsd workin with newer linksysfirmware
Changed lines 49-58 from:

Sorry, I RTFW myself. Just followed the first link on this page, about code pages and got it working. /Macks

to:

Sorry, I RTFW myself. Just followed the first link on this page, about code pages and got it working. /Macks

Note: If you get an Error that downloading NSLU2_V23R63.zip from www.linksys.com has failed, just upload an up-to-date linksys firmware (currently V23RA5?) to the /tem directory and do the following: dd if=NAME_OF_FIRMWARE.bin of=ramdisk.gz bs=16 skip=90113 gunzip ramdisk.gz /opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /lib/modules/ufsd.o /opt/bin/e2cp ramdisk:/lib/modules/ufsd.o /initrd/lib/modules/ufsd.o

November 16, 2006, at 03:58 PM by fcarolo -- fixed formatting
Changed lines 32-33 from:

''Notice (by dglaude): DO NOT donwload ftp://ftp.linksys.com/opensourcecode/nslu2/2.3R63/NSLU2_V23R63.zip. It is not the firmware but the source code.

to:

Notice (by dglaude): DO NOT donwload ftp://ftp.linksys.com/opensourcecode/nslu2/2.3R63/NSLU2_V23R63.zip. It is not the firmware but the source code.

November 16, 2006, at 03:58 PM by fcarolo -- reformatting and clarification about install procedure
Changed lines 3-4 from:

Yes. The latest stock firmware from Linksys (2.3R63 and above) allows an NTFS drive to be attached to Port 1. Be aware that the Release notes for 2.3R63 are wrong, here is the correction:

to:

Yes, if you are using either the latest stock firmware from Linksys (2.3R63 and above) or Unslung 6.8. Both allow an NTFS drive to be attached to Port 1. Be aware that the Release notes for 2.3R63 are wrong, here is the correction:

Added lines 13-14:

NTFS drivers

Changed lines 17-24 from:
  • Captive - http://www.jankratochvil.net/project/captive/

This driver has full read/write support for NTFS because it uses a wrapper around the Windows ntfs.sys binary driver. Porting this to the NSLU2 would require finding a ntfs.sys compiled for ARM and then trying to port the Captive wrapper. Finding a ARM compatible ntfs.sys from Microsoft is basically impossible unless Microsoft decide to port Windows to ARM. Using something like QEMU to emulate a x86 platform to run the ntfs.sys driver is in theory possible but it is not an ideal solution and would entail a large amount of work. You could for example boot a full i386 linux installation in qemu. This installation could access the NTFS via a network block device from the ARM side of things. The i386 qemu could then export the accessed file system via NFS or other means back to the ARM. Short answer is still no. Plus it would be rather slow.

  • Linux NTFS project - http://www.linux-ntfs.org/

This is a reimplementation of the NTFS file system as a normal Linux driver. As such, it is probably more portable, but it is also more limited. Write support is extremely limited (can only modify existing files, no file size changes), and probably not useful to most NSLU2 users.

to:
Captive - http://www.jankratochvil.net/project/captive/: This driver has full read/write support for NTFS because it uses a wrapper around the Windows ntfs.sys binary driver. Porting this to the NSLU2 would require finding a ntfs.sys compiled for ARM and then trying to port the Captive wrapper. Finding a ARM compatible ntfs.sys from Microsoft is basically impossible unless Microsoft decide to port Windows to ARM. Using something like QEMU to emulate a x86 platform to run the ntfs.sys driver is in theory possible but it is not an ideal solution and would entail a large amount of work. You could for example boot a full i386 linux installation in qemu. This installation could access the NTFS via a network block device from the ARM side of things. The i386 qemu could then export the accessed file system via NFS or other means back to the ARM. Short answer is still no. Plus it would be rather slow.
Linux NTFS project - http://www.linux-ntfs.org/: This is a reimplementation of the NTFS file system as a normal Linux driver. As such, it is probably more portable, but it is also more limited. Write support is extremely limited (can only modify existing files, no file size changes), and probably not useful to most NSLU2 users.\\
Changed lines 22-38 from:
  • Commercial Paragon NTFS for Linux - http://www.ntfs-linux.com/

This is a commercial package which fully supports NTFS read and write. Linksys has included a copy of the driver in 2.3R63 and above.

The Paragon driver is available installation in Unslung as a ipkg. Install it (ipkg install ufsd) and the ipkg will download the Linksys firmware, extract the kernel module and install it. We can not distribute the module itself and must do it via this method.

For me the automatic download of the Linksys firmware failed during execution of /usr/lib/ipkg/info/ufsd.postinst. I had to download/copy NSLU2_V23R63.zip manually to /tmp and configure ufsd again (ipkg configure ufsd) to succeed with the install. - J With

DO NOT donwload ftp://ftp.linksys.com/opensourcecode/nslu2/2.3R63/NSLU2_V23R63.zip it is not the firmware but the source code. - dglaude

How I got this working on Unslung 5.5: I had an exisitng harddrive in a USB enclosure, formatted half-and-half with FAT32? and NTFS. I'd already unslung to a USB flash disk. I got the FAT32? partition working by following the instructions in AttachAFAT32FormattedDrive. To get the NTFS partition working was similar, but after running ipkg install ufsd as detailed above, I also had to do insmod ufsd and then use ufsd as the filesystem type in the mount command (discovered by flicking through http://download.paragon.ag/doc/manual_ntfsl_eng.pdf). - Lurch

OpenSlug is not supported as the kernel module is built specifically for the 2.4 kernel that the stock firmware uses. There is no workaround unfortunately.

Note: If during installation it complains about the zip file it downloads from Linksys, this may be because the script is calling /usr/bin/unzip, which is the busybox version of unzip that cannot be used by the ufsd ipkg install script. Try installing the unzip ipkg first, then either modify your path (export PATH=/opt/bin:$PATH if using bash) or temporarily replace /usr/bin/unzip with a link to the installed unzip (mv /usr/bin/unzip /usr/bin/unzip_busybox; ln -s /opt/bin/unzip /usr/bin/unzip; and then to restore things, rm -f /usr/bin/unzip; mv /usr/bin/unzip_busybox /usr/bin/unzip).

to:
Commercial Paragon NTFS for Linux - http://www.ntfs-linux.com/: This is a commercial package which fully supports NTFS read and write. Linksys has included a copy of the driver in 2.3R63 and above.

Using the Paragon driver with Unslung 5.5 and 6.8

The Paragon driver is already available in Unslung as a ipkg. Install it (ipkg install ufsd) and the ipkg will download the Linksys firmware, extract the kernel module and install it. We can not distribute the module itself and must do it via this method.

The current version of the usfd package takes care of the dependency on unzip and should extract the necessary module file from the zip file without problems.

Notice (by J With): if the automatic download of the firmare fails you should download it manually from the Linksys support site (you can use this link) and save it as NSLU2_V23R63.zip in /tmp. After that, run ipkg configure usfd to proceed with the install.

''Notice (by dglaude): DO NOT donwload ftp://ftp.linksys.com/opensourcecode/nslu2/2.3R63/NSLU2_V23R63.zip. It is not the firmware but the source code.

Notice (by Lurch): How I got this working on Unslung 5.5: I had an exisitng harddrive in a USB enclosure, formatted half-and-half with FAT32? and NTFS. I'd already unslung to a USB flash disk. I got the FAT32? partition working by following the instructions in AttachAFAT32FormattedDrive. To get the NTFS partition working was similar, but after running ipkg install ufsd as detailed above, I also had to do insmod ufsd and then use ufsd as the filesystem type in the mount command (discovered by flicking through http://download.paragon.ag/doc/manual_ntfsl_eng.pdf).

OpenSlug is not supported as the kernel module is built specifically for the 2.4 kernel that the stock firmware uses. There is no workaround unfortunately.

---

User notes

Note: If during installation it complains about the zip file it downloads from Linksys, this may be because the script is calling /usr/bin/unzip, which is the busybox version of unzip that cannot be used by the ufsd ipkg install script. Try installing the unzip ipkg first, then either modify your path (export PATH=/opt/bin:$PATH if using bash) or temporarily replace /usr/bin/unzip with a link to the installed unzip (mv /usr/bin/unzip /usr/bin/unzip_busybox; ln -s /opt/bin/unzip /usr/bin/unzip; and then to restore things, rm -f /usr/bin/unzip; mv /usr/bin/unzip_busybox /usr/bin/unzip). Notice: this is no longer necessary, as the current package correctly handles the dependency on unzip.

October 02, 2006, at 11:57 PM by dglaude -- Remove mistake about file to download.
October 02, 2006, at 11:57 PM by dglaude -- Remove mistake about file to download.
Changed lines 33-34 from:

You can donwload that file by cd /tmp; wget ftp://ftp.linksys.com/opensourcecode/nslu2/2.3R63/NSLU2_V23R63.zip . -dglaude

to:

DO NOT donwload ftp://ftp.linksys.com/opensourcecode/nslu2/2.3R63/NSLU2_V23R63.zip it is not the firmware but the source code. - dglaude

October 02, 2006, at 08:39 PM by dglaude -- Adding URL for NSLU2_V23R63.zip
Added lines 33-34:

You can donwload that file by cd /tmp; wget ftp://ftp.linksys.com/opensourcecode/nslu2/2.3R63/NSLU2_V23R63.zip . -dglaude

September 10, 2006, at 03:08 PM by marceln -- Added notes about ntfs stability problems
Changed lines 9-10 from:

Also, keep an eye out for this gotcha in Uslung 6.8 - UnslungLanguageSupport

to:

Also, keep an eye out for this gotcha in Uslung 6.8 - UnslungLanguageSupport.

Finaly the ntfs driver isn't as stable as it should be. Test shows that the slug will hang when writing to ntfs under high io load.

September 05, 2006, at 07:29 AM by Macks --
Changed lines 41-43 from:

Thanks /Macks

to:

Thanks /Macks

Sorry, I RTFW myself. Just followed the first link on this page, about code pages and got it working. /Macks

September 04, 2006, at 09:29 PM by Macks -- Is NTFS support really working in ver 6.8?
Added lines 36-41:

Help, please Does anyone have this working in ver 6.8? I have tried all of the above on a newly flashed 6.8 without luck. Get the NSLU2_V23R63.zip download error message. Does not help if I download the zip to /tmp. Neither does the unzip note. - Is NTFS supposed to work "out of the box" for ver 6.8 since it is based on firmware with that support? - Any input would be appreciated, if it is just a note that you actually have it working, then at least I will not give up. Thanks /Macks

May 16, 2006, at 11:58 PM by Eddie -- Clarified the unzip binary issue
Changed lines 35-38 from:

Note: If during installation it complains about the zip file it downloads from Linksys, make sure you have the unzip from the ipkg in your path before /usr/bin/unzip. /usr/bin/unzip will not extract the zip file from Linksys properly.

  1. I dont understand that last statement. I need to use a path in the IPKG command line?, modify a path statement in a file somewhere? or relocate/copy 'unzip' to another location ? Please clarify. Thank you.
to:

Note: If during installation it complains about the zip file it downloads from Linksys, this may be because the script is calling /usr/bin/unzip, which is the busybox version of unzip that cannot be used by the ufsd ipkg install script. Try installing the unzip ipkg first, then either modify your path (export PATH=/opt/bin:$PATH if using bash) or temporarily replace /usr/bin/unzip with a link to the installed unzip (mv /usr/bin/unzip /usr/bin/unzip_busybox; ln -s /opt/bin/unzip /usr/bin/unzip; and then to restore things, rm -f /usr/bin/unzip; mv /usr/bin/unzip_busybox /usr/bin/unzip).

May 13, 2006, at 05:36 PM by Lurch -- Added link to UnslungLanguageSupport
Changed lines 9-10 from:
to:

Also, keep an eye out for this gotcha in Uslung 6.8 - UnslungLanguageSupport

May 01, 2006, at 05:15 PM by JWith --
Changed lines 28-29 from:
For me the automatic download of the Linksys firmware failed during execution of /usr/lib/ipkg/info/ufsd.postinst. I had to download/copy NSLU2_V23R63.zip manually to /tmp and configure it again (ipkg configure ufsd) to succeed with the install. - J With
to:
For me the automatic download of the Linksys firmware failed during execution of /usr/lib/ipkg/info/ufsd.postinst. I had to download/copy NSLU2_V23R63.zip manually to /tmp and configure ufsd again (ipkg configure ufsd) to succeed with the install. - J With
May 01, 2006, at 05:14 PM by JWith --
Changed lines 28-29 from:
For me the automatic download of the Linksys firmware failed during execution of /usr/lib/ipkg/info/ufsd.postinst. I had to download/copy NSLU2_V23R63.zip manually to /tmp and configure it again (ipkg configure ufsd) to succeed with the install. - JWith?
to:
For me the automatic download of the Linksys firmware failed during execution of /usr/lib/ipkg/info/ufsd.postinst. I had to download/copy NSLU2_V23R63.zip manually to /tmp and configure it again (ipkg configure ufsd) to succeed with the install. - J With
May 01, 2006, at 05:11 PM by JWith -- Supplying Linksys firmware
Added lines 28-29:
For me the automatic download of the Linksys firmware failed during execution of /usr/lib/ipkg/info/ufsd.postinst. I had to download/copy NSLU2_V23R63.zip manually to /tmp and configure it again (ipkg configure ufsd) to succeed with the install. - JWith?
April 08, 2006, at 01:59 PM by Diode -- More information about the tip is needed please
Added lines 33-35:
  1. I dont understand that last statement. I need to use a path in the IPKG command line?, modify a path statement in a file somewhere? or relocate/copy 'unzip' to another location ? Please clarify. Thank you.
February 28, 2006, at 07:58 AM by mindbender -- corrected link
Changed lines 16-17 from:
  • Linux NTFS project - http://linux-ntfs.sourceforge.net/status.html
to:
  • Linux NTFS project - http://www.linux-ntfs.org/
February 27, 2006, at 09:20 PM by viewer -- fixed 2 typos
Changed lines 8-9 from:

One limitation of doing so it that you will not be able to assign an security settings (users/groups) to the drive like you could with the ext3 extension.

to:

One limitation of doing so is that you will not be able to assign any security settings (users/groups) to the drive like you could with the ext3 extension.

February 05, 2006, at 02:34 PM by Lurch -- Details about using the Paragon NTFS driver
Added lines 28-29:

How I got this working on Unslung 5.5: I had an exisitng harddrive in a USB enclosure, formatted half-and-half with FAT32? and NTFS. I'd already unslung to a USB flash disk. I got the FAT32? partition working by following the instructions in AttachAFAT32FormattedDrive. To get the NTFS partition working was similar, but after running ipkg install ufsd as detailed above, I also had to do insmod ufsd and then use ufsd as the filesystem type in the mount command (discovered by flicking through http://download.paragon.ag/doc/manual_ntfsl_eng.pdf). - Lurch

December 17, 2005, at 07:01 AM by tman --
Changed lines 4-8 from:
       Disk 1 The Disk 1 port of the Network Storage Link supports 
              EXT3?, FAT32?, and NTFS file systems. (Flash drives will not be recognized.) 
       Disk 2 The Disk 2 port supports EXT3? and FAT32? file systems. 
              Insert your USB flash drive (USB key) or USB disk here.  
to:
Disk 1 - The Disk 1 port of the Network Storage Link supports Ext3, FAT32, and NTFS file systems. (Flash drives will not be recognized.)
Disk 2 - The Disk 2 port supports Ext3 and FAT32 file systems. Insert your USB flash drive (USB key) or USB disk here.
December 08, 2005, at 01:32 AM by jkpeters_37 -- stock firmware is 2.4 kernel
Changed lines 29-30 from:

OpenSlug is not supported as the kernel module is built specifically for the 2.2 kernel that the stock firmware uses. There is no workaround unfortunately.

to:

OpenSlug is not supported as the kernel module is built specifically for the 2.4 kernel that the stock firmware uses. There is no workaround unfortunately.

November 25, 2005, at 08:59 AM by cbxtom -- correction of File systems supported by port 1 and 2
Changed lines 3-4 from:

Yes. The latest stock firmware from Linksys (2.63R63 and above) allows an NTFS drive to be attached to Port 2. One limitation of doing so it that you will not be able to assign an security settings (users/groups) to the drive like you could with the ext3 extension.

to:

Yes. The latest stock firmware from Linksys (2.3R63 and above) allows an NTFS drive to be attached to Port 1. Be aware that the Release notes for 2.3R63 are wrong, here is the correction:

       Disk 1 The Disk 1 port of the Network Storage Link supports 
              EXT3?, FAT32?, and NTFS file systems. (Flash drives will not be recognized.) 
       Disk 2 The Disk 2 port supports EXT3? and FAT32? file systems. 
              Insert your USB flash drive (USB key) or USB disk here.  

One limitation of doing so it that you will not be able to assign an security settings (users/groups) to the drive like you could with the ext3 extension.

October 29, 2005, at 04:03 AM by tman --
Deleted lines 4-7:

What about with OpenSlug or Unslung? Currently, no. It is being worked on however.

October 29, 2005, at 04:03 AM by tman --
Changed lines 3-5 from:

Yes. The latest stock firmware from Linksys (2.63R63) allows an NTFS drive to be attached to Port 2. One limitation of doing so it that you will not be able to assign an security settings (users/groups) to the drive like you could with the ext3 extension.

to:

Yes. The latest stock firmware from Linksys (2.63R63 and above) allows an NTFS drive to be attached to Port 2. One limitation of doing so it that you will not be able to assign an security settings (users/groups) to the drive like you could with the ext3 extension.

Changed lines 17-18 from:

This is a reimplementation of the NTFS file system as a normal Linux driver. As such, it is probably more portable, but it is also more limited. Write support is extremely limited (can only modify existing files, no file size changes), and probably not useful to most NSLU2 users. The new, rewritten version of the NTFS driver is included in the Linux 2.6.9 kernel, so once the OpenSlug project succeeds in getting the 2.6 kernel running on the NSLU2, it will be possible to see if this driver works.

to:

This is a reimplementation of the NTFS file system as a normal Linux driver. As such, it is probably more portable, but it is also more limited. Write support is extremely limited (can only modify existing files, no file size changes), and probably not useful to most NSLU2 users.

Recent (April 2005+) builds of OpenSlug come with the Linux NTFS project kernel module in the flash (though not installed). mount -t ntfs /dev/sdb1 /mnt (with appropriate device/directory) will mount a Windows NTFS partition for read access. At present the (experimental) write access is not compiled in - so the mount is read-only.

Changed lines 23-27 from:

This is a commercial package which fully supports NTFS read and write. Linksys has included a copy of the driver in 2.3R63 and work is underway to provide a method of extracting this driver and integrating it.

update: Recent (April 2005+) builds of OpenSlug come with the Linux NTFS project kernel module in the flash (though not installed). mount -t ntfs /dev/sdb1 /mnt (with appropriate device/directory) will mount a Windows NTFS partition for read access. At present the (experimental) write access is not compiled in - so the mount is read-only.

update: Since sometime in Oct 2005, there is an ipkg available called "ufsd". Install it (ipkg install ufsd) and you will install the NTFS module that linksys provides (that is, the Paragon NTFS driver). Note: if you have trouble installing the ipkg, complaining about the zip file it downloads from linksys, make sure you have the unzip from the ipkg in your path, before /usr/bin/unzip which will not extract the zip file from linksys properly.

to:

This is a commercial package which fully supports NTFS read and write. Linksys has included a copy of the driver in 2.3R63 and above.

The Paragon driver is available installation in Unslung as a ipkg. Install it (ipkg install ufsd) and the ipkg will download the Linksys firmware, extract the kernel module and install it. We can not distribute the module itself and must do it via this method.

OpenSlug is not supported as the kernel module is built specifically for the 2.2 kernel that the stock firmware uses. There is no workaround unfortunately.

Note: If during installation it complains about the zip file it downloads from Linksys, make sure you have the unzip from the ipkg in your path before /usr/bin/unzip. /usr/bin/unzip will not extract the zip file from Linksys properly.

October 25, 2005, at 05:24 AM by Eddie -- Added note on installing the ufsd package
Added lines 24-25:

update: Since sometime in Oct 2005, there is an ipkg available called "ufsd". Install it (ipkg install ufsd) and you will install the NTFS module that linksys provides (that is, the Paragon NTFS driver). Note: if you have trouble installing the ipkg, complaining about the zip file it downloads from linksys, make sure you have the unzip from the ipkg in your path, before /usr/bin/unzip which will not extract the zip file from linksys properly.

September 21, 2005, at 07:38 AM by anonymous -- Added info about 2.63R63
Added lines 3-6:

Yes. The latest stock firmware from Linksys (2.63R63) allows an NTFS drive to be attached to Port 2. One limitation of doing so it that you will not be able to assign an security settings (users/groups) to the drive like you could with the ext3 extension.

What about with OpenSlug or Unslung?

August 22, 2005, at 03:26 PM by tman --
Added lines 1-19:

Can I setup the NSLU2 to use NTFS partitions?

Currently, no. It is being worked on however.

There are three NTFS drivers for Linux in existance:

  • Captive - http://www.jankratochvil.net/project/captive/

This driver has full read/write support for NTFS because it uses a wrapper around the Windows ntfs.sys binary driver. Porting this to the NSLU2 would require finding a ntfs.sys compiled for ARM and then trying to port the Captive wrapper. Finding a ARM compatible ntfs.sys from Microsoft is basically impossible unless Microsoft decide to port Windows to ARM. Using something like QEMU to emulate a x86 platform to run the ntfs.sys driver is in theory possible but it is not an ideal solution and would entail a large amount of work. You could for example boot a full i386 linux installation in qemu. This installation could access the NTFS via a network block device from the ARM side of things. The i386 qemu could then export the accessed file system via NFS or other means back to the ARM. Short answer is still no. Plus it would be rather slow.

  • Linux NTFS project - http://linux-ntfs.sourceforge.net/status.html

This is a reimplementation of the NTFS file system as a normal Linux driver. As such, it is probably more portable, but it is also more limited. Write support is extremely limited (can only modify existing files, no file size changes), and probably not useful to most NSLU2 users. The new, rewritten version of the NTFS driver is included in the Linux 2.6.9 kernel, so once the OpenSlug project succeeds in getting the 2.6 kernel running on the NSLU2, it will be possible to see if this driver works.

  • Commercial Paragon NTFS for Linux - http://www.ntfs-linux.com/

This is a commercial package which fully supports NTFS read and write. Linksys has included a copy of the driver in 2.3R63 and work is underway to provide a method of extracting this driver and integrating it.

update: Recent (April 2005+) builds of OpenSlug come with the Linux NTFS project kernel module in the flash (though not installed). mount -t ntfs /dev/sdb1 /mnt (with appropriate device/directory) will mount a Windows NTFS partition for read access. At present the (experimental) write access is not compiled in - so the mount is read-only.

view · edit · print · history · Last edited by mkurtz.
Based on work by mwester, emm_is, foobar, slw, os, gna, fcarolo, dglaude, marceln, Macks, Eddie, Lurch, JWith, Diode, mindbender, viewer, tman, jkpeters_37, cbxtom, and anonymous.
Originally by tman.
Page last modified on July 28, 2008, at 12:16 AM