NSLU2-Linux
view · edit · print · history

Unslung.R63DiskBehaviour History

Hide minor edits - Show changes to markup

December 29, 2009, at 10:33 AM by PaulBrandt -- Added solution to section OddBehaviour
Added lines 76-80:

Solution to Odd behaviour

Added 2009-12-29 by PaulBrandt?

Indeed the incorrect mounting of both drive's /conf onto /dev/sdb is the source of this issue. An apparent solution has been described in CorrectBadSharingWithTwoDrives . Thanks to Alain for pointing this out.

October 05, 2008, at 11:31 PM by CncZane --
Added lines 84-85:

Of course, if disk 1 had exploded and I had tried to institute my mad plan of then booting off disk 2, THEN I would have been bit by disk 2 having disk 1's conf partition...

October 05, 2008, at 11:28 PM by CncZane -- Why I never ran into the problem w/2 natively formatted drives.
Changed lines 74-84 from:

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.

to:

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.

=====

I have ~never~ run into this problem in my 6.8 setup, and I consciously (but ineffectively, according to this article) elected to format BOTH 300Mb drives using Linksys's format util because I wanted to be able to "boot off the other one if the first one failed." (I had no idea that the second one's conf was being blown away each time.)

However, puzzling over why I never had a problem with my shares, I realized its because I never used the webpages to define them! Instead, I (apparently) edited smb.conf via ssh and used smbpasswd to create smbpasswd, only on the master disk. I accessed the second drive's "share" folders by putting links to them in the first drive's data/public folder, so it appeared that all my shares resided on disk 1. As a result, no share information lived on drive 2 so blowing it away never affected anything.

Sometimes it's better to be lucky than smart...

=====

September 21, 2007, at 09:27 PM by fcarolo -- undid spam
Changed lines 1-74 from:

