Openfiler安装aoe做san启动XP.doc

Openfiler安装aoe，dhcp，tftp支持xp利用gpxe从san启动。Openfiler本身不支持aoe，dhcp和tftp，这些需要安装和编译。具体过程如下：1、 安装openfiler升级组件主要是支持GCC编译，列表如下conary update gccconary update libtoolconary update glibconary update glib:develconary update glibcconary update glibc:develconary update automakeconary update autoconfconary update pkgconfig升级完毕。安装DHCP和TFTP-SERVER2、 下载安装aoeTarget端主机需下载vblade软件来编译使用 ，下载网址/projects/aoetools//sourceforge/aoetools/vblade-18.tgz下载后解压tar zxvf vblade-18.tgzmakemake install到此软件安装完成AOE，DHCP和TFTP SERVER。3、 xp的安装和配置（转自/wiki/sanboot）Windows XP boot from SANWindows XP supports booting from an AoE SAN. You cannot install directly to the SAN target; you must first install Windows XP to a physical disk. InstallationStart by installing Windows XP to a physical disk. It is best to use an external USB, FireWire, or eSATA disk; this will make later stages easier. When installing, use a small partition (around 4GB) rather than the whole disk. At the partitioning screen: press C to create a partition and enter 4096 as the size (in MB). You should then see a screen that looks like: You can now press Enter to install Windows XP to this partition. The rest of the installation will proceed as normal. Preparation for SAN bootInstalling the AoE initiatorYou need to download and install the Windows AoE initiator (WinAoE). Download the latest WinAoE package from / and extract the contents of the .zip file to a temporary directory. Start up the Add Hardware Wizard (Start Control Panel Add Hardware) and proceed to the “Is the hardware connected?” screen: Click on “Yes, I have already connected the hardware”, then click on Next. Scroll down to the bottom of the list and choose “Add a new hardware device”, then click on Next. Click on “Install the hardware that I manually select from a list (Advanced)”, then click on Next. Choose “SCSI and RAID controllers”, then click on Next. Click on “Have Disk”. Click on “Browse”. Browse to the directory containing the extracted WinAoE files, then to the bin directory within this directory. Click on “OK”. You should see “AoE Driver” show up in a list of available drivers to install: Continue clicking on Next until the installation process is complete. You will see a warning about the driver being unsigned: Ignore this warning and click on “Continue Anyway” to complete the installation of the AoE initiator. Identifying the network service nameOpen up the System Properties (Start Control Panel System) and go to the Hardware tab. Click on “Device Manager”. Locate your network card within the device list. Right-click on your network card and choose “Properties”. Go to the Details tab and choose “Service” from the drop-down menu. Make a note of the network card service name (“E1000” in the above example). Enabling network bootStart up Registry Editor (Start Run regedit) and browse to the key HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices. Click on the network card service key (“E1000” in this example), then double-click on “Start” in the right-hand panel. Change the Value data to 0 and click on OK. NOTE: If you are using a Nvidia network card, you may have to use the RIS drivers or set the “Start” to 0 for the nvnetbus service as well. NOTE: It is reported that using the Nvidia nForce drivers (service names NVENETFD and nvnetbus) does not work with WinAoE booting. See nvidia_nforceTransferring the disk image to a SAN target Shut down the operating system that you want to transfer to the SAN target. Unplug the disk containing the operating system image, and attach it to the SAN target machine. Take a look at the disks partition table; on Linux this can be achieved by running fdisk -l (lower-case L) on the SAN target machine: rootchipmunk# fdisk -l /dev/sdXwhere /dev/sdX is the disk that you just plugged in, containing the operating system image to be transferred. You should see something like: Disk /dev/sdX: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdX1 * 1 1825 14659281 7 HPFS/NTFSIn this example, the disk (/dev/sdX) contains a single partition (/dev/sdX1) which contains the operating system image that we want to extract. We need to extract enough of the disk to fully contain this partition. (We could just extract the whole disk, but this would be wasteful; the disk is 80GB but the partition we need is only 15GB). The key numbers that we need to get from the fdisk output are the number of bytes per cylinder (8225280 in the above example) and the ending cylinder number of the partition that we are interested in (1825 in the above example). Once we have identified these numbers, we can construct the command to extract the relevant portion of the disk dd if=/dev/sdX of=/path/to/image/file.img bs=8225280 count=1825where the numbers 8225280 and 1825 should be replaced with the numbers extracted from your own fdisk output. This command will extract the relevant portion of the disk to a file (/path/to/image/file.img) on your SAN target. Note that dd is reading from /dev/sdX (i.e. the raw disk device) rather than /dev/sdX1 (the partition device); we cannot extract the partition alone because we also need the Master Boot Record located at the start of the disk. Also, after creating the disk image run a ” file file.img” and make sure the image file doesnt contain part of a second partition. You should see something like (no partition 2 referenced): file.img: x86 boot sector, Microsoft Windows XP MBR, Serial 0xd056d056; partition 1: ID=0x7, active, starthead 1, startsector 63, 8385867 sectorsNow that the disk image is available on the SAN target machine, you need to make the disk image available via the appropriate SAN protocol: Make the disk image available via iSCSI Make the disk image available via AoEExporting disk images via AoEInstalling the AoE target softwareIf you do not have dedicated AoE target hardware, you will need to install the vblade package. Most distros seem to provide this package; if yours doesnt then you can download the source for the latest version from /project/showfiles.php?group_id=130453&package_id=143790. Adding an AoE target imageTo add a disk image file as an AoE target, you need to add a single line to /etc/vblade.conf: ethX N M /path/to/image/file.imgwhere ethX is the network device via which you want to serve the image, /path/to/image/file.img is the path to the disk image file, and N M is a unique AoE shelf:slot number within your network. (If this is the only AoE target disk you are setting up, just use 0 0.) The AoE target name for this disk image is eN.Mwhere N and M are the shelf and slot numbers you specified in /etc/vblade.conf. For example, if your /etc/vblade.conf line reads eth2 0 0 /var/lib/images/win2k3.imgthen the AoE target name is e0.0Make a note of this AoE target name. You are now ready to Boot from your AoE target imageBooting from an AoE targetPlace the following two lines in /etc/dhcpd.conf: filename ; option root-path aoe:eN.M;where eN.M is the AoE target name that you selected for your target. You will probably need to restart your DHCP server for the changes to take effect: rootchipmunk# /etc/init.d/dhcpd restartBoot your diskless client using gPXE. If all has gone well, you should see it boot from your AoE target image. Congratulations on a successful boot from SAN! 转载结束。4、 按教程装好的XP，需要下载/的AOE驱动。关机，卸下硬盘，挂到openfiler的机器上。VM就方便了，关掉openfiler，添加上xp的硬盘。再重新启动。启动后配置dhcpd.conf vi /etc/dhcpd.conf内容如下：ddns-update-style interim;