TeraStation larger disks - Revision history

Kenatonline at 11:03, 5 February 2011

Kenatonline — Sat, 05 Feb 2011 11:03:18 GMT

← Older revision		Revision as of 11:03, 5 February 2011
Line 437:		Line 437:

	If you attempt a flash upgrade on a system that has been setup as described in this article and the firmware updater program gives any warnings about invalid partition structure or wants to format any of the disks you should abandon the firmware update as otherwise you will almost certainly lose data.		If you attempt a flash upgrade on a system that has been setup as described in this article and the firmware updater program gives any warnings about invalid partition structure or wants to format any of the disks you should abandon the firmware update as otherwise you will almost certainly lose data.
-
-	~~==External Links==~~
-	~~[http://mackeeper.zeobit.com/mac-recovery-software mac data recovery software]~~

Roderio at 13:10, 28 October 2010

Roderio — Thu, 28 Oct 2010 13:10:58 GMT

← Older revision		Revision as of 13:10, 28 October 2010
Line 437:		Line 437:

	If you attempt a flash upgrade on a system that has been setup as described in this article and the firmware updater program gives any warnings about invalid partition structure or wants to format any of the disks you should abandon the firmware update as otherwise you will almost certainly lose data.		If you attempt a flash upgrade on a system that has been setup as described in this article and the firmware updater program gives any warnings about invalid partition structure or wants to format any of the disks you should abandon the firmware update as otherwise you will almost certainly lose data.
		+
		+	==External Links==
		+	[http://mackeeper.zeobit.com/mac-recovery-software mac data recovery software]

Itimpi: /* SATA Disks on IDE Based Systems */

Itimpi — Sat, 02 Oct 2010 13:31:06 GMT

SATA Disks on IDE Based Systems

← Older revision		Revision as of 13:31, 2 October 2010
Line 30:		Line 30:
	[[Image: Pata-sata.jpg]]		[[Image: Pata-sata.jpg]]

-	The board plugged into the back of the drive and simply converted the connectors from SATA to IDE and there was just enough clearance inside the case to fit the power and IDE cables. The cables are a very tight fit, but you can give yourself a little more space by drilling new holes in the cage that holds the drives about a 1/4 inch nearer the front than the existing holes. This can only be done on the top part of the cage but that is normally enough to hold the drive firmly.	+	The board plugged into the back of the drive and simply converted the connectors from SATA to IDE and there was just enough clearance inside the case to fit the power and IDE cables.
		+
		+	<font color="red">TIP:</font> The cables are a very tight fit, but you can give yourself a little more space by drilling new holes in the cage that holds the drives about a 1/4 inch nearer the front than the existing holes. This can only be done on the top part of the cage but that is normally enough to hold the drive firmly.
	<br>		<br>

Itimpi: /* SATA Disks on IDE Based Systems */

Itimpi — Sat, 02 Oct 2010 13:29:12 GMT

SATA Disks on IDE Based Systems

← Older revision		Revision as of 13:29, 2 October 2010
Line 26:		Line 26:

	=SATA Disks on IDE Based Systems=		=SATA Disks on IDE Based Systems=
-	It is possible to use disks larger than 750GB on an IDE based system via a SATA/IDE converter, although you have to make sure you get one small enough to fit into the available space. The ones tested were obtained via eBay, and consisted of a small PCB that was the same size as the back of a 3.5" drive with a SATA connector on one side and an IDE socket on the other as shown below:	+	It is possible to use disks larger than 750GB on an IDE based system via a SATA/IDE converter, although you have to make sure you get one small enough to fit into the available space. The ones tested were obtained via eBay, and consisted of a small PCB that was the same size as the back of a 3.5" drive with a SATA connector on one side and an IDE socket on the other as shown below: For large disks a SATA drive plus a converter is normally cheaper than the equivalent size IDE drive, so this is attractive from a price point of view.

	[[Image: Pata-sata.jpg]]		[[Image: Pata-sata.jpg]]

-	The board plugged into the back of the drive and simply converted the connectors from SATA to IDE and there was just enough clearance inside the case to fit the power and IDE cables. ~~For large disks~~ a ~~SATA drive plus~~ a ~~converter~~ is normally ~~cheaper than~~ the ~~equivalent size IDE~~ drive~~, so this is attractive from a price point of view~~.	+	The board plugged into the back of the drive and simply converted the connectors from SATA to IDE and there was just enough clearance inside the case to fit the power and IDE cables. The cables are a very tight fit, but you can give yourself a little more space by drilling new holes in the cage that holds the drives about a 1/4 inch nearer the front than the existing holes. This can only be done on the top part of the cage but that is normally enough to hold the drive firmly.
-		+
	<br>		<br>

Itimpi: /* Changing/Upgrading a Single Drive */

Itimpi — Wed, 21 Oct 2009 15:30:48 GMT

Changing/Upgrading a Single Drive

← Older revision		Revision as of 15:30, 21 October 2009
Line 412:		Line 412:
	df		df
	You will see that the disk you have just added is not shown as a mounted filesystem.		You will see that the disk you have just added is not shown as a mounted filesystem.
-	* Use the <code>mfdisk</code> utility as described earlier to set up the partitions. This time you will also have to set up partions 1 and 2 as well as 3 and 4. Partitions 1 and 2 must be at least as large as these partitions on the other disk (you can safely use the <code>mfdisk -c /dev/xxx</code> style command to look at these as long as you do not write out any changes).	+	* Use the <code>mfdisk</code> utility as described earlier to set up the partitions. This time you will also have to set up partions 1 and 2 as well as 3 and 4. Partitions 1 and 2 must be at least as large as these partitions on the other disk (you can safely use the <code>mfdisk -c /dev/xxx</code> style command to look at these as long as you do not write out any changes). <BR>It is probably worth at this point allocating extra space to the system Partition 1 (pobably something more like 1GB rather than the default of around 385MB). You will not use this extra space at this stage but it is the first step towards increasing the free space in the System parition.
	* Format the data partition using a command of the form:		* Format the data partition using a command of the form:
	mkfs.xfs -f /dev/xxx3		mkfs.xfs -f /dev/xxx3

Itimpi: /* material copied from forum thread (temporary) */

Itimpi — Mon, 28 Sep 2009 00:44:03 GMT

material copied from forum thread (temporary)

Show changes

Itimpi: /* Flashing with new Firmware versions */

Itimpi — Mon, 28 Sep 2009 00:40:59 GMT

Flashing with new Firmware versions

Show changes

Itimpi: /* Sample Scripts */

Itimpi — Sun, 06 Sep 2009 16:01:47 GMT

Sample Scripts

← Older revision		Revision as of 16:01, 6 September 2009
Line 396:		Line 396:
	done		done
	</PRE>		</PRE>
		+	Hopefully these scripts can either be used 'as is', or if you have slightly different requirements
		+	they can act as a basis for constructing your own custom scripts.
	<br>		<br>

Itimpi: /* Sample Script */

Itimpi — Sun, 06 Sep 2009 15:59:53 GMT

Sample Script

Show changes

Itimpi: /* Telnet Enabled Firmware */

Itimpi — Sat, 15 Aug 2009 13:28:05 GMT

Telnet Enabled Firmware

← Older revision		Revision as of 13:28, 15 August 2009
Line 60:		Line 60:

	=Telnet Enabled Firmware=		=Telnet Enabled Firmware=
-	TeraStations internally run the Linux operating system. Buffalo hide this from the average user providing the system "packaged" and with a browser based GUI to control and configure iy. Telnet enabled firmware allows users to log in using a telnet client to control and manipulate the system at the Linux command line level.	+	TeraStations internally run the Linux operating system. Buffalo hide this from the average user providing the system "packaged" and with a browser based GUI to control and configure the system. Telnet enabled firmware allows users to log in using a telnet client to control and manipulate the system at the Linux command line level.

	This allows users to do things like:		This allows users to do things like:
Line 70:		Line 70:
	The changes described in this article require the use of a telnet enabled release. Hopefully the instructions provided are detailed enough that users can carry out the steps provided without needing much linux knowledge.		The changes described in this article require the use of a telnet enabled release. Hopefully the instructions provided are detailed enough that users can carry out the steps provided without needing much linux knowledge.

-	The standard software supplied with buffalo PPC based TeraStations does not provide for telnet access. Telnet enabled releases of firmware corresponding to virtually all Buffalo firmware releases can be found at [http://homepage.ntlworld.com/itimpi/buffalo.htm#TERA_TELNET itimpi's website]. These are identical in functionality to the corresponding Buffalo firmware releases - the modification to add ~~telent~~ functionality being trivial. This means they will have exactly the same bugs (if any) as are found in the Buffalo releases.	+	The standard software supplied with buffalo PPC based TeraStations does not provide for telnet access. Telnet enabled releases of firmware corresponding to virtually all Buffalo firmware releases can be found at [http://homepage.ntlworld.com/itimpi/buffalo.htm#TERA_TELNET itimpi's website]. These are identical in functionality to the corresponding Buffalo firmware releases - the modification to add telnet functionality being trivial. This means they will have exactly the same bugs (if any) as are found in the Buffalo releases.

	The itimpi firmware releases are the ones that have been used while preparing this article. Firmware from other sources should work fine as long as it is telnet enabled.		The itimpi firmware releases are the ones that have been used while preparing this article. Firmware from other sources should work fine as long as it is telnet enabled.
Line 80:		Line 80:
	<font color="red">'''TIP:'''</font> If you already have a telnet enabled version of the firmware installed and you want to continue to use that version then you can run the Firmware updater in '''Debug''' mode and elect to not rewrite the linux kernel or boot image in flash, but merely update the hard disk. This is slightly safer as the flash chips have been known to fail.		<font color="red">'''TIP:'''</font> If you already have a telnet enabled version of the firmware installed and you want to continue to use that version then you can run the Firmware updater in '''Debug''' mode and elect to not rewrite the linux kernel or boot image in flash, but merely update the hard disk. This is slightly safer as the flash chips have been known to fail.
	<br><br>		<br><br>
-
-

	=Setting up for Larger Disks=		=Setting up for Larger Disks=