[url=http://biotechteensex.741.com/sitemap.xml]wet blonde teen sex[/url] <a href="http://biotechteensex.741.com/sitemap.xml">wet blonde teen sex</a>

to:

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

ScenarioDeviceMount pointWeb interface
512MB flash (FAT) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 486MB (0% Free)
512MB flash (FAT) in Disk2/dev/sda1/share/flash/data/FLASH_2_1_1USB Port 2: Ready (FAT/NTFS), 486MB (100% Free)
1.5GB Cornice (NTFS) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
1.5GB Cornice (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB Port 2: Not Formatted
40GB hard disk (NTFS) in Disk1/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38857MB (0% Free)
40GB hard disk (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB 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

ScenarioDeviceMount pointWeb interface
1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/FLASH_1_1_2USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb3/share/hdd/data/FLASH_1_1_3USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (FAT partition)/dev/sdb4/share/hdd/data/FLASH_1_1_4USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
ScenarioDeviceMount pointWeb interface
40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38792MB (0% Free)
+ 40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/HDD_1_1_2USB 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)

ScenarioDeviceMount pointWeb interface
512MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB 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_1USB 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_1USB 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_1USB 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

See WhichUSBPortforUnslung6.

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.

September 21, 2007, at 09:06 PM by medved --
Changed lines 1-74 from:

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

ScenarioDeviceMount pointWeb interface
512MB flash (FAT) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 486MB (0% Free)
512MB flash (FAT) in Disk2/dev/sda1/share/flash/data/FLASH_2_1_1USB Port 2: Ready (FAT/NTFS), 486MB (100% Free)
1.5GB Cornice (NTFS) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
1.5GB Cornice (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB Port 2: Not Formatted
40GB hard disk (NTFS) in Disk1/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38857MB (0% Free)
40GB hard disk (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB 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

ScenarioDeviceMount pointWeb interface
1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/FLASH_1_1_2USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb3/share/hdd/data/FLASH_1_1_3USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (FAT partition)/dev/sdb4/share/hdd/data/FLASH_1_1_4USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
ScenarioDeviceMount pointWeb interface
40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38792MB (0% Free)
+ 40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/HDD_1_1_2USB 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)

ScenarioDeviceMount pointWeb interface
512MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB 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_1USB 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_1USB 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_1USB 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

See WhichUSBPortforUnslung6.

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.

to:

[url=http://biotechteensex.741.com/sitemap.xml]wet blonde teen sex[/url] <a href="http://biotechteensex.741.com/sitemap.xml">wet blonde teen sex</a>

September 21, 2007, at 01:52 PM by Trurl --
Changed lines 1-74 from:

[url=http://mp3zz.741.com/sitemap.xml]mp3 zz[/url] <a href="http://mp3zz.741.com/sitemap.xml">mp3 zz</a>

to:

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

ScenarioDeviceMount pointWeb interface
512MB flash (FAT) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 486MB (0% Free)
512MB flash (FAT) in Disk2/dev/sda1/share/flash/data/FLASH_2_1_1USB Port 2: Ready (FAT/NTFS), 486MB (100% Free)
1.5GB Cornice (NTFS) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
1.5GB Cornice (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB Port 2: Not Formatted
40GB hard disk (NTFS) in Disk1/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38857MB (0% Free)
40GB hard disk (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB 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

ScenarioDeviceMount pointWeb interface
1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/FLASH_1_1_2USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb3/share/hdd/data/FLASH_1_1_3USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (FAT partition)/dev/sdb4/share/hdd/data/FLASH_1_1_4USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
ScenarioDeviceMount pointWeb interface
40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38792MB (0% Free)
+ 40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/HDD_1_1_2USB 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)

ScenarioDeviceMount pointWeb interface
512MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB 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_1USB 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_1USB 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_1USB 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

See WhichUSBPortforUnslung6.

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.

September 21, 2007, at 08:26 AM by preved --
Changed lines 1-74 from:

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

ScenarioDeviceMount pointWeb interface
512MB flash (FAT) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 486MB (0% Free)
512MB flash (FAT) in Disk2/dev/sda1/share/flash/data/FLASH_2_1_1USB Port 2: Ready (FAT/NTFS), 486MB (100% Free)
1.5GB Cornice (NTFS) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
1.5GB Cornice (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB Port 2: Not Formatted
40GB hard disk (NTFS) in Disk1/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38857MB (0% Free)
40GB hard disk (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB 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

ScenarioDeviceMount pointWeb interface
1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/FLASH_1_1_2USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb3/share/hdd/data/FLASH_1_1_3USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (FAT partition)/dev/sdb4/share/hdd/data/FLASH_1_1_4USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
ScenarioDeviceMount pointWeb interface
40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38792MB (0% Free)
+ 40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/HDD_1_1_2USB 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)

ScenarioDeviceMount pointWeb interface
512MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB 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_1USB 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_1USB 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_1USB 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

See WhichUSBPortforUnslung6.

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.

to:

[url=http://mp3zz.741.com/sitemap.xml]mp3 zz[/url] <a href="http://mp3zz.741.com/sitemap.xml">mp3 zz</a>

July 16, 2007, at 10:03 PM by pedxing --
Deleted lines 67-69:

NOTE: The information below should be moved to its own wiki article - ~mwester

Changed lines 70-71 from:

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.

to:

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.

Changed lines 74-121 from:

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.

How to set up a workable two-disk configuration in R63/Unslung6

Due to the odd behavior of rc.bootbin as discussed above, it is not advisable to use two natively-formatted disks in R63 or Unslung6!

The following setup does work, however!

We will use a USB flash disk in port 2 (/dev/sda) and a USB hard disk in port 1 (/dev/sdb). This maximizes flexibility and compatibility.

  1. Start with a fresh NSLU2!
  2. Install Unslung 6.x. Do not configure any shares or users yet!
  3. Insert the flash drive in port 2 and format it through the Web interface. It will remain here forever!
  4. Reboot
  5. Get a shell and unsling to the flash with "unsling disk2"
  6. Reboot
  7. Use another PC to configure your USB hard disk (or second flash device) with a single large partition, if it isn't that way already. You will not be using the GUI on the NSLU2 to partition it!
  8. Plut the second USB drive into port 1 of the NSLU2
  9. Get a shell and format it as ext3 with "mkfs.ext3 /dev/sdb1"
  10. We will mount it under the flash disk at /share/flash/data/sdb. You must create this directory now from the shell with "mkdir /share/flash/data/sdb".
  11. Now we have to tell the slug to mount the drive on startup after running rc.bootbin but before starting Samba. We'll do this with a diversion script called /unslung/rc.samba. From the shell, type "cat > /unslung/rc.samba" and paste in the following text:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
#! /bin/sh
# Diversion script: to mount a formatted drive under /share/flash/data
#
mount /dev/sdb1 /share/flash/data/sdb

return 1

(:tableend:)

  1. Now reboot. When it comes up, your df output should look like this:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 
# df
Filesystem           1k-blocks      Used Available Use% Mounted on
rootfs                  723320     34748    681224   5% /
/dev/sda1                 6528      6328       200  97% /initrd
/dev/sda1               723320     34748    681224   5% /
/dev/sda1               723320     34748    681224   5% /share/flash/data
/dev/sda2               123811      4144    118389   3% /share/flash/conf
/dev/sdb1            480719056   5497276 450802580   1% /share/flash/data/sdb

(:tableend:)

  1. Now you can create users and shares. Specify "Disk 2" for shares and specify "/sdb/whatever" when creating a share. For example, a music share would be on "Disk 2" and would specify the "/sdb/music/" folder in the GUI. Don't worry - it'll actually reside on the disk you mounted on sdb.
  2. Note that any user shares you create will be created on the disk in port 2 (the flash disk) as you can't specify where to put them! So maybe you won't want to create them...
to:

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.

July 13, 2007, at 10:47 PM by mwester -- Note that this article is now overloaded and needs to be split
Changed lines 68-69 from:

NOTE: The information below should be moved to its own wiki article - mwester

to:

NOTE: The information below should be moved to its own wiki article - ~mwester

July 13, 2007, at 10:46 PM by mwester -- Note that this article is now overloaded and needs to be split
Added lines 68-69:

NOTE: The information below should be moved to its own wiki article - mwester

July 13, 2007, at 05:54 PM by pedxing --
Changed lines 97-98 from:

[=#! /bin/sh

to:
 [=
  1. ! /bin/sh
Changed lines 109-110 from:

[=# df

to:
 [=
  1. df
July 13, 2007, at 05:53 PM by pedxing --
Changed line 97 from:
 [=#! /bin/sh
to:

[=#! /bin/sh

Changed line 108 from:
 [=# df
to:

[=# df

July 13, 2007, at 05:50 PM by pedxing --
Changed lines 95-100 from:
  #! /bin/sh
  # Diversion script: to mount a formatted drive under /share/flash/data
  #
  mount /dev/sdb1 /share/flash/data/sdb

  return 1
to:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 #! /bin/sh
# Diversion script: to mount a formatted drive under /share/flash/data
#
mount /dev/sdb1 /share/flash/data/sdb

return 1

(:tableend:)

Changed lines 106-113 from:
  # df
  Filesystem           1k-blocks      Used Available Use% Mounted on
  rootfs                  723320     34748    681224   5% /
  /dev/sda1                 6528      6328       200  97% /initrd
  /dev/sda1               723320     34748    681224   5% /
  /dev/sda1               723320     34748    681224   5% /share/flash/data
  /dev/sda2               123811      4144    118389   3% /share/flash/conf
  /dev/sdb1            480719056   5497276 450802580   1% /share/flash/data/sdb
to:

(:table border=0 width=100% bgcolor=#eeeeff:) (:cell:)

 # df
Filesystem           1k-blocks      Used Available Use% Mounted on
rootfs                  723320     34748    681224   5% /
/dev/sda1                 6528      6328       200  97% /initrd
/dev/sda1               723320     34748    681224   5% /
/dev/sda1               723320     34748    681224   5% /share/flash/data
/dev/sda2               123811      4144    118389   3% /share/flash/conf
/dev/sdb1            480719056   5497276 450802580   1% /share/flash/data/sdb

(:tableend:)

July 13, 2007, at 05:49 PM by pedxing --
Changed lines 94-102 from:
  1. Now we have to tell the slug to mount the drive on startup after running rc.bootbin but before starting Samba. We'll do this with a diversion script called /unslung/rc.samba. From the shell, type "cat > /unslung/rc.samba" and paste in the following text:

<pre>

  1. ! /bin/sh
  2. Diversion script: to mount a formatted drive under /share/flash/data

mount /dev/sdb1 /share/flash/data/sdb

return 1 </pre>

to:
  1. Now we have to tell the slug to mount the drive on startup after running rc.bootbin but before starting Samba. We'll do this with a diversion script called /unslung/rc.samba. From the shell, type "cat > /unslung/rc.samba" and paste in the following text:
    1. ! /bin/sh
    2. Diversion script: to mount a formatted drive under /share/flash/data
    mount /dev/sdb1 /share/flash/data/sdb
    return 1
Changed lines 102-111 from:

<pre>

  1. df

Filesystem 1k-blocks Used Available Use% Mounted on rootfs 723320 34748 681224 5% / /dev/sda1 6528 6328 200 97% /initrd /dev/sda1 723320 34748 681224 5% / /dev/sda1 723320 34748 681224 5% /share/flash/data /dev/sda2 123811 4144 118389 3% /share/flash/conf /dev/sdb1 480719056 5497276 450802580 1% /share/flash/data/sdb </pre>

to:
  # df
  Filesystem           1k-blocks      Used Available Use% Mounted on
  rootfs                  723320     34748    681224   5% /
  /dev/sda1                 6528      6328       200  97% /initrd
  /dev/sda1               723320     34748    681224   5% /
  /dev/sda1               723320     34748    681224   5% /share/flash/data
  /dev/sda2               123811      4144    118389   3% /share/flash/conf
  /dev/sdb1            480719056   5497276 450802580   1% /share/flash/data/sdb
July 13, 2007, at 05:47 PM by pedxing --
Changed lines 80-115 from:

The following setup does work, however!

to:

The following setup does work, however!

We will use a USB flash disk in port 2 (/dev/sda) and a USB hard disk in port 1 (/dev/sdb). This maximizes flexibility and compatibility.

  1. Start with a fresh NSLU2!
  2. Install Unslung 6.x. Do not configure any shares or users yet!
  3. Insert the flash drive in port 2 and format it through the Web interface. It will remain here forever!
  4. Reboot
  5. Get a shell and unsling to the flash with "unsling disk2"
  6. Reboot
  7. Use another PC to configure your USB hard disk (or second flash device) with a single large partition, if it isn't that way already. You will not be using the GUI on the NSLU2 to partition it!
  8. Plut the second USB drive into port 1 of the NSLU2
  9. Get a shell and format it as ext3 with "mkfs.ext3 /dev/sdb1"
  10. We will mount it under the flash disk at /share/flash/data/sdb. You must create this directory now from the shell with "mkdir /share/flash/data/sdb".
  11. Now we have to tell the slug to mount the drive on startup after running rc.bootbin but before starting Samba. We'll do this with a diversion script called /unslung/rc.samba. From the shell, type "cat > /unslung/rc.samba" and paste in the following text:

<pre>

  1. ! /bin/sh
  2. Diversion script: to mount a formatted drive under /share/flash/data

mount /dev/sdb1 /share/flash/data/sdb

return 1 </pre>

  1. Now reboot. When it comes up, your df output should look like this:

<pre>

  1. df

Filesystem 1k-blocks Used Available Use% Mounted on rootfs 723320 34748 681224 5% / /dev/sda1 6528 6328 200 97% /initrd /dev/sda1 723320 34748 681224 5% / /dev/sda1 723320 34748 681224 5% /share/flash/data /dev/sda2 123811 4144 118389 3% /share/flash/conf /dev/sdb1 480719056 5497276 450802580 1% /share/flash/data/sdb </pre>

  1. Now you can create users and shares. Specify "Disk 2" for shares and specify "/sdb/whatever" when creating a share. For example, a music share would be on "Disk 2" and would specify the "/sdb/music/" folder in the GUI. Don't worry - it'll actually reside on the disk you mounted on sdb.
  2. Note that any user shares you create will be created on the disk in port 2 (the flash disk) as you can't specify where to put them! So maybe you won't want to create them...
July 13, 2007, at 05:31 PM by pedxing -- Workable solution
Changed lines 74-80 from:

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.

to:

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.

How to set up a workable two-disk configuration in R63/Unslung6

Due to the odd behavior of rc.bootbin as discussed above, it is not advisable to use two natively-formatted disks in R63 or Unslung6!

The following setup does work, however!

July 13, 2007, at 02:10 PM by pedxing --
Changed line 74 from:

The solution to this problem is simply to follow the "exception to rule #1" in WhichUSBPortforUnslung6. That is, put the root (flash) device in port 1 and the usb disk in port 2.

to:

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.

July 12, 2007, at 05:38 PM by pedxing -- fix
Changed lines 72-74 from:

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).

to:

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 to this problem is simply to follow the "exception to rule #1" in WhichUSBPortforUnslung6. That is, put the root (flash) device in port 1 and the usb disk in port 2.

July 12, 2007, at 04:31 PM by pedxing -- Bad behavior!
Changed lines 66-72 from:

mailinglist.

to:

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).

March 05, 2006, at 06:56 AM by mwester --
Changed lines 19-20 from:

FAT partitions are recognised on Disk1 and Disk2. NTFS partitions are only recognised on Disk1.

to:

FAT partitions are recognised on Disk1 (USB Port 1) and Disk2 (USB Port 2). NTFS partitions are only recognised on Disk1.

March 05, 2006, at 06:55 AM by mwester --
Changed lines 50-51 from:

Installation recommendations

to:

Installation Recommendations

March 05, 2006, at 06:54 AM by mwester --
Added lines 3-5:

This article pertains to:

  • Unslung 6.x only
March 05, 2006, at 06:54 AM by mwester --
Changed lines 1-2 from:

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 become part of Unslung 6.x).

to:

Disk Behaviour with Linksys R63 Firmware

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).

Changed lines 43-46 from:

Multiple FAT/NTFS devices behind a hub are only recognised on Disk1.

On Disk2, only the first single device plugged in is mounted and any additional devices are ignored (even if the first device is subsequently disconnected).

to:

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).

Changed lines 49-50 from:

If you want to use a hub with unslung 6.x it has to be connected to port 1. The firmware is able to recognize

to:

See WhichUSBPortforUnslung6.

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

Changed line 55 from:

Unfortunately you can't put your root disk in the hub. The

to:

Unfortunately you can't put your root disk on the hub. The

Changed lines 60-61 from:

The solution is to put the unslung root disk on port 2.

to:

The best solution is to simply put the Unslung root disk on USB Port 2.

January 12, 2006, at 01:56 PM by marceln -- Installation recommendations
Added lines 44-59:

Installation recommendations

If you want to use a hub with unslung 6.x it has to be connected to 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 in 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 solution is to put the unslung root disk on port 2.

There is a discusion about this on the mailinglist.

December 12, 2005, at 09:04 PM by rwhitby --
Deleted lines 24-27:

Disk1 will mount multiple FAT and NTFS partitions. Disk2 will only mount FAT partitions.

Multiple FAT/NTFS devices per port (using a hub)

Added lines 27-35:
40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38792MB (0% Free)
+ 40GB hard disk (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/HDD_1_1_2USB 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)

ScenarioDeviceMount pointWeb interface
December 12, 2005, at 07:13 PM by rwhitby --
Changed lines 14-17 from:

Multiple partitions per device

to:

FAT partitions are recognised on Disk1 and Disk2. NTFS partitions are only recognised on Disk1.

Multiple partitions per single device

Changed lines 21-24 from:
1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/FLASH_1_1_2USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb3/share/hdd/data/FLASH_1_1_3USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
1.5GB Cornice (NTFS) in Disk1 (FAT partition)/dev/sdb4/share/hdd/data/FLASH_1_1_4USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
to:
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/FLASH_1_1_2USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb3/share/hdd/data/FLASH_1_1_3USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
+ 1.5GB Cornice (NTFS) in Disk1 (FAT partition)/dev/sdb4/share/hdd/data/FLASH_1_1_4USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)

Disk1 will mount multiple FAT and NTFS partitions. Disk2 will only mount FAT partitions.

December 12, 2005, at 07:07 PM by rwhitby --
Changed lines 14-15 from:

Multiple FAT/NTFS devices per port (using a hub)

to:

Multiple partitions per device

Added lines 17-25:
1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb2/share/hdd/data/FLASH_1_1_2USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
1.5GB Cornice (NTFS) in Disk1 (NTFS partition)/dev/sdb3/share/hdd/data/FLASH_1_1_3USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
1.5GB Cornice (NTFS) in Disk1 (FAT partition)/dev/sdb4/share/hdd/data/FLASH_1_1_4USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)

Multiple FAT/NTFS devices per port (using a hub)

ScenarioDeviceMount pointWeb interface
December 12, 2005, at 06:33 PM by rwhitby --
Added line 10:
1.5GB Cornice (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB Port 2: Not Formatted
Changed lines 12-13 from:
to:
40GB hard disk (NTFS) in Disk2N/AUnable to mount NTFS on Disk2USB Port 2: Not Formatted
December 12, 2005, at 06:25 PM by rwhitby --
Added line 9:
1.5GB Cornice (NTFS) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 1378MB (0% Free)
Changed lines 18-20 from:
+ 256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdd1/share/hdd/data/FLASH_1_3_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
+ 1.5GB Cornice (NTFS) in Disk1 (via USB 1.1 hub)/dev/sde1/share/hdd/data/FLASH_1_4_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
to:
+ 1.5GB Cornice (NTFS) in Disk1 (via USB 1.1 hub)/dev/sdd1/share/hdd/data/FLASH_1_3_1USB 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_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
December 12, 2005, at 06:19 PM by rwhitby --
Changed lines 9-10 from:
to:
40GB hard disk (NTFS) in Disk1/dev/sdb1/share/hdd/data/HDD_1_1_1USB Port 1: Ready (FAT/NTFS), 38857MB (0% Free)
December 12, 2005, at 05:32 PM by rwhitby --
Changed lines 19-21 from:

Multiple FAT/NTFS devices behind a hub are only recognised on Disk1. On Disk2, only the first single device plugged in is mounted and any additional devices are ignored (even if the first device is subsequently disconnected).

to:

Multiple FAT/NTFS devices behind a hub are only recognised on Disk1.

On Disk2, only the first single device plugged in is mounted and any additional devices are ignored (even if the first device is subsequently disconnected).

December 12, 2005, at 05:31 PM by rwhitby --
Changed lines 15-18 from:
256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdc1/share/hdd/data/FLASH_1_2_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdd1/share/hdd/data/FLASH_1_3_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
1.5GB Cornice (NTFS) in Disk1 (via USB 1.1 hub)/dev/sde1/share/hdd/data/FLASH_1_4_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
to:
+ 256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdc1/share/hdd/data/FLASH_1_2_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
+ 256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdd1/share/hdd/data/FLASH_1_3_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
+ 1.5GB Cornice (NTFS) in Disk1 (via USB 1.1 hub)/dev/sde1/share/hdd/data/FLASH_1_4_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
December 12, 2005, at 05:31 PM by rwhitby --
Deleted line 16:

<<<<<<<

Deleted lines 19-26:

=======

1.5GB Cornice (NTFS) in Disk1 (via USB 1.1 hub)/dev/sde1/share/hdd/data/FLASH_1_4_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...

Multiple FAT/NTFS devices behind a hub are not recognised on Disk2. Only the first device plugged in is mounted. >>>>>>>

December 12, 2005, at 05:30 PM by rwhitby --
Added line 17:

<<<<<<<

Added lines 20-25:

Multiple FAT/NTFS devices behind a hub are only recognised on Disk1. On Disk2, only the first single device plugged in is mounted and any additional devices are ignored (even if the first device is subsequently disconnected).

=======

1.5GB Cornice (NTFS) in Disk1 (via USB 1.1 hub)/dev/sde1/share/hdd/data/FLASH_1_4_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
Changed lines 27-28 from:
to:

>>>>>>>

December 12, 2005, at 05:27 PM by rwhitby --
Changed lines 3-4 from:

Single device per port

to:

Single FAT/NTFS device per port

Changed lines 10-11 from:

Multiple devices per port

to:

Multiple FAT/NTFS devices per port (using a hub)

Changed lines 17-20 from:
to:
1.5GB Cornice (NTFS) in Disk1 (via USB 1.1 hub)/dev/sde1/share/hdd/data/FLASH_1_4_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...

Multiple FAT/NTFS devices behind a hub are not recognised on Disk2. Only the first device plugged in is mounted.

December 12, 2005, at 05:21 PM by rwhitby --
Changed lines 15-17 from:
256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdc1/share/hdd/data/FLASH_1_2_1USB Port 1: Multiple Drives Ready (FAT/NTFS) OTi? Flash Disk : 242MB (95% Free) FLASH: 486MB (0% Free)
to:
256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdc1/share/hdd/data/FLASH_1_2_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdd1/share/hdd/data/FLASH_1_3_1USB Port 1: Multiple Drives Ready (FAT/NTFS) ...
December 12, 2005, at 05:18 PM by rwhitby --
Added lines 3-4:

Single device per port

Changed lines 9-10 from:
256MB flash (FAT) in Disk1\\(via USB 1.1 hub alongside existing 512MB flash)/dev/sdc1/share/hdd/data/FLASH_1_2_1USB Port 1: Multiple Drives Ready (FAT/NTFS)\\OTi? Flash Disk : 242MB (95% Free)\\FLASH: 486MB (0% Free)
to:

Multiple devices per port

ScenarioDeviceMount pointWeb interface
512MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdb1/share/hdd/data/FLASH_1_1_1USB 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_1USB Port 1: Multiple Drives Ready (FAT/NTFS) OTi? Flash Disk : 242MB (95% Free) FLASH: 486MB (0% Free)
December 12, 2005, at 05:16 PM by rwhitby --
Changed lines 7-8 from:
Additional 256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdc1/share/hdd/data/FLASH_1_2_1USB Port 1: Multiple Drives Ready (FAT/NTFS) OTi? Flash Disk : 242MB (95% Free) FLASH: 486MB (0% Free)
to:
256MB flash (FAT) in Disk1\\(via USB 1.1 hub alongside existing 512MB flash)/dev/sdc1/share/hdd/data/FLASH_1_2_1USB Port 1: Multiple Drives Ready (FAT/NTFS)\\OTi? Flash Disk : 242MB (95% Free)\\FLASH: 486MB (0% Free)
December 12, 2005, at 05:15 PM by rwhitby --
Changed lines 5-6 from:
512MB flash disk (FAT) plugged into Disk1 port/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 486MB (0% Free)
512MB flash disk (FAT) plugged into Disk2 port/dev/sda1/share/flash/data/FLASH_2_1_1USB Port 2: Ready (FAT/NTFS), 486MB (100% Free)
to:
512MB flash (FAT) in Disk1/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 486MB (0% Free)
512MB flash (FAT) in Disk2/dev/sda1/share/flash/data/FLASH_2_1_1USB Port 2: Ready (FAT/NTFS), 486MB (100% Free)
Additional 256MB flash (FAT) in Disk1 (via USB 1.1 hub)/dev/sdc1/share/hdd/data/FLASH_1_2_1USB Port 1: Multiple Drives Ready (FAT/NTFS) OTi? Flash Disk : 242MB (95% Free) FLASH: 486MB (0% Free)
December 12, 2005, at 05:12 PM by rwhitby --
Added lines 1-6:

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 become part of Unslung 6.x).

ScenarioDeviceMount pointWeb interface
512MB flash disk (FAT) plugged into Disk1 port/dev/sdb1/share/hdd/data/FLASH_1_1_1USB Port 1: Ready (FAT/NTFS), 486MB (0% Free)
512MB flash disk (FAT) plugged into Disk2 port/dev/sda1/share/flash/data/FLASH_2_1_1USB Port 2: Ready (FAT/NTFS), 486MB (100% Free)
view · edit · print · history · Last edited by PaulBrandt.
Based on work by CncZane, fcarolo, medved, Trurl, preved, pedxing, mwester, marceln, and rwhitby.
Originally by rwhitby.
Page last modified on December 29, 2009, at 10:33 AM