{"id":14785,"date":"2024-10-24T22:51:07","date_gmt":"2024-10-24T19:51:07","guid":{"rendered":"https:\/\/sarzimanli.com\/?p=14785"},"modified":"2024-11-27T22:53:34","modified_gmt":"2024-11-27T19:53:34","slug":"vsan-fiziksel-disk-sorun-giderme-rehberi","status":"publish","type":"post","link":"https:\/\/sarzimanli.com\/index.php\/2024\/10\/24\/vsan-fiziksel-disk-sorun-giderme-rehberi\/","title":{"rendered":"vSAN Fiziksel Disk Sorun Giderme Rehberi"},"content":{"rendered":"\n

Web kullan\u0131c\u0131 aray\u00fcz\u00fcnden vSAN Fiziksel Disk durumunu kontrol etme:<\/strong><\/p>\n\n\n\n

vCenter Server Web \u0130stemcisine ba\u011flan\u0131n ve disk durumunu \u015furadan kontrol edin:
 
Stok > Ana Bilgisayar ve K\u00fcmeler > vSAN K\u00fcmesi vSAN Disk Y\u00f6netimini >> Yap\u0131land\u0131rma Resim 1: vSAN Disk Y\u00f6netimi g\u00f6r\u00fcn\u00fcm\u00fc Etkilenen ana bilgisayar\u0131 se\u00e7in ve ard\u0131ndan disk g\u00f6r\u00fcn\u00fcm\u00fc b\u00f6l\u00fcm\u00fcn\u00fc geni\u015fletin:Resim 2: vSAN > Disk<\/strong>Grubu g\u00f6r\u00fcn\u00fcm\u00fc<\/p>\n\n\n\n

\"vSAN \"vSAN<\/p>\n\n\n\n

Burada bir diskin \u015fu \u015fekilde alg\u0131lan\u0131p alg\u0131lanmad\u0131\u011f\u0131n\u0131 do\u011frulayabilirsiniz:<\/p>\n\n\n\n

Sa\u011fl\u0131ks\u0131z
Ba\u011fl\u0131
De\u011fil 0 Kapasite
Kal\u0131c\u0131 Disk Ar\u0131zas\u0131 Disk Kapal\u0131
Disk Yok<\/p>\n\n\n\n

Ayr\u0131ca, vSAN Skyline Health b\u00f6l\u00fcm\u00fcnden tetiklenen diskle ilgili alarmlar\u0131 kontrol edin: 

Stok > Ana Bilgisayar ve K\u00fcmeler > vSAN K\u00fcme Monit\u00f6r\u00fc >> vSAN > Skyline Sa\u011fl\u0131k > Fiziksel diski<\/strong><\/p>\n\n\n\n

Resim 3: Skyline Sa\u011fl\u0131k g\u00f6r\u00fcn\u00fcm\u00fc
\"Skyline
Burada, a\u015fa\u011f\u0131daki alarmlardan herhangi birinin tetiklenip tetiklenmedi\u011fini do\u011frulayabilirsiniz:

Kal\u0131c\u0131 disk ar\u0131zas\u0131 yakla\u015f\u0131yor, veriler bo\u015falt\u0131l\u0131yor (Sa\u011fl\u0131k durumu – Sar\u0131).
Yakla\u015fan kal\u0131c\u0131 disk ar\u0131zas\u0131, yetersiz kaynaklar nedeniyle veri tahliyesi ba\u015far\u0131s\u0131z oldu (Sa\u011fl\u0131k durumu – K\u0131rm\u0131z\u0131).
Yakla\u015fan kal\u0131c\u0131 disk ar\u0131zas\u0131, eri\u015filemeyen nesneler nedeniyle veri tahliyesi ba\u015far\u0131s\u0131z oldu (Sa\u011fl\u0131k durumu – K\u0131rm\u0131z\u0131).
Yakla\u015fan kal\u0131c\u0131 disk ar\u0131zas\u0131, veri tahliyesi tamamland\u0131 (Sa\u011fl\u0131k durumu – Sar\u0131)

Ayr\u0131ca, etkilenen ana bilgisayar\u0131n Depolama Ayg\u0131tlar\u0131 listesinden disk durumunu kontrol edebilirsiniz:

Stok > Ana Bilgisayar ve K\u00fcmeler vSAN K\u00fcmesi Etkilenen > vSAN ESXi Ana Bilgisayar\u0131 > Depolama > Depolama Ayg\u0131tlar\u0131n\u0131 >><\/strong><\/p>\n\n\n\n

Yap\u0131land\u0131rma Resim 4: Ana Bilgisayar Depolama Ayg\u0131tlar\u0131 g\u00f6r\u00fcn\u00fcm\u00fc
\"Ana
Burada bir disk durumunun \u015fu \u015fekilde olup olmad\u0131\u011f\u0131n\u0131 do\u011frulayabilirsiniz:

0 Capacity Disk Absent<\/p>\n\n\n\n

Disk Unmounted<\/p>\n\n\n\n

Resync olup olmad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n: 

Stok > Ana Bilgisayar ve K\u00fcmeler > vSAN K\u00fcme Monit\u00f6r\u00fc >> vSAN > Yeniden Senkronizasyon Nesneleri<\/strong>:Resim 5:<\/p>\n\n\n\n

Nesneleri Yeniden Senkronize Etme g\u00f6r\u00fcn\u00fcm\u00fc
\"Nesneleri<\/p>\n\n\n\n

NOT:<\/strong> Yeniden e\u015fitleme, etkilenen bir diskten veya disk grubundan verilerin bo\u015falt\u0131lmakta oldu\u011funu g\u00f6sterebilir. Etkilenen diskin kald\u0131r\u0131lmaya veya de\u011fi\u015ftirilmeye haz\u0131r olup olmad\u0131\u011f\u0131n\u0131 belirlemek i\u00e7in daha fazla ara\u015ft\u0131rma yap\u0131lmas\u0131 gerekir.<\/p>\n\n\n\n

 
VSAN Nesnelerinin durumunu do\u011frulay\u0131n:

Stok > Ana Bilgisayar ve K\u00fcmeler > vSAN K\u00fcme Monit\u00f6r\u00fc >> vSAN Skyline Sa\u011fl\u0131k > Verileri > vSAN nesne sa\u011fl\u0131\u011f\u0131 Resim 6: vSAN > nesne sa\u011fl\u0131\u011f\u0131<\/strong><\/p>\n\n\n\n

g\u00f6r\u00fcn\u00fcm\u00fc
\"vSAN<\/p>\n\n\n\n

NOT:<\/strong> Eri\u015filemeyen nesne olmad\u0131\u011f\u0131n\u0131 do\u011frulamak \u00f6nemlidir. Object inaccessible, “nesnenin t\u00fcm kopyalar\u0131 eksik” anlam\u0131na gelir. DL’ye neden olabilecek bir diski kald\u0131r\u0131r veya de\u011fi\u015ftirirseniz.<\/p>\n\n\n\n

 
Bir sonraki ad\u0131m, CLI \u00fczerinden sorun hakk\u0131nda daha fazla bilgi toplamak ve g\u00fcnl\u00fckleri kontrol etmektir:CLI’dan vSAN Fiziksel Disk durumunu kontrol etme:Etkilenen ana bilgisayara SSH \u00fczerinden ba\u011flan\u0131n ve a\u015fa\u011f\u0131daki komutlar\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n\n\n\n

vdq -qH<\/strong><\/pre>\n\n\n\n
“IsPDL” (kal\u0131c\u0131 cihaz kayb\u0131) parametresini kontrol edin. 1’e e\u015fitse, disk kaybolur.

Example:
 <\/p>\n\n\n\n
DiskResults:\n DiskResult[0]:\n Name: naa.600508b1001c4b820b4d80f9f8acfa95\n VSANUUID: 5294bbd8-67c4-c545-3952-7711e365f7fa\n State: In-use for VSAN\n ChecksumSupport: 0\n Reason: Non-local disk\n IsSSD?: 0\nIsCapacityFlash?: 0\n IsPDL?: 0\n <<truncated>>\n DiskResult[18]:\n Name:\n VSANUUID: 5227c17e-ec64-de76-c10e-c272102beba7\n State: In-use for VSAN\n ChecksumSupport: 0\n Reason: None\n IsSSD?: 0\nIsCapacityFlash?: 0\n IsPDL?: 1<\/strong><\/pre>\n\n\n\n
vdq -iH<\/strong><\/pre>\n\n\n\n
Disk grubunda eksik bir disk olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.

Example:
 <\/p>\n\n\n\n
Mappings:\nDiskMapping[0]:\nSSD: naa.58ce38ee2016ffe5\nMD: naa.5002538a4819e3e0\n \nDiskMapping[2]:\nSSD: naa.58ce38ee2016fe55\nMD: naa.5002538a48199ca0\nMD: naa.5002538a48199e20\nMD: naa.5002538a48199e00<\/pre>\n\n\n\n
esxcli vsan storage list<\/strong><\/pre>\n\n\n\n
In CMMDS” parametresini kontrol edin. False ise diskle ileti\u015fim kaybolur.

Example:
 <\/p>\n\n\n\n
Device: Unknown\nDisplay Name: Unknown\nIs SSD: false\nVSAN UUID: 529cadbc-acd1-b588-8643-68336d5512d6\nVSAN Disk Group UUID:\nVSAN Disk Group Name:\nUsed by this host: false\nIn CMMDS: false<\/strong>\nOn-disk format version: <Unknown>\nDeduplication: false\nCompression: false\nChecksum:\nChecksum OK: false\nIs Capacity Tier: false<\/pre>\n\n\n\n
for i in `esxcli  storage core device list | grep ^naa` ; do echo $i; esxcli storage core device smart get -d $i; done.<\/strong><\/pre>\n\n\n\n
Smart get komutuyla okuma\/yazma hatalar\u0131n\u0131 kontrol edin.

Example:
 <\/p>\n\n\n\n
naa.55cd2e404c1f35a1\nParameter                   Value  Threshold  Worst  Raw\n--------------------------  -----  ---------  -----  ---\nHealth Status               OK     N\/A        N\/A    N\/A\nMedia Wearout Indicator     100    0          100    86\nRead Error Count            130    39         130    133\nPower-on Hours              100    0          100    110\nPower Cycle Count           100    0          100    106\nDrive Temperature           100    0          100    26\nUncorrectable Sector Count  100    0          100    0<\/pre>\n\n\n\n
naa.55cd2e404c1f35a5\nParameter                   Value  Threshold  Worst  Raw\n--------------------------  -----  ---------  -----  ---\nHealth Status               OK     N\/A        N\/A    N\/A\nMedia Wearout Indicator     100    0          100    10\nRead Error Count            130    39         130    53\nPower-on Hours              100    0          100    110\nPower Cycle Count           100    0          100    106\nDrive Temperature           100    0          100    27\nUncorrectable Sector Count  100    0          100    0<\/pre>\n\n\n\n
esxcli vsan storage list | grep \"VSAN Disk Group UUID:\" | sort | uniq -c<\/strong><\/pre>\n\n\n\n
Kullan\u0131labilir disk gruplar\u0131n\u0131 kontrol edin.

Example:
 <\/p>\n\n\n\n
      2    VSAN Disk Group UUID: 5203424c-ee56-497d-75d1-fcf73ae997cb\n      2    VSAN Disk Group UUID: 52af8e5c-77d1-b552-3310-ec5fef09edf4<\/pre>\n\n\n\n
while true;do echo \" ****************************************** \"; echo \"\" > \/tmp\/resyncStats.txt ;cmmds-tool find -t DOM_OBJECT -f json |grep uuid |awk -F \\\" '{print $4}' |while read i;do pendingResync=$(cmmds-tool  find -t DOM_OBJECT -f json -u $i|grep -o \"\\\"bytesToSync\\\": [0-9]*,\"|awk -F \" |,\" '{sum+=$2} END{print sum \/ 1024 \/ 1024 \/ 1024;}');if [ ${#pendingResync} -ne 1 ]; then echo \"$i: $pendingResync GiB\";fi;done |tee -a \/tmp\/resyncStats.txt;total=$(cat \/tmp\/resyncStats.txt |awk '{sum+=$2} END{print sum}');echo \"Total: $total GiB\" |tee -aa \/tmp\/resyncStats.txt;total=$(cat \/tmp\/resyncStats.txt  |grep Total);totalObj=$(cat \/tmp\/resyncStats.txt|grep -vE \" 0 GiB|Total\"|wc -l);echo \"`date +%Y-%m-%dT%H:%M:%SZ` $total ($totalObj objects)\" >> \/tmp\/totalHistory.txt; echo `date `; sleep 60; done<\/strong><\/pre>\n\n\n\n
Devam eden veya tak\u0131lm\u0131\u015f yeniden senkronizasyon i\u015flemleri olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.

Example:
 <\/p>\n\n\n\n
Total: 0 GiB\nMon Feb 13 17:32:06 UTC 2023<\/pre>\n\n\n\n
Komutu durdurmak i\u00e7in Ctrl+C<\/strong> tu\u015flar\u0131na bas\u0131n.
 <\/p>\n\n\n\n
cmmds-tool find -f python | grep CONFIG_STATUS -B 4 -A 6 | grep 'uuid\\|content' | grep -o 'state\\\\\\\":\\ [0-9]*' | sort | uniq -c<\/strong><\/pre>\n\n\n\n
Bile\u015fenlerin durumunu kontrol edin.

Sa\u011fl\u0131kl\u0131 — durum 7
Eri\u015filemez — durum 13
Yok veya Bozulmu\u015f — durum 15

\u00d6rnek:
 <\/p>\n\n\n\n
    425 state\\\": 7<\/pre>\n\n\n\n
 
Ar\u0131zal\u0131 SSD veya SAB\u0130T S\u00dcR\u00dcC\u00dcN\u00dcN CLI \u00fczerinde nerede bulundu\u011fu nas\u0131l belirlenir:<\/strong>

Kullan\u0131labilir t\u00fcm ayg\u0131tlar\u0131 listeleyin:<\/p>\n\n\n\n
esxcli storage core device list | grep \"naa\" | awk '{print $1}' | grep \"naa\"<\/strong><\/pre>\n\n\n\n
Example:<\/p>\n\n\n\n
naa.5000c500852df8d3\nnaa.55cd2e404c1f35a1\nnaa.55cd2e404c1f35a5\nnaa.5000c500852dd5e7<\/pre>\n\n\n\n
Listeden her bir disk naa’y\u0131 kullanarak konumu kontrol edin:<\/p>\n\n\n\n
esxcli storage core device physical get -d<\/strong><\/pre>\n\n\n\n
 
Example:
 <\/p>\n\n\n\n
esxcli storage core device physical get -d naa.5000c500852df8d3\nesxcli storage core device physical get -d naa.55cd2e404c1f35a1\nesxcli storage core device physical get -d naa.55cd2e404c1f35a5\nesxcli storage core device physical get -d naa.5000c500852dd5e7\n \n   Physical Location: enclosure 65535 slot 0\n   Physical Location: enclosure 65535 slot 1\n   Physical Location: enclosure 65535 slot 2\n   Physical Location: enclosure 65535 slot 3<\/pre>\n\n\n\n
Ayg\u0131t ad\u0131 eksikse ar\u0131zal\u0131 SAB\u0130T S\u00dcR\u00dcC\u00dc veya SSD’yi belirleme:<\/strong><\/p>\n\n\n\n
Ar\u0131zal\u0131 disk alg\u0131lanmayabilir ve ilgili naa kullan\u0131larak tan\u0131mlanamayabilir. Bu senaryoda, t\u00fcm diskleri bulmak gerekir ve fiziksel olarak bulunmayan disk, ba\u015far\u0131s\u0131z olan disktir.<\/p>\n\n\n\n
G\u00f6revi biraz daha h\u0131zl\u0131 ger\u00e7ekle\u015ftirmek i\u00e7in kullan\u0131labilecek bir komut dosyas\u0131 a\u015fa\u011f\u0131da verilmi\u015ftir:<\/p>\n\n\n\n
echo \"=============Physical disks placement==============\"\necho \"\"\nesxcli storage core device list | grep \"naa\" | awk '{print $1}' | grep \"naa\" | while read in; do\necho \"$in\"\nesxcli storage core device physical get -d \"$in\"\nsleep 1\necho \"====================================================\"\ndone<\/strong><\/pre>\n\n\n\n
Depolama ile ilgili sorunlar i\u00e7in vSAN ile ilgili g\u00fcnl\u00fckler:<\/strong>

\/var\/log\/vmkernel.log
vSAN diskleri, vSAN ana bilgisayar kalp at\u0131\u015flar\u0131, PDL’ler, SCSI alg\u0131lama kodlar\u0131 ve G\/\u00c7 istekleri (Okuma\/Yazma) ve k\u00fcme \u00fcyeli\u011fi bilgilerini okuma ve yazma sorunlar\u0131.

Example:
 <\/p>\n\n\n\n
2021-06-22T12:02:08.408Z cpu30:1001397101)ScsiDeviceIO: PsaScsiDeviceTimeoutHandlerFn:12834: TaskMgmt op to cancel IO succeeded for device naa.55cd2e404b7736d0 and the IO did not complete. WorldId 0, Cmd 0x28, CmdSN = 0x428.Cancelling of IO will be\n2021-06-22T12:02:08.408Z cpu30:1001397101)retried.<\/pre>\n\n\n\n
\/var\/log\/vobd.log
Disk durumu, kal\u0131c\u0131 ayg\u0131t kay\u0131p diskleri (PDL’ler), disk gecikme s\u00fcresi ve bir ana bilgisayar\u0131n bak\u0131m moduna ne zaman girip \u00e7\u0131kt\u0131\u011f\u0131n\u0131 raporlar.

