NSLU2-Linux
- FAQ: Frequently Asked Questions
- Donations
- Downloads
- Trac Bug Tracker
- Package Search Engine
- All Recent Wiki Changes
General
- HowTo Recipes
- Cool Peripherals
- Cool Applications
- Information Pages
- Ideas and Wish List
- Slug Success Stories
- Slug-Related Articles
- Project Mailing Lists
- Project IRC Channels
- Donations and Sponsors
- NSLU2-Linux Photo Gallery
Projects
- NSLU2-Linux Development
- How Do I Get Involved?
- Unslung Firmware
- Optware Packages
- Debian Installation
- SlugOS Firmware
- OpenSlug Firmware
- SlugOS/LE Firmware
- OpenWrt Firmware
- Angstrom Firmware
- UcSlugC Firmware
- GentooSlug Firmware
- UpSlug Upload Tool
- Synology DS-101(g+)
- Iomega NAS 100d
- D-Link DSM-G600
- Freecom FSG-3
- Linksys NAS200
- Maxtor MSS II
- Qnap TurboStation
- Iomega StorCenter
- Puppy Topfield Access
Wiki Resources
Sponsored Links
hosting by:
Disk Behaviour with Linksys R63 Firmware
This article pertains to:
- Unslung 6.x only
Linksys version 2.3R63 has support for NTFS disks, and changes the handling of attached disks significantly from previous versions. This page documents our current knowledge about that new behaviour (which will be mainly preserved in Unslung 6.x).
Single FAT/NTFS device per port
| Scenario | Device | Mount point | Web interface |
| 512MB flash (FAT) in Disk1 | /dev/sdb1 | /share/hdd/data/FLASH_1_1_1 | USB Port 1: Ready (FAT/NTFS), 486MB (0% Free) |
| 512MB flash (FAT) in Disk2 | /dev/sda1 | /share/flash/data/FLASH_2_1_1 | USB Port 2: Ready (FAT/NTFS), 486MB (100% Free) |
| 1.5GB Cornice (NTFS) in Disk1 | /dev/sdb1 | /share/hdd/data/FLASH_1_1_1 | USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free) |
| 1.5GB Cornice (NTFS) in Disk2 | N/A | Unable to mount NTFS on Disk2 | USB Port 2: Not Formatted |
| 40GB hard disk (NTFS) in Disk1 | /dev/sdb1 | /share/hdd/data/HDD_1_1_1 | USB Port 1: Ready (FAT/NTFS), 38857MB (0% Free) |
| 40GB hard disk (NTFS) in Disk2 | N/A | Unable to mount NTFS on Disk2 | USB Port 2: Not Formatted |
FAT partitions are recognised on Disk1 (USB Port 1) and Disk2 (USB Port 2). NTFS partitions are only recognised on Disk1.
Multiple partitions per single device
| Scenario | Device | Mount point | Web interface |
| 1.5GB Cornice (NTFS) in Disk1 (NTFS partition) | /dev/sdb1 | /share/hdd/data/FLASH_1_1_1 | USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free) |
| + 1.5GB Cornice (NTFS) in Disk1 (NTFS partition) | /dev/sdb2 | /share/hdd/data/FLASH_1_1_2 | USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free) |
| + 1.5GB Cornice (NTFS) in Disk1 (NTFS partition) | /dev/sdb3 | /share/hdd/data/FLASH_1_1_3 | USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free) |
| + 1.5GB Cornice (NTFS) in Disk1 (FAT partition) | /dev/sdb4 | /share/hdd/data/FLASH_1_1_4 | USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free) |
| Scenario | Device | Mount point | Web interface |
| 40GB hard disk (NTFS) in Disk1 (NTFS partition) | /dev/sdb1 | /share/hdd/data/HDD_1_1_1 | USB Port 1: Ready (FAT/NTFS), 38792MB (0% Free) |
| + 40GB hard disk (NTFS) in Disk1 (NTFS partition) | /dev/sdb2 | /share/hdd/data/HDD_1_1_2 | USB Port 1: Ready (FAT/NTFS), 38792MB (0% Free) |
Disk1 will mount multiple FAT and NTFS partitions. Disk2 will only mount FAT partitions.
Multiple FAT/NTFS devices per port (using a hub)
| Scenario | Device | Mount point | Web interface |
| 512MB flash (FAT) in Disk1 (via USB 1.1 hub) | /dev/sdb1 | /share/hdd/data/FLASH_1_1_1 | USB Port 1: Ready (FAT/NTFS), 486MB (0% Free) |
| + 256MB flash (FAT) in Disk1 (via USB 1.1 hub) | /dev/sdc1 | /share/hdd/data/FLASH_1_2_1 | USB Port 1: Multiple Drives Ready (FAT/NTFS) ... |
| + 1.5GB Cornice (NTFS) in Disk1 (via USB 1.1 hub) | /dev/sdd1 | /share/hdd/data/FLASH_1_3_1 | USB Port 1: Multiple Drives Ready (FAT/NTFS) ... |
| + 40GB hard disk (NTFS) in Disk1 (via USB 1.1 hub) | /dev/sde1 | /share/hdd/data/HDD_1_4_1 | USB Port 1: Multiple Drives Ready (FAT/NTFS) ... |
Multiple FAT/NTFS devices behind a hub are only recognised on USB Port 1.
On USB Port 2, only the first single device plugged in is mounted and any additional devices are ignored (even if the first device is subsequently disconnected).
Installation Recommendations
If you want to use a hub with Unslung 6.x it has to be connected to USB Port 1. The firmware is able to recognize multiple disks behind the hub and mount them auto magically.
Unfortunately you can't put your root disk on the hub. The first found disk on the hub will be used as "/dev/sdb" and there is no reliable way to ensure that the root disk is always "/dev/sdb".
The best solution is to simply put the Unslung root disk on USB Port 2.
There is a discusion about this on the mailinglist.
Odd Behavior
rc.bootbin in 2.3R63 (and thus Unslung 6.x) behaves oddly when confronted with two native ext3 formatted drives. In short, it mounts the conf partition (number 2) of the device in slot 2 (/dev/sdb) in both /share/hdd/conf and /share/flash/conf! This is Very Bad since it effectively deletes your share configuration (and password file) every time it reboots, resulting in an odd appearance of tilde-1 versions of your shares.
For example, let's say you unslung to a flash drive in slot 2 and have a native-formatted hard disk in slot 1 (as suggested in numerous 6.x documents). Now you create a "music" share on the hard disk. This creates /share/flash/data/music and adds it to /share/flash/conf/share.info. Now you reboot. You will be surprised to find an unusable "music" share pointing to the nonexistant /share/hdd/data/music, and a usable but unmanageable "music~1" share pointing to /share/flash/data/music. Now reboot again. Your music share is gone (though the data remains).
The solution suggested as "exception to rule #1" in WhichUSBPortforUnslung6, putting the root (flash) device in port 1 and the usb disk in port 2, does not solve this problem. See NonNativeDiskMount for a workable solution.