1 Rookie

 • 

11 Posts

July 4th, 2018 01:00

OK, managed to do using t10.ATA_____DELLBOSS_VD_____________________________5eef6c0ee6e3001000000000

name.

Now another question. Is this name will be different on another server? Is that 5eef6c0ee6e3001000000000 numbers is like UID?

Cheers,

1 Rookie

 • 

11 Posts

July 8th, 2018 16:00

Anyone? Dell?

1 Rookie

 • 

11 Posts

July 25th, 2018 18:00

If here is no Dell representative on the forum maybe someone can recommend a proper way to raise such kind of cases with Dell?

Cheers

1 Rookie

 • 

11 Posts

July 25th, 2018 22:00

I solved it. Use disk model.

1 Message

August 29th, 2018 23:00

Can you please share the exact parameter passed in the kickstart file.

1 Rookie

 • 

3 Posts

December 10th, 2018 08:00

I am having trouble selecting the BOSS as the target for installing, tried many options but haven't found the right syntax. Does anyone have a solution ?

2 Posts

December 27th, 2018 05:00

Disk model that is claimed by ESXi is "DELLBOSS VD" with space name between. Unfortunately pointing this in ks.cfg under "install --firstdisk=DELLBOSS VD --overwritevmfs" brings the error message during installation. I have tried pointing different names like "DELLBOSS", "DELLBOSS_VD" but none of them does seems to work. Alexey, can you please share your solution?

2 Posts

December 28th, 2018 02:00

Ok, I have found workaround. For those who use Dell BOSS together with local SSDs (not spindle disks). As Dell BOSS is not claimed as SSD and other local disks are (you can always check that using esxcli storage core device list | less), you can specify --ignoressd in your ks.cfg file so SSDs will be skipped during instalation process.

install --ignoressd --firstdisk=local --overwritevmfs

As only one non-SSD is Dell BOSS, ESXi will be installed there.

1 Rookie

 • 

1 Message

August 21st, 2019 09:00

You just need to escape the space FYI "firstdisk=DELLBOSS\ VD" no quotes.

No Events found!

Top