Automatic diskless boot of media directors - Revision history

Mcefan at 16:07, 19 October 2012

2012-10-19T16:07:56Z

←Older revision		Revision as of 16:07, 19 October 2012
Line 1:		Line 1:
	{{versioninfo}}		{{versioninfo}}
	~~[[Category: Tutorials]]~~
	[[Category: Networking\|Netboot, media director]]		[[Category: Networking\|Netboot, media director]]
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
Line 6:		Line 5:
	\| __TOC__		\| __TOC__
	\|}		\|}

	LinuxMCE allows [[media director]]s to be booted over the network. This means that you can boot up thin clients without hard drives, or systems with other operating systems without affecting what is already on the disk.		LinuxMCE allows [[media director]]s to be booted over the network. This means that you can boot up thin clients without hard drives, or systems with other operating systems without affecting what is already on the disk.

Mcefan at 11:05, 8 October 2012

2012-10-08T11:05:26Z

←Older revision		Revision as of 11:05, 8 October 2012
Line 1:		Line 1:
	{{versioninfo}}		{{versioninfo}}
	[[Category: Tutorials]]		[[Category: Tutorials]]
	[[Category: Networking]]		[[Category: Networking\|Netboot, media director]]
	[[Category: Programmer's Guide]]		[[Category: Programmer's Guide]]
	{\| align="right"		{\| align="right"

PlatypusPedersen: /* Troubleshooting */ MD splash freeze

2011-10-22T04:51:47Z

Troubleshooting: MD splash freeze

←Older revision		Revision as of 04:51, 22 October 2011
Line 40:		Line 40:

	==Troubleshooting==		==Troubleshooting==

			===MD freezes when the splash screen loads===

			My MD freezes when the splash screen loads, where can I find out what is causing the issue?

			====Answer====

			Remove the splashscreen from the append- in /tftpboot/pxelinux.cfg/aa-bb-cc-dd-ee-ff (mac address) to see the kernel boot messages.

	===PXE-Boot hangs up, looping......===		===PXE-Boot hangs up, looping......===

Line 56:		Line 65:

	====Answer====		====Answer====

	It is switching NICs during the PXE boot. Disable one of the on-board NICs via the BIOS.		It is switching NICs during the PXE boot. Disable one of the on-board NICs via the BIOS.

Line 74:		Line 84:

	*Note: For the core, core/hybrid install CD/DVD's, amd64 simply means 64bit- while i386 means 32bit; It does not mean amd64 is only for Amd processors and i386 is only for Intel. Amd came out with 64bit before Intel, so for a time all 64bit hardware was Amd- 64bit installs often retained the amd64 name even after Intel came out with 64bit hardware. My intel i7 core/hybrid for example is running amd64, and I've not found any issues . While researching my own (amd) net boot problem, I read a post mentioning changing the field to i386 in the panel for an Amd MD, and the machine correctly reporting Amd while net booting, I'm not 100% sure, but this seams to support the conclusion that the architecture field in the admin panel is like the install disks, and denotes the install type (32 or 64bit) rather then the actual physical architecture of the hardware (amd or intel). 32bit currently (7.10) has better hardware support 64bit, especially for NIC's- the marvel yukon for example- so a 32bit install is often recommended as a simple solution to net boot compatibility problems. Also of note, a 64bit (core) install can run 32bit MD's, but not the other way around. A 32bit core install will only configure 32bit MD's, thereby avoiding some potential problems.		*Note: For the core, core/hybrid install CD/DVD's, amd64 simply means 64bit- while i386 means 32bit; It does not mean amd64 is only for Amd processors and i386 is only for Intel. Amd came out with 64bit before Intel, so for a time all 64bit hardware was Amd- 64bit installs often retained the amd64 name even after Intel came out with 64bit hardware. My intel i7 core/hybrid for example is running amd64, and I've not found any issues . While researching my own (amd) net boot problem, I read a post mentioning changing the field to i386 in the panel for an Amd MD, and the machine correctly reporting Amd while net booting, I'm not 100% sure, but this seams to support the conclusion that the architecture field in the admin panel is like the install disks, and denotes the install type (32 or 64bit) rather then the actual physical architecture of the hardware (amd or intel). 32bit currently (7.10) has better hardware support 64bit, especially for NIC's- the marvel yukon for example- so a 32bit install is often recommended as a simple solution to net boot compatibility problems. Also of note, a 64bit (core) install can run 32bit MD's, but not the other way around. A 32bit core install will only configure 32bit MD's, thereby avoiding some potential problems.


	==GRUB PXE network boot==		==GRUB PXE network boot==

Valent: /* Answer */

2010-07-08T18:58:47Z

Answer

←Older revision		Revision as of 18:58, 8 July 2010
Line 62:		Line 62:
	[[LinuxMCE-0810 beta]]		[[LinuxMCE-0810 beta]]

	Run '/usr/pluto/bin/Diskless_CreateTBZ.sh' on the core to created the MD image.		Run 'sudo /usr/pluto/bin/Diskless_CreateTBZ.sh' on the core to created the MD image.

	===Diskless Setup Failed===		===Diskless Setup Failed===

Zaerc: restoring a non fucked-up version

2010-06-29T18:03:00Z

restoring a non fucked-up version

←Older revision		Revision as of 18:03, 29 June 2010
Line 9:		Line 9:

	==How to set it up==		==How to set it up==
	~~===PXE netboot in a nutshell===~~
	~~#[[Automatic_diskless_boot_of_media_directors#Create_PXE_Netboot_image_on_your_Core.2FHybrid\|Create PXE Netboot_image on your Core/Hybrid]]~~
	~~#Enable PXE boot on your MD~~
	~~#Connect MD to internal NIC or to same switch~~
	~~#Boot your MD via PXE Netboot~~
	~~#During first PXE boot Core/Hybrid adds new MD to list, after that you need to do a Quick Reload of Core/Hybrid~~
	~~#Boot your MD via PXE Netboot~~

	~~===Create PXE Netboot image on your Core/Hybrid===~~
	~~login to your Core/Hybrid and issue this command:~~
	~~sudo /usr/pluto/bin/Diskless_CreateTBZ.sh~~

	===Enable PXE boot===		===Enable PXE boot===
	This is also known as network boot and can be accessed in your computer's [http://en.wikipedia.org/wiki/BIOS BIOS]. The exact procedure varies depending on your PC. Normally you press F2 or DEL right after turning the PC on to enter the BIOS settings. There is then usually an advanced option to enable this.		This is also known as network boot and can be accessed in your computer's [http://en.wikipedia.org/wiki/BIOS BIOS]. The exact procedure varies depending on your PC. Normally you press F2 or DEL right after turning the PC on to enter the BIOS settings. There is then usually an advanced option to enable this.

	*Set the correct boot order===		===Set the correct boot order===
	**You are also going to want to set the boot order in the BIOS so the network boot comes first, and your hard drive second. However most BIOS's will make you first enable network boot, save your changes, restart the computer, and then enter the BIOS settings a second time to set the boot order.		You are also going to want to set the boot order in the BIOS so the network boot comes first, and your hard drive second. However most BIOS's will make you first enable network boot, save your changes, restart the computer, and then enter the BIOS settings a second time to set the boot order.


	~~<del>~~===Determine your network card's MAC address===~~</del>~~		===Determine your network card's MAC address===

	~~<del>~~'''This step is not needed since version 7.04'''~~</del>~~		'''This step is not needed since version 7.04'''

	~~<del>~~When network boot is working you should see at bootup the PC's mac address, and a messages about trying to contact a DHCP server, or trying to find a network boot image. This will be a new message you didn't see before and it means network boot is active on the PC. It will usually try for about 10 seconds to do a network boot image, and then give up and boot off the hard drive. This is what you want. When you see the message that it is trying to do the network boot, write down the mac address.~~</del>~~		When network boot is working you should see at bootup the PC's mac address, and a messages about trying to contact a DHCP server, or trying to find a network boot image. This will be a new message you didn't see before and it means network boot is active on the PC. It will usually try for about 10 seconds to do a network boot image, and then give up and boot off the hard drive. This is what you want. When you see the message that it is trying to do the network boot, write down the mac address.

	~~<del>~~You can also get the mac address in Windows by running IPCONFIG command prompt, or in Linux by typing ifconfig as root from a console or a terminal.~~</del>~~		You can also get the mac address in Windows by running IPCONFIG command prompt, or in Linux by typing ifconfig as root from a console or a terminal.

	~~<del>~~===Setup the media director in LinuxMCE===~~</del>~~		===Setup the media director in LinuxMCE===

	~~<del>~~'''This step is not needed since version 7.04 although the May 7th release of 7.10 appears to require it'''~~</del>~~		'''This step is not needed since version 7.04 although the May 7th release of 7.10 appears to require it'''

	~~<del>~~In LinuxMCE Admin go to '''Wizard > Devices > Media Directors'''. Add the media director if this is a new one, and set the mac address. The mac address should be a series of six 2 character sequences separated by colons, like this: 1A:00:F2:21:23:9F~~</del>~~		In LinuxMCE Admin go to '''Wizard > Devices > Media Directors'''. Add the media director if this is a new one, and set the mac address. The mac address should be a series of six 2 character sequences separated by colons, like this: 1A:00:F2:21:23:9F

	~~<del>~~Click 'update' to save your changes, and then click 'Setup Diskless Media Directors'. Wait for the popup window to finish. If this is a new media director you just added, go to Wizard, Restart and click 'Quick Reload Router' so the Router is aware of this new device.~~</del>~~		Click 'update' to save your changes, and then click 'Setup Diskless Media Directors'. Wait for the popup window to finish. If this is a new media director you just added, go to Wizard, Restart and click 'Quick Reload Router' so the Router is aware of this new device.

	===Boot up from the network===		===Boot up from the network===

Valent: /* PXE netboot in a nutshell */

2010-06-26T18:12:27Z

PXE netboot in a nutshell

←Older revision		Revision as of 18:12, 26 June 2010
Line 10:		Line 10:
	==How to set it up==		==How to set it up==
	===PXE netboot in a nutshell===		===PXE netboot in a nutshell===
	#Create PXE ~~boot image~~		#[[Automatic_diskless_boot_of_media_directors#Create_PXE_Netboot_image_on_your_Core.2FHybrid\|Create PXE Netboot_image on your Core/Hybrid]]
	#Enable PXE boot on your MD		#Enable PXE boot on your MD
	#Connect MD to internal NIC or to same switch		#Connect MD to internal NIC or to same switch

Valent at 18:05, 26 June 2010

2010-06-26T18:05:41Z

@@ Line 9: / Line 9: @@
 ==How to set it up==
 ===Enable PXE boot===
 This is also known as network boot and can be accessed in your computer's [http://en.wikipedia.org/wiki/BIOS BIOS]. The exact procedure varies depending on your PC.  Normally you press F2 or DEL right after turning the PC on to enter the BIOS settings.  There is then usually an advanced option to enable this.

Valent at 17:58, 26 June 2010

2010-06-26T17:58:40Z

←Older revision		Revision as of 17:58, 26 June 2010
Line 12:		Line 12:
	This is also known as network boot and can be accessed in your computer's [http://en.wikipedia.org/wiki/BIOS BIOS]. The exact procedure varies depending on your PC. Normally you press F2 or DEL right after turning the PC on to enter the BIOS settings. There is then usually an advanced option to enable this.		This is also known as network boot and can be accessed in your computer's [http://en.wikipedia.org/wiki/BIOS BIOS]. The exact procedure varies depending on your PC. Normally you press F2 or DEL right after turning the PC on to enter the BIOS settings. There is then usually an advanced option to enable this.

	~~===~~Set the correct boot order===		*Set the correct boot order===
	You are also going to want to set the boot order in the BIOS so the network boot comes first, and your hard drive second. However most BIOS's will make you first enable network boot, save your changes, restart the computer, and then enter the BIOS settings a second time to set the boot order.		**You are also going to want to set the boot order in the BIOS so the network boot comes first, and your hard drive second. However most BIOS's will make you first enable network boot, save your changes, restart the computer, and then enter the BIOS settings a second time to set the boot order.

	~~===Determine your network card's MAC address===~~

	'~~''This step is not needed since version 7.04'''~~		<del>===Determine your network card's MAC address===</del>

	~~When network boot is working you should see at bootup the PC~~'~~s mac address, and a messages about trying to contact a DHCP server, or trying to find a network boot image. This will be a new message you didn~~'~~t see before and it means network boot is active on the PC. It will usually try for about 10 seconds to do a network boot image, and then give up and boot off the hard drive.~~ This is ~~what you want. When you see the message that it is trying to do the network boot, write down the mac address~~.		<del>'''This step is not needed since version 7.04'''</del>

	~~You can also get~~ the mac address ~~in Windows by running IPCONFIG command prompt~~, or ~~in Linux by typing ifconfig as root from~~ a ~~console or~~ a ~~terminal~~.		<del>When network boot is working you should see at bootup the PC's mac address, and a messages about trying to contact a DHCP server, or trying to find a network boot image. This will be a new message you didn't see before and it means network boot is active on the PC. It will usually try for about 10 seconds to do a network boot image, and then give up and boot off the hard drive. This is what you want. When you see the message that it is trying to do the network boot, write down the mac address.</del>

	~~===Setup~~ the ~~media director~~ in ~~LinuxMCE===~~		<del>You can also get the mac address in Windows by running IPCONFIG command prompt, or in Linux by typing ifconfig as root from a console or a terminal.</del>

	~~'''This step is not needed since version 7.04 although~~ the ~~May 7th release of 7.10 appears to require it'''~~		<del>===Setup the media director in LinuxMCE===</del>

	~~In LinuxMCE Admin go to '''Wizard > Devices~~ > ~~Media Directors~~'''. ~~Add~~ the ~~media director if this is a new one, and set the mac address~~. ~~The mac address should be a series of six 2 character sequences separated by colons, like this: 1A:00:F2:21:23:9F~~		<del>'''This step is not needed since version 7.04 although the May 7th release of 7.10 appears to require it'''</del>

	Click 'update' to save your changes, and then click 'Setup Diskless Media Directors'. Wait for the popup window to finish. If this is a new media director you just added, go to Wizard, Restart and click 'Quick Reload Router' so the Router is aware of this new device.		<del>In LinuxMCE Admin go to '''Wizard > Devices > Media Directors'''. Add the media director if this is a new one, and set the mac address. The mac address should be a series of six 2 character sequences separated by colons, like this: 1A:00:F2:21:23:9F</del>

			<del>Click 'update' to save your changes, and then click 'Setup Diskless Media Directors'. Wait for the popup window to finish. If this is a new media director you just added, go to Wizard, Restart and click 'Quick Reload Router' so the Router is aware of this new device.</del>

	===Boot up from the network===		===Boot up from the network===

Ajdaniels63 at 19:29, 5 June 2010

2010-06-05T19:29:18Z

←Older revision		Revision as of 19:29, 5 June 2010
Line 51:		Line 51:

	is repeated about hours in a really fast way.....		is repeated about hours in a really fast way.....


			I have a single NIC motherboard and the exact same thing is happen. After the MD registers and reboots, it loads the Kubuntu splash screen and hangs as the filename: tftpboot/pxelinux.0 and then after a bit reboots.

	====Answer====		====Answer====

Wierdbeard65 at 08:41, 5 May 2010

2010-05-05T08:41:57Z

←Older revision		Revision as of 08:41, 5 May 2010
Line 1:		Line 1:
			{{versioninfo}}
	[[Category: Tutorials]]		[[Category: Tutorials]]
	[[Category: Networking]]		[[Category: Networking]]