Build your own NAS recovery - Revision history

Lsuser1985: /* Method 2: Use ACP Commander */

Lsuser1985 — Wed, 04 May 2011 09:50:25 GMT

Method 2: Use ACP Commander

← Older revision		Revision as of 09:50, 4 May 2011
Line 48:		Line 48:
	If your can still access your NAS with [[ACP Commander]], you can use (put the correct IP-address and password into the next line, of course):		If your can still access your NAS with [[ACP Commander]], you can use (put the correct IP-address and password into the next line, of course):
	java -jar acp_commander.jar -t 192.168.x.x -ip 192.168.x.x -pw password -c "cat /proc/buffalo/firmware"		java -jar acp_commander.jar -t 192.168.x.x -ip 192.168.x.x -pw password -c "cat /proc/buffalo/firmware"
		+
		+	Within the output clutter spy the section which looks like in Method 1.

	=== Method 3: Lookup in LSUpdater ===		=== Method 3: Lookup in LSUpdater ===

Lsuser1985: /* Method 1: Log into your LS */

Lsuser1985 — Wed, 04 May 2011 09:48:55 GMT

Method 1: Log into your LS

← Older revision		Revision as of 09:48, 4 May 2011
Line 32:		Line 32:
	If you opened your NAS (or another one with the same hardware) for telnet or ssh and can still log in, you may get the produc-id by executing the following command on the LS:		If you opened your NAS (or another one with the same hardware) for telnet or ssh and can still log in, you may get the produc-id by executing the following command on the LS:
	cat /proc/buffalo/firmware		cat /proc/buffalo/firmware
		+
		+	The output will be something like
		+	SERIES=LinkStation
		+	PRODUCTNAME=LS-WVL(KOUGYOKU)
		+	VERSION=0.16
		+	SUBVERSION=FLASH 0.00
		+	PRODUCTID=0x00003008
		+	BUILDDATE=2011/04/05 09:26:24
		+	BOOTVER=0.25
		+
		+	Needless to say: the line ''PRODUCTID'' holds the product-id :-)

	=== Method 2: Use ACP Commander ===		=== Method 2: Use ACP Commander ===

Lsuser1985: /* Getting th Product-ID */

Lsuser1985 — Wed, 04 May 2011 09:46:33 GMT

Getting th Product-ID

← Older revision		Revision as of 09:46, 4 May 2011
Line 24:		Line 24:


-	== Getting th Product-ID ==	+	== Getting the Product-ID ==

	To know which files to extract from ''initrd.img'' and ''uImage.img'', you'll need the product-id of your Linkstation.		To know which files to extract from ''initrd.img'' and ''uImage.img'', you'll need the product-id of your Linkstation.

-	If you opened your NAS (or another one with the same hardware) for telnet or ssh and ~~still~~ can log in, you may get it by ~~running~~ on the LS:	+	=== Method 1: Log into your LS ===
		+
		+	If you opened your NAS (or another one with the same hardware) for telnet or ssh and can still log in, you may get the produc-id by executing the following command on the LS:
	cat /proc/buffalo/firmware		cat /proc/buffalo/firmware
		+
		+	=== Method 2: Use ACP Commander ===
		+
		+	If your can still access your NAS with [[ACP Commander]], you can use (put the correct IP-address and password into the next line, of course):
		+	java -jar acp_commander.jar -t 192.168.x.x -ip 192.168.x.x -pw password -c "cat /proc/buffalo/firmware"
		+
		+	=== Method 3: Lookup in LSUpdater ===

	Otherwise: Look into the file ''linkstation_version.ini'' of the extracted firmware. There are sections like this one:		Otherwise: Look into the file ''linkstation_version.ini'' of the extracted firmware. There are sections like this one:

Lsuser1985: /* Getting th Product-ID */

Lsuser1985 — Tue, 03 May 2011 16:50:39 GMT

Getting th Product-ID

← Older revision		Revision as of 16:50, 3 May 2011
Line 26:		Line 26:
	== Getting th Product-ID ==		== Getting th Product-ID ==

-	~~First of all~~ you'll need the product id ~~or you~~ Linkstation.	+	To know which files to extract from ''initrd.img'' and ''uImage.img'', you'll need the product-id of your Linkstation.

-	~~short~~: ~~look~~ into linkstation_version.ini	+	If you opened your NAS (or another one with the same hardware) for telnet or ssh and still can log in, you may get it by running on the LS:
		+	cat /proc/buffalo/firmware
		+
		+	Otherwise: Look into the file ''linkstation_version.ini'' of the extracted firmware. There are sections like this one:
		+	[TARGET_INFO1]
		+	PID=0x00000011
		+	KERNEL=2011/04/05 09:26:24
		+	FILE_BOOT_APPLY=u-boot_lsxh.bin
		+	BOOT=0.21
		+
		+	Find the section where ''FILE_BOOT_APPLY'' contains your model name. The example above is for LS-XH.
		+
		+	The line ''PID'' of this section is the product-id of your device, ''0x00000011'' in this example.

	== Unpacking the file ==		== Unpacking the file ==

Lsuser1985 at 14:36, 2 May 2011

Lsuser1985 — Mon, 02 May 2011 14:36:53 GMT

← Older revision		Revision as of 14:36, 2 May 2011
Line 1:		Line 1:
		+	{{Articles\|Rescue-Backup}}
	= Overview =		= Overview =
	If there is no NAS-recovery package available for your Linkstation, you may build your own.		If there is no NAS-recovery package available for your Linkstation, you may build your own.

Lsuser1985: /* Overview */

Lsuser1985 — Mon, 02 May 2011 14:30:47 GMT

Overview

