Hi, thank you so much for the detailed response... Out of interest, rather than Raid 5/6 - what is your preference - 10?
In this instance, I'm still not 100% clear on some things. So, from the vCenter, it shows my SAN as (inactive). From one of the hosts:
/dev/disks # ls
ls: ./t10.IET_____000100010000000000000000000000000000000000000000: No such file or directory
ls: ./t10.IET_____000100010000000000000000000000000000000000000000:1: No such file or directory
naa.6782bcb059e5bd0019e9f9772a8b4460
<snip>
I think these "IET" are my SAN LUNs vs. the local storage drives. I can't really do anything with the drive from the ESXi hosts itself. which brings me back to the RHEL server itself and if there's an issue here first
On RHEL storage server, I see from fdisk -l:
WARNING: GPT (GUID Partition Table) detected on '/dev/cciss/c0d2'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/cciss/c0d2: 3750.6 GB, 3750613606400 bytes
255 heads, 63 sectors/track, 455986 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/cciss/c0d2p1 1 267350 2147483647+ ee GPT
But, pvdisplay shows only:
[root@san1 ~]# pvdisplay
--- Physical volume ---
PV Name /dev/cciss/c0d0p2
VG Name vg_san1
PV Size 698.12 GiB / not usable 3.00 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 178717
Free PE 0
Allocated PE 178717
PV UUID qk1tgC-5PWE-M3cX-vb5e-Xnjd-Q7UD-n0HP33
No c0d2xx there.
Partitions:
[root@san1 ~]# cat /proc/partitions
major minor #blocks name
104 0 732541816 cciss/c0d0
104 1 512000 cciss/c0d0p1
104 2 732027904 cciss/c0d0p2
104 16 732541816 cciss/c0d1
104 17 51200000 cciss/c0d1p1
104 18 102400 cciss/c0d1p2
104 19 681236480 cciss/c0d1p3
104 32 3662708600 cciss/c0d2
253 0 52428800 dm-0
253 1 4063232 dm-1
253 2 675532800 dm-2
So there, the disk c0d2 is seen, but the partition is not.
The targets.conf is still set accordingly to:
<target iqn.anzse.xxxxxxxx.com:x.x.x.x.target1>
direct-store /dev/cciss/c0d2p1
initiator-address ALL
</target>
Given c0d2p1 does not seem to properly exist at the RHEL level, how is the ESXi going to connect to it...?
I feel that until I correct this at RHEL level, there's little to be done from within the VMWare world - or am I off beam here?
Thanks again,