Hi,
Trying to launch an ESXi machine but I am not able to select the VMFS7 Layout. Whenever I try to do so it just goes to the vmfs6 one as can be seen below:
I am trying to use the VMFS7 due to the issue I am having after installing esxi through MaaS the datastore size doesn’t match with the physical disk space available (it is much less) as can be seen on this github issue:
https://github.com/canonical/packer-maas/issues/25#issuecomment-856453300
Thanks a lot
BR
Trying from the maas-cli it yields the some result:
maas admin machine set-storage-layout yswsk8 storage_layout=vmfs7
…
“path”: “/dev/disk/by-dname/datastore1”,
“filesystem”: {
“fstype”: “vmfs6”,
“label”: null,
“uuid”: “0c2129a2-5e4d-44cd-b1ec-c834d0e57740”,
“mount_point”: “/vmfs/volumes/datastore1”,
“mount_options”: null
},
…
I have tried now with an ESXI6 image and VMFS6 storage and the same thing happens unfortunately.
Out of the 500GB of real space only 50GB appear on the ESXI datastore.
Some logs from /var/log/maas on the esxi host after deployment:
FixGpt tries to fix any problems detected in GPT table.
Please ensure that you don’t run this on any RDM (Raw Device Mapping) disk.
Are you sure you want to continue (Y/N): Error: The backup GPT table is not at the end of the disk, as it should be. This might mean that another operating system believes the disk is smaller. Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? gpt
58365 255 63 937637552
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 20971486 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
gpt
58365 255 63 937637552
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 0
9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 0
2 7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 0
3 15472640 130742272 AA31E02A400F11DB9590000C2911D1B8 0
create fs deviceName:‘/vmfs/devices/disks/naa.600508b1001c2c4e1d89b7af0e6f8b53:3’, fsShortName:‘vmfs6’, fsName:‘datastore1’
deviceFullPath:/dev/disks/naa.600508b1001c2c4e1d89b7af0e6f8b53:3 deviceFile:naa.600508b1001c2c4e1d89b7af0e6f8b53:3
ATS on device /dev/disks/naa.600508b1001c2c4e1d89b7af0e6f8b53:3: not supported
.
Checking if remote hosts are using this device as a valid file system. This may take a few seconds…
Creating vmfs6 file system on “naa.600508b1001c2c4e1d89b7af0e6f8b53:3” with blockSize 1048576, unmapGranularity 1048576, unmapPriority default and volume label “datastore1”.
Successfully created new volume: 618cec0b-7b392104-a0cc-08f1eaf5fc5c
INFO: Removing the default datastore.
INFO: Creating partition 3 on /vmfs/devices/disks/naa.600508b1001c2c4e1d89b7af0e6f8b53
INFO: Creating VMFS6 datastore datastore1 using /vmfs/devices/disks/naa.600508b1001c2c4e1d89b7af0e6f8b53:3 as the head partition
INFO: Done applying storage configuration!
Inside ESXI:
New update, for esxi7 it doesn’t even create the datastore:
FixGpt tries to fix any problems detected in GPT table.
Please ensure that you don’t run this on any RDM (Raw Device Mapping) disk.
Are you sure you want to continue (Y/N): Error: The backup GPT table is not at the end of the disk, as it should be. This might mean that another operating system believes the disk is smaller. Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? gpt
58365 255 63 937637552
1 64 204863 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 208896 2306047 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 2308096 4405247 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 4407296 20971486 4EB2EA3978554790A79EFAE495E21F8D vmfsl 0
gpt
58365 255 63 937637552
1 64 204863 C12A7328F81F11D2BA4B00A0C93EC93B 128
5 208896 2306047 EBD0A0A2B9E5443387C068B6B72699C7 0
6 2308096 4405247 EBD0A0A2B9E5443387C068B6B72699C7 0
7 4407296 20971486 4EB2EA3978554790A79EFAE495E21F8D 0
8 20971487 21044447 AA31E02A400F11DB9590000C2911D1B8 0
gpt
58365 255 63 937637552
1 64 204863 C12A7328F81F11D2BA4B00A0C93EC93B 128
5 208896 2306047 EBD0A0A2B9E5443387C068B6B72699C7 0
6 2308096 4405247 EBD0A0A2B9E5443387C068B6B72699C7 0
7 4407296 20971486 4EB2EA3978554790A79EFAE495E21F8D 0
8 20971487 21044447 AA31E02A400F11DB9590000C2911D1B8 0
9 21044448 21699808 AA31E02A400F11DB9590000C2911D1B8 0
create fs deviceName:‘/vmfs/devices/disks/naa.600508b1001cdaffa8262068caadbbc1:3’, fsShortName:‘vmfs6’, fsName:‘datastore1’
Device path name “/vmfs/devices/disks/naa.600508b1001cdaffa8262068caadbbc1:3” is not a valid absolute or relative path
Failed to resolve device name path /vmfs/devices/disks/naa.600508b1001cdaffa8262068caadbbc1:3
VmkfslibExtractObjectName failedUsage: vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/vml… or,
vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/naa… or,
vmkfstools -C [vmfs5|vmfs6|vfat] /vmfs/devices/disks/mpx.vmhbaA:T:L:P
Error: No such file or directory
INFO: Creating partition 8 on /vmfs/devices/disks/naa.600508b1001cdaffa8262068caadbbc1
INFO: Creating partition 9 on /vmfs/devices/disks/naa.600508b1001cdaffa8262068caadbbc1
INFO: Creating VMFS6 datastore datastore1 using /vmfs/devices/disks/naa.600508b1001cdaffa8262068caadbbc1:3 as the head partition
Traceback (most recent call last):
File “/altbootbank/maas/storage-esxi”, line 460, in
main()
File “/altbootbank/maas/storage-esxi”, line 454, in main
mkvmfs(disks, partitions, vmfs_datastores)
File “/altbootbank/maas/storage-esxi”, line 330, in mkvmfs
check_call(
File “/lib64/python3.8/subprocess.py”, line 364, in check_call
subprocess.CalledProcessError: Command ‘[‘vmkfstools’, ‘-C’, ‘vmfs6’, ‘-S’, ‘datastore1’, ‘/vmfs/devices/disks/naa.600508b1001cdaffa8262068caadbbc1:3’]’ returned non-zero exit status 255.
For ESXI6 this solved the issue: https://github.com/canonical/packer-maas/issues/25#issuecomment-828827244
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
