Enabling Rsync on a Linkstation Mini - Revision history

Walton: /* ACP */

Walton — Tue, 17 Feb 2009 14:22:35 GMT

ACP

← Older revision		Revision as of 14:22, 17 February 2009
Line 74:		Line 74:
	and try it out.		and try it out.

-	First, you need to set up your Mini ~~and connected~~ to the ethernet and ~~establish~~ a fixed IP address for it (using your router). Then you open the Mini's web page using the IP address, set the Mini hostname using the Basic subpage, and if you like, tell your own computer about the hostname you have choosen, say by editing your /etc/hosts file or equivalent. I gave my Mini the name linkstation1.walton (walton is my router's domain name) and will use this name hereafter in place of the Mini's IP address.	+	First, you need to set up your Mini by connecting it to the ethernet and establishing a fixed IP address for it (using your router). Then you open the Mini's web page using the IP address, set the Mini hostname using the Basic subpage, and if you like, tell your own computer about the hostname you have choosen, say by editing your /etc/hosts file or equivalent. I gave my Mini the name linkstation1.walton (walton is my router's domain name) and will use this name hereafter in place of the Mini's IP address.

	IMPORTANT: The Mini comes without RAID turned on, so the full 500GB or 1TB is available. If you want to use RAID1 so the two disks back up each other, you should change to RAID1 NOW, before you start changing other Mini configuration. See the Mini Disk Management/RAID Setup subpage and click on the tool icon.		IMPORTANT: The Mini comes without RAID turned on, so the full 500GB or 1TB is available. If you want to use RAID1 so the two disks back up each other, you should change to RAID1 NOW, before you start changing other Mini configuration. See the Mini Disk Management/RAID Setup subpage and click on the tool icon.

Walton: User talk:Walton moved to Enabling Rsync on a Linkstation Mini: Of general interest to Linux users buying a Linkstation Mini

Walton — Tue, 17 Feb 2009 13:34:45 GMT

User talk:Walton moved to Enabling Rsync on a Linkstation Mini: Of general interest to Linux users buying a Linkstation Mini

← Older revision

Revision as of 13:34, 17 February 2009

Walton: /* How Boot Works */

Walton — Tue, 17 Feb 2009 10:44:52 GMT

How Boot Works

← Older revision		Revision as of 10:44, 17 February 2009
Line 315:		Line 315:

	I connected up a USB to serial cable and during all the boot phases its lights stayed off, suggesting that the flash boot ignores the USB. At the end of boot one of the lights comes on, and looking in /proc/bus/usb/devices I find the serial cable is listed and has been recognized by Linux.		I connected up a USB to serial cable and during all the boot phases its lights stayed off, suggesting that the flash boot ignores the USB. At the end of boot one of the lights comes on, and looking in /proc/bus/usb/devices I find the serial cable is listed and has been recognized by Linux.
		+
		+	Its clear from [[Add a Serial port to the LS MINI]] that the Mini is not designed to use the serial port, as there is no easy way to connect to it even after opening the box up, although the flash boot loader does communicate with the serial port.

	Disappointment so far. Some other method of figuring out if and when TFTP mode is triggered is needed.		Disappointment so far. Some other method of figuring out if and when TFTP mode is triggered is needed.
Line 323:		Line 325:
	[[LS Mini: Serial Port Output - Boot-Log]]		[[LS Mini: Serial Port Output - Boot-Log]]
	[[LS Mini: Serial Port Output - U-Boot]]		[[LS Mini: Serial Port Output - U-Boot]]
-		+	[[Add a Serial port to the LS MINI]]

	Result of fdisk -l /dev/sda:		Result of fdisk -l /dev/sda:

Walton: /* How Boot Works */

Walton — Tue, 17 Feb 2009 10:41:40 GMT

How Boot Works

← Older revision		Revision as of 10:41, 17 February 2009
Line 309:		Line 309:
	Hitting the top button during boot does nothing. However, holding it down when turning power on causes the Mini to go into a special state where it is rapidly blinking just its topmost blue LED. If you release and repress the top button, it goes into a different state in which the topmost blue LED and the LinkStation Logo blue LED blink rapidly, and then after a while it goes into its normal boot state where		Hitting the top button during boot does nothing. However, holding it down when turning power on causes the Mini to go into a special state where it is rapidly blinking just its topmost blue LED. If you release and repress the top button, it goes into a different state in which the topmost blue LED and the LinkStation Logo blue LED blink rapidly, and then after a while it goes into its normal boot state where
	just the Logo LED blinks rapidly.		just the Logo LED blinks rapidly.
		+
		+	The only thing the above sequence seems to do differently from the standard boot sequence is that it resets the `admin' user password to `password'.
		+
		+	Below the contents of the proported flash boot contain lines suggesting that if the Mini has ip address 192.168.11.150 and your computer has ip address 192.168.11.1 then the flash boot has a TFTP mode for booting over the internet. My computer did not come with a TFTP server, but I was able to obtain one named `tftpd' via `yum install tftp-server'. I set the ip addresses as indicated, turned my firewall off, and used tcpdump to monitor packets to my computer. I did not see any coming from the Mini during the above non-normal boot sequence.

	I connected up a USB to serial cable and during all the boot phases its lights stayed off, suggesting that the flash boot ignores the USB. At the end of boot one of the lights comes on, and looking in /proc/bus/usb/devices I find the serial cable is listed and has been recognized by Linux.		I connected up a USB to serial cable and during all the boot phases its lights stayed off, suggesting that the flash boot ignores the USB. At the end of boot one of the lights comes on, and looking in /proc/bus/usb/devices I find the serial cable is listed and has been recognized by Linux.

-	So far ~~I have not seen any packets on the ether from the flash boot program, BUT, it looks like my router is suppressing packets with IPs 192~~.~~168.11.XX (my D-link~~ is ~~set for 192.168.0.XX), so nothing definitive yet~~.	+	Disappointment so far. Some other method of figuring out if and when TFTP mode is triggered is needed.

	References:		References:

Walton: /* How Boot Works */

Walton — Tue, 17 Feb 2009 10:27:24 GMT

How Boot Works

← Older revision		Revision as of 10:27, 17 February 2009
Line 349:		Line 349:
	-rw-r--r-- 1 walton 1757604 Jun 30 2008 boot/uImage.buffalo		-rw-r--r-- 1 walton 1757604 Jun 30 2008 boot/uImage.buffalo

-	Note the u-boot just fits in 256KB.	+	Note the u-boot just fits in 256KB, and is the only likely candidate for the contents of FLASH.
		+
		+	Result with deletings (indicated by . . . . .) of `strings u-boot.buffalo':
		+
		+	buffalo_change_power_status
		+	buffalo_IsStopAtUbootStatus
		+	. . . . .
		+	power sw is pushed
		+	power sw is released
		+	init
		+	init sw is pushed
		+	init sw is released
		+	auto
		+	auto sw is pushed
		+	auto sw is released
		+	func
		+	func sw is pushed
		+	func sw is released
		+	. . . . .
		+	func switch pushed, and exited loop
		+	wait until func switch released.
		+	. . . . .
		+	Present led on off status=0x%04x
		+	Present led blink status=0x%04x
		+	Present led control status=0x%04x
		+	. . . . .
		+	missing or unknown FLASH type
		+	. . . . .
		+	=== BUFFALO LS-GL U-Boot. ===
		+	=== BUFFALO LS-GL High Speed U-Boot. ===
		+	=== BUFFALO TS-HTGL R5 U-Boot. ===
		+	=== BUFFALO TS-HTGL R1 U-Boot. ===
		+	=== BUFFALO LS-GL R1 U-Boot. ===
		+	=== BUFFALO HS-WDHTGL/R1 U-Boot. ===
		+	=== BUFFALO LS-WTGL/R1 U-Boot. ===
		+	=== BUFFALO LS-WGL U-Boot. ===
		+	=== BUFFALO LS-WSGL/R1 U-Boot. ===
		+	=== BUFFALO LS-HGL U-Boot. ===
		+	=== BUFFALO Unknown U-Boot. ===
		+	. . . . .
		+	USB 0: host mode
		+	USB 1: host mode
		+	. . . . .
		+	BOOTVER=1.13
		+	build_time
		+	18:48:49
		+	. . . . .
		+	disaMvPnp
		+	overEthAddr
		+	usb0Mode
		+	host
		+	usb1Mode
		+	force_tftp
		+	Switched to func-boot mode.
		+	Now waiting for func switch release.
		+	Funcka switch is release.
		+	Now waiting for func switch pushed or timeout.
		+	The power switch was moved to "off" position.
		+	Func switch pushed.
		+	Go on func-boot mode.
		+	func-boot mode, timed out.
		+	Switch to normal boot mode.
		+	func=1
		+	bootargs_func
		+	func=0
		+	both power and init switch pushed. change to force tftp mode
		+	Eht phy is not found
		+	. . . . .
		+	Please Press HDD power button to continue ...
		+	Magic key condition is ups shutdown.
		+	Indicate ups error and wait re power active.
		+	HDD is not found
		+	. . . . .
		+	BOOTP broadcast %d
		+	RARP broadcast %d
		+	. . . . .
		+	hit any key to switch tftp boot.
		+	Hit any key to stop autoboot: %2d
		+	. . . . .
		+	switched to TFTP boot.
		+	. . . . .
		+	rarpboot- boot image via network using RARP/TFTP protocol
		+	. . . . .
		+	tftpboot- boot image via network using TFTP protocol
		+	. . . . .
		+	bootp - boot image via network using BootP/TFTP protocol
		+	. . . . .
		+	ethaddr=00:00:00:00:51:81
		+	bootargs=$(bootargs_base) $(bootargs_root)
		+	bootcmd=ide reset; ext2load ide 1:1 0x00100000 /$(kernel);ext2load ide 1:1 0x00800000 /$(initrd);setenv bootargs $(bootargs_base)
		+	$(bootargs_root) $(buffalo_ver);bootm 0x00100000 0x00800000
		+	bootdelay=3
		+	baudrate=115200
		+	loads_echo=0
		+	ipaddr=192.168.11.150
		+	serverip=192.168.11.1
		+	. . . . .

Walton: /* Adding Users */

Walton — Tue, 17 Feb 2009 06:05:09 GMT

Adding Users

← Older revision		Revision as of 06:05, 17 February 2009
Line 261:		Line 261:
	# Using the `User Management' page add `ruser' as a user.		# Using the `User Management' page add `ruser' as a user.
	# Using the `Group Management' page add `ruser' as a group and put the user `ruser' in this group (normally as its only member).		# Using the `Group Management' page add `ruser' as a group and put the user `ruser' in this group (normally as its only member).
-	# Using the `Shared Folders/Shared Folders Setup' page add `ruser' as a shared folder, enable it for FTP and read/write, enable access restrictions, and give the user `ruser' read/write access. WARNING: do NOT give any group `read only' access if the user `ruser' is in that group (see below).	+	# Using the `Shared Folders/Shared Folders Setup' page add `ruser' as a shared folder, enable it for FTP and read/write, enable access restrictions, and give the user `ruser' read/write access. WARNING: do NOT give any group `read only' access if the user `ruser' is in that group (see below). I also disable `Recycle Bin', which if enabled causes files that are deleted by FTP to be moved to the trashbox directory inside the `ruser' shared folder, instead of really being deleted.
	# Edit the `ruser' line in /etc/passwds to replace `/home' by `/mnt/array1/ruser' and to replace the hdusers group number (which is 100 on my Mini) by the `ruser' group's group number (the group number is the second of the two numbers in the line, and the `rusers' group number is in the /etc/group file).		# Edit the `ruser' line in /etc/passwds to replace `/home' by `/mnt/array1/ruser' and to replace the hdusers group number (which is 100 on my Mini) by the `ruser' group's group number (the group number is the second of the two numbers in the line, and the `rusers' group number is in the /etc/group file).
	# Execute		# Execute

Walton: /* Configuring the Mini for SSH and RSYNC */

Walton — Tue, 17 Feb 2009 05:57:13 GMT

Configuring the Mini for SSH and RSYNC

← Older revision		Revision as of 05:57, 17 February 2009
Line 131:		Line 131:
	(8) create the /var/log/lastlog file		(8) create the /var/log/lastlog file

-	(Note: all this comes from [[Open Stock Firmware]]: many thanks to the authors of this page. Also: my Mini firmware is 1.04 which appears to be a later version than the 1.11a firmware mentioned in this reference, which is for an older LinkStation model.)	+	(Note: all this comes from [[Open Stock Firmware]]: many thanks to the authors of this page. Also: my Mini firmware version is 1.04 which appears to be a later version than the 1.11a firmware mentioned in this reference, which is for an older LinkStation model.)

	The sshd.sh file contents are		The sshd.sh file contents are

Walton: /* ACP */

Walton — Tue, 17 Feb 2009 05:55:26 GMT

ACP

← Older revision		Revision as of 05:55, 17 February 2009
Line 92:		Line 92:
	java -jar acp_commander.jar -t linkstation1.walton -o		java -jar acp_commander.jar -t linkstation1.walton -o

-	at which point your manufacturer's warranty is gonzo, at least a little bit. This zeros the root password so you can log in as root, and also executes `telnetd' which starts the telnet daemon, so you can now telnet into the Mini.	+	at which point your manufacturer's warranty is gonzo, at least a little bit. This zeros the root password so you can log in as root without giving a password, and also executes `telnetd' which starts the telnet daemon, so you can now telnet into the Mini.

	You can now turn your firewall back on. You are done with ACP.		You can now turn your firewall back on. You are done with ACP.

-	However, if you want to play before you change anything, you can do	+	However, if you want to play before you change anything more, you can do

	java -jar acp_commander.jar -t linkstation1.walton -s		java -jar acp_commander.jar -t linkstation1.walton -s

-	which allows you to type shell commands at the Mini. However, each command is executed in a separate instance of the shell, and interactive commands will hang the Mini ACP interface (you can recover by using the Mini web page to reboot).	+	which allows you to type shell commands at the Mini. However, each command is executed in a separate instance of the shell, and interactive commands will hang the Mini ACP interface (you can recover by using the Mini web page or the power switch to reboot).

	Some more info is in the ACP Commander README;		Some more info is in the ACP Commander README;

Walton: /* LinkStation Mini Description */

Walton — Tue, 17 Feb 2009 05:53:42 GMT

LinkStation Mini Description

← Older revision		Revision as of 05:53, 17 February 2009
Line 55:		Line 55:
	/mnt/array1 xfs /dev/md2 /dev/sd{a,b}6 236GB		/mnt/array1 xfs /dev/md2 /dev/sd{a,b}6 236GB

-	In addition, 15MB of RAM is used as a RAM disk for /tmp. The flash memory ~~which~~ is only 256KB and is not used by Linux (it contains a bootstrap program). The /boot partition has all the firmware and possibly can be used to restore the machine to its delivered state, possibly by using the web Maintainance/Initialization page `Reset LinkStation Configuration to Factory Defaults'.	+	In addition, 15MB of RAM is used as a RAM disk for /tmp. The flash memory is only 256KB and is not used by Linux (it contains a bootstrap program). The /boot partition has all the firmware and possibly can be used to restore the machine to its delivered state, possibly by using the web Maintainance/Initialization page `Reset LinkStation Configuration to Factory Defaults'.

	/boot also contains a save of the `current configuration', which includes files such as /etc/passwd, /etc/shadow, etc in		/boot also contains a save of the `current configuration', which includes files such as /etc/passwd, /etc/shadow, etc in

Walton: /* LinkStation Mini Description */

Walton — Tue, 17 Feb 2009 05:52:59 GMT

LinkStation Mini Description

← Older revision		Revision as of 05:52, 17 February 2009
Line 35:		Line 35:
	The LinkStation Mini hardware is:		The LinkStation Mini hardware is:

-	ARM9 CPU (266 BogoMIPS: 15 times slower than a 2Gz Intel)[http://www.marvell.com/files/products/media/88F5182_Data_Sheet.pdf Datasheet]	+	ARM9 CPU (266 BogoMIPS: 15 times slower than a 2Gz Intel) [http://www.marvell.com/files/products/media/88F5182_Data_Sheet.pdf Datasheet]
	2 hard drives, either 250GB or 500GB each (30 Mbyte/sec transfer to /dev/null)		2 hard drives, either 250GB or 500GB each (30 Mbyte/sec transfer to /dev/null)
	128 MB RAM		128 MB RAM
Line 55:		Line 55:
	/mnt/array1 xfs /dev/md2 /dev/sd{a,b}6 236GB		/mnt/array1 xfs /dev/md2 /dev/sd{a,b}6 236GB

-	In addition, 15MB of RAM is used as a RAM disk for /tmp. The flash memory which is ~~reported to be~~ only 256KB is not used by Linux. The /boot partition has all the firmware and possibly can be used to restore the machine to its delivered state, possibly by using the web Maintainance/Initialization page `Reset LinkStation Configuration to Factory Defaults'.	+	In addition, 15MB of RAM is used as a RAM disk for /tmp. The flash memory which is only 256KB and is not used by Linux (it contains a bootstrap program). The /boot partition has all the firmware and possibly can be used to restore the machine to its delivered state, possibly by using the web Maintainance/Initialization page `Reset LinkStation Configuration to Factory Defaults'.

	/boot also contains a save of the `current configuration', which includes files such as /etc/passwd, /etc/shadow, etc in		/boot also contains a save of the `current configuration', which includes files such as /etc/passwd, /etc/shadow, etc in