zerglings wrote: » Not sure if you're still looking at building a white box, but I just built one and maybe you're interested building a similar one as mine.AMD X6 1090T with ASUS M4A88TD-V EVO/USB3 - you need to downgrade the BIOS to 1106G.SKILL Ripjaws 8GB DDR3 1600Intel Gigabit NICCorsair AX850 PSU Perc 5i RAID Controller with SAS to SATA cables Old 4GB USB flash drive - VMware ESXi 4.1 2 x WD Caviar Black 640GB 2 x WD Caviar Black 750GB 2 x WD Caviar Black 1.5TB
zerglings wrote: » I found out that my IDE DVD/RW was not compatible with ESXi.
zerglings wrote: » I found out while I was transferring all my files to VMFS formatted drives that the maximum throughput of ESXi is not that high, hovering around ~40 MB/s and I was transferring about 1TB of data.
zerglings wrote: » I found out that since ESXi formatted my RAID 1 1.5TB drive and RAID 1 640GB to the default block size of 1MB automatically, I was limited to only 256GB of data. I was scratching my head why I was getting this I/O occurred error. After reading several forums, people were suggesting to install FastSCP or WinSCP to transfer files. Did that, but finally the I/O occurred error that I was getting was because of no space on the drive - I found out that when ESXi formatted my 1.5TB to 1MB block size, I couldn't take it out from storage section. Tried different things suggested on VMware forum and nothing worked except the guy who suggested to format it to other file system and ESXi should see it as a new drive.
MentholMoose wrote: » It's probably the PATA controller that's unsupported, not the drive itself. ESXi works fine with PATA CD/DVD drives, on supported controllers, in my experience. Intel and AMD dropped PATA support a long time ago in their chipsets, so the PATA port on most recent motherboards is handled by some add-on controller, often from JMicron or VIA (I check the specs on the M4A88TD-V EVO and it uses a VIA controller for the PATA port).
MentholMoose wrote: » I guess you are transferring it over your network. There may be some bottleneck somewhere, plus using unsupported hardware may not give the best performance.
MentholMoose wrote: » This is where those Configuration Maximums come in handy.
zerglings wrote: » - I found out that since ESXi formatted my RAID 1 1.5TB drive and RAID 1 640GB to the default block size of 1MB automatically, I was limited to only 256GB of data. I was scratching my head why I was getting this I/O occurred error. After reading several forums, people were suggesting to install FastSCP or WinSCP to transfer files. Did that, but finally the I/O occurred error that I was getting was because of no space on the drive
MSNinja wrote: » Block size does not determine how much data each vmfs LUN can hold. It only represent how large the .vmdk files (aka virtual hard drives or files) can be on the VFMS volume. So on a 640GB volume you should be able to keep almost 2.5x 250 GB virtual disks.
MSNinja wrote: » Here is a great kb from VMware VMware KB: Reformatting the local VMFS partition's block size in ESX 4.x (post-installation) regarding setting the block size during installation.