Citrix XenServer 6.2: Archived Installation With a Supplemental RAID Driver
This is an archived XenServer 6.2 installation example; screenshots identify build 6.2.0-70446c and an Inspur NF5240M3 host. Match the exact platform, supported installation media and driver pack. It is not an installation procedure for current XenServer releases.
1. Prepare the system and driver media
Prepare the XenServer installation disc and the correct supplemental-driver ISO/disc for the target controller and release. The source uses separate optical media, not an arbitrary Windows driver file. Confirm the intended installation disks and protect existing data before proceeding.
In the source’s legacy BIOS workflow, open Boot → Boot Option Priorities, select the intended optical drive (a DVD device without the UEFI prefix), and use the documented save/reboot action. The example BIOS picture actually lists an ASR-5805 RAID controller first, not a selected DVD drive; do not treat it as proof that optical boot was already configured:
2. Boot and load the required driver
Boot the verified installation disc, press Enter at the XenServer boot prompt, and wait for the installer to load:
Select the correct keyboard mapping and confirm:
At Welcome to XenServer Setup, the source swaps the installation disc for the driver disc and presses F9 to load a required device driver. The screen also warns that selected installation disks will be erased:
Select Local media and confirm; select the detected AACRAID driver and choose Use. Confirm the driver-loaded message:
3. Return to system media, accept the license and verify storage
Replace the driver disc with the XenServer installation disc and continue from the welcome screen. Review and accept the EULA when authorized:
Verify the actual system disk and intended VM-storage choice. The source capture shows a selected 446GB Adaptec disk named sda with thin provisioning unchecked. That is one example, not a disk identity for another server:
Choose Local media for the installation source. The next capture selects Skip verification; that records the source’s choice, not a requirement to bypass integrity checking. Use verified media and the applicable installation procedure:
4. Configure the administrator account and management network
Set and confirm the actual root-account credential. The historical dialog mentions a six-character minimum and masks the entered value; no literal password is reproduced or recommended:
Select the management interface. The source selects eth0, while eth2/eth3 are labeled no link. Match the real MAC, cabling and management VLAN:
Configure the planned management address/mask/gateway. The shown example selects DHCP; static addressing is a separate option and must use the actual deployment plan. Set the intended hostname and DNS configuration:
5. Configure time
Select the actual region and city. The source illustrates Asia → Shanghai. Choose NTP or the supported manual-time workflow; its captures select NTP and obtaining NTP configuration from DHCP:
6. Confirm installation and complete the required supplemental pack
Review the final target carefully. The source’s confirmation explicitly says all data on sda will be destroyed. Install XenServer only after the actual disk and intended erasure have been verified:
The installer subsequently asks for the required Adaptec:aacraid 6.2.0-70446c supplemental pack. Replace the system disc with the matching driver media, confirm, select the detected driver and choose Use. Loading a driver for the installer earlier does not by itself prove that the installed host has received the required supplemental package:
If there are no further required packs, choose Skip at the next prompt and allow completion:
7. Reboot and verify the installed host
At Installation Complete, remove local media and confirm the reboot through the installer. The source then shows the boot splash and local configuration console:
The final console identifies eth0 but its pictured IP/netmask/gateway fields are blank. It does not demonstrate successful management connectivity or a complete storage/network health check. Verify the real host’s networking, controller driver, disks and management access using the matching release procedure. No installation or reboot was performed by this translation.