Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 180923

ESXi 6.7 Trying to Expand VMFS with an error

$
0
0

Maybe this is easy for some people to work out but i have been trying for hours.

I added an extra disk to my Virtual Drive in Raid 6 on my R720 waiting for the array to rebuild.

I can see the space in the datastore on Esxi 6.7 but when i try fill the space on the VMFS it just errors when i click finish.

 

I read online because i have the OS installed and there are other partitions the resize function in the UI is broken.

 

So i tried the CLI way but i can't work this out and i keep getting these errors that make me nervous to make changes.

 

 

[root@localhost:~] vmkfstools -P "/vmfs/volumes/datastore1"

VMFS-6.82 (Raw Major Version: 24) file system spanning 1 partitions.

File system label (if any): datastore1

Mode: public

Capacity 2989565673472 (2851072 file blocks * 1048576), 556723601408 (530933 blocks) avail, max supporte                                  d file size 70368744177664

Disk Block Size: 512/512/0

UUID: 5c9068ba-3063c75c-e113-90b11c3cba96

Partitions spanned (on "lvm"):

        naa.6848f690ec5e0e0024231fc30bbc2b94:3

Is Native Snapshot Capable: NO

 

[root@localhost:~] partedUtil get "/vmfs/devices/disks/naa.6848f690ec5e0e0024231fc30bbc2b94:3"

363492 255 63 5839513567

[root@localhost:~] partedUtil get "/vmfs/devices/disks/naa.6848f690ec5e0e0024231fc30bbc2b94"

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)?

Warning: Not all of the space available to /dev/disks/naa.6848f690ec5e0e0024231fc30bbc2b94 appears to be used, you can fix the GPT to use all of the space (an extra 1170997248 blocks) or continue with the current setting? This will also move the backup table at the end if is is not at the end already. diskSize (7025983488) AlternateLBA (5854986239) LastUsableLBA (5854986206) NewLastUsableLBA (7025983454)

437347 255 63 7025983488

1 64 8191 0 128

5 8224 520191 0 0

6 520224 1032191 0 0

7 1032224 1257471 0 0

8 1257504 1843199 0 0

9 1843200 7086079 0 0

2 7086080 15472639 0 0

3 15472640 5854986206 0 0

 

 

[root@localhost:~] partedUtil getUsableSectors "/vmfs/devices/disks/naa.6848f690ec5e0e0024231fc30bbc2b94"

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)?

Warning: Not all of the space available to /dev/disks/naa.6848f690ec5e0e0024231fc30bbc2b94 appears to be used, you can fix the GPT to use all of the space (an extra 1170997248 blocks) or continue with the current setting? This will also move the backup table at the end if is is not at the end already. diskSize (7025983488) AlternateLBA (5854986239) LastUsableLBA (5854986206) NewLastUsableLBA (7025983454)

34 7025983454

[root@localhost:~] partedUtil getUsableSectors "/vmfs/devices/disks/naa.6848f690ec5e0e0024231fc30bbc2b94"

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)?

Warning: Not all of the space available to /dev/disks/naa.6848f690ec5e0e0024231fc30bbc2b94 appears to be used, you can fix the GPT to use all of the space (an extra 1170997248 blocks) or continue with the current setting? This will also move the backup table at the end if is is not at the end already. diskSize (7025983488) AlternateLBA (5854986239) LastUsableLBA (5854986206) NewLastUsableLBA (7025983454)

34 7025983454

[root@localhost:~]


Viewing all articles
Browse latest Browse all 180923

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>