Okay this is weird.
I shutdown and booted xenserver to see if it see's the hard driver natively, which it does and the I deceided to check the bios settings. I had read about C1E needing to be disabled. So I disabled that and reduced the video memory and enabled smart fan.
Rebooted back into Esxi and what do you know I can see the intel nic again. I don't know if the C1E had to do with it.
Jul 20 06:53:08 vmkernel: 0:00:00:21.262 cpu1:4593)Loading module e1000 ...
Jul 20 06:53:08 vmkernel: 0:00:00:21.263 cpu1:4593)Elf: 2187: <e1000> provides name-space <esx:nover>
Jul 20 06:53:08 vmkernel: 0:00:00:21.264 cpu1:4593)Elf: 1612: <e1000> : R_X86_64_32 relocation(s) ignored
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)module heap : Initial heap size : 102400, max heap size: 5750784
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)module heap vmklnx_e1000: creation succeeded. id = 0x4100b4400000
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)module skb heap : Initial heap size : 524288, max heap size: 23068672
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)module skb heap : creation succeeded
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)<6>Intel(R) PRO/1000 Network Driver - version 8.0.3.2-1vmw-NAPI
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)<6>Copyright (c) 1999-2008 Intel Corporation.
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: driver e1000 is looking for devices
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:03.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:03.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:04.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:08.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:08.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:09.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:09.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:0e.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:0e.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:0f.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:00:10.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:00:10.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Trying 0000:01:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)PCI: Announcing 0000:01:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.265 cpu1:4593)socket buffer cache creation succeeded for vmnic%d
Jul 20 06:53:08 vmkernel: <6>e1000: 0000:01:04.0: e1000_probe: (PCI:33MHz:32-bit) 00: 04:23:a8:e3:e8
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)<6>e1000: vmnic1: e1000_probe: Intel(R) PRO/1000 Network Connection
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)PCI: driver e1000 claimed device 0000:01:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)PCI: Registering network device 0000:01:04.0
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)VMK_PCI: 646: Device 000:001:04.0 name: vmnic3
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)Uplink: 11078: Device vmnic3 not yet opened
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)LinPCI: LinuxPCI_DeviceClaimed: Device 1:20 claimed.
Jul 20 06:53:08 vmkernel:
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)PCI: Trying 0000:01:04.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.609 cpu1:4593)PCI: Announcing 0000:01:04.1
Jul 20 06:53:08 vmkernel: <6>e1000: 0000:01:04.1: e1000_probe: (PCI:33MHz:32-bit) 00: 04:23:a8:e3:e9
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)<6>e1000: vmnic1: e1000_probe: Intel(R) PRO/1000 Network Connection
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)PCI: driver e1000 claimed device 0000:01:04.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)PCI: Registering network device 0000:01:04.1
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)VMK_PCI: 646: Device 000:001:04.1 name: vmnic4
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)Uplink: 11078: Device vmnic4 not yet opened
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)LinPCI: LinuxPCI_DeviceClaimed: Device 1:21 claimed.
Jul 20 06:53:08 vmkernel:
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)PCI: driver e1000 claimed 2 devices
Jul 20 06:53:08 vmkernel: 0:00:00:21.951 cpu0:4593)Uplink: 13003: Opening device vmnic3
Jul 20 06:53:08 vmkernel: 0:00:00:21.963 cpu1:4123)IDT: 1036: 0x88 <vmnic3> sharable (entropy source), flags 0x10
Jul 20 06:53:08 vmkernel: 0:00:00:21.963 cpu1:4123)VMK_VECTOR: 143: Added handler for shared vector 136, flags 0x10
Jul 20 06:53:08 vmkernel: 0:00:00:21.963 cpu1:4123)IDT: 1133: 0x88 for vmkernel
Jul 20 06:53:08 vmkernel: 0:00:00:21.963 cpu1:4123)VMK_VECTOR: 231: vector 136 enabled
Jul 20 06:53:08 vmkernel: 0:00:00:21.964 cpu0:4593)NetPort: 982: enabled port 0x3 with mac 00:00:00:00:00:00
Jul 20 06:53:08 vmkernel: 0:00:00:21.964 cpu0:4593)Uplink: 13145: vmnic3 is opened
Jul 20 06:53:08 vmkernel: 0:00:00:21.964 cpu0:4593)Uplink: 13003: Opening device vmnic4
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4123)IDT: 1036: 0x88 <vmnic4> sharable (entropy source), flags 0x10
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4123)VMK_VECTOR: 143: Added handler for shared vector 136, flags 0x10
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4123)IDT: 1133: 0x88 for vmkernel
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4123)VMK_VECTOR: 231: vector 136 enabled
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu1:4593)NetPort: 982: enabled port 0x4 with mac 00:00:00:00:00:00
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4593)Uplink: 13145: vmnic4 is opened
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4593)Mod: 4163: Initialization of e1000 succeeded with module ID 32.
Jul 20 06:53:08 vmkernel: 0:00:00:21.976 cpu0:4593)e1000 loaded successfully.
So odd. I am trying a vm on it now (vCMA) to see if it can boot and not PSOD.
.
.
.
.
So far the vm is running.
I don't understand.
Any ideas? Think it will be reliable? Using the stock settings from 4.1.U1.
Anyone know where the sata_nv enable might have been? I think I uncommented something. I had to do with during the install and on the installed drive.