{"id":495321,"date":"2022-09-22T21:00:40","date_gmt":"2022-09-22T18:00:40","guid":{"rendered":"https:\/\/en.buradabiliyorum.com\/how-to-fix-the-linux-boots-into-the-bios-error\/"},"modified":"2022-09-22T21:00:40","modified_gmt":"2022-09-22T18:00:40","slug":"how-to-fix-the-linux-boots-into-the-bios-error","status":"publish","type":"post","link":"https:\/\/buradabiliyorum.com\/en\/how-to-fix-the-linux-boots-into-the-bios-error\/","title":{"rendered":"#How to Fix the Linux Boots Into the BIOS Error"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_84 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-6a2e0712168fa\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #dd3333;color:#dd3333\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #dd3333;color:#dd3333\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-6a2e0712168fa\" checked aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-1'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-fix-the-linux-boots-into-the-bios-error\/#%E2%80%9CHow_to_Fix_the_Linux_Boots_Into_the_BIOS_Error%E2%80%9D\" >&#8220;How to Fix the Linux Boots Into the BIOS Error&#8221;<\/a><ul class='ez-toc-list-level-2' ><li class='ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-fix-the-linux-boots-into-the-bios-error\/#A_Case_Study_GRUB_2_206r322\" >A Case Study: GRUB 2:2.06.r322<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-fix-the-linux-boots-into-the-bios-error\/#The_Technique_Well_Use\" >The Technique We\u2019ll Use<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-fix-the-linux-boots-into-the-bios-error\/#Putting_It_Into_Practice\" >Putting It Into Practice<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-fix-the-linux-boots-into-the-bios-error\/#Repair_or_Replace\" >Repair or Replace<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n<h1><span class=\"ez-toc-section\" id=\"%E2%80%9CHow_to_Fix_the_Linux_Boots_Into_the_BIOS_Error%E2%80%9D\"><\/span>&#8220;How to Fix the Linux Boots Into the BIOS Error&#8221;<span class=\"ez-toc-section-end\"><\/span><\/h1>\n<div>\n<figure style=\"width: 1200px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" class=\"type:primaryImage size-full wp-image-770699\" data-pagespeed-no-defer=\"\" src=\"https:\/\/www.howtogeek.com\/wp-content\/uploads\/2021\/11\/shutterstock_1278851809.png?width=1198&amp;trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"Laptop on a blue background showing a Linux command prompt.\" width=\"1200\" height=\"675\"\/><figcaption class=\"wp-caption-text\"><span class=\"type:primaryImage imagecredit\"><a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.shutterstock.com\/image-vector\/command-line-interface-cli-programming-language-1278851809\">fatmawati achmad zaenuri\/Shutterstock.com<\/a><\/span><\/figcaption><\/figure>\n<p>GRUB updates have been known to result in Linux computers booting into the BIOS or UEFI settings. The fix for this takes advantage of a useful system recovery trick you really ought to know about.<\/p>\n<h2 id=\"grub-22.06.r322\"><span class=\"ez-toc-section\" id=\"A_Case_Study_GRUB_2_206r322\"><\/span>A Case Study: GRUB 2:2.06.r322<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>A system update for Arch and Arch-based Linux distributions in summer 2022 included a new version of\u00a0<a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.gnu.org\/software\/grub\/\">GRUB<\/a>. GRUB stands for\u00a0<strong>gr<\/strong>and\u00a0<strong>u<\/strong>nified\u00a0<strong>b<\/strong>ootloader.<\/p>\n<p>A bootloader is an <a href=\"https:\/\/buradabiliyorum.com\/en\/category\/download-scripts-themes-apps\/\" data-internallinksmanager029f6b8e52c=\"9\" title=\"Download Scripts &amp; Themes &amp; Apps\" target=\"_blank\" rel=\"noopener\">app<\/a>lication that kicks off the boot-up process when your computer is turned on. Several software tools and utilities need to be launched\u2014from the right partition and in the right order\u2014to eventually result in an operational and accessible operating system. GRUB kicks off that cascade of events.<\/p>\n<p>If you have more than one operating system installed on your computer, GRUB provides a menu so that you can select which operating system to use.\u00a0One of the code changes to GRUB 2:2.06.r322 added support for a new GRUB option, <code>--is-supported<\/code>. The option is used to indicate whether a boot to firmware capability is present or not. If it is, GRUB adds an entry to the boot menu to let you boot into your EUFI settings.<\/p>\n<p>The new option\u00a0<a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/git.savannah.gnu.org\/cgit\/grub.git\/tree\/util\/grub.d\/30_uefi-firmware.in?id=26031d3b101648352e4e427f04bf69d320088e77\">was referenced in a script<\/a>\u00a0called \u201c30_uefi-firmware.in.\u201d\u00a0The\u00a0<a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/git.savannah.gnu.org\/cgit\/grub.git\/commit\/util\/grub.d\/30_uefi-firmware.in?id=26031d3b101648352e4e427f04bf69d320088e77\">diff for this file<\/a>\u00a0shows that an <code>if<\/code> statement was removed, and two lines were added.<\/p>\n<p>One of the new lines was a replacement\u00a0<code>if<\/code> statement. The other new line contains <code>fwsetup --is-supported<\/code> . The \u201cfw\u201d in \u201cfwsetup\u201d stands for firmware. But because that line is\u00a0<em>above<\/em>\u00a0the new\u00a0<code>if<\/code> statement, it is always going to run. If it was inside the body of the\u00a0<code>if<\/code> statement it would only run when the test in the <code>if<\/code> statement resolved to true.<\/p>\n<p>This caused problems on many, but not all, UEFI computers. It depended on whether the version of GRUB you already had installed supported this command. Affected machines would do one of two things. They\u2019d either go into a boot-loop where the boot process was never completed but continually restarted, or the computer would boot straight into the UEFI firmware settings. Either way, there was no way to force your computer to boot into Linux.<\/p>\n<p>When you\u2019re faced with situations like this there is always the nuclear option of doing a complete reinstall. That\u2019ll work, but depending on how your hard drive has been partitioned, without a recent backup, you may lose data.<\/p>\n<p>The low-impact method uses <code>chroot<\/code> and a Live USB or Live CD\/DVD. This is a good technique to understand and have up your sleeve for all sorts of system failures when you can\u2019t boot or log in to your Linux computer.<\/p>\n<h2 id=\"the-technique-well-use\"><span class=\"ez-toc-section\" id=\"The_Technique_Well_Use\"><\/span>The Technique We\u2019ll Use<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>In order to use this technique you need to have either a bootable USB or CD\/DVD with a Linux distribution on it, that boots into a live Linux instance. Typically these are called a Live USB or Live CD\/DVD. All the major distributions support this function.<\/p>\n<p>We\u2019re not going to install anything, so the live <a href=\"https:\/\/buradabiliyorum.com\/en\/category\/social-mediaa\/\" data-internallinksmanager029f6b8e52c=\"1\" title=\"Social Media\" target=\"_blank\" rel=\"noopener\">media<\/a> doesn\u2019t have to be the same distribution that you have installed on your computer. You could use an Ubuntu USB to repair an EndeavourOS computer, for example. If you don\u2019t have access to any live media, you\u2019ll need to use another computer to download an image and write it to a USB memory stick or to a CD\/DVD.<\/p>\n<p>When you boot from the live media you\u2019ll be able to mount and access your existing file system. Your installed file system will appear as part of the file system of the Linux that was booted from the live media. That\u2019s great. If we can access it, we have a chance of repairing it. But it does raise an issue.<\/p>\n<p>The root of this hybrid file system is the root of the live media file system, not the root of your installed file system. To make the file paths configured in your Linux system reference their correct target locations\u2014somewhere inside your file system, and not somewhere relative to the root of the live Linux\u2014we need to use <code>chroot<\/code> to set a new root that points to the root of your <em>installed<\/em> file system. In other words, paths that start with \u201c\/\u201d will use the root of your file system as their starting point.<\/p>\n<p>The test computer we used for this uses the <code>ext4<\/code> file system, but you can use this technique on other file systems too. You just have to identify which partitions or volumes you need to mount, and where to mount them. The principles are the same.<\/p>\n<h2 id=\"putting-it-into-practice\"><span class=\"ez-toc-section\" id=\"Putting_It_Into_Practice\"><\/span>Putting It Into Practice<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>We created a bootable USB drive and booted our stricken computer from it. The distribution we used was EndeavourOS. The EndeavourOS live media boots into the <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.xfce.org\/\">XFCE<\/a> 4 desktop environment.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-830575\" data-pagespeed-lazy-src=\"https:\/\/www.howtogeek.com\/wp-content\/uploads\/2022\/09\/1-1.png?trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"The EndeavourOS live media booted into the XFCE desktop environment\" width=\"644\" height=\"362\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p>To identify which partitions hold the root of your file system, and which is the boot partition, open a terminal window and use the <code>fdisk<\/code> command. We\u2019re using the <code>-l<\/code> (list partition) option. You\u2019ll need to use <code>sudo<\/code>, too.<\/p>\n<pre>sudo fdisk -l<\/pre>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-830576\" data-pagespeed-lazy-src=\"https:\/\/www.howtogeek.com\/wp-content\/uploads\/2022\/09\/2-1.png?trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"Using the sudo fdisk -l command to list partitions and devices\" width=\"644\" height=\"55\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p>Scroll through the output until you see entries labeled \u201cEFI System\u201d and \u201cLinux filesystem.\u201d<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-830577\" data-pagespeed-lazy-src=\"https:\/\/www.howtogeek.com\/wp-content\/uploads\/2022\/09\/4-1.png?trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"The output from the sudo fdisk -l command with the boot and root partitions highlighted\" width=\"644\" height=\"370\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p>On this computer, they\u2019re both on the <code>sda<\/code> hard drive. They\u2019re in partitions one and two, as indicated by the partition labels <code>\/dev\/sda1<\/code> and <code>\/dev\/sda2<\/code>.<\/p>\n<p>On your computer, they might be on different hard drives and partitions. Take care to note the partitions they\u2019re on, we\u2019ll need to use these in the next commands.<\/p>\n<p>We need to mount the file systems on these partitions by attaching them to the live file system. The <code>mount<\/code> command will do that for us. Remember, your partition labels are likely to be different, so make sure you use the ones from the results of your <code>fdisk<\/code> command.<\/p>\n<pre>sudo mount \/dev\/sda2 \/mnt<\/pre>\n<pre>sudo mount \/dev\/sda1 \/mnt\/boot\/efi<\/pre>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-830578\" data-pagespeed-lazy-src=\"https:\/\/www.howtogeek.com\/wp-content\/uploads\/2022\/09\/5.png?trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"Mounting the boot and file system root file systems\" width=\"644\" height=\"95\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p>To make the effective root of the file system start at the root of your actual, installed file system, we\u2019ll use <code>chroot<\/code> to set the root to be the \u201c\/mnt\u201d mount point. This is where the root of your installed file system is grafted onto the live file system.<\/p>\n<pre>sudo chroot \/mnt<\/pre>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-830579\" data-pagespeed-lazy-src=\"https:\/\/www.howtogeek.com\/wp-content\/uploads\/2022\/09\/6.png?trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"Using the chroot command to create a new effective root\" width=\"644\" height=\"75\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p>Note that the command prompt changes to show you are now effectively logged in as root, and you are at the root directory \u201c\/\u201dof the file system of your computer.<\/p>\n<p>We can easily test this, by changing into the \u201c\/home\u201d directory and checking what directories exist inside it.<\/p>\n<pre>cd \/home<\/pre>\n<pre>ls<\/pre>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-830580\" data-pagespeed-lazy-src=\"https:\/\/www.howtogeek.com\/wp-content\/uploads\/2022\/09\/8.png?trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"Using ls to list user accounts\" width=\"644\" height=\"110\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p>You should see a directory for each user configured on your computer, including one for your own user account. This computer has a single user, called \u201cdave.\u201d If we\u2019d used <code>cd \/home<\/code> before we used the <code>chroot<\/code> command, we\u2019d have entered the \u201c\/home\u201d directory of the live file system.<\/p>\n<p>Just to be clear, you\u2019re now accessing\u00a0<strong>your real file system<\/strong>\u00a0as the\u00a0<strong>root<\/strong>\u00a0user, so be careful.<\/p>\n<p>To fix the issue with GRUB 2:2.06.r322, all we needed to do was run the <code>grub-install<\/code> command.<\/p>\n<pre>grub-install<\/pre>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-830581\" data-pagespeed-lazy-src=\"https:\/\/www.howtogeek.com\/wp-content\/uploads\/2022\/09\/7.png?trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"Running the grub-install command to fix the GRUB boot to BIOS error\" width=\"644\" height=\"55\" src=\"\/pagespeed_static\/1.JiBnMqyl6S.gif\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p>Running <code>grub-install<\/code> blindly like this isn\u2019t usually recommended. In this instance, it is what was required.<\/p>\n<h2 id=\"repair-or-replace\"><span class=\"ez-toc-section\" id=\"Repair_or_Replace\"><\/span>Repair or Replace<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>If you\u2019re trying to fix a different problem, you\u2019ll need to check the forums for your distribution for the appropriate fix for your issue. If it is a widespread complaint, you\u2019ll soon find a resolution for it.<\/p>\n<p>At the very least, now that you can access your file system, you\u2019re able to copy your data to some removable media. If you decide to do a full reinstall, you won\u2019t lose data.<\/p>\n<p><strong>RELATED:<\/strong> <strong><em>How to Copy Files Using the &#8220;install&#8221; Command on Linux<\/em><\/strong><\/p>\n<\/div>\n<p><script>\n setTimeout(function(){\n  !function(f,b,e,v,n,t,s)\n  {if(f.fbq)return;n=f.fbq=function(){n.callMethod?\n  n.callMethod.apply(n,arguments):n.queue.push(arguments)};\n  if(!f._fbq)f._fbq=n;n.push=n;n.loaded=!0;n.version='2.0';\n  n.queue=[];t=b.createElement(e);t.async=!0;\n  t.src=v;s=b.getElementsByTagName(e)[0];\n  s.parentNode.insertBefore(t,s) } (window, document,'script',\n  'https:\/\/connect.facebook.net\/en_US\/fbevents.js');\n   fbq('init', '335401813750447');\n   fbq('track', 'PageView');\n  },3000);\n<\/script><\/p>\n<blockquote><p><strong><span style=\"color: #ff6600;\">If you liked the article, do not forget to share it with your friends. Follow us on\u00a0<span style=\"color: #ff0000;\"><a style=\"color: #ff0000;\" href=\"https:\/\/news.google.com\/publications\/CAAqBwgKMLG0nwswvr63Aw\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Google News<\/a><\/span>\u00a0too, click on the star and choose us from your favorites.<\/span><\/strong><\/p><\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\">For forums sites go to <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/forum.buradabiliyorum.com\/\" target=\"_blank\" rel=\"noopener\">Forum.BuradaBiliyorum.Com<\/a><\/span><\/strong><\/p>\n<\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\"><strong>If you want to read more like this article, you can visit our <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/en.buradabiliyorum.com\/technology\/\" target=\"_blank\" rel=\"noopener\">Technology category.<\/a><\/span><\/strong><\/p>\n<\/blockquote>\n<p><span style=\"color: black;\"><a style=\"color: #ff9900;\" href=\"https:\/\/www.howtogeek.com\/830574\/how-to-fix-the-linux-boots-into-the-bios-error\/\" target=\"_blank\" rel=\"noopener\">Source<\/a><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;How to Fix the Linux Boots Into the BIOS Error&#8221; fatmawati achmad zaenuri\/Shutterstock.com GRUB updates have been known to result in Linux computers booting into the BIOS or UEFI settings. The fix for this takes advantage of a useful system recovery trick you really ought to know about. A Case Study: GRUB 2:2.06.r322 A system&#8230;<\/p>\n","protected":false},"author":1,"featured_media":495322,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/www.howtogeek.com\/wp-content\/uploads\/2021\/11\/shutterstock_1278851809.png?height=200p&trim=2,2,2,2","fifu_image_alt":"","footnotes":""},"categories":[18],"tags":[],"class_list":["post-495321","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/495321","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/comments?post=495321"}],"version-history":[{"count":0,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/495321\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media\/495322"}],"wp:attachment":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media?parent=495321"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/categories?post=495321"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/tags?post=495321"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}