Vmware проверка диска на ошибки

• 

  Is this on a SAN/NAS or a local disk on the ESXi Server?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Jaguar

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  habanero

  What’s running this ESXi Host?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  ACTS360 is an IT service provider.

  poblano

  This is on a local RAID array on the ESXi server.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  ACTS360 is an IT service provider.

  poblano

  ESXi is running on a dell power edge 2950 server.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Replicate your data and replace your array. As far as I know, VMFS does it’s own housekeeping and there is no way to force a disk check on the VMFS level. An NTFS chkdisk will only be so effective. Because, as you said, it’s sitting on top of VMFS.

  Whenever you suspect a bad block on disk in a production environment, it’s always better to replace first ask questions later.

  And I would also advise to stay away from RAID 5 if that is what you are using currently:

  RAID 5 vs RAID 10 Opens a new window

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  ACTS360 is an IT service provider.

  poblano

  Wow….that seems very drastic…can I just replace a drive? Is there a way to tell which drive in the array has the bad block?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Is the hardware under any type of warranty?  If so, you can probably get it replaced on that error by talking to a support person.  I’ve done it — as far as seeing which one is bad, you will need to go into the RAID controller software.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  ACTS360 is an IT service provider.

  poblano

  Yes, the server is under warranty. Ok, I’ll see if Dell will replace the drive. Thanks

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Wow….that seems very drastic…can I just replace a drive? Is there a way to tell which drive in the array has the bad block?

  Doesn’t the server tell you where the error is when it tells you that there is an error?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

• 

  Scott does make a point.  Can you not see from the health status in vCenter which disk?  You still may need the OMSA to rebuild your array and it’s nice to have available. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

• 

  Jaguar

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  habanero

  Scott Alan Miller wrote:

  Josh@Acts360 wrote:

  Wow….that seems very drastic…can I just replace a drive? Is there a way to tell which drive in the array has the bad block?

  Doesn’t the server tell you where the error is when it tells you that there is an error?

  ESXi should be able to tell you (Though I’ve got the «Dell customized» version of ESXi installed, you can get it of vmware’s site.

  attach_file
  Attachment
  
  vcenterstorage.PNG
  112 KB
  
  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Yeah, Jaguar nailed it.  You should, at minimum, be able to see the state of your storage in vCenter.  At that point you can identify the drive.  Having OMSA on your host just makes it easier to perform some of your functions, like storage configurations and changes, without having to reboot and go through the bios to get to it. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  ACTS360 is an IT service provider.

  poblano

  No Vcenter all I have is the free stuff. I can see some information listed. It actually shows that there is no problem with the system… I also have an ISCSI device connected so maybe that device is the one throwing the errors.

  Oh, looks like that is it…I just looked and the event logs and I see the hard disk is disk 1 which points to the ISCSI disk. I updated the firmware on this device (which is a Synology disk station 1010+) and this fixed the issue with this device.

  Log Name:      System
  Source:        disk
  Date:          9/17/2010 9:11:31 AM
  Event ID:      51
  Task Category: None
  Level:         Warning
  Keywords:      Classic
  User:          N/A
  Computer:      FBLDC.fbdomain.local
  Description:
  An error was detected on device DeviceHarddisk1DR4 during a paging operation.
  Event Xml:
  <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event Opens a new window«>
    <System>
      <Provider Name=»disk» />
      <EventID Qualifiers=»32772″>51</EventID>
      <Level>3</Level>
      <Task>0</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated SystemTime=»2010-09-17T13:11:31.421Z» />
      <EventRecordID>177451</EventRecordID>
      <Channel>System</Channel>
      <Computer>FBLDC.fbdomain.local</Computer>
      <Security />
    </System>
    <EventData>
      <Data>DeviceHarddisk1DR4</Data>
      <Binary>030080000100000000000000330004802D0100000E0000C0000000000000000000000000000000006262170000000000FFFFFFFF010000005800002100000000BB20101242032040001000003C0000000000000000000000789BF70C80FAFFFF0000000000000000909B010A80FAFFFF0000000000000000E807640000000000880000000000006407E8000000080000000000000000000000000000000000000000000000000000</Binary>
    </EventData>
  </Event>

  attach_file
  Attachment
  
  VMWare.png
  9.18 KB
  
  

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  ACTS360 is an IT service provider.

  poblano

  Turns out that if I had just looked at the event log closer I would have noticed that the drive that the event refered to was pointing to my ISCSI, which was offline…

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Jaguar

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  habanero

  should have said it was an iSCSI

  Glad you got it fixed.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

Since ESXi 5.1 it is possible to check VMFS for metadata inconsistency with a tool called VOMA (VMware Ondisk Metadata Analyser). With VOMA you can check VMFS3 and VMFS5 datastores.

Please note, that the tool can only identify problems, as it runs in a read-only mode. So it does not help you to fix detected errors.

Reasons to use VOMA:

• occurrence of metadata errors in the vmkernel log
• if you experience SAN outages
• after rebuilding a RAID
• if you cannot modify, erase or access files on a VMFS datastore, that is not in use by another host

Before you start VOMA from the CLI of your ESXi host, take care of the following guidelines:

• Shut down all virtual machines running on the VMFS datastore (or migrate them)
• make sure that the VMFS volume is not in use by other hosts (best practice: unmount the datastore on the other hosts)
• make sure that the datastore is not in use by vSphere HA for heartbeating
• make sure that the datastore is not in use by other features like Storage I/O control,…
• make sure that the volume is not a multi-extent volume

Now log on to your ESXi host and let’s take a look at the available parameters of VOMA (voma -h)

First, you need to know the path to the partition (naa.xxxxxx:1). Run the following command to display a list with Volume Name, VMFS UUID and Device Name:

esxcli storage vmfs extent list

The output should be simular like this:

If we want to scan VMLUN_01 we have to combine the Device Name (naa.60a98000646e6c…) and the partition number (1) with a “:”.

voma -m vmfs -f check -d /vmfs/devices/disks/naa.60a98000646e6c50566f6a6c6a683164:1

If VOMA runs successfully, you should see something like this:

Checking if device is actively used by other hosts

Running VMFS Checker version 0.9 in check mode

Initializing LVM metadata, Basic Checks will be done

Phase 1: Checking VMFS header and resource files

Detected file system (labeled:’VMLUN_01′) with UUID:4fa227b8-8d16cdf3-4816-984be103b9a0, Version 5:54

Phase 2: Checking VMFS heartbeat region

Phase 3: Checking all file descriptors.

Phase 4: Checking pathname and connectivity.

Phase 5: Checking resource reference counts.

Total Errors Found:           0

What should I do if VOMA detects an error?

The tool can only find errors – but not fix them. So if VOMA detects any errors, please consult VMware support for further help.

Possible reasons/messages for stopping the VOMA scan:

If there is activity on the datastore you try to scan with VOMA, you will see the following output:

Found 1 actively heartbeating hosts on device / 1): MAC address xx:xx:xx:xx:xx:xx

