• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

ESX 4.0 gurus - new disk issue

SolMiester

Diamond Member
hi all, hoping to find a GUI approach to creating a partition on a new logical drive to present to ESX to use for a datastore...wow that was a mouthful...would any Linux bootdisk disu do?

I have learn when building the host o/s the installer allows you to partition free space on logical drives to present to the host o/s. However on a running host with no live migration, i have had to create the array using the hpacucli commands....not quite keen enough to try destructive CLI on it while running though...

ideas?
 
If I understand your question correctly you want to create a new datastore on a newly created array. If the array is created and the controller is supported, you should be able to do it from the Configuration tab, then selecting storage. You may have to tell the host to recan itself for new storage devices.
 
If I understand your question correctly you want to create a new datastore on a newly created array. If the array is created and the controller is supported, you should be able to do it from the Configuration tab, then selecting storage. You may have to tell the host to recan itself for new storage devices.

This. Any drive manipulation (partition etc.) is doable within the client. I know I've done it with my ESXi box, and it was a breeze. Haven't had to do it with a production box unless we're talking about iSCSI, and that is a breeze also.
 
Yeah guys, I know the add storage wizard.....I am having issues with ESX creating a datastore from the newly created array....I'm getting partition update errors...
 
If I recall, you need to set the partition ID as an ESX volume. Been a while since I've done it though. Also if this is a SAN environment, make sure the SAN gives access to the hosts. Easy step to forget. And yeah you have to rescan, if you did not do that.
 
Back
Top