{"id":418011,"date":"2024-06-30T01:54:43","date_gmt":"2024-06-30T01:54:43","guid":{"rendered":"http:\/\/savepearlharbor.com\/?p=418011"},"modified":"-0001-11-30T00:00:00","modified_gmt":"2024-06-30T01:54:43","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=418011","title":{"rendered":"<span>How to Recover Data from RAID 5, 1, 0 on Linux<\/span>"},"content":{"rendered":"<div><!--[--><!--]--><\/div>\n<div id=\"post-content-body\">\n<div>\n<div class=\"article-formatted-body article-formatted-body article-formatted-body_version-1\">\n<div xmlns=\"http:\/\/www.w3.org\/1999\/xhtml\">In this article, you will find a detailed tutorial on data recovery from RAID 0, 1 or 5. The array we have been testing was built on Linux, and the methods described here will help you recover your files even if one or several disks break down.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/how-to-recover-hardware-raid-on-operating-system-linux.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/how-to-recover-hardware-raid-on-operating-system-linux.png\"\/><br \/>  <a name=\"habracut\"><\/a><br \/>  A Linux-based hardware RAID is hardly a good example of a reliable storage system \u2013 if one of the disks within the array gets disconnected, the whole RAID can\u2019t be mounted, and all the information becomes inaccessible in a second. In this case, you will need a special utility to rebuild the array with the remaining (healthy) drives. It will find and display the data which is still there, and restore this information.<\/p>\n<p>  We will perform all the tests with <a href=\"https:\/\/hetmanrecovery.com\/raid-data-recovery-software\">Hetman RAID Recovery<\/a>. Its main purpose is to search and restore information from inoperable drives which used to be a part of the disk array. The program will identify automatically which controller, motherboard or software tool were used to build the array, and will rebuild the RAID with the remaining disks which are still in good condition. The final step is to find all the data you need and save it to healthy drives.<\/p>\n<p>  At the moment, there is no version of Hetman RAID Recovery for Linux, but running the utility on this specific operating system is still possible.<\/p>\n<div class=\"oembed\">\n<div class=\"tm-iframe_temp\" data-src=\"https:\/\/embedd.srv.habr.com\/iframe\/605259468a93442df67822b3\" data-style=\"\" id=\"605259468a93442df67822b3\" width=\"\"><\/div>\n<\/div>\n<p>  To recover information from a damaged Linux-based RAID, connect the hard disks to a Windows computer. If you don\u2019t have access to such a computer, you can install a Windows virtual machine or install this operating system along with Linux.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/virtual-machine.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/virtual-machine.png\"\/><\/p>\n<h2>How to recover data from a RAID 1 system<\/h2>\n<p>  First of all, let\u2019s explore the recovery procedure for a RAID 1 device built on Linux and consisting of two hard disks of the same model.<\/p>\n<p>  This RAID type can use an even number of drives (at least two) which are used for \u201dmirroring\u201d all the data.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-1.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-1.png\"\/><\/p>\n<p>  This disk array type is one of the most popular. It is characterized by high resilience: if one of the drives fails, you can replace it with the \u201dmirrored\u201d copy, and then add another (new) drive, and the entire storage system will work again as if nothing happened. However, when only one HDD broke down, we couldn\u2019t mount it properly in Linux. It is still available in the disk utility, but there is no button to mount it, and the automount feature can\u2019t be enabled too.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-1-02.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-1-02.png\"\/><\/p>\n<p>  Hetman RAID Recovery managed to identify all properties at once, built and displayed the disk array automatically.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery.png\"\/><\/p>\n<p>  To start the scan in the Drive Manager, right-click on the device icon and open it.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-02.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-02.png\"\/><\/p>\n<p>  Run the Fast scan first.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-03.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-03.png\"\/><\/p>\n<p>  When the scan is over, the program will display the results in the right side of the window. It finds all data which is still on the disk without effort, and the contents can be previewed.<\/p>\n<p>  Select the files you want to restore and click Recovery.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-04.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-04.png\"\/><\/p>\n<p>  Choose where to save them, then click \u201dNext\u201d and hit \u201dRecovery\u201d again.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-05.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-05.png\"\/><\/p>\n<p>  Wait until the system recovery process is complete and click \u201dFinish\u201d.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-06.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-06.png\"\/><\/p>\n<p>  When the process is over, you will find the recovered files in the folder you have chosen.<\/p>\n<p>  A hardware Linux-based RAID 1 is designed in such a way that it writes service information on this array type to all of its disks (this information includes the number of disks, their serial numbers, and where each disk begins). That is why if one of the disks is missing, the program reads this data from other disks and adds the data on the missing disk when rebuilding a damaged RAID.<\/p>\n<p>  In some cases, this information can be damaged, and while building the array the utility can\u2019t understand where the data on a certain disk is located, and what kind of offset is used for a specific disk. If that\u2019s the case, the utility won\u2019t find any data after the scan. In order to find the information which is still on the disk, you\u2019ll have to use a special tool known as RAID Constructor.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-07.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-07.png\"\/><\/p>\n<p>  In addition to all the properties, you have to specify the offset by which you can locate the beginning of the disk.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-08.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-08.png\"\/><\/p>\n<p>  Every file system has specific signatures which help us to identify its beginning. When you specify this offset you\u2019ll be able to rebuild the damaged RAID and extract data from there.<\/p>\n<p>  To find the offset, use the HEX-editor: right-click on the disk and open HEX, or press the key shortcut \u201dCtrl+H\u201d.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-09.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-09.png\"\/><\/p>\n<p>  In Linux, you can find the beginning of the disk by the field with the name like \u201d\/media\/lin\/\u201d, \u2013 where lin stands for the user\u2019s account name.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-10.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-10.png\"\/><\/p>\n<p>  As we know, information about the beginning of the disk in this file system is written to the second sector from the beginning, so we need to go two sectors up. After that, use a calculator to convert the HEX value into the decimal system.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-11.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-11.png\"\/><\/p>\n<p>  In the calculator, open the programmer mode, select HEX and enter the value (8200000). Immediately, you get the value in the decimal system (136 314 880).<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/calculator.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/calculator.png\"\/><\/p>\n<p>  Now that we know the offset, specify it in the Constructor.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-12.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-12.png\"\/><\/p>\n<p>  Now you should add the device, scan it and recover the found information.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-13.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-13.png\"\/><\/p>\n<p>  Recovering files from RAID 5<br \/>  In the next example, we\u2019ll explore the recovery procedure for RAID 5 arrays.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-5.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-5.png\"\/><\/p>\n<p>  RAID-5 is a hard disk array with redundancy and striping, but without a separate parity drive.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-5-02.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-5-02.png\"\/><\/p>\n<p>  It is designed to remain operable even if one of the disks fails. However, in practice it becomes impossible to mount RAID in Linux, when one disk breaks down. Therefore, you can\u2019t copy any data from there. In order to restore the information, you need to connect a new disk or use additional software.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/linux.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/linux.png\"\/><\/p>\n<p>  RAID 5 consists of 5 HDDs one of which is damaged. Connect the remaining hard disks to a Windows computer, or add them to a virtual machine. When the program starts, Hetman RAID Recovery identifies the array type and properties without effort.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-14.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-14.png\"\/><\/p>\n<p>  One HDD is empty. (Right-click on the array \u2013 Properties \u2013 the RAID tab)<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-15.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-15.png\"\/><\/p>\n<p>  Right-click on it, then select Open.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-16.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-16.png\"\/><\/p>\n<p>  Analyze the array \u2013 select Fast scan.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-17.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-17.png\"\/><\/p>\n<p>  The program has found the remaining files easily. Select the ones you need and click Recovery.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-18.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-18.png\"\/><\/p>\n<p>  Choose where to save them, then click Recovery again.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-19.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-19.png\"\/><\/p>\n<p>  In the end, you\u2019ll find all the information in the folder you have specified for saving.<\/p>\n<p>  The program will be able to identify the RAID type, all the properties and the file system even if several disks break down at the same time.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-21.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-21.png\"\/><\/p>\n<p>  Two disks are empty (Right-click \u2013 Properties \u2013 jump to the RAID tab).<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-22.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-22.png\"\/><\/p>\n<p>  Scan the device: right-click on it and select Open.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-23.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-23.png\"\/><\/p>\n<p>  For starters, we only run Fast scan.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-24.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-24.png\"\/><\/p>\n<p>  As a result, the Fast scan couldn\u2019t find any healthy data \u2013 all the data it has identified is damaged. After that, we decided to run Full analysis.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-25.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-25.png\"\/><\/p>\n<p>  After full analysis, the utility was able to find the necessary information which remained intact, but some data is damaged.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-26.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-26.png\"\/><\/p>\n<p>  When two or more hard disks break down, this array type becomes completely inoperable and restoring information becomes a challenging task.<\/p>\n<p>  That is why such result can be considered quite good as we managed to recover a part of the remaining data. Select and recover it.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-27.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-27.png\"\/><\/p>\n<h2>How to recover data from RAID 0<\/h2>\n<p>  For the last test, we have built a RAID 0 consisting of five hard disks.<\/p>\n<p>  If one disk in this array breaks down, the whole storage system becomes inoperable and all the information is actually lost. We can\u2019t mount it in Linuxeither \u2013 the disks won\u2019t open.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-0.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-0.png\"\/><\/p>\n<p>  Let\u2019s see if we can extract at least a bit of the information with the help of Hetman RAID Recovery.<\/p>\n<p>  RAID-0 is a striped hard disk array with improved performance but without any fault tolerance in terms of the equipment involved. After one of the disks fails or breaks down, the entire device becomes inoperable.<\/p>\n<p>  As a matter of fact, RAID-0 is not a RAID array, technically, as it doesn\u2019t provide any data redundancy. The core advantage of this system is the suggested performance boost.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-0-01.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/raid-0-01.png\"\/><\/p>\n<p>  The program has identified the type and properties of the damaged device.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-28.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-28.png\"\/><\/p>\n<p>  In the properties, we can see that one disk is empty. (Right-click on the array \u2013 Properties \u2013 the RAID tab).<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-29.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-29.png\"\/><\/p>\n<p>  In this case the fast scan hasn\u2019t found anything, so we had to use an in-depth analysis.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-30.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-30.png\"\/><\/p>\n<p>  After the deep scan, the utility can find the data, but some files are damaged.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-31.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-31.png\"\/><\/p>\n<p>  Hetman RAID Recovery managed to detect a part of the remaining information. Select the files you want to restore and click Recovery,<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-32.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-32.png\"\/><\/p>\n<p>  Specify where to save them, Next, and click Recovery again.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-33.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-33.png\"\/><\/p>\n<p>  When the process is over, click Finish.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-34.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/hetman-raid-recovery-34.png\"\/><\/p>\n<p>  All the files will be placed to the folder you have specified.<\/p>\n<p>  See the <a href=\"https:\/\/hetmanrecovery.com\/recovery_news\/how-to-recover-hardware-raid-on-operating-system-linux.htm\">full article<\/a> with all additional video tutorials.<\/div>\n<\/div>\n<\/div>\n<p><!----><!----><\/div>\n<p><!----><!----><br \/> \u0441\u0441\u044b\u043b\u043a\u0430 \u043d\u0430 \u043e\u0440\u0438\u0433\u0438\u043d\u0430\u043b \u0441\u0442\u0430\u0442\u044c\u0438 <a href=\"https:\/\/habr.com\/ru\/articles\/547630\/\"> https:\/\/habr.com\/ru\/articles\/547630\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<div><!--[--><!--]--><\/div>\n<div id=\"post-content-body\">\n<div>\n<div class=\"article-formatted-body article-formatted-body article-formatted-body_version-1\">\n<div xmlns=\"http:\/\/www.w3.org\/1999\/xhtml\">In this article, you will find a detailed tutorial on data recovery from RAID 0, 1 or 5. The array we have been testing was built on Linux, and the methods described here will help you recover your files even if one or several disks break down.<\/p>\n<p>  <img decoding=\"async\" src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/how-to-recover-hardware-raid-on-operating-system-linux.png\" alt=\"image\" data-src=\"https:\/\/hetmanrecovery.com\/pic\/blog\/a248\/how-to-recover-hardware-raid-on-operating-system-linux.png\"\/>  <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-418011","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/418011","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=418011"}],"version-history":[{"count":0,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=\/wp\/v2\/posts\/418011\/revisions"}],"wp:attachment":[{"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=418011"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=418011"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/savepearlharbor.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=418011"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}