Unraid Setup Vmware Direct Lun Assigning Drive Issue

Hello Everyone.

I am having a slight issue with a new unraid instance. I have it installed in vmware and have 3 3tb drives passed through to it using the steps here. http://www.ostricher.com/2012/09/setting-up-unraid-vm/

I am able to see the drives in unraid, both gui and cli. I try to assign the drive to parity and Disk 1 or 2, but as soon as I select any of the disk, the windows spins and then act like it refreshes. When it refreshes it does not have the disk selected any more. I have tried this many times with the same results. Different Browsers, different computers. I do not see anything in the logs. This is a brand new build, latest version of esxi, unraid. last part of the Logs are below. I am not sure what else to try. I have used this exact same set up before, but it was older version of unraid.

Dec  7 17:58:27 Tower emhttp: SanDisk_Cruzer_Glide_4C530101560724102555-0:0 (sda) 7816672

Dec  7 17:58:27 Tower emhttp: ST3000DM001-9YN1_Z1F25RCQ_35000c5004f7ff5cc (sdb) 2930266532

Dec  7 17:58:27 Tower emhttp: ST3000VX000-1CU1_Z1F3EVQ4_35000c500641e5fbb (sdc) 2930266532

Dec  7 17:58:27 Tower emhttp: ST3000DM001-1CH1_W1F51GJZ_35000c5007365a0fe (sdd) 2930266532

Dec  7 17:58:27 Tower kernel: mdcmd (1): import 0

Dec  7 17:58:27 Tower kernel: mdcmd (2): import 1

Dec  7 17:58:27 Tower kernel: mdcmd (3): import 2

Dec  7 17:58:27 Tower kernel: mdcmd (4): import 3

Dec  7 17:58:27 Tower kernel: mdcmd (5): import 4

Dec  7 17:58:27 Tower kernel: mdcmd (6): import 5

Dec  7 17:58:27 Tower kernel: mdcmd (7): import 6

Dec  7 17:58:27 Tower kernel: mdcmd (: import 7

Dec  7 17:58:27 Tower kernel: mdcmd (9): import 8

Dec  7 17:58:27 Tower kernel: mdcmd (10): import 9

Dec  7 17:58:27 Tower kernel: mdcmd (11): import 10

Dec  7 17:58:27 Tower kernel: mdcmd (12): import 11

Dec  7 17:58:27 Tower kernel: mdcmd (13): import 12

Dec  7 17:58:27 Tower kernel: mdcmd (14): import 13

Dec  7 17:58:27 Tower kernel: mdcmd (15): import 14

Dec  7 17:58:27 Tower kernel: mdcmd (16): import 15

Dec  7 17:58:27 Tower kernel: mdcmd (17): import 16

Dec  7 17:58:27 Tower kernel: mdcmd (18): import 17

Dec  7 17:58:27 Tower kernel: mdcmd (19): import 18

Dec  7 17:58:27 Tower kernel: mdcmd (20): import 19

Dec  7 17:58:27 Tower kernel: mdcmd (21): import 20

Dec  7 17:58:27 Tower kernel: mdcmd (22): import 21

Dec  7 17:58:27 Tower kernel: mdcmd (23): import 22

Dec  7 17:58:27 Tower kernel: mdcmd (24): import 23

Dec  7 17:58:27 Tower kernel: mdcmd (25): import 24

Dec  7 17:58:27 Tower kernel: mdcmd (26): import 25

Dec  7 17:58:27 Tower kernel: mdcmd (27): import 26

Dec  7 17:58:27 Tower kernel: mdcmd (28): import 27

Dec  7 17:58:27 Tower kernel: mdcmd (29): import 28

Dec  7 17:58:27 Tower emhttp: import 30 cache device: no device

Dec  7 17:58:27 Tower kernel: mdcmd (30): import 29

Dec  7 17:58:27 Tower emhttp: import flash device: sda

After doing more checking I found the Issue. They where SAS drive.

Assuming you are running unRAID 6.2, go to Settings -> Display Settings and change Display world-wide-name in device ID from Disabled to Automatic.  Click Apply then Done, and then go see if unRAID will let it be assigned!