Talk:The LinkStation firmware flasher - Revision history

85.124.221.56: /* Analysis of /etc/scripts/melsub_flash */

85.124.221.56 — Tue, 01 Aug 2006 22:34:43 GMT

Analysis of /etc/scripts/melsub_flash

← Older revision		Revision as of 22:34, 1 August 2006
Line 175:		Line 175:
	then the file gets deleted		then the file gets deleted
	rm -f "$fileMELSETTMP".gz 1> /dev/null 2> /dev/null		rm -f "$fileMELSETTMP".gz 1> /dev/null 2> /dev/null
		+
		+	'''the counterpart to as_flash on ppc-Linkstations is ls_flash on the LS2 (mips)'''

	these are the options of as_flash		these are the options of as_flash

85.124.221.56: added idea that /etc/init.,

85.124.221.56 — Tue, 01 Aug 2006 13:27:48 GMT

added idea that /etc/init.,

← Older revision		Revision as of 13:27, 1 August 2006
Line 126:		Line 126:
	Inside these files I could find a backup of the usual config files. Don't know if this a template to fill up the usual Linux config files with restored data again, or if this is only a sort of backup.		Inside these files I could find a backup of the usual config files. Don't know if this a template to fill up the usual Linux config files with restored data again, or if this is only a sort of backup.

-	== ~~ANALYSIS~~ of /etc/scripts/melsub_flash ==	+	== Analysis of /etc/scripts/melsub_flash ==
	'''a hint:'''		'''a hint:'''
	/www/cgi-bin/mellib.pl (seems to be equal to /www.cgi-bin2/mellib2.pl)		/www/cgi-bin/mellib.pl (seems to be equal to /www.cgi-bin2/mellib2.pl)
