ESX 4.1 vmdk lock arızası Cannot delete file [Datastore] VM_NAME

ESX4.1 de Datastore dan dosya silmeye kalktığımızda  aşağıdaki gibi Cannot delete file hatası alırsanız

Konsol dan bağlanıp   aşağıdaki  komutunu çalıştırıyoruz resimdeki gibi owner ın mac id'sini alıyoruz.

RVTools programı ile vNIC tabından bu mac id nin hangi ESX host'a ait olduğuna bakıyoruz.
Program yok ise ifconfig ile tek tek bakmanız veya PowerCLI scriptler ile bulmanız gerekecektir. Bana göre en basit yöntem RVTools kullanmak.

Bulduğumuz host'a konsol dan bağlanıp Management Servisini restart ediyoruz.

service mgmt-vmware restart

Ardından ilgili vmdk dosyasını silebiliriz. ilk resimde delete file complete i görebilirsiniz.


Volkan Vural
aytvolkan@hotmail.com

Internet Explorer cmd kapatma

taskkill /IM iexplore.exe /F

komutu ile cmd üzerinden Internet Explorer kapatılabilir.

vMA BAD PASSWORD : is too simple

vMA de basit şifre veya kompleks olmayan şifre hatası için  sudo -s ile root shell e düşülür. ardından
sudo passwd vi-admin komutu kullanılarak şifre değiştirilir.

Kaunak : http://www.boche.net/blog/index.php/2011/06/27/forc-a-simple-vmware-vma-password/

ESXi 4.1. VSphere Client Bağlantı Hatası

Eğer Free ESXi 4.1 kullanıyorsanız Vsphere Client bağlantı problemi yaşarsanız aşağıdaki komut ile servisleri yeniden başlatıp deneyebilirsiniz.

services.sh restart

aşağıda örnekkonsol mesajlarını görebilirsiniz


You have activated Tech Support Mode.
The time and date of this activation have been sent to the system logs.

VMware offers supported, powerful system administration tools.  Please
see www.vmware.com/go/sysadmintools for details.

Tech Support Mode may be disabled by an administrative user.
Please consult the ESXi Configuration Guide for additional
important information.

~ # services.sh restart
Running sfcbd-watchdog stop
Running usbarbitrator stop
watchdog-usbarbitrator: Terminating watchdog with PID 39271091
usbarbitrator stopped.
Running wsman stop
Stopping openwsmand
Openwsmand is not running.
Running slpd stop
Stopping slpd
Running hostd stop
watchdog-hostd: Terminating watchdog with PID 38562266
Running lbtd stop
watchdog-net-lbt: Terminating watchdog with PID 39315918
net-lbt stopped.
Running sensord stop
watchdog-sensord: Terminating watchdog with PID 39283128
sensord stopped.
Running storageRM stop
watchdog-storageRM: Terminating watchdog with PID 39274914
storageRM module stopped.
Running vobd stop
watchdog-vobd: Terminating watchdog with PID 39315847
Vobd stopped.
Running vprobed stop
watchdog-vprobed: Terminating watchdog with PID 39299441
vprobed stopped.
Running lsassd stop
Stopping Likewise Identity and Authentication Service...ok
Running lwiod stop
Stopping Likewise IO Manager Service...ok
Running TSM-SSH stop
Stopping tech support mode ssh server
Running DCUI stop
Disabling DCUI logins
Running ntpd stop
Stopping ntpd
Running TSM stop
Hiding TSM login
Running netlogond stop
Stopping Likewise Site Affinity Service...ok
Running netlogond restart
Starting Likewise Site Affinity Servicetouch: /var/lock/subsys/netlogond: No such file or directory
...ok
Running TSM restart
Displaying TSM login: runlevel =
Running ntpd restart
Starting ntpd
Running DCUI restart
Enabling DCUI login: runlevel =
Running TSM-SSH restart
Starting tech support mode ssh server
Running lwiod restart
Starting Likewise IO Manager Servicetouch: /var/lock/subsys/lwiod: No such file or directory
...ok
Running lsassd restart
Starting Likewise Identity and Authentication Servicetouch: /var/lock/subsys/lsassd: No such file or directory
...ok
Running vprobed restart
vprobed started.
Running vobd restart
Vobd started.
Running storageRM restart
storageRM module started.
Running sensord restart
sensord started.
Running lbtd restart
net-lbt started.
Running hostd restart
Running slpd restart
[39299459] Begin 'hostd ++min=0,swap,group=hostd /etc/vmware/hostd/config.xml', min-uptime = 60, max-quick-failures = 1, max-total-failures = 1000000
Starting slpd
Running wsman restart
Starting openwsmand
Running usbarbitrator restart
Rescanning all adapters..
usbarbitrator started.
Running sfcbd-watchdog restart
~ #

ESX Server Disable Remapping ayarı APIC: 1823: APICID 0×00000000 – ESR = 0×40

ESX de Purple Screen Of Death hatası için aşağıdaki aşamaları yapmak gerekiyor ve Hardware e ait Updatelerin yapılmasıda yerinde olacaktır.

• HBAs stop responding
• Other PCIs devices may also stop responding
• You see an an illegal vector shortly before an HBA stops responding to the driver. For example:
  vmkernel: 6:01:34:46.970 cpu0:4120)ALERT: APIC: 1823: APICID 0×00000000 – ESR = 0×40
• The HBA stops responding to commands. For example:
  vmkernel: 6:01:42:36.189 cpu15:4274)<6>qla2xxx 0000:1a:00.0: qla2x00_abort_isp: **** FAILED ****
  vmkernel: 6:01:47:36.383 cpu14:4274)<4>qla2xxx 0000:1a:00.0: Failed mailbox send register test
• The HBA card gets marked offline. For example:
  vmkernel: 6:01:47:36.383 cpu14:4274)<4>qla2xxx 0000:1a:00.0: ISP error recovery failed – board disabled

Console da ve vSphere de aşağıdaki işlemleri yapıyoruz.

• Run the commands: # esxcfg-advcfg -k TRUE iovDisableIR
  # reboot
  To check if interrupt mapping is set after the reboot, run the command:
  # esxcfg-info -c
  iovDisableIR=TRUE
  
• In vSphere Client:
  1. Click Configuration > (Software) Advanced Settings > VMkernel.
  2. Select VMkernel.Boot.iovDisableIR and click OK.
  3. Reboot the ESX host.
  
  Kolay gelsin
  
  

At the moment, vSphere Client does not support the renaming of virtual disks as the machines that use this disk may loose access to the disk Hatası Çözümü

Vsphere de disk ismi değiştirmeye kalktığınızda "At the moment, vSphere Client does not support the renaming of virtual disks as the machines that use this disk may loose access to the disk." hatası aldığımızda aşağıdaki komut ile değiştirebilirsiniz.

    
   
         

 [root@example]# vmkfstools -E exampledisk1_1.vmdk yeniexampledisk2_1.vmdk

Kolay Gelsin

Kaynak : http://kb.vmware.com/kb/1002491

Volkan Vural

Linux dosya içinde metin arama

plus.google.com adresinin geçtiği metin dosyalarını görmek için aşağıdaki komutu kullanabiliriz.

find / -type f -name "*"|xargs grep -l 'plus.google.com'