Hello all
when i Deploy Compute Node Images

i see progress installation ESXI

but all time see this error.....

Hello,

Thank you for your question!

Can you explain your setup? Ie. Local disk install, San boot, or USB hypervisor. Also, if installing to local hard drives can you give is your deploy method and if using a raid controller that a raid array is created and online.

Thanks!

Thx 4 u reply

FullWide Node
Non local disk installed
Installed ONLY "USB 0 Storage Hypervisor" ( 1 USB Flash card inside node )

i remove old image 5.1 from NODE ( CLI )
i copy to /home/USERID new .ISO ( ESXi-5.5u1-1746018-IBM_20140522.iso )
and them installed to FSM

next step go Web FSM
-> Deploy Compute Node Images
-> mark node
-> Change username and password inside Global Settings
-> Click Deploy Images
-> and them i see progress bar installing ESXI
-> and stack on this error

i think ( really i dont know )

problem in ks.cfg

# Install on the first local disk available on machine
install --firstdisk --overwritevmfs

but I dont have local disk.....

Global Settings Username and Password in WEB FSM before deploy i think rewriten ks.cfg file in this line ->

# Set the root password for the DCUI and Tech Support Mode
rootpw mypassword

mb FSM change any other line too

And WHY! ESXI dont get me choice ( Grey Menu ) USB Storage or another Storage

in BIOS i see this USB

Sorry for the BAD BAD Eng

caught error ( very quick hiding )

Liks,

What version of FSM are you running? Have you updated to 1.3.2? Also, we recommend opening a ticket with IBM support in conjunction with MyPureSupport. This way we can chat about what IBM says and what our experience has shown.

I am going to test this feature in our lab now using FSM version 1.3.2 and installing ESXi 5.5 to our x440.

Could you also copy the FSM job logs for the deploy?

Liks,

I may have some bad news to report. See link below and excerpt.

"Target installation device
You must use a local hard disk drive as the target storage device for operating-system deployment to a compute node. Storage devices that are connected to the compute node and that are not a local hard disk drive (for example, USB and SAN devices) are not supported for use with deployment.
Important: Legacy boot mode (non-UEFI) is not supported. Make sure that the target compute node has at least one local hard disk drive and that the hard disk drive is recognized by the compute node firmware in the UEFI boot device list.
Both RAID and non-RAID configurations are supported."

Go to Operating-system Settings during and after deployement
http://pic.dhe.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fcom.ibm.acc.8731.doc%2Fcom.ibm.director.osdeployment_ngui.helps.doc%2Ffsm_deploying_compute_node_images.html

So it looks like for the install you are attempting it is going to fail because you are trying to install to the embedded hypervisor instead of a "local disk".

I would still open a ticket with IBM and press them for answers as to why they have it configured this way but my guess is that if you are choosing to run the hypervisor off of the USB key (like most are doing these days) then they would want you to purchase the key with 5.5 already installed to avoid needing to do any upgrades.

For now, it sounds like you may need to do it the old fashioned way. 

Liks,

Also as an FYI. During my testing the OS deployment installed to my local hard drives with no issues. So it appears the limitation is being able to install to the USB key.

If you decide to open a ticket, again please let us know the status and IBMs response.

Thanks!!

man, you great!

never seen "pro" help on the forum

thx u

when i do installing  ESXI againg, press ALT+F1 and i looked in the ks.cfg FILE and i understood "FSM deploy ESXI(OS)"  makes many costumization settings in this file and all installation ESXI at all
No make sense loaded ks.cfg from usb or http how I previously thoughted or makes any change during installation ESXI

now i order HDD in this node 90Y8877

thx u again and again
 
open ticket anyway and post offical answer from IBM later