• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 540
  • Last Modified:

Unable to create new partition on SAN

Hi,
I have recently blown away my SAN recently and am busy now creating new virtual disks for ESX to use. My SAN is a Dell MD3000i with 30 x 400GB SAS disks. I have assigned 8 of the physical disks into a RAID 5 group for use by an ESX cluster. I am able to mount and format LUN 0 successfully but I cannot get LUN 2 to format no matter what I try. I have looked at a bunch of posts around the new related to this issue and they all talk about using fdisk which doesn't work for me.

This is where I am at right now.

ESX can see all the LUN's on the SAN as per the output below

esxcfg-mpath -l
Disk vmhba0:0:0 /dev/sda (69376MB) has 1 paths and policy of Fixed
Local 2:14.0 vmhba0:0:0 On active preferred

Enclosure vmhba0:264:0 (0MB) has 1 paths and policy of Fixed
Local 2:14.0 vmhba0:264:0 On active preferred

Disk vmhba40:0:0 /dev/sdb (512000MB) has 1 paths and policy of Fixed
iScsi sw iqn.1998-01.com.vmware:mbtkyesx003-5e8e60e7<->iqn.1984-05.com.dell:powervault.6001e4f0003e0b4c0000000047fdc353 vmhba40:0:0 On active preferred

Disk vmhba40:0:2 (512000MB) has 1 paths and policy of Fixed
iScsi sw iqn.1998-01.com.vmware:mbtkyesx003-5e8e60e7<->iqn.1984-05.com.dell:powervault.6001e4f0003e0b4c0000000047fdc353 vmhba40:0:2 On active preferred

Doing a "fdisk -l" does not show up anything related to the new non-accessible LUN

I can mount vmhba40:0:2:0 on a windows machine, format it and use it without any issues.

This is the output from /vmfs/devices/disks

ls: vml.02000200006001e4f0003e139200001fac4910c89f4d4433303030: No such file or directory
vmhba0:0:0:0 vml.0200000000600188b03eb8f8000ce3fd966390184b504552432035
vmhba40:0:0:0 vml.02000000006001e4f0003e0b4c000034874910c4004d4433303030
vmhba40:0:2:0

How can I get fdisk to create a partition on the new LUN when it won't even see it?

I did see a post elsewhere that talked about a reprovisioned HP SAN having similar issues due to NTFS data being left behind and I tried everything in that post to no avail.

Please help if you can!

Cheers
0
markpascoe
Asked:
markpascoe
1 Solution
 
larstrCommented:
If ESX detects an NTFS volume it will not automatically resignature it to VMFS just like that.

Try doing the steps described here:
http://vmfaq.com/entry/47/

Lars
0
 
markpascoeAuthor Commented:
The solution to this issue was to change the preferred owner of the volume to the other RAID controller on the SAN.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now