Example:
 <\/p>\n\n\n\n
2022-05-31T11:42:46.065Z: [vSANCorrelator] 10605891965954us: [vob.vsan.lsom.devicerepair] vSAN device 521a74ce-c980-c16c-ff3d-38a036233daf is being repaired due to I\/O failures, and will be out of service until the repair is complete. If the device is part of a dedup disk group, the entire disk group will be out of service until the repair is complete.\n2022-05-31T11:42:46.065Z: [vSANCorrelator] 10606062774178us: [esx.problem.vob.vsan.lsom.devicerepair] Device 521a74ce-c980-c16c-ff3d-38a036233daf is in offline state and is getting repaired<\/pre>\n\n\n\n
\/var\/log\/vsandevicemonitord.log
Bu, diskin a\u015f\u0131r\u0131 g\u00fcnl\u00fck t\u0131kan\u0131kl\u0131\u011f\u0131 veya G\/\u00c7 gecikmeleri nedeniyle iyi durumda de\u011fil olarak i\u015faretlenip i\u015faretlenmedi\u011fini belirlemenize yard\u0131mc\u0131 olur.

Example:
 <\/p>\n\n\n\n
INFO vsandevicemonitord WARNING - WRITE Average Latency on VSAN device naa.50000xxxxxxxx has exceeded threshold value 2000000 us 2 times.\nINFO vsandevicemonitord Tier 2 (naa.50000xxxxxxxx) as unhealthy<\/pre>\n\n\n\n
Etkilenen \u00dcr\u00fcnler<\/h4>\n\n\n\n
VMware ESXi 7.x, VMware VSAN<\/p>\n\n\n\n
Kaynak: vSAN Fiziksel Disk Sorun Giderme Rehberi | Dell Turkey<\/a><\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Web kullan\u0131c\u0131 aray\u00fcz\u00fcnden vSAN Fiziksel Disk durumunu kontrol etme: vCenter Server Web \u0130stemcisine ba\u011flan\u0131n […]<\/p>\n","protected":false},"author":1,"featured_media":14726,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[372],"tags":[],"class_list":["post-14785","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/posts\/14785","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/comments?post=14785"}],"version-history":[{"count":1,"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/posts\/14785\/revisions"}],"predecessor-version":[{"id":14786,"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/posts\/14785\/revisions\/14786"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/media\/14726"}],"wp:attachment":[{"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/media?parent=14785"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/categories?post=14785"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sarzimanli.com\/index.php\/wp-json\/wp\/v2\/tags?post=14785"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}