VOMA stops the scan, as there is activity on the VMFS filesystem. The MAC address indicates the management interface of the ESXi host causing the activity.

Reasons for this can be:

• a running VM on the scanned datastore
• other hosts are accessing the datastore
• vSphere HA is using the datastore for heartbeating
• Storage I/O Control is turned on

Здравствуйте!
Увидел в логах ошибки

Device tlO.ATA_TO5HIBA_DT01ACA200_X3FBT5LK5 performance has deteriorated. I/O latency increased from average value of 2410 microseconds to 78012 microseconds.

И задумался о состоянии жестких дисков, но в разделе Health Status не отображаются HDD.
На сколько я знаю, это связано с тем, что нету драйвера для этого контроллера.
И я где-то читал, что его нужно скачать у вендора и установить .
Но мои поиски не увенчались успехом.
ESXi 5.5.0, 1331820
Материнская плата P8B-M с контроллером intel c204.
Возможно есть другие способы посмотреть SMART?

з.ы. знаю что ESXi не работает с программный рейдом, но и не стоит задачи его использовать, контроллер работает в режиме SATA

з.ы.ы.
Подключился по ssh, и с помощью скрипта получил вот это:

/usr/lib/vmware/vm-support/bin # ./smartinfo.sh
SMART Information for disks.

Device:  t10.ATA_____TOSHIBA_DT01ACA200_________________________________X3FBTSLKS
Parameter                     Value  Threshold  Worst
-----------------------------------------------------
Health Status                 OK     N/A        N/A
Media Wearout Indicator       N/A    N/A        N/A
Write Error Count             N/A    N/A        N/A
Read Error Count              100    16         100
Power-on Hours                99     0          99
Power Cycle Count             100    0          100
Reallocated Sector Count      100    5          100
Raw Read Error Rate           100    16         100
Drive Temperature             142    0          142
Driver Rated Max Temperature  N/A    N/A        N/A
Write Sectors TOT Count       200    0          200
Read Sectors TOT Count        N/A    N/A        N/A
Initial Bad Block Count       N/A    N/A        N/A


Device:  t10.ATA_____TOSHIBA_DT01ACA200_________________________________739NE17KS
Parameter                     Value  Threshold  Worst
-----------------------------------------------------
Health Status                 OK     N/A        N/A
Media Wearout Indicator       N/A    N/A        N/A
Write Error Count             N/A    N/A        N/A
Read Error Count              100    16         100
Power-on Hours                99     0          99
Power Cycle Count             100    0          100
Reallocated Sector Count      100    5          100
Raw Read Error Rate           100    16         100
Drive Temperature             142    0          142
Driver Rated Max Temperature  N/A    N/A        N/A
Write Sectors TOT Count       200    0          200
Read Sectors TOT Count        N/A    N/A        N/A
Initial Bad Block Count       N/A    N/A        N/A