Hello Everyone,
I have my two ESXI's 6.7 running on individual machines.
The one is fine with the two HDD each of (1 TB) added as an extent to Booting HDD(2 TB) comprising of single Datastore..
The real problem lies with the other ESXI 6.7 well, as i can't expand by adding extent with the booting HDD (2TB)..
Surprisingly, if i left the booting HDD 2TB as one Datastore and configure the other HDD of 1TB as other Datastore individually, i can expand by adding extent to the later one
but not with the 2TB..
I have attached some pictures within this..
Any Help would be greatly appreciated..
I understand that the datastore is also a booting LUN?
If yes, then partition sectors might not be continuous which may cause this problem.
Run below command to check that
partedUtil getptbl /vmfs/devices/disks/naa.xxxxxxxxxxxxxxxxxxxxxx
ashishsingh1508
Hello Sir,
Thankyou for the reply,
Please have a look over the o/p.
Hope the partition seems okay..
[root@virtual1:~] partedUtil getptbl /vmfs/devices/disks/t10.ATA_____ST2000VM0032D1ET164__________________________________W5236S02
gpt
243201 255 63 3907029168
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
2 7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
3 15472640 3907029134 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
Partition looks good.
Try adding this filter and let me know if you see the LUN to use as an extent?
The article is for 5.1 but its valid for 6.5 or 6.7 as well
ashishsingh1508
I have doubt over "Same Host and Transports Filter" ..
But, i can't find relevant filters too in ESXI 6.7.
Thank you..
You have to add it
ashishsingh1508
Sorry to say but i can't add the filter too ..
I would recommend thatyou review your plan of adding an extent to an existing datastore.
Instead just create a new 2TB datastore.
A datastore expanded with extents will become unreadable if one of both datastores fail - so effectively you add an unnecessary risk if you use extents.
continuum
Thankyou Sir,
I must do that by now but i only wanted to dig the problem regarding the extent..:)