Line 262:		Line 262:
	but when is this /etc/init.d/load_config started? there is no symlink anywhere. maybe somehow over ap_servd? maybe only if it was in EM Mode? maybe only if it was flashed in normal mode?		but when is this /etc/init.d/load_config started? there is no symlink anywhere. maybe somehow over ap_servd? maybe only if it was in EM Mode? maybe only if it was flashed in normal mode?

		+	what about the idea that /etc/init.d/load_config is triggered by ap_servd/firmware_updater in the config-restore step? maybe the reason for the update-error is because /etc/init.d/load_config isn`t there?
		+
		+	== Analysis of /www/script/melsub_init.sh ==
	i just also wanted to mention that there is file called /www/scripts/melsub_init.sh.		i just also wanted to mention that there is file called /www/scripts/melsub_init.sh.
	it takes down all services and afterwards overwrites all the config files by		it takes down all services and afterwards overwrites all the config files by

85.124.221.56: /* ANALYSIS of /etc/scripts/melsub_flash */

85.124.221.56 — Tue, 01 Aug 2006 13:22:44 GMT

ANALYSIS of /etc/scripts/melsub_flash

← Older revision		Revision as of 13:22, 1 August 2006
Line 141:		Line 141:
	* or it is used for clearing it totaly(as_flash /dev/fl0 init)		* or it is used for clearing it totaly(as_flash /dev/fl0 init)

-	before flashing, it creates an archive ~~for~~ the most important info	+	before flashing, it creates an archive of the most important info
	### Archive Make ###		### Archive Make ###
	tar cp "$fileIFCFG" > "$fileMELSETTMP" 2> /dev/null		tar cp "$fileIFCFG" > "$fileMELSETTMP" 2> /dev/null

Hanfbauer at 11:15, 1 August 2006

Hanfbauer — Tue, 01 Aug 2006 11:15:28 GMT

← Older revision		Revision as of 11:15, 1 August 2006
Line 59:		Line 59:

	If these requirements are met, I was able to use the flasher and put new images to my box. There's still much to be done, as at the moment the flashing procedure always ends up with an error message: "Attempt to renew firmware has failed". Nevertheless my box was always working.		If these requirements are met, I was able to use the flasher and put new images to my box. There's still much to be done, as at the moment the flashing procedure always ends up with an error message: "Attempt to renew firmware has failed". Nevertheless my box was always working.
-	~~--[[User:Hanfbauer\|Hanfbauer]] 15:39, 30 July 2006 (EDT)~~

	== Analysis of HD-HLAN FWUpdate.exe ==		== Analysis of HD-HLAN FWUpdate.exe ==
		+
		+	Following the flashing process on Windows, the process goes trough 5 different stages (at least when the software really does what it says):
		+	:Settings are being saved
		+	:Firmware is being transmitted
		+	:LinkStation firmware has been renewed
		+	:Settings are being restored
		+	:Attempt to renew firmware has failed
		+	If the melsub scripts are missing, the process ends up shortly after saying "Settings are being saved". If these scripts are in place, it ends up after saying "Settings are being restored".
		+	So probably there's a file or directory missing on the newcreated hda1 partition, where setting could be restored successfully.

	Leaving my ssh connection open while attempting to flash the box, i could see some errormessages during the flashing process:		Leaving my ssh connection open while attempting to flash the box, i could see some errormessages during the flashing process:
Line 74:		Line 82:
	PRODUCTID=0x00000006		PRODUCTID=0x00000006
	BUILDDATE=2005/04/01 13:35:54		BUILDDATE=2005/04/01 13:35:54
-	So i put this file inside /etc and flashed again, but ended up with "Attempt to renew firmware has failed"~~. So I have to analyse melsub_flash.sh to find out more~~.	+	So i put this file inside /etc and flashed again, but ended up with "Attempt to renew firmware has failed".

	== Wondering about settings restore ==		== Wondering about settings restore ==

Mindbender: /* ANALYSIS of /etc/scripts/melsub_flash */

Mindbender — Tue, 01 Aug 2006 10:14:53 GMT

ANALYSIS of /etc/scripts/melsub_flash

Show changes

Mindbender: added info about melsub_flash + as_flash

Mindbender — Tue, 01 Aug 2006 09:01:25 GMT

added info about melsub_flash + as_flash

← Older revision		Revision as of 09:01, 1 August 2006
Line 117:		Line 117:
	-rw-r--r-- 1 root root 0 Dec 20 2004 userinfo		-rw-r--r-- 1 root root 0 Dec 20 2004 userinfo
	Inside these files I could find a backup of the usual config files. Don't know if this a template to fill up the usual Linux config files with restored data again, or if this is only a sort of backup.		Inside these files I could find a backup of the usual config files. Don't know if this a template to fill up the usual Linux config files with restored data again, or if this is only a sort of backup.
		+
		+	== ANALYSIS of /etc/scripts/melsub_flash ==
		+	'''just a hint: /www/cgi-bin/mellib.pl is the file that includes all variables.'''
		+
		+	/etc/scripts/melsub_flash refers to a variable
		+	$fileMELSETTMP = '/tmp/conf_save.tar';
		+
		+	there are 2 different things that melsub_flash does
		+	* either it is used for flashing a conf_save.tar.gz additionally (as_flash /dev/fl0 add) to the flash
		+	* or it is used for clearing it totaly(as_flash /dev/fl0 init)
		+
		+	before flashing, it creates an archive for the most important info
		+	### Archive Make ###
		+	tar cp "$fileIFCFG" > "$fileMELSETTMP" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$dirSAMBA" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$dirATALK" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$dirMELCO" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$filePASSWD" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$fileGROUP" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$fileHOSTS" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$fileHTPASSWD" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$fileHTPASSWD1" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$fileHTPASSWD2" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$fileAPSERVD" 2> /dev/null
		+	tar rfp "$fileMELSETTMP" "$filePRINTCAP" 2> /dev/null
		+	if [ -f "$fileCRONTAB" ] ; then
		+	tar rfp "$fileMELSETTMP" "$fileCRONTAB" 2> /dev/null
		+	fi
		+	if [ -f "$filePCASTD" ] ; then
		+	tar rfp "$fileMELSETTMP" "$filePCASTD" 2> /dev/null
		+	fi
		+
		+	info about tar-options
		+	tar rfp
		+	-r, --append append files to the end of an archive
		+	-f, --file=ARCHIVE use archive file or device ARCHIVE
		+	-p, --same-permissions extract permissions information
		+
		+	afterwards it is zipped:
		+	gzip "$fileMELSETTMP" 1> /dev/null 2> /dev/null
		+	it is written to the end of the flash!
		+	### Flash Write ###
		+	as_flash /dev/fl0 add -n "$fileMELSETTMP".gz 1> /dev/null 2> /dev/null
		+	then the file gets deleted
		+	rm -f "$fileMELSETTMP".gz 1> /dev/null 2> /dev/null
		+
		+	these are the options of as_flash
		+	root@LINKSTATION:~# as_flash
		+	as_flash [device] [add\|del\|get\|init] [options]
		+	add -n <filename>
		+	add file image to end of flash
		+	del [-n <filename>\|-i <block number>]
		+	delete Entered file name or block number of block data from flash
		+	get [-n <filename>\|-i <block number>] [--output <filename>]
		+	read Entered file name or block number of block data from flash,
		+	and store output filename
		+	init
		+	clear device by zero
		+
		+	it seems that ''as_flash /dev/fl0 init'' seems to delete the whole content of the flash. but maybe this is only an area? i mean...maybe it clears only the area where the config-files are stored? i can only verify that when i finally get the JTAG-Equipment and it works.
		+
		+	we need to find all the files that use as_flash. especially all files/scripts that use ''as_flash /dev/fl0 get''. then we know where info is extracted and used from the flash. i think this will be another way to find out where the settings are restored and maybe we gain some useful information about different areas of the flash?

Hanfbauer at 01:47, 1 August 2006

Hanfbauer — Tue, 01 Aug 2006 01:47:24 GMT

← Older revision		Revision as of 01:47, 1 August 2006
Line 3:		Line 3:

	We have two ways of flashing: EM mode and normal mode.		We have two ways of flashing: EM mode and normal mode.
-	~~This is true only for '''normal''' mode on my LS2:~~

	== Flashing the image.dat to hda1 from Windows needs at least the follwing requirements: ==		== Flashing the image.dat to hda1 from Windows needs at least the follwing requirements: ==
		+
		+	This is true only for '''normal''' mode on my LS2:

	1. idtinfo loaded to create /proc/linkstation		1. idtinfo loaded to create /proc/linkstation
Line 59:		Line 60:
	If these requirements are met, I was able to use the flasher and put new images to my box. There's still much to be done, as at the moment the flashing procedure always ends up with an error message: "Attempt to renew firmware has failed". Nevertheless my box was always working.		If these requirements are met, I was able to use the flasher and put new images to my box. There's still much to be done, as at the moment the flashing procedure always ends up with an error message: "Attempt to renew firmware has failed". Nevertheless my box was always working.
	--[[User:Hanfbauer\|Hanfbauer]] 15:39, 30 July 2006 (EDT)		--[[User:Hanfbauer\|Hanfbauer]] 15:39, 30 July 2006 (EDT)
-	~~'''----'''~~	+
	== Analysis of HD-HLAN FWUpdate.exe ==		== Analysis of HD-HLAN FWUpdate.exe ==

Line 74:		Line 75:
	BUILDDATE=2005/04/01 13:35:54		BUILDDATE=2005/04/01 13:35:54
	So i put this file inside /etc and flashed again, but ended up with "Attempt to renew firmware has failed". So I have to analyse melsub_flash.sh to find out more.		So i put this file inside /etc and flashed again, but ended up with "Attempt to renew firmware has failed". So I have to analyse melsub_flash.sh to find out more.
-	~~'''----'''~~	+
-	~~This is true only for '''EM Mode ''' flashing on my LS2:~~	+
	== Wondering about settings restore ==		== Wondering about settings restore ==
		+
		+	This is true only for '''EM Mode ''' flashing on my LS2:

	By flashing a firmware after connecting an empty disk to the Linkstation I expected to loose all settings which I had before on my old disk. But this not true. I experienced that some settings must be restored from the flash. Flashing openlink 0.52b to an empty disk and opening buffalos webinterface, I could check for some settings restored from flash:		By flashing a firmware after connecting an empty disk to the Linkstation I expected to loose all settings which I had before on my old disk. But this not true. I experienced that some settings must be restored from the flash. Flashing openlink 0.52b to an empty disk and opening buffalos webinterface, I could check for some settings restored from flash:

Hanfbauer at 01:41, 1 August 2006

Hanfbauer — Tue, 01 Aug 2006 01:41:03 GMT

← Older revision		Revision as of 01:41, 1 August 2006
Line 5:		Line 5:
	This is true only for '''normal''' mode on my LS2:		This is true only for '''normal''' mode on my LS2:

-	~~'''~~Flashing the image.dat to hda1 from Windows needs at least the follwing requirements:~~'''~~	+	== Flashing the image.dat to hda1 from Windows needs at least the follwing requirements: ==

	1. idtinfo loaded to create /proc/linkstation		1. idtinfo loaded to create /proc/linkstation
Line 59:		Line 59:
	If these requirements are met, I was able to use the flasher and put new images to my box. There's still much to be done, as at the moment the flashing procedure always ends up with an error message: "Attempt to renew firmware has failed". Nevertheless my box was always working.		If these requirements are met, I was able to use the flasher and put new images to my box. There's still much to be done, as at the moment the flashing procedure always ends up with an error message: "Attempt to renew firmware has failed". Nevertheless my box was always working.
	--[[User:Hanfbauer\|Hanfbauer]] 15:39, 30 July 2006 (EDT)		--[[User:Hanfbauer\|Hanfbauer]] 15:39, 30 July 2006 (EDT)
-	----	+	'''----'''
-	'''Analysis of HD-HLAN FWUpdate.exe~~'''~~	+	== Analysis of HD-HLAN FWUpdate.exe ==

	Leaving my ssh connection open while attempting to flash the box, i could see some errormessages during the flashing process:		Leaving my ssh connection open while attempting to flash the box, i could see some errormessages during the flashing process:
Line 74:		Line 74:
	BUILDDATE=2005/04/01 13:35:54		BUILDDATE=2005/04/01 13:35:54
	So i put this file inside /etc and flashed again, but ended up with "Attempt to renew firmware has failed". So I have to analyse melsub_flash.sh to find out more.		So i put this file inside /etc and flashed again, but ended up with "Attempt to renew firmware has failed". So I have to analyse melsub_flash.sh to find out more.
		+	'''----'''
		+	This is true only for '''EM Mode ''' flashing on my LS2:
		+	== Wondering about settings restore ==
		+
		+	By flashing a firmware after connecting an empty disk to the Linkstation I expected to loose all settings which I had before on my old disk. But this not true. I experienced that some settings must be restored from the flash. Flashing openlink 0.52b to an empty disk and opening buffalos webinterface, I could check for some settings restored from flash:
		+	:Character code
		+	:Timezone
		+	:Shared folder information
		+	:LinkStation name
		+	:Linkstation description
		+	:IP adress
		+	:Default gateway settings
		+	:Workgroup setting
		+	are restored from flash, while
		+	:actual time was reset to 2002 01 01
		+	I relized that the restored settings where not those from my last openlink installation, but those which I did some weeks before, having the original 160 GB HD inside.
		+	Opening putty I could check for some files in root directory:
		+	: /etc/resolv.conf
		+	:/etc/samba/smb.conf
		+	:/etc/network/interfaces
		+	did not change. I discovered that there's a second directory with config files: /etc/melco
		+	bash-2.05a# ls -la
		+	total 44
		+	drw-rw-r-- 2 root root 4096 Jan 1 18:02 .
		+	drwxr-xr-x 23 root root 4096 Jan 1 18:02 ..
		+	-rw-r--r-- 1 root root 0 Dec 20 2004 backup_error_status
		+	-rw-r--r-- 1 root root 59 Jul 10 2006 ftpstatus
		+	-rw-r--r-- 1 root root 24 Dec 20 2004 groupinfo
		+	-rw--w---- 1 root root 105 Jul 15 2006 info
		+	-rw-r--r-- 1 root root 35 Aug 26 2005 ntp
		+	-rw-r--r-- 1 root root 0 Dec 20 2004 ntp_result
		+	-rw-r--r-- 1 root root 57 Aug 25 2005 pcast_mp2000
		+	-rw-r--r-- 1 root root 0 Dec 20 2004 pdcuserinfo
		+	-rw-r--r-- 1 root root 11 Aug 29 2005 printer
		+	-rw-r--r-- 1 root root 1544 Jan 1 18:02 shareinfo
		+	-rw-r--r-- 1 root root 135 Jul 15 2006 shareinfo.bak
		+	-rw-r--r-- 1 root root 0 Aug 26 2005 timer_backup.cron
		+	-rw-r--r-- 1 root root 0 Dec 20 2004 timer_backup_folder
		+	-rw-r--r-- 1 root root 133 Jul 10 2006 timer_status
		+	-rw-r--r-- 1 root root 0 Dec 20 2004 userinfo
		+	Inside these files I could find a backup of the usual config files. Don't know if this a template to fill up the usual Linux config files with restored data again, or if this is only a sort of backup.

Hanfbauer at 02:22, 31 July 2006

Hanfbauer — Mon, 31 Jul 2006 02:22:08 GMT

← Older revision		Revision as of 02:22, 31 July 2006
Line 63:		Line 63:

	Leaving my ssh connection open while attempting to flash the box, i could see some errormessages during the flashing process:		Leaving my ssh connection open while attempting to flash the box, i could see some errormessages during the flashing process:
-	root@FL060727:~# ~~netstat -ash~~: line 1: /www/script/melsub_flash.sh: No such file or directory	+	root@FL060727:~# sh: line 1: /www/script/melsub_flash.sh: No such file or directory
	/www/script/melsub_shutdown2.sh: /www/script/melsub_shutdown2.sh: No such file or directory		/www/script/melsub_shutdown2.sh: /www/script/melsub_shutdown2.sh: No such file or directory
	This was the reason to put the required scripts in right place.		This was the reason to put the required scripts in right place.

Hanfbauer at 23:46, 30 July 2006

Hanfbauer — Sun, 30 Jul 2006 23:46:13 GMT

← Older revision		Revision as of 23:46, 30 July 2006
Line 5:		Line 5:
	This is true only for '''normal''' mode on my LS2:		This is true only for '''normal''' mode on my LS2:

-	Flashing the image.dat to hda1 from Windows needs at least the follwing requirements:	+	'''Flashing the image.dat to hda1 from Windows needs at least the follwing requirements:'''

	1. idtinfo loaded to create /proc/linkstation		1. idtinfo loaded to create /proc/linkstation
Line 14:		Line 14:
	root@FL060727:~# insmod idtinfo		root@FL060727:~# insmod idtinfo
	Using /lib/modules/2.4.20_mipsel_linkstation/idtinfo.o		Using /lib/modules/2.4.20_mipsel_linkstation/idtinfo.o
-	Warning: loading /lib/modules/2.4.20_mipsel_linkstation/idtinfo.o will taint the kernel: no license	+	Warning: loading /lib/modules/2.4.20_mipsel_linkstation/idtinfo.o will taint the kernel: no license
	See http://www.tux.org/lkml/#export-tainted for information about tainted modules		See http://www.tux.org/lkml/#export-tainted for information about tainted modules
	Module idtinfo loaded, with warnings		Module idtinfo loaded, with warnings
Line 59:		Line 59:
	If these requirements are met, I was able to use the flasher and put new images to my box. There's still much to be done, as at the moment the flashing procedure always ends up with an error message: "Attempt to renew firmware has failed". Nevertheless my box was always working.		If these requirements are met, I was able to use the flasher and put new images to my box. There's still much to be done, as at the moment the flashing procedure always ends up with an error message: "Attempt to renew firmware has failed". Nevertheless my box was always working.
	--[[User:Hanfbauer\|Hanfbauer]] 15:39, 30 July 2006 (EDT)		--[[User:Hanfbauer\|Hanfbauer]] 15:39, 30 July 2006 (EDT)
		+	----
		+	'''Analysis of HD-HLAN FWUpdate.exe'''
		+
		+	Leaving my ssh connection open while attempting to flash the box, i could see some errormessages during the flashing process:
		+	root@FL060727:~# netstat -ash: line 1: /www/script/melsub_flash.sh: No such file or directory
		+	/www/script/melsub_shutdown2.sh: /www/script/melsub_shutdown2.sh: No such file or directory
		+	This was the reason to put the required scripts in right place.
		+	root@FL060729:/mnt# cat: /etc/linkstation_release: No such file or directory
		+	I checked the content of /etc/linkstation_release inside openlink 0.52b and found:
		+	PRODUCTNAME=HD-HLAN(IENOBU)
		+	VERSION=2.05
		+	SUBVERSION=HDD 1.2
		+	PRODUCTID=0x00000006
		+	BUILDDATE=2005/04/01 13:35:54
		+	So i put this file inside /etc and flashed again, but ended up with "Attempt to renew firmware has failed". So I have to analyse melsub_flash.sh to find out more.