Terastation Recovery - Revision history

Maettwurst: /* Recovering files from NAS with Windows PC */ - spelling and grammar

Maettwurst — Tue, 06 Nov 2012 18:05:40 GMT

Recovering files from NAS with Windows PC: - spelling and grammar

Maettwurst: /* Obtaining Files for System Partition */ - grammar and spelling

Maettwurst — Tue, 06 Nov 2012 17:55:50 GMT

Obtaining Files for System Partition: - grammar and spelling

← Older revision		Revision as of 17:55, 6 November 2012
Line 330:		Line 330:

	=Obtaining Files for System Partition=		=Obtaining Files for System Partition=
-	For some of the ~~types~~ of TeraStation recovery it can be useful to have copies of the files that the firmware updater would write to the ~~System~~ partition.	+	For some of the methods of TeraStation recovery it can be useful to have copies of the files that the firmware updater would write to the system partition.

-	This is easy if you have access to PPC based ~~linux~~ system. Proceed as follows:	+	This is easy if you have access to PPC based Linux system. Proceed as follows:
	* Download the file [http://homepage.ntlworld.com/itimpi/download/tera_newfiles.tgz tera_newfiles.tgz].		* Download the file [http://homepage.ntlworld.com/itimpi/download/tera_newfiles.tgz tera_newfiles.tgz].
	* Unpack this archive into the same location as the files holding the firmware release for which you want the files that belong on the system partition.		* Unpack this archive into the same location as the files holding the firmware release for which you want the files that belong on the system partition.
	* Change to the ''newfiles'' folder		* Change to the ''newfiles'' folder
-	* This file contains all that is used by ''itimpi'' to generate his telnet enabled variants of the Buffalo firmware releases. Of particular ~~interst~~ if you want a copy of the files that belong on partition 1 is the script ''unpackfw.sh''. Running this will extract all the files that belong on the root partition to a folder ''fw''. The passwords for each firmware release are in the file ''Password.txt''.	+	* This file contains all that is used by ''itimpi'' to generate his telnet enabled variants of the Buffalo firmware releases. Of particular interest if you want a copy of the files that belong on partition 1 is the script ''unpackfw.sh''. Running this will extract all the files that belong on the root partition to a folder ''fw''. The passwords for each firmware release are in the file ''Password.txt''.

-	This script should also work on ~~linux~~ systems that are not PPC based, but then you would have to make sure you have zip/unzip binaries that are compatible with the variant of ~~linux~~ you are using as the ones included in ~~thedownload~~ mentioned above are PPC specific.	+	This script should also work on Linux systems that are not PPC based, but then you would have to make sure you have zip/unzip binaries that are compatible with the variant of Linux you are using as the ones included in the download mentioned above are PPC specific.

	<br>		<br>

Maettwurst: /* Clearing Down the System Partition */ grammar

Maettwurst — Tue, 06 Nov 2012 17:52:39 GMT

Clearing Down the System Partition: grammar

← Older revision		Revision as of 17:52, 6 November 2012
Line 323:		Line 323:
	* Connect each disk in turn to a PC running Linux		* Connect each disk in turn to a PC running Linux
	* When the disk is mounted, go to the root of the disk and issue the command:		* When the disk is mounted, go to the root of the disk and issue the command:
-	<pre>rm -fr *</pre> to remove all files from the disk. Do not try ~~and~~ repartition the disk or reformat the partition as this will almost certainly later cause a reformat of the data area to happen as well.	+	<pre>rm -fr *</pre> to remove all files from the disk. Do not try to repartition the disk or reformat the partition as this will almost certainly later cause a reformat of the data area to happen as well.
	* Unmount the disk on the Linux system to ensure changes are written out to the disk.		* Unmount the disk on the Linux system to ensure changes are written out to the disk.
	* Put the disks back into the TeraStation.		* Put the disks back into the TeraStation.

Maettwurst: /* Clearing Down the System Partition */ grammar

Maettwurst — Tue, 06 Nov 2012 17:50:44 GMT

Clearing Down the System Partition: grammar

← Older revision		Revision as of 17:50, 6 November 2012
Line 324:		Line 324:
	* When the disk is mounted, go to the root of the disk and issue the command:		* When the disk is mounted, go to the root of the disk and issue the command:
	<pre>rm -fr *</pre> to remove all files from the disk. Do not try and repartition the disk or reformat the partition as this will almost certainly later cause a reformat of the data area to happen as well.		<pre>rm -fr *</pre> to remove all files from the disk. Do not try and repartition the disk or reformat the partition as this will almost certainly later cause a reformat of the data area to happen as well.
-	* Unmount the disk on the ~~linux~~ system to ensure changes are written out to the disk.	+	* Unmount the disk on the Linux system to ensure changes are written out to the disk.
	* Put the disks back into the TeraStation.		* Put the disks back into the TeraStation.
	* Reboot the TeraStation and it should come up in EM mode ready to be reflashed using the Firmware Updater.		* Reboot the TeraStation and it should come up in EM mode ready to be reflashed using the Firmware Updater.

Maettwurst: /* Making a Backup of the Partition */ - spelling

Maettwurst — Tue, 06 Nov 2012 17:49:10 GMT

Making a Backup of the Partition: - spelling

← Older revision		Revision as of 17:49, 6 November 2012
Line 306:		Line 306:
	==Making a Backup of the Partition==		==Making a Backup of the Partition==

-	It is ~~trongly~~ recommended that if at all possible you make a backup of the system partition before clearing it. This means if that for any reason you have misdiagnosed the problem with your TeraStation and you want to restore it you can do so.	+	It is strongly recommended that if at all possible you make a backup of the system partition before clearing it. This means if that for any reason you have misdiagnosed the problem with your TeraStation and you want to restore it you can do so.

	To do this:		To do this:
-	* Remove Disk 1 from the ~~teraStation~~ and attach it to another system. This can be done either internally or via an external Disk Enclosure attached via USB or Firewire.	+	* Remove Disk 1 from the TeraStation and attach it to another system. This can be done either internally or via an external Disk Enclosure attached via USB or Firewire.
-	* Boot the system into Linux. If your system does not run Linux normally, then you can use one of the "Live" ~~distirbutions~~ that run from CD/DVD rather than the hard disk. This would avoid you ~~ahving~~ to actually install Linux onto this system.	+	* Boot the system into Linux. If your system does not run Linux normally, then you can use one of the "Live" distributions that run from CD/DVD rather than the hard disk. This would avoid you having to actually install Linux onto this system.
-	* Make sure that you know how to run commands with 'root' ~~priveleges~~. Depending on the variant of ~~linux~~ chosen this may mean either logging in as 'root' or running commands via the 'sudoer' facility.	+	* Make sure that you know how to run commands with 'root' privileges. Depending on the variant of Linux chosen this may mean either logging in as 'root' or running commands via the 'sudoer' facility.
	* The system will probably have automounted the TeraStation hard disk. If so you check what it has been mounted as using the <code>mount</code> command. <br>Now unmount it using a command of the form:		* The system will probably have automounted the TeraStation hard disk. If so you check what it has been mounted as using the <code>mount</code> command. <br>Now unmount it using a command of the form:
	<pre>umount /dev/devicename</pre> where the ''devicename'' value will be the one you noticed was used for the TeraStation disk in the output of the <code>mount</code> command.		<pre>umount /dev/devicename</pre> where the ''devicename'' value will be the one you noticed was used for the TeraStation disk in the output of the <code>mount</code> command.
	* Make a copy of the TeraStation system partition using a command of the form:		* Make a copy of the TeraStation system partition using a command of the form:
	<pre>dd if=/dev/devicename of=/filename</pre>		<pre>dd if=/dev/devicename of=/filename</pre>
-	where ''devicename'' is as described above, and ''filename'' is the output file. This file will be a little under 400Mb in size. Make sure that it is secured somewhere that will not be lost when you reboot the ~~linux~~ system (such as USB stick or ~~ectenal~~ USB drive).	+	where ''devicename'' is as described above, and ''filename'' is the output file. This file will be a little under 400Mb in size. Make sure that it is secured somewhere that will not be lost when you reboot the Linux system (such as USB stick or external USB drive).

	==Clearing Down the System Partition==		==Clearing Down the System Partition==

Maettwurst: /* Network Will not Start */ - grammar and spelling

Maettwurst — Tue, 06 Nov 2012 17:44:33 GMT

Network Will not Start: - grammar and spelling

Maettwurst: /* Flash Error */

Maettwurst — Tue, 06 Nov 2012 17:34:05 GMT

Flash Error

← Older revision		Revision as of 17:34, 6 November 2012
Line 220:		Line 220:
	Flash errors are actually very rare unless they occur just after you have done a firmware upgrade and it turns out that you have a defective flash chip so that the update failed.		Flash errors are actually very rare unless they occur just after you have done a firmware upgrade and it turns out that you have a defective flash chip so that the update failed.

-	In ~~practise~~ it has been found that a good rule-of-thumb is that if the above error occurs very rapidly (i.e. within about 5 seconds) after power on then it probably really is a Flash error. If it takes much longer (greater than 30 seconds) and the system appears to start its normal booting sequence before this error is given then it is actually much more likely that the system files on the hard disk have become corrupted.	+	In practice it has been found that a good rule-of-thumb is that if the above error occurs very rapidly (i.e. within about 5 seconds) after power on then it probably really is a Flash error. If it takes much longer (greater than 30 seconds) and the system appears to start its normal booting sequence before this error is given then it is actually much more likely that the system files on the hard disk have become corrupted.

-	To recover from a genuine flash error requires use of the JTAG method of ~~reqriting~~ the flash. This is covered in a number of wiki articles if you want to attempt to do this yourself. There are also a number of forum members who are prepared to attempt JTAG recoveries on behalf of members. If you are interested in availing yourself of such a facility you should post a forum message giving your location so that members who are geographically closest to you can be ~~identifed~~.	+	To recover from a genuine flash error requires use of the JTAG method of rewriting the flash. This is covered in a number of wiki articles if you want to attempt to do this yourself. There are also a number of forum members who are prepared to attempt JTAG recoveries on behalf of members. If you are interested in availing yourself of such a facility you should post a forum message giving your location so that members who are geographically closest to you can be identified.

	To recover from the situation where the system will not boot look at the section below.		To recover from the situation where the system will not boot look at the section below.

Maettwurst: /* Telnet Enabled Firmware */

Maettwurst — Tue, 06 Nov 2012 17:30:35 GMT

Telnet Enabled Firmware

← Older revision		Revision as of 17:30, 6 November 2012
Line 109:		Line 109:
	This allows users to do things like:		This allows users to do things like:
	* Configure the system at a more detailed level than allowed for by the Buffalo GUI.		* Configure the system at a more detailed level than allowed for by the Buffalo GUI.
-	* Upgrade components of the underlying software to newer versions with additional ~~feature~~ and/or bug fixes included.	+	* Upgrade components of the underlying software to newer versions with additional features and/or bug fixes included.
	* Install new applications to extend the functionality of the Terastation.		* Install new applications to extend the functionality of the Terastation.
-	* In the event of any problems being encountered allow for a level of access that gives more chance of recovering user data without loss.	+	* In the event of any problems being encountered, allow for a level of access that gives more chance of recovering user data without loss.

-	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 telent functionality being trivial. This means they will have exactly the same bugs (if any) as are found in the Buffalo releases.
Line 119:		Line 119:
	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.

-	To use telnet you need a telnet client. A rudimentary one is included with Windows which you can ~~invoked~~ by typing a command of the following form into the Windows Run box:	+	To use telnet you need a telnet client. A rudimentary one is included with Windows which you can invoke by typing a command of the following form into the Windows Run box:
	telnet TeraStation_address		telnet TeraStation_address
	A freeware one called [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] is recommended as a much better alternative. In addition to the standard telnet protocol PuTTY also supports the more secure SSH variant (although additional components need installing at the TeraStation end to support this).		A freeware one called [http://www.chiark.greenend.org.uk/~sgtatham/putty/ PuTTY] is recommended as a much better alternative. In addition to the standard telnet protocol PuTTY also supports the more secure SSH variant (although additional components need installing at the TeraStation end to support this).

Maettwurst: /* Telnet Enabled Firmware */

Maettwurst — Tue, 06 Nov 2012 17:25:48 GMT

Telnet Enabled Firmware

← Older revision		Revision as of 17:25, 6 November 2012
Line 105:		Line 105:

	=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 hides this from the average user by providing the system "packaged" with a browser based GUI to control and configure it. 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:

Maettwurst at 17:22, 6 November 2012

Maettwurst — Tue, 06 Nov 2012 17:22:55 GMT

← Older revision		Revision as of 17:22, 6 November 2012
Line 34:		Line 34:
	* The Linux kernel is switched to running from the System area (partition 1) of the hard disk.		* The Linux kernel is switched to running from the System area (partition 1) of the hard disk.
	* The system services such as Samba file sharing, the Buffalo Web GUI and (if relevant) File Transfer service, Printer Service, Telnet and the Media server services are started.		* The system services such as Samba file sharing, the Buffalo Web GUI and (if relevant) File Transfer service, Printer Service, Telnet and the Media server services are started.
-	Failures can occur at any of these stages and the recovery process to be followed will be ~~dependant~~ on identifying at which stage he boot process failed.	+	Failures can occur at any of these stages and the recovery process to be followed will be dependent on identifying at which stage the boot process failed.

	=Failure Symptoms=		=Failure Symptoms=

← Older revision		Revision as of 18:05, 6 November 2012
Line 343:		Line 343:

	=Recovering files from NAS with Windows PC=		=Recovering files from NAS with Windows PC=
-	Buffalo ~~Terastation~~ and Linkstation products use XFS file system for ~~its~~ data storage. This file system has support of ~~deleted files recovery with commecial~~ data recovery software.	+	Buffalo TeraStation and Linkstation products use the XFS file system for their data storage. This file system has support of commercial data recovery software for recovery of deleted files.
-	The known software that supports deleted files ~~recovery~~ from XFS are:	+	The known software that supports recovery of deleted files from XFS are:
	* [http://www.ufsexplorer.com/download_std.php UFS Explorer Standard Recovery '''version 4'''];		* [http://www.ufsexplorer.com/download_std.php UFS Explorer Standard Recovery '''version 4'''];
	* [http://www.ufsexplorer.com/rdr_xfs.php Raise Data Recovery for XFS]		* [http://www.ufsexplorer.com/rdr_xfs.php Raise Data Recovery for XFS]
Line 389:		Line 389:

	UFS Explorer:		UFS Explorer:
-	- Right-click data ~~parition~~ of each disk and choose 'HEX preview...' option.	+	- Right-click data partition of each disk and choose 'HEX preview...' option.

-	Data partition of first drive should start with file system ~~suprblock~~. The key element is "XFSB" identification string. The data looks like this:	+	Data partition of first drive should start with file system superblock. The key element is "XFSB" identification string. The data looks like this:
	0000: 58 46 53 42 00 00 10 00 │ 00 00 00 00 2B 9C CD 10 XFSB ► +Ь═►		0000: 58 46 53 42 00 00 10 00 │ 00 00 00 00 2B 9C CD 10 XFSB ► +Ь═►
	0010: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00		0010: 00 00 00 00 00 00 00 00 │ 00 00 00 00 00 00 00 00
Line 450:		Line 450:


-	* Basing on this information, write down ~~drives~~ order detected by system. E.g. #1 = "HDD1: Fixed...", #2 = "HDD2: Fixed..." etc. In case you connected drives in reverse order, this could be #1 = "HDD4: ..", #2 = "HDD3: ..." and so on.	+	* Basing on this information, write down the order of drives detected by system. E.g. #1 = "HDD1: Fixed...", #2 = "HDD2: Fixed..." etc. In case you connected drives in reverse order, this could be #1 = "HDD4: ..", #2 = "HDD3: ..." and so on.
	* <b>Test RAID configuration</b>:		* <b>Test RAID configuration</b>:
	- Click 'Build RAID' button in UFS Explorer Professional Recovery.		- Click 'Build RAID' button in UFS Explorer Professional Recovery.
	- Choose 'RAID array on disk partition...' from drop-down and press 'Next';		- Choose 'RAID array on disk partition...' from drop-down and press 'Next';
-	- For each data ~~paritions~~, choose it at left list and press 'Add >>'. The drives order must be the same as ~~indentified~~ above;	+	- For each data partitions, choose it at left list and press 'Add >>'. The drives order must be the same as identified above;
	- Press 'Build' to open 'SoftRAID' in UFS Explorer.		- Press 'Build' to open 'SoftRAID' in UFS Explorer.

Line 463:		Line 463:
	- Press 'Open...' and then 'Build RAID' in drop-down menu;		- Press 'Open...' and then 'Build RAID' in drop-down menu;
	- Build the RAID like you did with UFS Explorer Professional Recovery;		- Build the RAID like you did with UFS Explorer Professional Recovery;
-	- Confirm RAID configuration and new RAID virtual drive drive will ~~apear~~ in UFS Explorer upper list.	+	- Confirm RAID configuration and new RAID virtual drive drive will appear in UFS Explorer upper list.
	* <b>Test the RAID configuration in UFS Explorer Standard Recovery:</b>		* <b>Test the RAID configuration in UFS Explorer Standard Recovery:</b>
	- Select RAID virtual drive in upper list (opened drives). Single XFS data partition should appear at bottom list;		- Select RAID virtual drive in upper list (opened drives). Single XFS data partition should appear at bottom list;
Line 496:		Line 496:
	- Click 'Build RAID' button in UFS Explorer Professional Recovery.		- Click 'Build RAID' button in UFS Explorer Professional Recovery.
	- Choose 'RAID array on disk partition...' from drop-down and press 'Next';		- Choose 'RAID array on disk partition...' from drop-down and press 'Next';
-	- For each data ~~paritions~~, choose it at left list and press 'Add >>'. The drives order must be the same as ~~indentified~~ above;	+	- For each data partitions, choose it at left list and press 'Add >>'. The drives order must be the same as identified above;
	- Press 'Build' to open 'SoftRAID' in UFS Explorer.		- Press 'Build' to open 'SoftRAID' in UFS Explorer.

← Older revision		Revision as of 17:44, 6 November 2012
Line 258:		Line 258:
	You cannot recover from this error by flashing, as the TeraStation will not be able to communicate over the ethernet interface, and thus the flashing process cannot be performed.		You cannot recover from this error by flashing, as the TeraStation will not be able to communicate over the ethernet interface, and thus the flashing process cannot be performed.

-	The most reliable way to recover from this type of error is to ue the JTAG method of clearing down the user config ~~are~~ in the flash. However most users will not want to go the lengths of using JTAG as it requires adding a JTAG header to the TeraStation motherboard; obtaining a JTAG cable; and then running JTAG software to rewrite the flash.	+	The most reliable way to recover from this type of error is to use the JTAG method of clearing down the user config area in the flash. However most users will not want to go the lengths of using JTAG as it requires adding a JTAG header to the TeraStation motherboard, obtaining a JTAG cable, and then running JTAG software to rewrite the flash.

-	Another ~~way~~ if you root access (as provided by the telnet enabled variants of firmware) is to add a serial port to the TeraStation. You can then log in via the serial port and make alterations ~~dicussed~~ below from that session.	+	Another solution if you have root access (as provided by the telnet enabled variants of firmware) is to add a serial port to the TeraStation. You can then log in via the serial port and make alterations discussed below from that session.

-	Another way to recover your TeraStation from this error ~~you~~ relies on you ~~haveing~~ a valid system partition on at least one disk. If you had a previously working system you almost certainly already have this in place. If not you would need to obtain a disk image of a working system or the files that belong on this partition. How to get ~~the~~ files is described at the end of this article.	+	Another way to recover your TeraStation from this error relies on you having a valid system partition on at least one disk. If you had a previously working system you almost certainly already have this in place. If not you would need to obtain a disk image of a working system or the files that belong on this partition. How to get these files is described at the end of this article.

	The recovery process is as follows:		The recovery process is as follows:

-	If you have serial console access and ~~you have~~ a username/password ~~to use~~ that can ~~give you~~ root level access (this would probably mean you had ~~previosuly~~ installed a telnet enabled release) then you can fix this by doing the following:	+	If you have serial console access and a username/password that you can use for root level access (this would probably mean you had previously installed a telnet enabled firmware release) then you can fix this by doing the following:
	* Login as a user with root privileges (typically the 'myroot' user on the itimpi firmware releases).		* Login as a user with root privileges (typically the 'myroot' user on the itimpi firmware releases).
-	* Check that you are running of the hard disk by using the 'mount' command. It ~~shoudl~~ display a line that looks like:	+	* Check that you are running off the hard disk by using the 'mount' command. It should display a line that looks like:
	/dev/md0 on / type auto (rw,noatime)		/dev/md0 on / type auto (rw,noatime)
	which shows that the hard disk is mounted as the root partition.		which shows that the hard disk is mounted as the root partition.
Line 280:		Line 280:
	broadcast 192.168.1.255		broadcast 192.168.1.255
	gateway 192.168.1.1		gateway 192.168.1.1
-	This file is to use a ~~fixed~~ IP address of 192.168.1.253. You can use a different one if it is more convenient.	+	This file is set to use a static IP address of 192.168.1.253. You can use a different one if it is more convenient.
	* Create an executable file ''/etc/init.d/network_workaround'' containing the following line to copy the good file over the bad file:		* Create an executable file ''/etc/init.d/network_workaround'' containing the following line to copy the good file over the bad file:
	cp /etc/networking/interfaces2 /etc/networking/interfaces		cp /etc/networking/interfaces2 /etc/networking/interfaces
Line 297:		Line 297:
	where xxx was the device name mentioned above		where xxx was the device name mentioned above

-	The purpose of the above modifications is to copy a good version of the /etc/network/interfaces file over the one restored from the flash area at the right point in the boot process so that the ethernet interface is started correctly. After this modification your TS should be reachable again. You can then try to fix it via web interface or flash it with a modified firmware and fix it manually.	+	The purpose of the above modifications is to copy a good version of the /etc/network/interfaces file over the one restored from the flash area at the right point in the boot process so that the ethernet interface is started correctly. After this modification your TS should be reachable again. You can then try to fix it via the web interface or flash it with a modified firmware and fix it manually.

	<br><br>		<br><br>