{"id":4583,"date":"2026-08-26T15:46:07","date_gmt":"2026-08-26T12:46:07","guid":{"rendered":"https:\/\/www.ozgurguler.net\/blog\/?p=4583"},"modified":"2026-08-26T15:53:04","modified_gmt":"2026-08-26T12:53:04","slug":"m-2-nvme-disklerde-sql-server-kurulum-hatasi-ve-cozumu","status":"publish","type":"post","link":"https:\/\/www.ozgurguler.net\/blog\/m-2-nvme-disklerde-sql-server-kurulum-hatasi-ve-cozumu\/","title":{"rendered":"M.2 NVMe Disklerde SQL Server Kurulum Hatas\u0131 ve \u00c7\u00f6z\u00fcm\u00fc"},"content":{"rendered":"

M.2 \/ NVMe Disklerde SQL Server Kurulum Hatas\u0131: 4 KB \u00dczeri Fiziksel Sekt\u00f6r Boyutu Sorunu ve \u00c7\u00f6z\u00fcm\u00fc<\/strong><\/p>\n

Son d\u00f6nemde \u00f6zellikle yeni nesil M.2 NVMe SSD kullan\u0131lan bilgisayarlarda SQL Server kurulumu s\u0131ras\u0131nda daha \u00f6nce al\u0131\u015f\u0131k olmad\u0131\u011f\u0131m\u0131z baz\u0131 hatalarla kar\u015f\u0131la\u015f\u0131labiliyor.<\/p>\n

Kurulum i\u015flemi normal \u015fekilde ilerliyor gibi g\u00f6r\u00fcnmesine ra\u011fmen Database Engine kurulumu ba\u015far\u0131s\u0131z olabiliyor,
\nSQL Server servisi ba\u015flat\u0131lamayabiliyor veya kurulum s\u0131ras\u0131nda<\/p>\n

** Wait on the Database Engine recovery handle failed **<\/strong> benzeri hatalar al\u0131nabiliyor.<\/p>\n

Bu problemlerin nedeni her zaman SQL Server kurulumu, Windows veya SQL Server s\u00fcr\u00fcm\u00fc olmayabilir.<\/p>\n

Baz\u0131 yeni NVMe depolama cihazlar\u0131nda Windows, fiziksel sekt\u00f6r boyutunu **4 KB’dan daha b\u00fcy\u00fck** olarak raporlayabiliyor.
\nSQL Server ise fiziksel sekt\u00f6r boyutu a\u00e7\u0131s\u0131ndan **512 byte ve 4096 byte (4 KB)** de\u011ferlerini destekliyor.
\n4 KB’dan b\u00fcy\u00fck fiziksel sekt\u00f6r boyutlar\u0131 desteklenmedi\u011fi i\u00e7in SQL Server kurulumu veya Database Engine’in ba\u015flat\u0131lmas\u0131 ba\u015far\u0131s\u0131z olabiliyor.<\/p>\n

Sorunun temel nedeni nedir?<\/p>\n

Disklerde sekt\u00f6r boyutu, i\u015fletim sisteminin ve uygulamalar\u0131n disk \u00fczerindeki fiziksel depolama birimleriyle nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 belirleyen \u00f6nemli bir de\u011ferdir.<\/p>\n

Geleneksel disklerde ve eski SSD\/NVMe yap\u0131land\u0131rmalar\u0131nda genellikle 512 byte veya 4096 byte de\u011ferleriyle kar\u015f\u0131la\u015f\u0131l\u0131r.<\/p>\n

Ancak yeni nesil baz\u0131 NVMe cihazlar\u0131nda, \u00f6zellikle Windows 11’in modern NVMe s\u00fcr\u00fcc\u00fcs\u00fcyle birlikte,
\ni\u015fletim sistemine **8192 byte veya 16384 byte gibi daha b\u00fcy\u00fck fiziksel sekt\u00f6r boyutlar\u0131** bildirilebilmektedir.<\/p>\n

Bu durum SQL Server a\u00e7\u0131s\u0131ndan \u00f6nemlidir.<\/p>\n

\u00c7\u00fcnk\u00fc SQL Server’\u0131n mevcut destek s\u0131n\u0131r\u0131 **4 KB’d\u0131r**.<\/strong>
\nYani disk Windows taraf\u0131ndan 8192 veya 16384 byte fiziksel sekt\u00f6r boyutuyla sunuluyorsa SQL Server bu diski desteklenen bir sekt\u00f6r yap\u0131s\u0131 olarak de\u011ferlendiremez.<\/p>\n

Bu nedenle problem do\u011frudan “M.2 disk SQL Server desteklemiyor” \u015feklinde de\u011ferlendirilmemelidir.<\/p>\n

As\u0131l problem: NVMe diskin Windows’a sundu\u011fu fiziksel sekt\u00f6r boyutunun SQL Server’\u0131n destekledi\u011fi de\u011ferden b\u00fcy\u00fck olmas\u0131d\u0131r.<\/strong><\/p>\n

\u00d6ncelikle disk sekt\u00f6r boyutunu kontrol edin<\/p>\n

SQL Server kurulumuna ba\u015flamadan \u00f6nce, SQL Server’\u0131n kurulaca\u011f\u0131 veya veritaban\u0131 dosyalar\u0131n\u0131n tutulaca\u011f\u0131 diskin sekt\u00f6r boyutunu kontrol etmek faydal\u0131d\u0131r.<\/p>\n

Y\u00f6netici olarak **PowerShell** veya **Komut \u0130stemi** a\u00e7arak a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131rabilirsiniz:<\/p>\n

powershell<\/p>\n

fsutil fsinfo sectorinfo C:<\/p><\/blockquote>\n

Buradaki ‘C:’ \u00f6rnektir.<\/p>\n

SQL Server’\u0131 hangi s\u00fcr\u00fcc\u00fcye kuracaksan\u0131z veya SQL Server veri\/log dosyalar\u0131n\u0131 hangi s\u00fcr\u00fcc\u00fcde tutacaksan\u0131z ilgili s\u00fcr\u00fcc\u00fc harfini kullanmal\u0131s\u0131n\u0131z.<\/p>\n

\u00d6rne\u011fin: fsutil fsinfo sectorinfo D:<\/p>\n

veya: fsutil fsinfo sectorinfo E:<\/p>\n

Komut sonucunda \u00f6zellikle \u015fu iki de\u011fere bak\u0131lmal\u0131d\u0131r:<\/p>\n

PhysicalBytesPerSectorForAtomicity
\nPhysicalBytesPerSectorForPerformance<\/p><\/blockquote>\n

Microsoft’un \u00f6nerisine g\u00f6re bu iki de\u011fer ayn\u0131 de\u011filse **b\u00fcy\u00fck olan de\u011fer**,
\ndiskin sekt\u00f6r boyutunu de\u011ferlendirirken dikkate al\u0131nmal\u0131d\u0131r. ‘4096’ de\u011feri 4 KB sekt\u00f6r boyutunu ifade eder.<\/p>\n

\u00d6rne\u011fin:
\n——–
\nPhysicalBytesPerSectorForAtomicity : 4096
\nPhysicalBytesPerSectorForPerformance : 4096<\/p>\n

Bu durumda disk SQL Server a\u00e7\u0131s\u0131ndan desteklenen 4 KB sekt\u00f6r yap\u0131s\u0131ndad\u0131r.<\/p>\n

Ancak:
\nPhysicalBytesPerSectorForAtomicity : 16384
\nPhysicalBytesPerSectorForPerformance : 16384<\/p>\n

gibi bir sonu\u00e7 al\u0131n\u0131yorsa, fiziksel sekt\u00f6r boyutu SQL Server’\u0131n destekledi\u011fi s\u0131n\u0131r\u0131n \u00fczerindedir.<\/p>\n

Hangi sekt\u00f6r boyutlar\u0131 destekleniyor?<\/strong><\/p>\n

Burada \u00f6nemli bir ayr\u0131nt\u0131y\u0131 \u00f6zellikle belirtmek gerekiyor.<\/p>\n

SQL Server s\u00fcr\u00fcm\u00fcn\u00fcn 2019, 2022 veya 2025 olmas\u0131 bu s\u0131n\u0131r\u0131 8 KB veya 16 KB’a \u00e7\u0131karm\u0131yor.<\/p>\n

G\u00fcncel Microsoft dok\u00fcmantasyonuna g\u00f6re yay\u0131mlanm\u0131\u015f SQL Server s\u00fcr\u00fcmlerinde desteklenen fiziksel sekt\u00f6r boyutlar\u0131:<\/p>\n

**512 byte**
\n**4096 byte (4 KB)**<\/p>\n

4 KB’dan b\u00fcy\u00fck sekt\u00f6r boyutlar\u0131 i\u00e7in yay\u0131mlanm\u0131\u015f bir SQL Server s\u00fcr\u00fcm\u00fcnde destek bulunmuyor.<\/p>\n

Dolay\u0131s\u0131yla a\u015fa\u011f\u0131daki gibi bir disk: 8192 byte veya: 16384 byte
\nraporluyorsa, SQL Server’\u0131n bunu do\u011fal olarak desteklemesi beklenmemelidir.<\/p>\n

Bu ayr\u0131m \u00f6nemlidir. \u00c7\u00fcnk\u00fc baz\u0131 sistemlerde g\u00f6r\u00fclen 8192 veya 16384 de\u011ferleri, “SQL Server art\u0131k 8 KB\/16 KB sekt\u00f6r destekliyor” anlam\u0131na gelmez.<\/p>\n

\u00c7\u00f6z\u00fcm 1:<\/strong>\u00a0 SQL Server dosyalar\u0131n\u0131 desteklenen ba\u015fka bir diske ta\u015f\u0131mak<\/p>\n

E\u011fer sistemde sekt\u00f6r boyutu 512 veya 4096 byte olan ba\u015fka bir disk mevcutsa, en temiz \u00e7\u00f6z\u00fcmlerden biri SQL Server dosyalar\u0131n\u0131 bu diskte tutmakt\u0131r.<\/p>\n

\u00d6zellikle birden fazla fiziksel disk bulunan sistemlerde \u00f6nce:<\/p>\n

fsutil fsinfo sectorinfo C:
\nfsutil fsinfo sectorinfo D:
\nfsutil fsinfo sectorinfo E:<\/p>\n

gibi kontroller yap\u0131larak uygun disk belirlenebilir.<\/p>\n

SQL Server’\u0131n kullanaca\u011f\u0131 veri ve log dosyalar\u0131n\u0131n desteklenen sekt\u00f6r boyutuna sahip bir volume \u00fczerinde bulunmas\u0131 sa\u011flanabilir.<\/p>\n

Bu y\u00f6ntem m\u00fcmk\u00fcnse tercih edilebilecek en sade \u00e7\u00f6z\u00fcmlerden biridir.<\/p>\n

\u00c7\u00f6z\u00fcm 2:<\/strong>\u00a0 NVMe sekt\u00f6r boyutunu Windows taraf\u0131nda 4 KB olarak em\u00fcle etmek<\/p>\n

E\u011fer SQL Server’\u0131n mutlaka sekt\u00f6r boyutu 4 KB’dan b\u00fcy\u00fck olarak raporlanan NVMe\/M.2 disk \u00fczerine kurulmas\u0131 gerekiyorsa,
\nWindows taraf\u0131nda sekt\u00f6r boyutunun 4 KB olarak em\u00fcle edilmesi m\u00fcmk\u00fcnd\u00fcr.<\/p>\n

Microsoft, modern NVMe depolama platformlar\u0131nda bu ama\u00e7la:
\n* ForcedPhysicalSectorSizeInBytes
\nregistry de\u011ferinin kullan\u0131lmas\u0131n\u0131 \u00f6neriyor. Bu ayar, Windows’un ilgili NVMe s\u00fcr\u00fcc\u00fcs\u00fc \u00fczerinden sekt\u00f6r boyutunu **4 KB olarak em\u00fcle etmesini** sa\u011flar.<\/p>\n

PowerShell ile ayar\u0131n olu\u015fturulmas\u0131<\/p>\n

Y\u00f6netici yetkisiyle PowerShell a\u00e7\u0131larak a\u015fa\u011f\u0131daki komut \u00e7al\u0131\u015ft\u0131r\u0131labilir:<\/p>\n

New-ItemProperty
\n-Path “HKLM:\\SYSTEM\\CurrentControlSet\\Services\\stornvme\\Parameters\\Device”
\n-Name “ForcedPhysicalSectorSizeInBytes”
\n-PropertyType MultiString
\n-Force -Value “* 4095”<\/p><\/blockquote>\n

 <\/p>\n

Buradaki ‘4095’ de\u011ferini ilk bak\u0131\u015fta g\u00f6rmek biraz \u015fa\u015f\u0131rt\u0131c\u0131 olabilir.<\/p>\n

Bu de\u011fer do\u011frudan “4095 byte sekt\u00f6r kullan” anlam\u0131na gelmez. <\/strong>
\nMicrosoft’un \u00f6nerdi\u011fi registry yap\u0131land\u0131rmas\u0131, Windows NVMe s\u00fcr\u00fcc\u00fcs\u00fcn\u00fcn sekt\u00f6r boyutunu **4 KB olarak em\u00fcle etmesini** sa\u011flamak i\u00e7in * 4095 de\u011ferini kullan\u0131r.<\/strong><\/p>\n

* \u0130\u015flem sonras\u0131nda bilgisayar yeniden ba\u015flat\u0131lmal\u0131d\u0131r<\/strong><\/p>\n

Registry de\u011fi\u015fikli\u011finin uygulanabilmesi i\u00e7in bilgisayar\u0131n yeniden ba\u015flat\u0131lmas\u0131 gerekir.<\/p>\n

Yeniden ba\u015flatma sonras\u0131nda sekt\u00f6r boyutunu tekrar kontrol etmek \u00f6nemlidir:<\/p>\n

fsutil fsinfo sectorinfo C:<\/p>\n

\u00d6rne\u011fin i\u015flem \u00f6ncesinde:
\nPhysicalBytesPerSectorForAtomicity : 16384
\nPhysicalBytesPerSectorForPerformance : 16384<\/p>\n

olarak g\u00f6r\u00fclen de\u011ferlerin i\u015flem sonras\u0131nda SQL Server a\u00e7\u0131s\u0131ndan desteklenen: 4096 – 4095
\nseviyesine gelmesi beklenir.<\/p>\n

Bu kontrol yap\u0131lmadan do\u011frudan SQL Server kurulumuna ge\u00e7mek yerine, \u00f6nce Windows’un yeni sekt\u00f6r de\u011ferini do\u011fru \u015fekilde g\u00f6rd\u00fc\u011f\u00fcnden emin olmak daha sa\u011fl\u0131kl\u0131 olacakt\u0131r.<\/p>\n

* SQL Server kurulumu sonras\u0131nda da kontrol edilmeli<\/p>\n

Kurulum tamamland\u0131ktan sonra problem tamamen \u00e7\u00f6z\u00fclm\u00fc\u015f kabul edilmeden SQL Server’\u0131n \u00e7al\u0131\u015fmas\u0131 kontrol edilmelidir.<\/p>\n

\u00d6zellikle a\u015fa\u011f\u0131daki durumlar incelenebilir:<\/p>\n

* SQL Server Database Engine servisinin ba\u015flat\u0131lmas\u0131
\n* SQL Server ERRORLOG
\n* SQL Server Setup Summary.txt
\n* Database Engine recovery handle hatalar\u0131
\n* 5178 \/ 5179 sekt\u00f6r boyutu hatalar\u0131
\n* “misaligned log IOs” uyar\u0131lar\u0131<\/p>\n

Microsoft, 4 KB’dan b\u00fcy\u00fck sekt\u00f6r boyutuyla ili\u015fkili problemlerde yaln\u0131zca kurulum hatas\u0131n\u0131n de\u011fil, SQL Server’\u0131n ba\u015flat\u0131lmas\u0131 s\u0131ras\u0131nda ortaya \u00e7\u0131kan hatalar\u0131n da g\u00f6r\u00fclebilece\u011fini belirtiyor.<\/p>\n

\u00d6rne\u011fin kar\u015f\u0131la\u015f\u0131labilecek hatalardan biri:<\/p>\n

Error: 5179, Severity: 16, State: 1.
\nCannot use file ‘data file path’, because it is on a volume with sector size 8192.
\nSQL Server supports a maximum sector size of 4096 bytes.<\/p>\n

\u015feklindedir.<\/p>\n

\u00d6nemli uyar\u0131<\/strong><\/p>\n

‘ForcedPhysicalSectorSizeInBytes’ registry ayar\u0131, diskin fiziksel yap\u0131s\u0131n\u0131 de\u011fi\u015ftirmez.<\/p>\n

Burada yap\u0131lan i\u015flem:<\/p>\n

**NVMe diskin fiziksel sekt\u00f6r boyutunu ger\u00e7ekten 4 KB’a d\u00f6n\u00fc\u015ft\u00fcrmek de\u011fil,
\nWindows’un depolama katman\u0131nda 4 KB sekt\u00f6r boyutunu em\u00fcle etmesini sa\u011flamakt\u0131r.<\/p>\n

Bu nedenle bu i\u015flemi “diski 4 KB’a \u00e7evirmek” \u015feklinde ifade etmek teknik olarak do\u011fru de\u011fildir.<\/p>\n

Ayr\u0131ca Windows Registry \u00fczerinde yap\u0131lan de\u011fi\u015fiklikler sistem davran\u0131\u015f\u0131n\u0131 etkileyebilece\u011finden,
\ni\u015flem \u00f6ncesinde registry yede\u011finin al\u0131nmas\u0131 ve Microsoft’un \u00f6nerdi\u011fi yap\u0131land\u0131rman\u0131n aynen uygulanmas\u0131 gerekir.
\nMicrosoft da bu konuda \u00f6zellikle uyar\u0131da bulunmaktad\u0131r.<\/p>\n

K\u0131saca \u00e7\u00f6z\u00fcm ad\u0131mlar\u0131<\/strong><\/p>\n

Sorun ya\u015fand\u0131\u011f\u0131nda uygulanabilecek i\u015flem s\u0131ras\u0131 \u015f\u00f6yledir:<\/p>\n

1. SQL Server’\u0131n kurulaca\u011f\u0131 diski belirleyin
\n2. Fiziksel sekt\u00f6r boyutunu kontrol edin<\/p>\n

fsutil fsinfo sectorinfo C:<\/p>\n

3. \u015eu iki de\u011feri kontrol edin
\nPhysicalBytesPerSectorForAtomicity
\nPhysicalBytesPerSectorForPerformance<\/p>\n

\u0130ki de\u011fer farkl\u0131ysa b\u00fcy\u00fck olan\u0131 dikkate al\u0131n.<\/p>\n

4. De\u011fer 4096 veya daha k\u00fc\u00e7\u00fckse<\/p>\n

Disk sekt\u00f6r boyutu a\u00e7\u0131s\u0131ndan SQL Server i\u00e7in problem bulunmamaktad\u0131r.<\/p>\n

5. De\u011fer 4096’dan b\u00fcy\u00fckse<\/p>\n

M\u00fcmk\u00fcnse SQL Server dosyalar\u0131n\u0131 sekt\u00f6r boyutu 512 veya 4096 byte olan ba\u015fka bir diske ta\u015f\u0131y\u0131n.<\/p>\n

6. Diskin de\u011fi\u015ftirilmesi m\u00fcmk\u00fcn de\u011filse<\/p>\n

Y\u00f6netici PowerShell ile:<\/strong><\/p>\n

New-ItemProperty <\/strong>
\n-Path “HKLM:\\SYSTEM\\CurrentControlSet\\Services\\stornvme\\Parameters\\Device” <\/strong>
\n-Name “ForcedPhysicalSectorSizeInBytes” <\/strong>
\n-PropertyType MultiString <\/strong>
\n-Force <\/strong>
\n-Value “* 4095”<\/strong><\/p>\n

komutunu \u00e7al\u0131\u015ft\u0131r\u0131n.<\/p>\n

7. Bilgisayar\u0131 yeniden ba\u015flat\u0131n
\n8. Sekt\u00f6r boyutunu tekrar kontrol edin
\nfsutil fsinfo sectorinfo C:<\/p>\n

9. De\u011ferin 4096 byte seviyesinde oldu\u011funu do\u011frulay\u0131n<\/p>\n

10. SQL Server kurulumunu tekrar \u00e7al\u0131\u015ft\u0131r\u0131n<\/p>\n

Sonu\u00e7<\/strong><\/p>\n

Yeni nesil M.2\/NVMe SSD’lerde SQL Server kurulumu s\u0131ras\u0131nda kar\u015f\u0131la\u015f\u0131lan baz\u0131 hatalar\u0131n nedeni do\u011frudan SQL Server kurulum paketinin bozuk olmas\u0131 veya SQL Server s\u00fcr\u00fcm\u00fcn\u00fcn Windows ile uyumsuz olmas\u0131 olmayabilir.<\/p>\n

\u00d6zellikle yeni Windows\/NVMe yap\u0131land\u0131rmalar\u0131nda **fiziksel sekt\u00f6r boyutunun 4 KB’dan b\u00fcy\u00fck olarak raporlanmas\u0131**,
\nSQL Server’\u0131n kurulmas\u0131n\u0131 veya Database Engine’in ba\u015flat\u0131lmas\u0131n\u0131 engelleyebilir.<\/p>\n

Bu nedenle SQL Server kurulumu ba\u015far\u0131s\u0131z oldu\u011funda yaln\u0131zca SQL Server Setup loglar\u0131na bakmak yerine, kurulumun yap\u0131laca\u011f\u0131 diskin fiziksel sekt\u00f6r boyutunu da kontrol etmek gerekir.<\/p>\n

\u0130lk kontrol i\u00e7in:<\/p>\n

fsutil fsinfo sectorinfo C:<\/p>\n

komutu \u00e7o\u011fu durumda problemin kayna\u011f\u0131n\u0131 ortaya \u00e7\u0131karmak i\u00e7in yeterlidir.<\/p>\n

E\u011fer fiziksel sekt\u00f6r boyutu 4 KB’dan b\u00fcy\u00fckse, m\u00fcmk\u00fcn olan en temiz \u00e7\u00f6z\u00fcm desteklenen sekt\u00f6r boyutuna sahip bir volume kullanmakt\u0131r.<\/p>\n

Bunun m\u00fcmk\u00fcn olmad\u0131\u011f\u0131 modern NVMe sistemlerinde ise Microsoft taraf\u0131ndan \u00f6nerilen ‘ForcedPhysicalSectorSizeInBytes’
\nyap\u0131land\u0131rmas\u0131yla Windows taraf\u0131nda 4 KB sekt\u00f6r em\u00fclasyonu uygulanabilir.<\/p>\n

\u00d6zetle:<\/strong> M.2\/NVMe disk SQL Server ile uyumsuz olmak zorunda de\u011fildir;
\nancak Windows’un diski SQL Server’\u0131n destekledi\u011finden daha b\u00fcy\u00fck bir fiziksel sekt\u00f6r boyutuyla sunmas\u0131 kurulum ve \u00e7al\u0131\u015fma sorunlar\u0131na neden olabilir.<\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

M.2 \/ NVMe Disklerde SQL Server Kurulum Hatas\u0131: 4 KB \u00dczeri Fiziksel Sekt\u00f6r Boyutu Sorunu ve \u00c7\u00f6z\u00fcm\u00fc Son d\u00f6nemde \u00f6zellikle yeni nesil M.2 NVMe SSD kullan\u0131lan bilgisayarlarda SQL Server kurulumu s\u0131ras\u0131nda daha \u00f6nce al\u0131\u015f\u0131k olmad\u0131\u011f\u0131m\u0131z baz\u0131 hatalarla kar\u015f\u0131la\u015f\u0131labiliyor. Kurulum i\u015flemi normal \u015fekilde ilerliyor gibi g\u00f6r\u00fcnmesine ra\u011fmen Database Engine kurulumu ba\u015far\u0131s\u0131z olabiliyor, SQL Server servisi ba\u015flat\u0131lamayabiliyor […]<\/p>\n","protected":false},"author":4,"featured_media":4105,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[28,13,15],"tags":[269,266,270,271,267,88,268],"class_list":["post-4583","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-genelbilgi","category-microsoft","category-teknoloji-haberleri","tag-fsutil","tag-m-2-nvme-disklerde-sql-server-kurulum-hatasi","tag-physicalbytespersectorforatomicity","tag-physicalbytespersectorforperformance","tag-sektor-boyutu-sorunu","tag-sql","tag-wait-on-the-database-engine-recovery-handle-failed"],"_links":{"self":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/4583","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/comments?post=4583"}],"version-history":[{"count":2,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/4583\/revisions"}],"predecessor-version":[{"id":4585,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/posts\/4583\/revisions\/4585"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/media\/4105"}],"wp:attachment":[{"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/media?parent=4583"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/categories?post=4583"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ozgurguler.net\/blog\/wp-json\/wp\/v2\/tags?post=4583"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}