NSLU2-Linux
view · edit · print · history

Unslung.WhichUSBPortforUnslung6 History

Hide minor edits - Show changes to markup

July 15, 2007, at 04:11 PM by mwester -- More formatting
Added line 54:

July 15, 2007, at 04:10 PM by mwester -- Reformatted correction
Deleted lines 22-33:

Addition by marc (http://marc.waeckerlin.org):

Point "The root [...] may not be on a USB hub with other storage devices [...]." seems to be wrong.

No, the statement is correct; the case described in this paragraph is a Multi-LUN device, not a USB hub. Multi-LUN devices are not recommended for use as a root device, as they are normally removable, thus which device becomes /dev/sdb may change. In this special case, the multi-LUN device is a pair of non-removable hard drives, which makes the determination of which is /dev/sdb and which /dev/sdc deterministic -- and thus it works. The original statement that root devices may NOT be on USB hubs stands. ~mwester

Actually I am using two harddisk on the first port in a dual-harddisk-case, one (IDE-Master) is recognized as /dev/sdb, the other (IDE-Slave) as /dev/sdc. The second one, I had to enter manually to /etc/fstab. So, for me it works to have the root device an a second device both on Port 1. I am using a "Sharkoon Twin Drive".

Port 2 is still free, shall be connected to a TV-card vor videorecording later.

Added lines 53-69:

Potential Points of Confusion

Marc writes:

Addition by marc (http://marc.waeckerlin.org):

Point "The root [...] may not be on a USB hub with other storage devices [...]." seems to be wrong.

Actually I am using two harddisk on the first port in a dual-harddisk-case, one (IDE-Master) is recognized as /dev/sdb, the other (IDE-Slave) as /dev/sdc. The second one, I had to enter manually to /etc/fstab. So, for me it works to have the root device an a second device both on Port 1. I am using a "Sharkoon Twin Drive".

Port 2 is still free, shall be connected to a TV-card vor videorecording later.

Response:

No, the original statement is correct; the case Marc describes in the paragraph above is a Multi-LUN device, not a USB hub. Multi-LUN devices are not recommended for use as a root device, as they are normally removable, thus which device becomes /dev/sdb may change. In this special case, the multi-LUN device is a pair of non-removable hard drives, which makes the determination of which is /dev/sdb and which /dev/sdc deterministic -- and thus it works. The original statement that root devices may NOT be on USB hubs stands.

~mwester

July 15, 2007, at 04:07 PM by mwester -- Correction to previous edit
Added line 26:
Added line 28:
Added lines 33-34:
July 15, 2007, at 04:06 PM by mwester -- Correction to previous edit
Changed line 26 from:
to:

No, the statement is correct; the case described in this paragraph is a Multi-LUN device, not a USB hub. Multi-LUN devices are not recommended for use as a root device, as they are normally removable, thus which device becomes /dev/sdb may change. In this special case, the multi-LUN device is a pair of non-removable hard drives, which makes the determination of which is /dev/sdb and which /dev/sdc deterministic -- and thus it works. The original statement that root devices may NOT be on USB hubs stands. ~mwester

July 15, 2007, at 12:36 PM by marcwaeckerlinorg -- Two drives on port 1 (including root) works
Added lines 23-30:

Addition by marc (http://marc.waeckerlin.org):

Point "The root [...] may not be on a USB hub with other storage devices [...]." seems to be wrong.

Actually I am using two harddisk on the first port in a dual-harddisk-case, one (IDE-Master) is recognized as /dev/sdb, the other (IDE-Slave) as /dev/sdc. The second one, I had to enter manually to /etc/fstab. So, for me it works to have the root device an a second device both on Port 1. I am using a "Sharkoon Twin Drive".

Port 2 is still free, shall be connected to a TV-card vor videorecording later.

July 13, 2007, at 10:44 PM by mwester -- Adjusted \\\"definitive\\\" solution to be \\\"a\\\" solution, not the ONLY solution.
Changed lines 39-40 from:

However, in 2.3R63 and unslung 6, if you do follow this rule, you can have odd unexpected behavior where the conf partition from the drive in slot 1 will be mounted for both drives - slot 1 and 2! This leads to very odd behavior with shares being "duplicated" with a tilde-1. e.g.: create "music" on the drive in slot 2 and reboot and you will have "music" pointing to a nonexistant spot on slot 1 and "music~1" pointing to the original spot on slot 2! Reboot again and both are lost. Therefore, the best practice is to only use a single natively formatted drive, and to use diversion scripts to mount the second drive as documented in Unslung.R63DiskBehaviour.

to:

However, in 2.3R63 and unslung 6, if you do follow this rule, you can have odd unexpected behavior where the conf partition from the drive in slot 1 will be mounted for both drives - slot 1 and 2! This leads to very odd behavior with shares being "duplicated" with a tilde-1. e.g.: create "music" on the drive in slot 2 and reboot and you will have "music" pointing to a nonexistant spot on slot 1 and "music~1" pointing to the original spot on slot 2! Reboot again and both are lost. One way to resolve this is to only use a single natively formatted drive, and to use diversion scripts to mount the second drive as documented (temporarily) in Unslung.R63DiskBehaviour.

July 13, 2007, at 05:29 PM by pedxing --
Changed lines 39-40 from:

However, in 2.3R63 and unslung 6, if you do follow this rule, you can have odd unexpected behavior where the conf partition from the drive in slot 1 will be mounted for both drives - slot 1 and 2! This leads to very odd behavior with shares being "duplicated" with a tilde-1. e.g.: create "music" on the drive in slot 2 and reboot and you will have "music" pointing to a nonexistant spot on slot 1 and "music~1" pointing to the original spot on slot 2! Reboot again and both are lost.

to:

However, in 2.3R63 and unslung 6, if you do follow this rule, you can have odd unexpected behavior where the conf partition from the drive in slot 1 will be mounted for both drives - slot 1 and 2! This leads to very odd behavior with shares being "duplicated" with a tilde-1. e.g.: create "music" on the drive in slot 2 and reboot and you will have "music" pointing to a nonexistant spot on slot 1 and "music~1" pointing to the original spot on slot 2! Reboot again and both are lost. Therefore, the best practice is to only use a single natively formatted drive, and to use diversion scripts to mount the second drive as documented in Unslung.R63DiskBehaviour.

July 13, 2007, at 01:34 PM by pedxing --
Added lines 39-40:

However, in 2.3R63 and unslung 6, if you do follow this rule, you can have odd unexpected behavior where the conf partition from the drive in slot 1 will be mounted for both drives - slot 1 and 2! This leads to very odd behavior with shares being "duplicated" with a tilde-1. e.g.: create "music" on the drive in slot 2 and reboot and you will have "music" pointing to a nonexistant spot on slot 1 and "music~1" pointing to the original spot on slot 2! Reboot again and both are lost.

March 01, 2007, at 11:38 AM by jjh -- added link to what is a native unslung disk page
Changed line 14 from:
  1. The root device for Unslung must be natively formatted by the NSLU2 (i.e. it is not sufficient that it simply be formatted as ext3).
to:
  1. The root device for Unslung must be natively formatted by the NSLU2 (i.e. it is not sufficient that it simply be formatted as ext3).
January 13, 2007, at 05:24 PM by Rienk -- Corrected sentence
Changed lines 6-7 from:

The choice of USB port to use as the primary or root device (hard drive or flash memory stick) for the unslung NSLU2 is an important one, because it can often limit future choices, and be difficult to change. This article sets out to assist the new user in determining the best port usage strategy.

to:

The choice of which USB port to use as the primary or root device (hard drive or flash memory stick) for the unslung NSLU2 is an important one, because it can often limit future choices, and be difficult to change. This article sets out to assist the new user in determining the best port usage strategy.

September 24, 2006, at 12:49 AM by mwester -- Root device must be 512MB or larger - corrected error.
Changed line 15 from:
  1. The root device must be 256MB or larger in size.
to:
  1. The root device must be 512MB or larger in size.
August 19, 2006, at 02:37 PM by garglebutt --
Changed lines 37-38 from:

Note also that this applies to both the situation at install time, as well as any future situation. If you do not follow this rule, and later plug a natively formatted device into port #1, the results will be unpredictable, but almost certainly bad. One outcome is loss of access to the slug via telnet, ssh and the web interface.

to:

Note also that this applies to both the situation at install time, as well as any future situation. If you do not follow this rule, and later plug a natively formatted device into port #1, the results will be unpredictable, but almost certainly bad. One outcome is loss of access to the slug via telnet, ssh and the web interface. If this occurs you will need to reflash the slug and unsling to the appropriate disc.

August 19, 2006, at 01:37 PM by garglebutt -- document at least one outcome
Changed lines 37-38 from:

Note also that this applies to both the situation at install time, as well as any future situation. If you do not follow this rule, and later plug a natively formatted device into port #1, the results will be unpredictable, but almost certainly bad.

to:

Note also that this applies to both the situation at install time, as well as any future situation. If you do not follow this rule, and later plug a natively formatted device into port #1, the results will be unpredictable, but almost certainly bad. One outcome is loss of access to the slug via telnet, ssh and the web interface.

May 11, 2006, at 12:07 PM by Jon --
Added lines 39-41:

Another exception?:

I have customised my root device so that it has the ext3 native partitions (which I have unslung on to) but also has an NTFS partition on there. Since NTFS isn't supported by Port2, I have to connect the device to Port1. This isn't ideal since it wastes the other flexibilities of Port1 (being able to connect a hub etc) but seems to be the only option in my case.

Deleted lines 50-51:

Another exception?: I have customised my root device so that it has the ext3 native partitions (which I have unslung on to) but also has an NTFS partition on there. Since NTFS isn't supported by Port2, I have to connect the device to Port1. This isn't ideal since it wastes the other flexibilities of Port1 (being able to connect a hub etc) but seems to be the only option in my case.

May 11, 2006, at 12:05 PM by Jon -- Exception to rule1 when NTFS partition on root device..
Added lines 48-49:

Another exception?: I have customised my root device so that it has the ext3 native partitions (which I have unslung on to) but also has an NTFS partition on there. Since NTFS isn't supported by Port2, I have to connect the device to Port1. This isn't ideal since it wastes the other flexibilities of Port1 (being able to connect a hub etc) but seems to be the only option in my case.

May 02, 2006, at 04:39 PM by mwester -- clarification for what is becoming a FAQ
Changed lines 1-2 from:

Which USB Port Should I Use For my Root Disk?

to:

Which USB Port Should I Use For my Root Device?

Changed lines 6-7 from:

The choice of USB port to use as the primary or root drive for the unslung NSLU2 is an important one, because it can often limit future choices, and be difficult to change. This article sets out to assist the new user in determining the best port usage strategy.

to:

The choice of USB port to use as the primary or root device (hard drive or flash memory stick) for the unslung NSLU2 is an important one, because it can often limit future choices, and be difficult to change. This article sets out to assist the new user in determining the best port usage strategy.

Changed lines 14-16 from:
  1. The root disk for Unslung must be natively formatted by the NSLU2 (i.e. it is not sufficient that it simply be formatted as ext3).
  2. The root disk must be 256MB or larger in size.
  3. The root disk may be on either USB Port 1 or on USB Port 2, but it may not be on a USB hub with other storage devices of any sort.
to:
  1. The root device for Unslung must be natively formatted by the NSLU2 (i.e. it is not sufficient that it simply be formatted as ext3).
  2. The root device must be 256MB or larger in size.
  3. The root device may be on either USB Port 1 or on USB Port 2, but it may not be on a USB hub with other storage devices of any sort.
Changed lines 21-22 from:
  1. If an unslung NSLU2 has a natively formatted disk in each of USB Ports 1 and 2, then the configuration data will always be stored on the disk in USB Port 1, regardless of which disk is the root disk.
to:
  1. If an unslung NSLU2 has a natively formatted device in each of USB Ports 1 and 2, then the configuration data will always be stored on the device in USB Port 1, regardless of which device is the root device.
Changed lines 25-30 from:

Rule #1: The root drive must be connected to USB Port 2.

One of the ports will always be consumed by the root drive. Since clearly USB Port 1 is the most flexible port, plugging the root drive into USB Port 2 and leaving Port 1 open for other devices is the most sensible choice.

But - a problem arises in one specific situation. If a system is Unslung following Rule #1, and a natively-formatted drive is attached to USB Port 1, some Not So Very Good Things can happen. Skipping the gory details, the configuration data that used to be stored on the drive in USB Port 2 will be copied to the new drive in USB Port 1 and it will be used from that location going forward. Once this happens, the NSLU2 is now dependent upon both drives for proper operation.

to:

Rule #1: The root device must be connected to USB Port 2.

One of the ports will always be consumed by the root device. Since clearly USB Port 1 is the most flexible port, plugging the root device into USB Port 2 and leaving Port 1 open for other devices is the most sensible choice.

But - a problem arises in one specific situation. If a system is Unslung following Rule #1, and a natively-formatted device is attached to USB Port 1, some Not So Very Good Things can happen. Skipping the gory details, the configuration data that used to be stored on the device in USB Port 2 will be copied to the new device in USB Port 1 and it will be used from that location going forward. Once this happens, the NSLU2 is now dependent upon both devices for proper operation. (User experiences as noted in the mailing lists seem to imply that the situation is not as simple as the previous sentences imply; and that the addition of a natively-formatted device to an already-unslung NSLU2 will lead to unpredictable but usually "bad" behavior.)

Changed lines 33-36 from:

Exception to Rule #1: If the NSLU2 will have two natively-formatted disks (one on port #1, and the another on port #2), the root drive should be the one connected to USB Port 1.

By doing this, a certain amount of flexibility is sacrificed. However, the resulting Unslung system is only dependent upon the first of the two drive for proper operation.

to:

Exception to Rule #1: If the NSLU2 will have two natively-formatted devices (one on port #1, and the another on port #2), the root device should be the one connected to USB Port 1.

By doing this, a certain amount of flexibility is sacrificed. However, the resulting Unslung system is only dependent upon the first of the two devices for proper operation. Note that this applies to both flash devices as well as disk drives; Unslung makes no distinction between the two.

Note also that this applies to both the situation at install time, as well as any future situation. If you do not follow this rule, and later plug a natively formatted device into port #1, the results will be unpredictable, but almost certainly bad.

Changed lines 41-42 from:

Yes. Using USB Port 2 for disks, and USB Port 1 for flash devices is contrary to the Linksys documentation. But consider that the documentation hasn't been updated since the product was released by Linksys, and they've fundamentally changed how the device handles storage in the R63 firmware. The documentation is just out-of-date.

to:

Yes. Using USB Port 2 for hard disks, and USB Port 1 for flash devices is contrary to the Linksys documentation. But consider that the documentation hasn't been updated since the product was released by Linksys, and they've fundamentally changed how the device handles storage in the R63 firmware. The Linksys documentation is simply out-of-date.

April 29, 2006, at 11:56 PM by K Carter --
Changed lines 33-34 from:

Exception to Rule #1: If the NSLU2 will only have natively-formatted disks, the root drive should be the one connected to USB Port 1.

to:

Exception to Rule #1: If the NSLU2 will have two natively-formatted disks (one on port #1, and the another on port #2), the root drive should be the one connected to USB Port 1.

March 12, 2006, at 01:15 PM by apu -- error corrected (port 1 was meant, not port2)
Changed lines 29-30 from:

But - a problem arises in one specific situation. If a system is Unslung following Rule #1, and a natively-formatted drive is attached to USB Port 2, some Not So Very Good Things can happen. Skipping the gory details, the configuration data that used to be stored on the drive in USB Port 2 will be copied to the new drive in USB Port 1 and it will be used from that location going forward. Once this happens, the NSLU2 is now dependent upon both drives for proper operation.

to:

But - a problem arises in one specific situation. If a system is Unslung following Rule #1, and a natively-formatted drive is attached to USB Port 1, some Not So Very Good Things can happen. Skipping the gory details, the configuration data that used to be stored on the drive in USB Port 2 will be copied to the new drive in USB Port 1 and it will be used from that location going forward. Once this happens, the NSLU2 is now dependent upon both drives for proper operation.

March 05, 2006, at 06:46 AM by mwester -- Initial creation - edits and corrections welcome!
Changed lines 39-40 from:

Yes. It's contrary to the Linksys documentation. But consider that the documentation hasn't been updated since the product was released by Linksys, and they've fundamentally changed how the device handles storage in the R63 firmware. The documentation is just out-of-date.

to:

Yes. Using USB Port 2 for disks, and USB Port 1 for flash devices is contrary to the Linksys documentation. But consider that the documentation hasn't been updated since the product was released by Linksys, and they've fundamentally changed how the device handles storage in the R63 firmware. The documentation is just out-of-date.

March 05, 2006, at 06:41 AM by mwester -- Initial creation - edits and corrections welcome!
Added lines 1-45:

Which USB Port Should I Use For my Root Disk?

This article pertains to:

  • Unslung 6.x only

The choice of USB port to use as the primary or root drive for the unslung NSLU2 is an important one, because it can often limit future choices, and be difficult to change. This article sets out to assist the new user in determining the best port usage strategy.

Before continuing here, please take a moment to read these Wiki articles:

Limitations and Constraints

  1. The root disk for Unslung must be natively formatted by the NSLU2 (i.e. it is not sufficient that it simply be formatted as ext3).
  2. The root disk must be 256MB or larger in size.
  3. The root disk may be on either USB Port 1 or on USB Port 2, but it may not be on a USB hub with other storage devices of any sort.
  4. FAT-formatted devices will be recognized on any port.
  5. NTFS-formatted devices will only be recognized on USB Port 1.
  6. Multi-LUN devices such as USB flash memory card readers will only be recognized on USB Port 1.
  7. USB Hubs will only be recognized (for storage devices) on USB Port 1.
  8. If an unslung NSLU2 has a natively formatted disk in each of USB Ports 1 and 2, then the configuration data will always be stored on the disk in USB Port 1, regardless of which disk is the root disk.

Conclusions

Rule #1: The root drive must be connected to USB Port 2.

One of the ports will always be consumed by the root drive. Since clearly USB Port 1 is the most flexible port, plugging the root drive into USB Port 2 and leaving Port 1 open for other devices is the most sensible choice.

But - a problem arises in one specific situation. If a system is Unslung following Rule #1, and a natively-formatted drive is attached to USB Port 2, some Not So Very Good Things can happen. Skipping the gory details, the configuration data that used to be stored on the drive in USB Port 2 will be copied to the new drive in USB Port 1 and it will be used from that location going forward. Once this happens, the NSLU2 is now dependent upon both drives for proper operation.

This leads us to the following:

Exception to Rule #1: If the NSLU2 will only have natively-formatted disks, the root drive should be the one connected to USB Port 1.

By doing this, a certain amount of flexibility is sacrificed. However, the resulting Unslung system is only dependent upon the first of the two drive for proper operation.

But This is Just Wrong!

Yes. It's contrary to the Linksys documentation. But consider that the documentation hasn't been updated since the product was released by Linksys, and they've fundamentally changed how the device handles storage in the R63 firmware. The documentation is just out-of-date.

I'm Upgrading from Unslung 5.5 - Should I Switch Ports?

Unless Exception #1 listed above applies to you, just move the root drive from USB Port 1 to USB Port 2. Your network shares will change from "DISK 1" to "DISK 2" but that's a small price to pay for the increased flexibility, in most cases.

Regardless of which USB port is chosen, each upgrader is strongly urged to read Unslung.UpgradingToUnslung6 to better understand the types of upgrade and the potential problems and solutions for each approach.

view · edit · print · history · Last edited by mwester.
Based on work by mwester, marcwaeckerlinorg, pedxing, jjh, Rienk, garglebutt, Jon, K Carter, and apu.
Originally by mwester.
Page last modified on July 15, 2007, at 04:11 PM