Did you try connecting an USB disk to your HOST and mounting it as an ext3 partition?
If its already installed, then from the console type: fdisk -l
This will list all your dirves/arrays as the system sees them. Find the device that is the drive you want to format/mount. It will be in the format /dev/sdb or similar.
Next you'll need to partition that drive. So now type fdisk /dev/sdb (or whatever your device name is). N for new partition. Make it the size you want or tab neter to accept defaults. Next change the type to Linux with the T command. Make type 83. Now W to write the changes.
Now format the partiton: mke2fs -j -L /iso/junk. Then: ls -al /iso, you should see a file called junk in this directory. If so, all is good.
I know there are folks that have gotten SATA configs to work, but it might be less of a hassle mounting those drives in a separate Linux/Windows box and exporting it as an NFS volume.
You can then mount this NFS volume from within the VI client under Configuration -> Storage.
SATA works fine for ext3 partitions. As for creating and formatting partitions under ESX, yes it is cumbersome. But creating and formatting partitons is a necessary skill of a VMware admin. Also, NFS is not the most stable, funny things can happen when the NFS mount goes away.
True on all counts, though I've not seen many who create and format partitions from the command prompt as a matter of routine!
The reason I'm hesitant to recommend it even for ext3 is that I have seen (unsubstantiated) accounts on ESX of issues with Linux and ATA drives larger than 137GB (128GB, really). With modern drive sizes, reaching that limit is almost inevitable.
The limit is apparently due to a limitation in the ATA driver included with the service console. Searching Google for "137gb limit" yields plenty of results.
Let me add some clarification to this, When I installed ESX the ide drive was installed, formated and given a mount point "/images" Now through the VI client I want to be able to save to and read from.
Also the SATA drives are seen as a SCSI device through the Dell CERC card and the IDE drive is well an IDE drive.
When ssh'd to my ESX server and under / i see /images now I need to know how to mount it so it's visable in ESX. I looked at the fstab and it did not seem this is where I would want to add /images to /vmimages (i'm probably wrong here)
Here is my fstab
UUID=9e17b70d-f4f3-4131-8fef-a87450c6b1bc / ext3 defaults 1 1
UUID=3bb84cb3-51be-4aa2-8802-7e36470ab900 /backup ext3 defaults 1 2
UUID=6bcd3673-84ec-4102-9965-c8c57b6da5fe /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
UUID=a9545a01-78fe-4e32-bd44-874672077d68 /images ext3 defaults 1 2
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
UUID=a9ec237d-29ce-4f7b-8097-bb0ff66d9dd1 /var/log ext3 defaults 1 2
UUID=dda35c10-bf0e-4bbd-adc3-70adae0c151b swap swap defaults 0 0
/dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0
You're almost there. ESX has been modified for security to only look in the vmimages folder. So all you need to do is either rename the partition or link to it using vmimages subfolder.
ln -s /vmimages/isos /images
Now when you connect to an image when you browse you'll see the isos folder.
I use SC nfs mounts, but I'm moving to SAN luns for my images.
NOTE: If you simply name it vmimages at the outset, you're done. Otherwise if you will be renaming your images partition be careful to move the existing /vmimages files and folders into the new structure. That's where the vmware tools isos reside.
Message was edited by:
Thanks that's what I needed, however the only thing was the paths were backwards. This is how it worked
ln -s /images /vmimages
that created the needed link and now I can access the files stored there.
Right you are. I always do that wrong with ln.