← Older revision		Revision as of 14:30, 2 May 2011
Line 12:		Line 12:
	# Start an TFTP-server		# Start an TFTP-server
	#:Below find some hints about where to get a TFTP server and how to start it.		#:Below find some hints about where to get a TFTP server and how to start it.
-		+	# Make the Linkstation load the files and reboot, as described elsewhere (e.g. in [[Revive your arm9 box from scratch]])

	= Unpack the kernel and initrd from the firmware package =		= Unpack the kernel and initrd from the firmware package =

Lsuser1985: /* Unpack the kernel and initrd from the firmware package */

Lsuser1985 — Mon, 02 May 2011 14:27:30 GMT

Unpack the kernel and initrd from the firmware package

← Older revision		Revision as of 14:27, 2 May 2011
Line 24:		Line 24:

	== Getting th Product-ID ==		== Getting th Product-ID ==
		+
		+	First of all you'll need the product id or you Linkstation.

	short: look into linkstation_version.ini		short: look into linkstation_version.ini
		+
		+	== Unpacking the file ==
		+
		+	For Linux/Unix simply use the script below.
		+
		+	* initrd.img and uImage.img are password protected zip file. You need to open it with an Unzip-Programm (Winzip, 7-zip, you name it). Passwords can be found on page [[Examine_ARM9_Firmware_without_Updating]].
		+	* From initrd.img extract the file initrd.buffalo
		+	* From uImage.img extract uImage.map
		+	* uImage.map contains the filenames for each product id.
		+	* From uImage.img extract the file matching your product id.
		+	* Rename this file into uImage.buffalo (or set a soft-link)

	== Helper script for Linux/Unix ==		== Helper script for Linux/Unix ==
Line 44:		Line 57:

	# unzip the required files		# unzip the required files
-	unzip -P "$passwd1" initrd.img	+	unzip -P "$passwd1" initrd.img initrd.buffalo
	unzip -P "$passwd2" uImage.img uImage.map		unzip -P "$passwd2" uImage.img uImage.map
	# which file will become uImage.buffalo		# which file will become uImage.buffalo
Line 51:		Line 64:
	ln -s "$FILE_BOOT_APPLY" uImage.buffalo		ln -s "$FILE_BOOT_APPLY" uImage.buffalo
	</code>		</code>
-
-

	= Getting a TFTP-Server =		= Getting a TFTP-Server =

Lsuser1985: Created page with "= Overview = If there is no NAS-recovery package available for your Linkstation, you may build your own. This has been tested with * LS-WVL/R1 with Firmware 1.40 and 1.41 Basic…"

Lsuser1985 — Mon, 02 May 2011 14:17:47 GMT

Created page with "= Overview = If there is no NAS-recovery package available for your Linkstation, you may build your own. This has been tested with * LS-WVL/R1 with Firmware 1.40 and 1.41 Basic…"

New page

= Overview =
If there is no NAS-recovery package available for your Linkstation, you may build your own.

This has been tested with
* LS-WVL/R1 with Firmware 1.40 and 1.41

Basic steps are:
# Download and unpack the current firmware including LSupdater.
#:This step should be easy and does not require explanation.
# Unpack the kernel and initrd from the firmware package
#:See below for how to to this.
# Start an TFTP-server
#:Below find some hints about where to get a TFTP server and how to start it.

= Unpack the kernel and initrd from the firmware package =

LSUpdater send archive to the Linkstation, but NAS-recovery requires unpacked files to be served via TFTP.

The firmware-package contains (among others):
* initrd.img - a ZIP-file containing initrds (initial ramdisks)
* uImage.img - a ZIP-file containing the kernels

== Getting th Product-ID ==

short: look into linkstation_version.ini

== Helper script for Linux/Unix ==

You may copy & paste the following lines into a shell:
<code>
PRODID=0x00003008 # see text for how to the this value

# from
# http://buffalo.nas-central.org/wiki/Examine_ARM9_Firmware_without_Updating
# for 1.40:
passwd1="aAhvlM1Yp7_2VSm6BhgkmTOrCN1JyE0C5Q6cB3oBB"
passwd2="aAhvlM1Yp7_2VSm6BhgkmTOrCN1JyE0C5Q6cB3oBB"

# for 1.41:
passwd1="IeY8omJwGlGkIbJm2FH_MV4fLsXE8ieu0gNYwE6Ty"
passwd2="YvSInIQopeipx66t_DCdfEvfP47qeVPhNhAuSYmA4"

# unzip the required files
unzip -P "$passwd1" initrd.img
unzip -P "$passwd2" uImage.img uImage.map
# which file will become uImage.buffalo
FILE_BOOT_APPLY=$(grep $PRODID uImage.map | cut -f 2)
unzip -P "$passwd2" uImage.img "$FILE_BOOT_APPLY"
ln -s "$FILE_BOOT_APPLY" uImage.buffalo
</code>

= Getting a TFTP-Server =
== Windows ==

Fetch one from you favorite software side.

== Linux ==

Several tftp servers should be available with your Linux distribution. The package names may vary. Simply choose one :-)

Please have in mind, that TFTP uses Port 69, thus the server has to be started as root.

* tftp-server
** '''is not working''', since it requires file-requests to contain absolute pathes, but the Linkstation requests without path.
** meant to be started via inetd, but can be run stand-alone
** To start in stand-alone use <code>in.tftpd --foreground --verbose /path/to/firmware</code>

* [http://pypi.python.org/pypi/tftpy python-tftpy] -- pure Python implemention
*:Can be run without installation:
wget http://pypi.python.org/packages/source/t/tftpy/tftpy-0.5.1.tar.gz
tar xzf tftpy-0.5.1.tar.gz
cd tftpy-0.5.1
export PYTHONPATH=$PWD:$PYTHONPATH
python bin/tftpy_server.py --root /path/to/firmware
::If you are an experience Python user, you may use easy_install or pip as usual.