Quantcast
Channel: VMware Communities: Message List - ESXi
Viewing all 28826 articles
Browse latest View live
↧

Re: Used space is much bigger than real used space

October 20, 2018, 6:02 am
$
0
0

Hello nasco.

 

 

From the timestamps it would appear that yes, these snapshots are likely part of the currently active disk-chain - this can be verified by looking at the chains parent-child info in each descriptor file and by looking at the .vmx (e.g. #cat VMname.vmx | grep vmdk   or Right-click > Edit Settings > Hard Disk 1/2/etc. > look at the path which will be -000004.vmdk).

How much space is free on the LUN/datastore that this VM resides on? I ask as if this is full then consolidation may not be possible until you extend the space or free up a little bit (e.g. by powering-off the VM and freeing up the 8GB the .vswp uses).

If there is free space on the datastore (if not thin then check with #df -h ), then you would likely be able to make a consolidatable reference by removing the current .vmsd (the file that shows snapshot chain in snapshot manager), then taking another snapshot of the VM and then using 'Delete All' snapshots option.

Another option would be to check can this job be performed from the CLI:

# vim-cmd vmsvc/snapshot.removeall <VM-ID>

If these are not working and you have free space then you likely have locked files which is a different issue.

Last resort would be to either clone the VM or consolidate the snapshots+base-disk into one vmsk using vmkfstools -i.

 


Bob

↧
Search

Re: Used space is much bigger than real used space

October 20, 2018, 8:10 am
$
0
0

Hi TheBobkin,

You are correct, the output is exact as your prediction. I've just created a snapshot and now I'm waiting for the result of command "vim-cmd vmsvc/snapshot.removeall 58" (58 is VMId). It has been idle for an hour as below:

esxi-2-ss.JPG

↧
↧

Re: Used space is much bigger than real used space

October 20, 2018, 10:43 am
$
0
0

TheBobkin

it does not help. I tried 2 times and now there are 2 new vmdk files as xxxx-000005.vmdk and xxxx-000006.vmdk (before is 000004.vmdk). The thin provision of this VM is bigger after trying this way. Pls help me, tks

↧

Re: Trying to upgrade Dell server - need to remove VIB

October 20, 2018, 11:55 am
$
0
0

i think that a 5.0 driver creates an unresolved dependency. So search for

 

 esxcli software vib list | grep -i 500

 

What ever it lists..... remove it, reboot and try upgrading again.

 

Regards,

Joerg

↧

Re: Used space is much bigger than real used space

October 20, 2018, 12:37 pm
$
0
0

Hello nasco,

 

 

"It has been idle for an hour as below"

It's not idling it's trying to write the ~2TB of data you appear to have in snapshots.

 

"it does not help. I tried 2 times and now there are 2 new vmdk files as xxxx-000005.vmdk and xxxx-000006.vmdk"

Yes because you took (assumedly more than 1) extra snapshot, the number of snapshots here is unlikely the problem more so the size of the snapshots and likely your storage timing out at some point while trying to write the all the data back to the base-disks - the vmkernel.log and/or vmware.log of the VM should indicate this (or some other cause) for to failing to consolidate the snapshots.

You *may* potentially have better luck consolidating them with the VM powered off as the IOs of the VM itself can also be a source of contention to the storage that is trying to write-back the snapshots here. If this also fails then potentially cloning the disk with the VM powered off might be your only option but do ensure you have adequate space to perform this.

 

 

Bob

↧
↧

Lots of "Deassert" messages about drives

October 20, 2018, 7:05 pm
$
0
0

I've got a whole lot of "Deassert" messages on my new install of ESXi:

 

SAS A 0: Config Error - DeassertGreen0Cable/InterconnectUnknown
Disk Drive Bay 1 Cable SAS B 0: Config Error - DeassertGreen0Cable/InterconnectUnknown
Disk Drive Bay 1 Drive 0: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 0: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 1: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 2: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 3: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 4: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 5: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 6: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Drive Fault - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: In Critical Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: In Failed Array - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Parity Check In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Predictive Failure - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Rebuild Aborted - DeassertGreen0StorageUnknown
Disk Drive Bay 1 Drive 7: Rebuild In Progress - DeassertGreen0StorageUnknown
Disk Drive Bay 3 ROMB Battery 0: Failed - DeassertGreen0BatteryUnknown
Disk Drive Bay 3 ROMB Battery 0: Low - Deassert

 

 

What's really odd about these messages is I only have FOUR drives. I'm seeing messages about EIGHT drives here and they seem to just repeat through these various messages.

 

Are these real or could I be mising an update?

 

I installed a customized ESXi for the Dell R710 from the Dell website.

 

Thanks in advance

↧

Re: vSphere 6.0.0 not seeing 82571EB Gigabit Ethernet Controller

October 20, 2018, 10:27 pm
$
0
0

I have the same problem as these two, but I have a quad port 82571EB and ESXi 6.7. All four interfaces show up in lspci just like above. None of them show up in the web based ESXi manager under Networking -> Physical NIC's.

 

However, all four show up under Host -> Manage -> Hardware. I can select them, to set them up as pass through devices, but they select and unselect in pairs. The addresses are also in the same pairs. After I setup pass through, I reboot, but the changes don't take as they still show up pass through disabled.

↧

Re: Used space is much bigger than real used space

October 21, 2018, 12:15 am
$
0
0

Dear TheBobkin

It's too difficult for me. This is the VM which is providing 24/7 service. I cannot turn it off

↧
Search

Re: Used space is much bigger than real used space

October 21, 2018, 12:38 am
$
0
0

After reading the comments, I would suggest to clone this VM to another Datastore if you don't have enough space.

The problem with orphaned snapshots is that if you check the .vmx file of the VM it will point to the latest snapshot you created (you can verified) and you can do nothing about it except consolidate as you can this VM.

So, you can clone the VM or try to consolidate it offline (couldn't work) but anyway you will end in power-off this VM.

The only thing is that if you clone the VM while is powered on, well changes that are ocurring maybe are not consistent, this is why cloning when is powered-off is usually a success.

Then you power on the new cloned VM shouldn't suppose any problem.

↧
↧

Re: Lots of "Deassert" messages about drives

October 21, 2018, 12:43 am
$
0
0

What about checking the logs from the ESXi?

The one to check here would be the vmkernel.log

↧

Re: Inital network setup on standalone ESXi

October 21, 2018, 2:53 am
$
0
0

Yes, that's exactly how it works.

This way the Ethernet package that's passed from the physical switch port to the vSwitch will contain the VLAN tag. The vSwitch will then remove the VLAN tag, and deliver the package to port groups with that VLAN ID.

Note that you must not set a VLAN ID on port groups for the native/default VLAN (if you are going to use this VLAN on the virtual side), because the physical switch will already remove the VLAN tag from the frame.

 

André

↧

Re: Used space is much bigger than real used space

October 21, 2018, 3:41 am
$
0
0

To find out what's possible, please answer the following questions and/or provide the required information.

  • provide the result of ls -lisa  (this will contain some more details, including used disk space)
  • attach the vmware.log file to a reply post (the important part is to find out the snapshot chain, i.e. the order of the .vmdk files)
  • how much free disk space do you currently have on the datastore?
  • is it possible to increase the LUN/datastore size?
  • do you have other datatores (how much free disk space do they have)?
  • which vSphere version/edition do you use? I'm asking to find out whether Storage vMotion is an option.

 

André

↧

ESXI 6.5 data recovery

October 21, 2018, 6:08 am
$
0
0

Dear's

 

we have ESXI 6.5 and VM 2008R2 working as file server , a snapshot was taken on last March and work proceed till october , for some unknown reason current stat was lost and it revert to last snapshot that taken at March so all of data on D drive return to March dated files and any other modifications was done at this period was lost , what kind of recovery should we make as there is no VMDK include this lost dates ,

↧
↧

Re: ESXI 6.5 data recovery

October 21, 2018, 6:36 am
$
0
0

If this was a snapshot reversion, normally there is no ability to recover that point in time because the host immediately discards it. Assuming you don't have a backup here (sounds like it), continuum may have some ideas.

↧

scratch partition and syslog

October 21, 2018, 8:15 am
$
0
0

Hi,

 

I see that the ESXi scratch partition is by default set to /tmp/scratch, where is this stored?

 

Is this local on the SD card used for the ESXi install or on ramdisk (space allocated in memory for storing these logs)?

 

Strangely when I enter df -h on an ESXi host, it does not list the local drive/partitions (SD Card).

 

For syslog, if I setup a remote host to send logs (syslog.gobal.logHost), do I also need to specify a datastore (Syslog.global.logDir) or can I set this to null?

 

 

Thanks

↧
Search

Re: scratch partition and syslog

October 21, 2018, 11:11 am
$
0
0

I see that the ESXi scratch partition is by default set to /tmp/scratch, where is this stored?

 

Is this local on the SD card used for the ESXi install or on ramdisk (space allocated in memory for storing these logs)?

On removable flash-based media this is mapped to a ramdisk.

 

For syslog, if I setup a remote host to send logs (syslog.gobal.logHost), do I also need to specify a datastore (Syslog.global.logDir) or can I set this to null?

 

If you specify a global log host you don't also need to specify a local destination unless you really want to.

↧

Re: scratch partition and syslog

October 21, 2018, 12:24 pm
$
0
0

how can I check the ramdisk used/available size?

 

will ramdisk delete old data if full to make space for the new?

 

df -h does not show used/available space of the SD card / root directory of ESXi install

 

↧
↧

Re: scratch partition and syslog

October 21, 2018, 3:56 pm
$
0
0

df -h does not show used/available space of the SD card / root directory of ESXi install

df -h does work as intended and shows the filesystem mounts ESXi is using. You can also use vdf -h to check.

 

will ramdisk delete old data if full to make space for the new?

No, if full it will prevent certain system functions from happening normally. Ramdisk will be discarded when the host is cycled.

↧

Re: Lots of "Deassert" messages about drives

October 21, 2018, 6:24 pm
$
0
0

I looked at the log you suggested.

I do not think I see anything related to the drives. I might not be looking for the right thing. I am not super familiar with Linux and these log messages look like linux/unix.

I can post the log here if it would help.

↧

Re: vmtools current but not running

October 21, 2018, 9:19 pm
$
0
0

This post is related:

 

https://communities.vmware.com/message/2809627#2809627

 

I can't speak for early versions, but current versions of VM Tools appears to clean up a previous install first.

 

This is vitally important as it keeps the vmxnet3 mac address.

 

Uninstalling VM Tools and re-installing a new VM Tools will generate a new mac address, which can certainly mess up certain licensings of sorts.

↧
Viewing all 28826 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>