Install pfSense and NAS4Free in ESXi5
Hardware configuration:
Motherboard: merceat SY-APU-E35D
NIC: Intel 82546EB PCI-X dual port Nic
Memory: Kingston 2G DDR3 X2
Hard Disk: Jinsheng 16 GB SSD
Hard drive: Seagate 500 GB
Software Configuration:
Install pfSense2.0.1 and NAS4Free X64 9.0.0.1.141 in ESXi5
Installation steps:
Part 1: Install ESXi5
Note: In actual tests, enabling the AHCI mode will make the ESXi Virtual Machine extremely inefficient, but the speed will be normal after the IDE mode is enabled. It is estimated that it is an ESXi driver problem. After all, it is not a professional server hardware.
Use UltraISO to open the ESXi5 installation image, write it to the prepared USB flash drive, and use the USB flash drive to boot the installation.
Install ESXi on a 16 gb ssd, and then use the VMware vSphere Client to enter the console.
Apsaravideo player UltraISO v9.5.3.2901 Simplified Chinese version
Part 2: Install pfSense and NAS4Free
Note: according to the actual installation of the landlord, if the pfSense LAN port and ESXi share the Management port Nic, pfSense can only be called when it is specified as em0. That is, pfSense_LAN needs to act as NIC 1, and em0 must be set as LAN port when pfSense is configured.
For details about the virtual network configuration, refer to the relevant forum of this forum.
Part 3: map local SATA disks to ESXi RDM
References: http://blog.davidwarburton.net/2010/10/25/rdm-mapping-of-local-sata-storage-for-esxi/
The first two parts are installed on SSD. Seagate's GB hard disk is used separately for NAS, but generally only the hard disk can be imported into ESXi storage first, and then formatted into a proprietary format to continue to use, but in NAS needs to be formatted into UFS format, so the hard disk cannot directly read data in other systems, very inconvenient, it is not safe.
Step 1: First enable SSH login in ESXi.
You need to use the keyboard on the machine where ESXi is installed. Press F2, enter the password of the Set root account, go to the settings page, find the SSH function, and enable it.
Step 2: Use an SSH Client to connect to ESXi. the user name and password are the same as those used when logging on to VMware vSphere Client.
Enter the command
Cd/dev/disks
Enter the following prompt:
~ # Cd/dev/disks
Continue Input
Ls-l
Press enter to display the following information:
-Rw ------- 1 root 16013942784 Jun 26 t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____
-Rw ------- 1 root 4161536 Jun 26 t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 1
-Rw ------- 1 root 4293918720 Jun 26 t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 2
-Rw ------- 1 root 10776288768 Jun 26 t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 3
-Rw ------- 1 root 262127616 Jun 26 t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 5
-Rw ------- 1 root 262127616 Jun 26 t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 6
-Rw ------- 1 root 115326976 Jun 26 t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 7
-Rw ------- 1 root 299876352 Jun 26 t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 8
-Rw ------- 1 root 500107862016 Jun 26 t10.ATA _____ st500dm0022d1bc142_____________________________________ w2a1w8sx
-Rw ------- 1 root 500107804672 Jun 26 t10.ATA _____ st500dm0022d1bc142_________________________________ w2a1w8sx: 1
Lrwxrwxrwx 1 root 73 Jun 26 pm-> t10.ATA _____ st500dm0022d1bc142_________________________________________ w2a1w8sx
Lrwxrwxrwx 1 root 75 Jun 26 connections: 1-> t10.ATA _____ st500dm0022d1bc142_________________________________________w2a1w8sx: 1
Lrwxrwxrwx 1 root 74 Jun 26 middle-> t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____
Lrwxrwxrwx 1 root 76 Jun 26 links: 1-> t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 1
Lrwxrwxrwx 1 root 76 Jun 26 links: 2-> t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 2
Lrwxrwxrwx 1 root 76 Jun 26 links: 3-> t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 3
Lrwxrwxrwx 1 root 76 Jun 26 links: 5-> t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 5
Lrwxrwxrwx 1 root 76 Jun 26 links: 6-> t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 6
Lrwxrwxrwx 1 root 76 Jun 26 connections: 7-> t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 7
Lrwxrwxrwx 1 root 76 Jun 26 links: 8-> t10.ATA _____ KingSpec_KSD2DSA25.52D016MJ _______________ SA25512022200051 ____: 8
Where
73 Jun 26 vml1_1_201720202020202020202020202057324131571_35853541_3044-> t10.ATA _____ st500dm0022d1bc142_____________________________________ w2a1w8sx
This section contains the first required information [t10.ATA _____ st500dm0022d1bc142_____________________________________________w2a1w8sx] Note: Not including 【].
Step 3:
Continue to enter the command
Cd/vmfs/volumes
Press enter to continue entering
Ls-l
Press enter to display the following information:
Drwxr-xr-x 1 root 8 Jan 1 1970 1dc4ac75-ded74c4e-1475-327d3614a311
Drwxr-xr-x 1 root 8 Jan 1 1970 4fe73732-ebedb4cf-afa0-0002a54f141d
Drwxr-xr-t 1 root 1820 Jun 25 4fe7374b-4a2b7be7-4099-0002a54f141d
Drwxr-xr-x 1 root 8 Jan 1 1970 4fe7374c-7b3dbdcb-d0e0-0002a54f141d
Drwxr-xr-x 1 root 8 Jan 1 1970 9bd4be73-8f116ce4-04fd-b73cec572268
Lrwxr-xr-x 1 root 35 Jun 26 SSD-> 4fe7374b-4a2b7be7-4099-0002a54f141d
The second required information is contained in
35 Jun 26 SSD-> 4fe7374b-4a2b7be7-4099-0002a54f141d
Second information [SSD]
Then enter
Vmkfstools-z/vmfs/devices/disks/[first information] [second information]/. vmdk
It is determined by yourself. Note: not included <>
Here I name it ST500DM0022D1BC142. vmdk
Therefore, use my instance to enter
Vmkfstools-z/vmfs/devices/disks/t10.ATA _____ st500dm0022d1bc142_________________________________________________ w2a1w8sx SSD/ST500DM0022D1BC142. vmdk
Part 4: Use a mapped physical hard disk
Edit the NAS4Free Vm and add the hard disk. Note that you can only select the SCSI interface as the disk controller.
Select to use an existing Virtual Disk
Then you can view the mapped VMDK file in the SSD storage. Select this file.
Then you can manage a series of operations on attaching a disk in NAS4Free, which are operations on using a physical disk directly.
Precautions for installing MLDonkey on FreeNAS
FreeNAS is very useful recently, but the problem is that it only supports BT. If you want to support ed2k, You have to install other software. The dog knows that MLDonkey is very powerful, so it is installed.
There are many installation processes online. For details, refer. However, the first step is to modify downloads. in ini, it is under the modified mlnet user directory, for example, I am in/mnt/DATA/mlnet /. mldonkey/downloads. ini, instead of/root /. under mldonkey. Note this, otherwise it will not be useful to modify the IP address.
After the installation was completed in two or three hours, it was stuck in the previous step. Every connection to // freenas: 4080 said that the IP address was rejected. After studying for a while, the above problem was discovered.
After the IP address is fixed, open webui, add several servers, and find that it cannot be connected. Then, put the dog for one afternoon, modify the parameters, and add the port ing and DMZ are invalid. Finally, I suddenly remembered whether FreeNAS was not connected to the Internet. As a result, FreeNAS's ip address was 192.168.1.250, while the router address pool was only 192.168.1.199. Set DHCP in FreeNAS. However, ping in shell still fails. So manually specify the ip address and DNS, and then the porttest In The mld quickly passes, and several servers are successfully added.
The biggest lesson: FreeNAS must first access the internet.
PfSense 2.2.4 use an iso image for local hard disk installation
PfSense details: click here
PfSense: click here
This article permanently updates the link address: