 |
 |
 |
 |
|
Thursday, March 11, 2010
|
|
|
|

|
|
 |
Membership:
|
 |
Latest:
Gsimon
|
 |
Past 24 Hours:
0
|
 |
Prev. 24 Hours:
0
|
 |
Overall:
82
|
 |
People Online:
|
 |
Visitors:
4
|
 |
Members:
0
|
 |
Total:
4
|
 |
Online Now:
|
|
|
|
|
|

 |
| Booting from a Ubuntu SAN
|
|
|
 |
|
The following section is a brief overview of "How to Boot from a Ubuntu SAN" with a Microsoft Server Operating System, and is intended as a reference.
These instructions were done as a guide to setup a test environment.
The following Microsoft Server Operating systems have been tested:
- Windows 2003 SP-3
- Windows 2008 SP-2 (Core)
- Windows 2008 SP-2 (Enterprise)
- Windows 2008 SP-2 (Standard)
If you see anything that is in "error" or would like to have something added, please feel free to contact us.
- SDC
|
| |
 |
| Basic Install and Configuration Procedures
|
|
|
 |
|
Install the Windows Operating System as you normally would, with the following notes:
- Install the OS unto an External Storage Device;
- This Device will later be moved and mounted on the Ubuntu target
- Format the OS installation partition as small as possible, but keep in mind:
- Physical RAM on the Initiator/Client machine;
- Windows Patching needs;
Minimal Recommendations:
Although numerous attempts were done with a bare minimal requirements, it is STRONGLY suggested that you install the following:
- Windows Server 2003 SP2 or Greater
If you are installing a Microsoft Windows OS 2003 SP2 (or below), then you will need to do the following:
- Download the "Microsoft iSCSI Software Initiator Boot Version"
- The BOOT version is REQUIRED
- It is also recommend the you download the Check version
- Downloads can be found here:
The basic installation of the software is straight forward,
- Run the setup program;
- In the Microsoft iSCSI Initiator Installation window, be sure to select:
- Initiator Service
- Software Service
- DO NOT SELECT "Microsoft MPIO Multipathing Support for iSCSI" because it is NOT COMPATIBLE with iSCSI boot.
- In the next dialog box, you will be asked to select "Configure iSCSI Network Boot Support"
- After the installation is complete, Reboot the system to check that is boots correctly.
In these steps, you will be physically and digitally transferring the Target OS image.
- Shut down the Windows OS machine;
- Disconnect the Drive from the Windows machine;
- Reconnect the Drive to the Ubuntu Server;
- Once mounted, Open a Terminal Window;
- Type in the following command:
sudo fdisk -l
Which should return something similar to:
You will need the the following information:
- Disk path - Example: /dev/sdb
- Bytes per Cylinder - Example: 8225280
- Ending cylinder number for the partition - Example: 1026
- Using this information, type in:
dd if=/dev/sdb of=/path/to/image/file.img bs=8225280 count=1026
It is strongly recommended that the /path/to/file.img, be placed into a LARGE /var path.
Note: Using /dev/sdb copies the Master Boot Record (MBR), while /dev/sdb1 just copies the partition.
- To verify the image transfer, use the following command:
fdisk -l /path/to/image/file.img
Now the Windows OS image need to be made available:
- In the terminal window, type in:
sudo gedit /etc/ietd.conf
- Add the following to the end of the file:
Target iqn.yyyy-mm.com.mydomain:[Optional identifier]
Lun 0 Path=/path/to/image,Type=fileio,IOMode=rw
Where:
- yyyy is the year and mm is the month that the domain became valid.
- is written as 1.168.192 or com.yourdomain (this will change in your environment).
- [Optional identifier] is used to further identify the target.
- Path= is where your files are located on the local machine.
- Restart the iSCSI daemon:
sudo invoke-rc.d iscsitarget restart
Now to configure your DHCP Server:
- In the terminal window, type in:
sudo gedit /etc/dhcpd.conf
- Add the following to the end of the file:
filename "";
option root-path "iscsi:my.target.dns.name::::iqn.2007-08.name.dns.target.my:iscsiboot";
Note: The second line ("Option...") should be all on one line.
- Restart the DHCP daemon:
sudo /etc/init.d/dhcpd restart
It is now possible to boot from your Diskless client:
- Insert and Boot the Initiator/Client from the Etherboot media.
- After a short time, the Target OS should start to boot in a Normal fashion.
|
| |
|
 |
| Google AdSense Advertising
|
|
|
 |
|
|
|
|
|
 |
|
|
|
 |
 |
 |
 |