{"id":58020,"date":"2026-10-30T14:59:50","date_gmt":"2026-10-30T06:59:50","guid":{"rendered":"https:\/\/www.amagicsoft.com\/?p=58020"},"modified":"2026-10-30T17:03:32","modified_gmt":"2026-10-30T09:03:32","slug":"lba","status":"publish","type":"post","link":"https:\/\/www.amagicsoft.com\/pt\/kb\/disk-partition\/lba.html","title":{"rendered":"Endere\u00e7amento L\u00f3gico de Blocos (LBA): Como funcionam os n\u00fameros de setor"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"58020\" class=\"elementor elementor-58020\" data-elementor-post-type=\"post\">\n\t\t\t\t<div class=\"elementor-element elementor-element-spzstek dtec-docx-root dtec-post-58020 e-flex e-con-boxed e-con e-parent\" data-id=\"spzstek\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-d4puuj7 elementor-widget elementor-widget-text-editor\" data-id=\"d4puuj7\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<div><div><p class=\"otl-paragraph\"><strong>Logical block addressing (LBA)<\/strong> is a method of identifying storage blocks with sequential numbers instead of cylinder, head, and sector coordinates. LBA 0 identifies the first logical block, LBA 1 identifies the second, and so on. However, an LBA number alone does not determine a byte offset: you also need the logical block size and the address-space origin. Understanding this relationship helps explain disk layouts, partition boundaries, and the differences between logical and physical sectors.<\/p><\/div><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-xwg5xlh elementor-toc--minimized-on-tablet elementor-widget elementor-widget-table-of-contents\" data-id=\"xwg5xlh\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;headings_by_tags&quot;:[&quot;h2&quot;,&quot;h3&quot;],&quot;exclude_headings_by_selector&quot;:&quot;.faq-no-toc, h2:contains(Data Recovery Assessment)&quot;,&quot;marker_view&quot;:&quot;bullets&quot;,&quot;no_headings_message&quot;:&quot;No headings were found on this page.&quot;,&quot;icon&quot;:{&quot;value&quot;:&quot;fas fa-circle&quot;,&quot;library&quot;:&quot;fa-solid&quot;},&quot;minimize_box&quot;:&quot;yes&quot;,&quot;minimized_on&quot;:&quot;tablet&quot;,&quot;hierarchical_view&quot;:&quot;yes&quot;,&quot;min_height&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:[]},&quot;min_height_tablet&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:[]},&quot;min_height_mobile&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:[]}}\" data-widget_type=\"table-of-contents.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<div class=\"elementor-toc__header\">\n\t\t\t\t\t\t<h4 class=\"elementor-toc__header-title\">\n\t\t\t\tTable of Contents\t\t\t<\/h4>\n\t\t\t\t\t\t\t\t\t\t<div class=\"elementor-toc__toggle-button elementor-toc__toggle-button--expand\" role=\"button\" tabindex=\"0\" aria-controls=\"elementor-toc__xwg5xlh\" aria-expanded=\"true\" aria-label=\"Open table of contents\"><i aria-hidden=\"true\" class=\"fas fa-chevron-down\"><\/i><\/div>\n\t\t\t\t<div class=\"elementor-toc__toggle-button elementor-toc__toggle-button--collapse\" role=\"button\" tabindex=\"0\" aria-controls=\"elementor-toc__xwg5xlh\" aria-expanded=\"true\" aria-label=\"Close table of contents\"><i aria-hidden=\"true\" class=\"fas fa-chevron-up\"><\/i><\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<div id=\"elementor-toc__xwg5xlh\" class=\"elementor-toc__body\">\n\t\t\t<div class=\"elementor-toc__spinner-container\">\n\t\t\t\t<i class=\"elementor-toc__spinner eicon-animation-spin eicon-loading\" aria-hidden=\"true\"><\/i>\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-0fj4d0y elementor-widget elementor-widget-heading\" data-id=\"0fj4d0y\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">LBA Explained: How Logical Block Addresses Work<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-o02qiy4 elementor-widget elementor-widget-text-editor\" data-id=\"o02qiy4\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>LBA treats a storage device&#8217;s addressable blocks as a linear sequence. Instead of describing a location using three coordinates, as Cylinder-Head-Sector (CHS) addressing does, it assigns each logical block an integer index.<\/p>\n<p>For example, the first four logical blocks are:<\/p>\n<table><tbody><tr><td><p><strong>LBA<\/strong><\/p><\/td><td><p><strong>Meaning<\/strong><\/p><\/td><\/tr><tr><td><p>0<\/p><\/td><td><p>First logical block<\/p><\/td><\/tr><tr><td><p>1<\/p><\/td><td><p>Second logical block<\/p><\/td><\/tr><tr><td><p>2<\/p><\/td><td><p>Third logical block<\/p><\/td><\/tr><tr><td><p>3<\/p><\/td><td><p>Fourth logical block<\/p><\/td><\/tr><\/tbody><\/table>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-724bf5b elementor-widget elementor-widget-html\" data-id=\"724bf5b\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div id=\"amg-lba-example-demo\" class=\"amg-lba-example-demo\">\r\n  <style>\r\n    #amg-lba-example-demo {\r\n      --ink: #172b45;\r\n      --muted: #5b6c80;\r\n      --line: #d8e2ec;\r\n      --blue: #1769aa;\r\n      --blue-soft: #eaf4ff;\r\n      --green: #18794e;\r\n      --green-soft: #eaf7ef;\r\n      font-family: inherit;\r\n      color: var(--ink);\r\n      width: 100%;\r\n      box-sizing: border-box;\r\n      border: 1px solid var(--line);\r\n      border-radius: 14px;\r\n      padding: clamp(14px, 3vw, 22px);\r\n      background: #fff;\r\n    }\r\n    #amg-lba-example-demo * { box-sizing: border-box; }\r\n    #amg-lba-example-demo .le-kicker { margin: 0 0 6px; color: var(--blue); font-size: 12px; font-weight: 800; letter-spacing: .07em; text-transform: uppercase; }\r\n    #amg-lba-example-demo .le-title { margin: 0; font-size: clamp(20px, 2.8vw, 26px); line-height: 1.25; font-weight: 800; }\r\n    #amg-lba-example-demo .le-intro { margin: 8px 0 16px; color: var(--muted); font-size: 14px; line-height: 1.55; }\r\n    #amg-lba-example-demo .le-scenario { border: 1px solid #cfe1f4; background: #f4f9ff; border-radius: 11px; padding: 13px 14px; }\r\n    #amg-lba-example-demo .le-scenario-label { margin: 0 0 5px; font-size: 12px; font-weight: 800; color: var(--blue); text-transform: uppercase; letter-spacing: .04em; }\r\n    #amg-lba-example-demo .le-scenario p { margin: 0; font-size: 14px; line-height: 1.55; }\r\n    #amg-lba-example-demo .le-actions { display: flex; align-items: center; flex-wrap: wrap; gap: 8px; margin: 14px 0 5px; }\r\n    #amg-lba-example-demo .le-action-label { margin-right: 3px; color: var(--muted); font-size: 13px; font-weight: 650; }\r\n    #amg-lba-example-demo .le-pick { appearance: none; border: 1px solid #bfd1e2; background: #fff; color: var(--ink); border-radius: 8px; padding: 8px 12px; font: inherit; font-size: 13px; font-weight: 750; cursor: pointer; }\r\n    #amg-lba-example-demo .le-pick[aria-pressed=\"true\"] { background: var(--blue); color: #fff; border-color: var(--blue); }\r\n    #amg-lba-example-demo button:focus-visible { outline: 3px solid #8dc5ff; outline-offset: 2px; }\r\n    #amg-lba-example-demo .le-flow-label { display: flex; justify-content: space-between; gap: 12px; flex-wrap: wrap; margin: 18px 0 8px; font-size: 13px; font-weight: 750; }\r\n    #amg-lba-example-demo .le-flow-label span:last-child { color: var(--muted); font-weight: 500; }\r\n    #amg-lba-example-demo .le-blocks { display: grid; grid-template-columns: repeat(8, minmax(0, 1fr)); gap: 7px; }\r\n    #amg-lba-example-demo .le-block { min-width: 0; border: 1px solid #cbd8e5; background: #f8fbfe; border-radius: 9px; min-height: 84px; padding: 9px 3px; text-align: center; color: var(--ink); cursor: pointer; }\r\n    #amg-lba-example-demo .le-block .le-num { display: block; font-size: clamp(12px, 1.7vw, 17px); font-weight: 850; line-height: 1.3; }\r\n    #amg-lba-example-demo .le-block .le-small { display: block; margin-top: 7px; font-size: 10px; line-height: 1.25; color: var(--muted); }\r\n    #amg-lba-example-demo .le-block[aria-pressed=\"true\"] { background: var(--blue-soft); border: 2px solid var(--blue); padding: 8px 2px; box-shadow: 0 0 0 2px rgba(23,105,170,.08); }\r\n    #amg-lba-example-demo .le-block[aria-pressed=\"true\"] .le-small { color: var(--blue); font-weight: 800; }\r\n    #amg-lba-example-demo .le-results { display: grid; grid-template-columns: minmax(0, 1.1fr) minmax(0, 1fr); gap: 12px; margin-top: 14px; }\r\n    #amg-lba-example-demo .le-result-main, #amg-lba-example-demo .le-result-side { min-width: 0; border: 1px solid #dce7f0; border-radius: 11px; padding: 14px; background: #fbfdff; }\r\n    #amg-lba-example-demo .le-result-main { background: var(--green-soft); border-color: #c8e6d2; }\r\n    #amg-lba-example-demo .le-label { margin: 0 0 5px; color: var(--muted); font-size: 11px; font-weight: 800; text-transform: uppercase; letter-spacing: .05em; }\r\n    #amg-lba-example-demo .le-answer { margin: 0; font-size: clamp(18px, 2.4vw, 23px); line-height: 1.3; font-weight: 850; }\r\n    #amg-lba-example-demo .le-copy { margin: 7px 0 0; font-size: 13px; line-height: 1.55; }\r\n    #amg-lba-example-demo .le-row { display: flex; justify-content: space-between; align-items: flex-start; gap: 10px; padding: 7px 0; border-bottom: 1px solid #e3ebf2; font-size: 13px; line-height: 1.4; }\r\n    #amg-lba-example-demo .le-row:last-child { border-bottom: 0; }\r\n    #amg-lba-example-demo .le-row span { color: var(--muted); }\r\n    #amg-lba-example-demo .le-row strong { text-align: right; font-variant-numeric: tabular-nums; overflow-wrap: anywhere; }\r\n    #amg-lba-example-demo .le-caution { margin: 13px 0 0; padding: 10px 12px; border-left: 3px solid #d18a24; border-radius: 5px; background: #fff8eb; color: #614718; font-size: 12px; line-height: 1.55; }\r\n    #amg-lba-example-demo .le-caution strong { color: #52380e; }\r\n    @media (max-width: 620px) {\r\n      #amg-lba-example-demo .le-blocks { grid-template-columns: repeat(4, minmax(0, 1fr)); }\r\n      #amg-lba-example-demo .le-block { min-height: 72px; }\r\n      #amg-lba-example-demo .le-results { grid-template-columns: 1fr; }\r\n    }\r\n    @media (prefers-reduced-motion: reduce) { #amg-lba-example-demo * { scroll-behavior: auto !important; } }\r\n  <\/style>\r\n\r\n  <p class=\"le-kicker\">A practical example<\/p>\r\n  <div class=\"le-title\">What Does \u201cRead LBA 3\u201d Mean?<\/div>\r\n  <p class=\"le-intro\">Imagine a USB drive that exposes 512-byte logical blocks. A disk tool requests one block by its LBA number. Select an example to see which block the number refers to.<\/p>\r\n\r\n  <div class=\"le-scenario\">\r\n    <p class=\"le-scenario-label\">The request<\/p>\r\n    <p id=\"amg-le-request\">\u201cRead LBA 3.\u201d The drive is being asked for the block numbered 3\u2014not the third block.<\/p>\r\n  <\/div>\r\n\r\n  <div class=\"le-actions\" aria-label=\"Choose an example LBA\">\r\n    <span class=\"le-action-label\">Try an example:<\/span>\r\n    <button type=\"button\" class=\"le-pick\" data-choice=\"0\" aria-pressed=\"false\">LBA 0<\/button>\r\n    <button type=\"button\" class=\"le-pick\" data-choice=\"3\" aria-pressed=\"true\">LBA 3<\/button>\r\n    <button type=\"button\" class=\"le-pick\" data-choice=\"7\" aria-pressed=\"false\">LBA 7<\/button>\r\n  <\/div>\r\n\r\n  <div class=\"le-flow-label\"><span>Logical blocks on the drive<\/span><span>Numbering starts at zero \u2192<\/span><\/div>\r\n  <div class=\"le-blocks\" id=\"amg-le-blocks\" aria-label=\"Eight example logical blocks\">\r\n    <button type=\"button\" class=\"le-block\" data-lba=\"0\" aria-pressed=\"false\"><span class=\"le-num\">LBA 0<\/span><span class=\"le-small\">1st block<\/span><\/button>\r\n    <button type=\"button\" class=\"le-block\" data-lba=\"1\" aria-pressed=\"false\"><span class=\"le-num\">LBA 1<\/span><span class=\"le-small\">2nd block<\/span><\/button>\r\n    <button type=\"button\" class=\"le-block\" data-lba=\"2\" aria-pressed=\"false\"><span class=\"le-num\">LBA 2<\/span><span class=\"le-small\">3rd block<\/span><\/button>\r\n    <button type=\"button\" class=\"le-block\" data-lba=\"3\" aria-pressed=\"true\"><span class=\"le-num\">LBA 3<\/span><span class=\"le-small\">4th block<\/span><\/button>\r\n    <button type=\"button\" class=\"le-block\" data-lba=\"4\" aria-pressed=\"false\"><span class=\"le-num\">LBA 4<\/span><span class=\"le-small\">5th block<\/span><\/button>\r\n    <button type=\"button\" class=\"le-block\" data-lba=\"5\" aria-pressed=\"false\"><span class=\"le-num\">LBA 5<\/span><span class=\"le-small\">6th block<\/span><\/button>\r\n    <button type=\"button\" class=\"le-block\" data-lba=\"6\" aria-pressed=\"false\"><span class=\"le-num\">LBA 6<\/span><span class=\"le-small\">7th block<\/span><\/button>\r\n    <button type=\"button\" class=\"le-block\" data-lba=\"7\" aria-pressed=\"false\"><span class=\"le-num\">LBA 7<\/span><span class=\"le-small\">8th block<\/span><\/button>\r\n  <\/div>\r\n\r\n  <div class=\"le-results\" aria-live=\"polite\">\r\n    <div class=\"le-result-main\">\r\n      <p class=\"le-label\">In plain English<\/p>\r\n      <p class=\"le-answer\" id=\"amg-le-answer\">LBA 3 = the 4th block<\/p>\r\n      <p class=\"le-copy\" id=\"amg-le-explanation\">Three blocks come before it: LBA 0, LBA 1, and LBA 2. Because counting starts at zero, address 3 points to position four.<\/p>\r\n    <\/div>\r\n    <div class=\"le-result-side\">\r\n      <div class=\"le-row\"><span>Selected LBA<\/span><strong id=\"amg-le-selected\">3<\/strong><\/div>\r\n      <div class=\"le-row\"><span>Blocks before it<\/span><strong id=\"amg-le-before\">3<\/strong><\/div>\r\n      <div class=\"le-row\"><span>Logical block size<\/span><strong>512 bytes<\/strong><\/div>\r\n      <div class=\"le-row\"><span>Byte range in this example<\/span><strong id=\"amg-le-range\">1,536\u20132,047<\/strong><\/div>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <p class=\"le-caution\"><strong>Important distinction:<\/strong> LBA 3 means \u201clogical block number 3,\u201d not \u201cfile number 3\u201d and not \u201cphysical location 3.\u201d The byte range above follows from the example\u2019s 512-byte logical block size. A file system\u2019s metadata is needed to determine which file, if any, uses that block.<\/p>\r\n\r\n  <script>\r\n    (function () {\r\n      var root = document.getElementById('amg-lba-example-demo');\r\n      if (!root || root.dataset.initialized === 'true') return;\r\n      root.dataset.initialized = 'true';\r\n      var selected = 3;\r\n      var blocks = root.querySelector('#amg-le-blocks');\r\n      var request = root.querySelector('#amg-le-request');\r\n      var answer = root.querySelector('#amg-le-answer');\r\n      var explanation = root.querySelector('#amg-le-explanation');\r\n      var selectedText = root.querySelector('#amg-le-selected');\r\n      var beforeText = root.querySelector('#amg-le-before');\r\n      var rangeText = root.querySelector('#amg-le-range');\r\n      function ordinal(n) {\r\n        var suffix = 'th';\r\n        if (n % 100 < 11 || n % 100 > 13) {\r\n          if (n % 10 === 1) suffix = 'st';\r\n          else if (n % 10 === 2) suffix = 'nd';\r\n          else if (n % 10 === 3) suffix = 'rd';\r\n        }\r\n        return n + suffix;\r\n      }\r\n      function fmt(n) { return n.toLocaleString('en-US'); }\r\n      function update(value) {\r\n        selected = Number(value);\r\n        var position = selected + 1;\r\n        var start = selected * 512;\r\n        var end = start + 511;\r\n        request.textContent = '\u201cRead LBA ' + selected + '.\u201d The drive is being asked for the block numbered ' + selected + '\u2014the ' + ordinal(position) + ' block in this example.';\r\n        answer.textContent = 'LBA ' + selected + ' = the ' + ordinal(position) + ' block';\r\n        if (selected === 0) {\r\n          explanation.textContent = 'There are no blocks before it. The first block is numbered LBA 0 because LBA numbering starts at zero.';\r\n        } else {\r\n          var prior = [];\r\n          for (var i = Math.max(0, selected - 3); i < selected; i++) prior.push('LBA ' + i);\r\n          explanation.textContent = selected + ' block' + (selected === 1 ? '' : 's') + ' come before it. ' + (selected <= 3 ? 'Those blocks are ' + prior.join(', ') + '.' : 'The immediately preceding blocks include ' + prior.join(', ') + '.');\r\n        }\r\n        selectedText.textContent = String(selected);\r\n        beforeText.textContent = String(selected);\r\n        rangeText.textContent = fmt(start) + '\u2013' + fmt(end);\r\n        blocks.querySelectorAll('[data-lba]').forEach(function (button) {\r\n          var n = Number(button.getAttribute('data-lba'));\r\n          button.setAttribute('aria-pressed', n === selected ? 'true' : 'false');\r\n        });\r\n        root.querySelectorAll('.le-pick').forEach(function (button) {\r\n          button.setAttribute('aria-pressed', Number(button.getAttribute('data-choice')) === selected ? 'true' : 'false');\r\n        });\r\n      }\r\n      root.querySelectorAll('.le-pick').forEach(function (button) {\r\n        button.addEventListener('click', function () { update(button.getAttribute('data-choice')); });\r\n      });\r\n      blocks.addEventListener('click', function (event) {\r\n        var button = event.target.closest('button[data-lba]');\r\n        if (button && blocks.contains(button)) update(button.getAttribute('data-lba'));\r\n      });\r\n      update(3);\r\n    })();\r\n  <\/script>\r\n<\/div>\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-e8q1948 elementor-widget elementor-widget-text-editor\" data-id=\"e8q1948\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>This numbering is zero-based. If a device exposes (N) logical blocks, its last valid LBA is <code class=\"dtec-inline-code\">N \u2212 1<\/code>, assuming the address space begins at LBA 0 and contains no gaps in its numbering.<\/p><p>For example, a device exposing 2,000,000 logical blocks has a last LBA of <code class=\"dtec-inline-code\">1,999,999<\/code>. The number of blocks is therefore one greater than the last LBA.<\/p><p>LBA is an addressing convention, not a file system. It does not describe filenames, directories, or file allocation. Partition tables use logical block addresses to describe where partitions begin and end, while file systems use their own metadata to organize files within those partitions.<\/p><p>The address-space origin also matters. A disk-relative LBA and a volume-relative block number may refer to different locations even when their numeric values are identical. Always establish whether a tool reports addresses relative to the entire device or to a partition before combining its results with partition-table information.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-yq39sfg elementor-widget elementor-widget-heading\" data-id=\"yq39sfg\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">How to Calculate an LBA Sector Number's Byte Offset<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-pl2u1vk elementor-widget elementor-widget-text-editor\" data-id=\"pl2u1vk\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>An <strong>LBA sector number<\/strong> identifies a logical block, but converting that number into a byte position requires the logical block size.<\/p><p>The starting byte offset is calculated as:<\/p><p><code class=\"dtec-inline-code\">Starting byte offset = LBA \u00d7 Logical block size<\/code><\/p><p>If the logical block size is represented by (B), the inclusive byte range of an LBA is:<\/p><p><code class=\"dtec-inline-code\">Start offset = LBA \u00d7 B<\/code><\/p><p><code class=\"dtec-inline-code\">End offset = (LBA + 1) \u00d7 B \u2212 1<\/code><\/p><p>The subtraction of one is necessary because byte offsets are zero-based and the end offset is inclusive.<\/p><h3>Example: LBA 50 with different logical block sizes<\/h3><p>Consider LBA 50 under two common logical block sizes.<\/p><table><tbody><tr><td><p><strong>Calculation<\/strong><\/p><\/td><td><p><strong>512-byte logical block<\/strong><\/p><\/td><td><p><strong>4,096-byte logical block<\/strong><\/p><\/td><\/tr><tr><td><p>Starting offset<\/p><\/td><td><p>25,600 bytes<\/p><\/td><td><p>204,800 bytes<\/p><\/td><\/tr><tr><td><p>Starting offset in hexadecimal<\/p><\/td><td><p><code class=\"dtec-inline-code\">0x6400<\/code><\/p><\/td><td><p><code class=\"dtec-inline-code\">0x32000<\/code><\/p><\/td><\/tr><tr><td><p>Last byte offset<\/p><\/td><td><p>26,111 bytes<\/p><\/td><td><p>208,895 bytes<\/p><\/td><\/tr><tr><td><p>Last offset in hexadecimal<\/p><\/td><td><p><code class=\"dtec-inline-code\">0x65FF<\/code><\/p><\/td><td><p><code class=\"dtec-inline-code\">0x32FFF<\/code><\/p><\/td><\/tr><tr><td><p>Total bytes addressed<\/p><\/td><td><p>512<\/p><\/td><td><p>4,096<\/p><\/td><\/tr><\/tbody><\/table><p>For a 512-byte logical block, LBA 50 starts at byte offset <code class=\"dtec-inline-code\">25,600<\/code> and covers bytes <code class=\"dtec-inline-code\">25,600\u201326,111<\/code>. That inclusive range contains exactly 512 bytes.<\/p><p>For a 4,096-byte logical block, the same LBA starts at byte offset <code class=\"dtec-inline-code\">204,800<\/code> and covers bytes <code class=\"dtec-inline-code\">204,800\u2013208,895<\/code>, a total of 4,096 bytes.<\/p><p>These are illustrative calculations, not measurements from a physical disk.<\/p><p>The important result is that <strong>the same LBA can correspond to different byte offsets when the logical block size changes<\/strong>. You cannot assume that multiplying every LBA by 512 will produce the correct byte offset for every device.<\/p><p>The calculation also assumes that the LBA and logical block size refer to the same address space. If a tool reports a partition-relative block number but you need a disk-relative address, you must account for the partition&#8217;s starting LBA and confirm that both values use the same logical block unit.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-faa4010 elementor-widget elementor-widget-html\" data-id=\"faa4010\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"html.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div id=\"amagicsoft-lba-explorer\" class=\"alba-root\">\r\n  <style>\r\n    #amagicsoft-lba-explorer,\r\n    #amagicsoft-lba-explorer * { box-sizing: border-box; }\r\n    #amagicsoft-lba-explorer {\r\n      --alba-border: #d7dee8;\r\n      --alba-muted: #536273;\r\n      --alba-ink: #172433;\r\n      --alba-panel: #f5f8fb;\r\n      --alba-accent: #245ca6;\r\n      width: 100%;\r\n      max-width: 900px;\r\n      margin: 1.25rem auto;\r\n      color: var(--alba-ink);\r\n      font: 16px\/1.5 system-ui, -apple-system, BlinkMacSystemFont, \"Segoe UI\", sans-serif;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-shell {\r\n      border: 1px solid var(--alba-border);\r\n      border-radius: 14px;\r\n      padding: clamp(16px, 3vw, 24px);\r\n      background: #fff;\r\n      box-shadow: 0 5px 18px rgba(20, 40, 60, .06);\r\n    }\r\n    #amagicsoft-lba-explorer .alba-title {\r\n      margin: 0 0 6px;\r\n      font-size: clamp(1.2rem, 2.6vw, 1.55rem);\r\n      line-height: 1.25;\r\n      font-weight: 700;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-intro,\r\n    #amagicsoft-lba-explorer .alba-note { color: var(--alba-muted); }\r\n    #amagicsoft-lba-explorer .alba-intro { margin: 0 0 18px; }\r\n    #amagicsoft-lba-explorer .alba-controls {\r\n      display: grid;\r\n      grid-template-columns: minmax(0, 1fr) auto;\r\n      align-items: end;\r\n      gap: 12px;\r\n      margin-bottom: 16px;\r\n    }\r\n    #amagicsoft-lba-explorer label {\r\n      display: block;\r\n      margin-bottom: 6px;\r\n      font-weight: 650;\r\n    }\r\n    #amagicsoft-lba-explorer input {\r\n      width: 100%;\r\n      min-height: 44px;\r\n      border: 1px solid #aeb9c7;\r\n      border-radius: 8px;\r\n      padding: 9px 12px;\r\n      color: var(--alba-ink);\r\n      background: #fff;\r\n      font: inherit;\r\n    }\r\n    #amagicsoft-lba-explorer input:focus-visible {\r\n      outline: 3px solid rgba(36, 92, 166, .25);\r\n      outline-offset: 1px;\r\n      border-color: var(--alba-accent);\r\n    }\r\n    #amagicsoft-lba-explorer .alba-reset {\r\n      min-height: 44px;\r\n      padding: 9px 14px;\r\n      border: 1px solid #aeb9c7;\r\n      border-radius: 8px;\r\n      color: var(--alba-ink);\r\n      background: #fff;\r\n      font: inherit;\r\n      font-weight: 650;\r\n      cursor: pointer;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-reset:hover { background: var(--alba-panel); }\r\n    #amagicsoft-lba-explorer .alba-reset:focus-visible {\r\n      outline: 3px solid rgba(36, 92, 166, .25);\r\n      outline-offset: 2px;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-results {\r\n      display: grid;\r\n      grid-template-columns: repeat(2, minmax(0, 1fr));\r\n      gap: 12px;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-card {\r\n      min-width: 0;\r\n      border: 1px solid var(--alba-border);\r\n      border-radius: 10px;\r\n      padding: 15px;\r\n      background: var(--alba-panel);\r\n    }\r\n    #amagicsoft-lba-explorer .alba-card-title {\r\n      margin: 0 0 12px;\r\n      font-size: 1rem;\r\n      line-height: 1.35;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-metric { margin: 0 0 12px; }\r\n    #amagicsoft-lba-explorer .alba-metric:last-child { margin-bottom: 0; }\r\n    #amagicsoft-lba-explorer .alba-label {\r\n      display: block;\r\n      margin-bottom: 3px;\r\n      color: var(--alba-muted);\r\n      font-size: .88rem;\r\n    }\r\n    #amagicsoft-lba-explorer output {\r\n      display: block;\r\n      overflow-wrap: anywhere;\r\n      font-variant-numeric: tabular-nums;\r\n      font-weight: 700;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-hex {\r\n      color: var(--alba-accent);\r\n      font-weight: 650;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-formula {\r\n      margin: 16px 0 0;\r\n      padding: 12px 14px;\r\n      border-left: 3px solid var(--alba-accent);\r\n      border-radius: 4px;\r\n      background: #f1f6fc;\r\n      overflow-wrap: anywhere;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-formula code {\r\n      font-family: ui-monospace, SFMono-Regular, Menlo, Consolas, monospace;\r\n      font-size: .94em;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-error {\r\n      min-height: 1.5em;\r\n      margin: 8px 0 0;\r\n      color: #9b1c1c;\r\n      font-size: .92rem;\r\n    }\r\n    #amagicsoft-lba-explorer .alba-note {\r\n      margin: 14px 0 0;\r\n      font-size: .88rem;\r\n    }\r\n    @media (max-width: 620px) {\r\n      #amagicsoft-lba-explorer .alba-controls { grid-template-columns: 1fr; }\r\n      #amagicsoft-lba-explorer .alba-reset { width: 100%; }\r\n      #amagicsoft-lba-explorer .alba-results { grid-template-columns: 1fr; }\r\n    }\r\n  <\/style>\r\n\r\n  <div class=\"alba-shell\">\r\n    <p class=\"alba-title\">LBA-to-Byte-Offset Explorer<\/p>\r\n    <p class=\"alba-intro\">Change the LBA number to compare the byte range it identifies under two common logical block sizes.<\/p>\r\n\r\n    <div class=\"alba-controls\">\r\n      <div>\r\n        <label for=\"alba-lba-input\">LBA number (zero-based)<\/label>\r\n        <input id=\"alba-lba-input\" type=\"text\" inputmode=\"numeric\" pattern=\"[0-9]*\" value=\"50\" autocomplete=\"off\" aria-describedby=\"alba-input-help alba-error\">\r\n        <div id=\"alba-input-help\" class=\"alba-note\">Enter a non-negative whole number.<\/div>\r\n      <\/div>\r\n      <button class=\"alba-reset\" id=\"alba-reset-button\" type=\"button\">Reset example<\/button>\r\n    <\/div>\r\n\r\n    <p class=\"alba-error\" id=\"alba-error\" role=\"status\" aria-live=\"polite\"><\/p>\r\n\r\n    <div class=\"alba-results\" aria-live=\"polite\" aria-atomic=\"true\">\r\n      <section class=\"alba-card\" aria-labelledby=\"alba-512-title\">\r\n        <p class=\"alba-card-title\" id=\"alba-512-title\">With a 512-byte logical block<\/p>\r\n        <p class=\"alba-metric\"><span class=\"alba-label\">Starting byte offset<\/span><output id=\"alba-512-start\">25,600 bytes<\/output><output class=\"alba-hex\" id=\"alba-512-start-hex\">0x6400<\/output><\/p>\r\n        <p class=\"alba-metric\"><span class=\"alba-label\">Inclusive byte range<\/span><output id=\"alba-512-range\">25,600\u201326,111<\/output><\/p>\r\n        <p class=\"alba-metric\"><span class=\"alba-label\">Last byte offset<\/span><output id=\"alba-512-end\">26,111 bytes<\/output><output class=\"alba-hex\" id=\"alba-512-end-hex\">0x65FF<\/output><\/p>\r\n      <\/section>\r\n\r\n      <section class=\"alba-card\" aria-labelledby=\"alba-4096-title\">\r\n        <p class=\"alba-card-title\" id=\"alba-4096-title\">With a 4,096-byte logical block<\/p>\r\n        <p class=\"alba-metric\"><span class=\"alba-label\">Starting byte offset<\/span><output id=\"alba-4096-start\">204,800 bytes<\/output><output class=\"alba-hex\" id=\"alba-4096-start-hex\">0x32000<\/output><\/p>\r\n        <p class=\"alba-metric\"><span class=\"alba-label\">Inclusive byte range<\/span><output id=\"alba-4096-range\">204,800\u2013208,895<\/output><\/p>\r\n        <p class=\"alba-metric\"><span class=\"alba-label\">Last byte offset<\/span><output id=\"alba-4096-end\">208,895 bytes<\/output><output class=\"alba-hex\" id=\"alba-4096-end-hex\">0x32FFF<\/output><\/p>\r\n      <\/section>\r\n    <\/div>\r\n\r\n    <p class=\"alba-formula\"><strong>Calculation:<\/strong> <code>start offset = LBA \u00d7 logical block size<\/code><br><strong>Inclusive end:<\/strong> <code>end offset = (LBA + 1) \u00d7 logical block size \u2212 1<\/code><\/p>\r\n    <p class=\"alba-note\">Teaching example only. This calculator does not read a disk. The calculation assumes the LBA and block size refer to the same logical device, with byte offsets measured from that device's beginning.<\/p>\r\n  <\/div>\r\n\r\n  <script>\r\n    (function () {\r\n      const root = document.getElementById('amagicsoft-lba-explorer');\r\n      if (!root || root.dataset.albaInitialized === 'true') return;\r\n      root.dataset.albaInitialized = 'true';\r\n\r\n      const input = root.querySelector('#alba-lba-input');\r\n      const error = root.querySelector('#alba-error');\r\n      const reset = root.querySelector('#alba-reset-button');\r\n      const formatter = new Intl.NumberFormat('en-US');\r\n\r\n      function setText(id, value) {\r\n        const node = root.querySelector('#' + id);\r\n        if (node) node.textContent = value;\r\n      }\r\n\r\n      function renderForSize(lba, size, prefix) {\r\n        const start = lba * BigInt(size);\r\n        const end = start + BigInt(size) - 1n;\r\n        setText(prefix + '-start', formatter.format(start) + ' bytes');\r\n        setText(prefix + '-start-hex', '0x' + start.toString(16).toUpperCase());\r\n        setText(prefix + '-range', formatter.format(start) + '\u2013' + formatter.format(end));\r\n        setText(prefix + '-end', formatter.format(end) + ' bytes');\r\n        setText(prefix + '-end-hex', '0x' + end.toString(16).toUpperCase());\r\n      }\r\n\r\n      function render() {\r\n        const raw = input.value.trim();\r\n        if (!\/^\\d+$\/.test(raw)) {\r\n          error.textContent = 'Enter a valid non-negative whole number to calculate the offsets.';\r\n          return;\r\n        }\r\n        let lba;\r\n        try {\r\n          lba = BigInt(raw);\r\n        } catch (e) {\r\n          error.textContent = 'The LBA value could not be read. Enter a whole number.';\r\n          return;\r\n        }\r\n        error.textContent = '';\r\n        renderForSize(lba, 512, 'alba-512');\r\n        renderForSize(lba, 4096, 'alba-4096');\r\n      }\r\n\r\n      input.addEventListener('input', render);\r\n      reset.addEventListener('click', function () {\r\n        input.value = '50';\r\n        render();\r\n        input.focus();\r\n      });\r\n      render();\r\n    })();\r\n  <\/script>\r\n<\/div>\r\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-ed99osx elementor-widget elementor-widget-heading\" data-id=\"ed99osx\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">LBA vs. CHS Addressing<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-w1fdxit elementor-widget elementor-widget-text-editor\" data-id=\"w1fdxit\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p><strong>LBA vs. CHS<\/strong> is primarily a comparison between two ways of expressing a storage address.<\/p>\n<p>CHS stands for Cylinder, Head, and Sector. It represents a location using three coordinates, while LBA assigns the location a single sequential number.<\/p>\n<table><tbody><tr><td><p><strong>Feature<\/strong><\/p><\/td><td><p><strong>LBA<\/strong><\/p><\/td><td><p><strong>CHS<\/strong><\/p><\/td><\/tr><tr><td><p>Address representation<\/p><\/td><td><p>One linear block number<\/p><\/td><td><p>Cylinder, head, and sector coordinates<\/p><\/td><\/tr><tr><td><p>Numbering<\/p><\/td><td><p>LBA starts at 0<\/p><\/td><td><p>Traditional sector numbers start at 1<\/p><\/td><\/tr><tr><td><p>Address calculation<\/p><\/td><td><p>Multiply the LBA by the logical block size to obtain a byte offset<\/p><\/td><td><p>Requires geometry parameters to translate the coordinates<\/p><\/td><\/tr><tr><td><p>Modern disk interpretation<\/p><\/td><td><p>Logical address exposed by the storage interface<\/p><\/td><td><p>May represent translated geometry rather than actual physical geometry<\/p><\/td><\/tr><tr><td><p>Partition-table use<\/p><\/td><td><p>Explicit LBA fields are used by modern partitioning structures<\/p><\/td><td><p>Legacy fields remain in MBR entries for compatibility<\/p><\/td><\/tr><\/tbody><\/table>\n<h3>How CHS coordinates map to LBA<\/h3>\n<p>A traditional CHS-to-LBA conversion requires the number of heads per cylinder and the number of sectors per track.<\/p>\n<p>Using zero-based cylinder and head numbers and a one-based sector number:<\/p>\n<p><code class=\"dtec-inline-code\">LBA = ((Cylinder \u00d7 Heads per cylinder) + Head) \u00d7 Sectors per track + (Sector \u2212 1)<\/code><\/p>\n<p>For example, suppose a hypothetical geometry has 16 heads per cylinder and 63 sectors per track. The CHS address <code class=\"dtec-inline-code\">(1, 2, 3)<\/code> converts to:<\/p>\n<p><code class=\"dtec-inline-code\">LBA = ((1 \u00d7 16) + 2) \u00d7 63 + (3 \u2212 1)<\/code><\/p>\n<p><code class=\"dtec-inline-code\">LBA = 18 \u00d7 63 + 2<\/code><\/p>\n<p><code class=\"dtec-inline-code\">LBA = 1,136<\/code><\/p>\n<p>This example demonstrates the conversion formula; it does not describe the physical layout of a particular drive.<\/p>\n<p>Modern drives do not necessarily expose a CHS geometry that corresponds to their actual physical tracks and heads. Legacy software may use translated CHS values for compatibility, so those values should not automatically be interpreted as physical locations.<\/p>\n<p>The <a href=\"https:\/\/uefi.org\/specs\/UEFI\/2.11\/05_GUID_Partition_Table_Format.html\" rel=\"nofollow\">UEFI specification&#8217;s MBR partition-record definition<\/a> explicitly distinguishes the CHS fields from the LBA fields used by UEFI firmware to determine partition locations.<\/p>\n<p>LBA is simpler to use as a linear addressing scheme, but its addressable capacity still depends on the width of the address field and the storage interface. The term LBA alone does not specify a universal address width.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-q0y8pyn elementor-widget elementor-widget-heading\" data-id=\"q0y8pyn\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Logical Block Size vs. Physical Sector Size<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-ii87dny elementor-widget elementor-widget-text-editor\" data-id=\"ii87dny\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>An LBA identifies a logical block exposed by the storage device or interface. That logical block is not necessarily the same size as a physical sector on the underlying medium.<\/p>\n<p>Three common hard-drive formats illustrate the distinction:<\/p>\n<table><tbody><tr><td><p><strong>Format<\/strong><\/p><\/td><td><p><strong>Logical sector size<\/strong><\/p><\/td><td><p><strong>Physical sector size<\/strong><\/p><\/td><\/tr><tr><td><p>512n<\/p><\/td><td><p>512 bytes<\/p><\/td><td><p>512 bytes<\/p><\/td><\/tr><tr><td><p>512e<\/p><\/td><td><p>512 bytes<\/p><\/td><td><p>4,096 bytes<\/p><\/td><\/tr><tr><td><p>4Kn<\/p><\/td><td><p>4,096 bytes<\/p><\/td><td><p>4,096 bytes<\/p><\/td><\/tr><\/tbody><\/table>\n<p>These are common formats, not an exhaustive list of every block size that a storage interface may report.<\/p>\n<p>In a 512e drive, eight 512-byte logical sectors fit within one 4,096-byte physical sector. The operating system addresses the logical sectors, while the device manages the relationship between those sectors and the physical storage layout.<\/p>\n<p>This difference matters for two reasons:<\/p>\n<ul><li><strong>Address calculation:<\/strong> Use the logical block size associated with the LBA address space to calculate the byte offset.<\/li><li><strong>Alignment and performance:<\/strong> Physical sector boundaries can affect how efficiently the device performs writes. If the device&#8217;s logical address zero is aligned to a physical boundary, an LBA that is a multiple of eight aligns to a 4,096-byte boundary on a 512e layout. Actual alignment can also depend on device-reported offsets and transfer-granularity requirements.<\/li><\/ul>\n<p>Microsoft&#8217;s documentation on <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows\/compatibility\/advanced-format-disk-compatibility-update\" rel=\"nofollow\">Advanced Format disk compatibility<\/a> explains why Windows and storage applications need to account for differences between logical and physical sector sizes.<\/p>\n<p>Do not use the physical sector size as a substitute for the logical block size in the basic LBA-to-byte-offset formula. They describe different aspects of the storage layout.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-jcszxbh elementor-widget elementor-widget-heading\" data-id=\"jcszxbh\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">How LBA Is Used in MBR and GPT<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-lfil1kt elementor-widget elementor-widget-text-editor\" data-id=\"lfil1kt\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>LBA becomes especially useful when examining partition tables because these structures use block addresses to describe disk layout.<\/p>\n<h3>LBA fields in MBR<\/h3>\n<p>The Master Boot Record (MBR) occupies LBA 0 on an MBR-partitioned disk. Its partition table contains four 16-byte partition entries.<\/p>\n<p>Each entry includes two important 32-bit fields:<\/p>\n<ul><li><code class=\"dtec-inline-code\">StartingLBA<\/code>, at byte offset 8 relative to the beginning of the partition entry, identifies the partition&#8217;s starting logical block.<\/li><li><code class=\"dtec-inline-code\">SizeInLBA<\/code>, at byte offset 12 relative to the beginning of the partition entry, specifies the number of logical blocks in the partition.<\/li><\/ul>\n<p>If the partition size is nonzero, its ending LBA can be calculated as:<\/p>\n<p><code class=\"dtec-inline-code\">Ending LBA = StartingLBA + SizeInLBA \u2212 1<\/code><\/p>\n<p>For example, a partition beginning at LBA 2,048 and containing 1,000,000 logical blocks ends at LBA <code class=\"dtec-inline-code\">1,002,047<\/code>. The <a href=\"https:\/\/www.amagicsoft.com\/wiki\/mbr-partition-table.html\">Amagicsoft MBR partition table guide<\/a> explains the partition-entry layout and how the starting address and block count determine partition boundaries.<\/p>\n<h3>LBA fields in GPT<\/h3>\n<p>The GUID Partition Table (GPT) uses LBA to locate its metadata and define partition ranges.<\/p>\n<p>On a conventional GPT-partitioned disk, the layout includes:<\/p>\n<table><tbody><tr><td><p><strong>Location<\/strong><\/p><\/td><td><p><strong>Structure<\/strong><\/p><\/td><\/tr><tr><td><p>LBA 0<\/p><\/td><td><p>Protective MBR<\/p><\/td><\/tr><tr><td><p>LBA 1<\/p><\/td><td><p>Primary GPT header<\/p><\/td><\/tr><tr><td><p>Following LBAs<\/p><\/td><td><p>Primary partition-entry array<\/p><\/td><\/tr><tr><td><p>Usable LBA range<\/p><\/td><td><p>Space available for partitions<\/p><\/td><\/tr><tr><td><p>Near the end of the device<\/p><\/td><td><p>Backup partition-entry array<\/p><\/td><\/tr><tr><td><p>Last LBA<\/p><\/td><td><p>Backup GPT header<\/p><\/td><\/tr><\/tbody><\/table>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-f0mlg01 elementor-widget elementor-widget-image\" data-id=\"f0mlg01\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"image.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<img decoding=\"async\" src=\"https:\/\/www.amagicsoft.com\/wp-content\/uploads\/2026\/10\/gpt-disk-layout-lba-positions-to-webp.webp\" title=\"\" alt=\"gpt-disk-layout-lba-positions\" loading=\"lazy\" \/>\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-o3dle1i elementor-widget elementor-widget-text-editor\" data-id=\"o3dle1i\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>The exact usable range depends on the disk layout, logical block size, and the locations reserved for GPT metadata.<\/p>\n<p>GPT partition entries contain 64-bit <code class=\"dtec-inline-code\">StartingLBA<\/code> and <code class=\"dtec-inline-code\">EndingLBA<\/code> fields. Both boundaries are inclusive, so the number of logical blocks in a partition is:<\/p>\n<p><code class=\"dtec-inline-code\">Partition size in blocks = EndingLBA \u2212 StartingLBA + 1<\/code><\/p>\n<p>The GPT header also includes <code class=\"dtec-inline-code\">PartitionEntryLBA<\/code>, which identifies the starting LBA of the associated partition-entry array.<\/p>\n<p>For a field-level explanation of these addresses and the primary and backup headers, see <a href=\"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/gpt-header.html\">Amagicsoft&#8217;s GPT Header guide<\/a>.<\/p>\n<p>The official <a href=\"https:\/\/uefi.org\/specs\/UEFI\/2.11\/05_GUID_Partition_Table_Format.html\" rel=\"nofollow\">UEFI specification, Section 5<\/a>, defines the GPT layout and its address fields. It specifies 64-bit LBAs for GPT, whereas MBR partition entries use 32-bit starting-LBA and size fields.<\/p>\n<h3>Why MBR and GPT have different addressing limits<\/h3>\n<p>With 32-bit sector-address fields, MBR has a commonly encountered capacity boundary of approximately 2 TiB when logical sectors are 512 bytes.<\/p>\n<p>The arithmetic is:<\/p>\n<p><code class=\"dtec-inline-code\">2\u00b3\u00b2 logical blocks \u00d7 512 bytes = 2 TiB<\/code><\/p>\n<p>This is approximately 2.2 trillion bytes in decimal units. The limit comes from the address-field width and the assumed logical sector size; it is not a universal limit for every device or every possible logical block size.<\/p>\n<p>GPT&#8217;s 64-bit LBA fields provide a much larger theoretical address space. Actual usable capacity still depends on the operating system, firmware, drivers, device interface, and partitioning implementation.<\/p>\n<p>Microsoft&#8217;s documentation on <a href=\"https:\/\/learn.microsoft.com\/en-us\/troubleshoot\/windows-server\/backup-and-storage\/support-for-hard-disks-exceeding-2-tb\" rel=\"nofollow\">Windows support for disks exceeding 2 TB<\/a> explains the relationship between the MBR addressing limitation and GPT.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-e5a07ic elementor-widget elementor-widget-heading\" data-id=\"e5a07ic\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">How to Check Logical and Physical Sector Information in Windows<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-pe4ct52 elementor-widget elementor-widget-text-editor\" data-id=\"pe4ct52\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Windows provides a command for querying sector information reported by the storage device and its driver.<\/p>\n<ol><li>Open Command Prompt.<\/li><li>Run <code class=\"dtec-inline-code\">fsutil fsinfo sectorinfo D:<\/code>, replacing <code class=\"dtec-inline-code\">D:<\/code> with the appropriate drive letter.<\/li><li>Examine the reported logical and physical sector information.<\/li><\/ol>\n<p>Microsoft documents this command in <a href=\"https:\/\/learn.microsoft.com\/en-us\/windows-server\/administration\/windows-commands\/fsutil-fsinfo\" rel=\"nofollow\">Fsutil fsinfo<\/a>. Its example output includes fields such as <code class=\"dtec-inline-code\">LogicalBytesPerSector<\/code> and <code class=\"dtec-inline-code\">PhysicalBytesPerSectorForAtomicity<\/code>.<\/p>\n<p>For example, if the system reports <code class=\"dtec-inline-code\">LogicalBytesPerSector : 4096<\/code>, a 4,096-byte logical block size is appropriate for the corresponding LBA-to-byte-offset calculation.<\/p>\n<p>Compare the logical sector size with the reported physical-sector information to understand the device&#8217;s addressing and alignment characteristics. The available fields and values may vary with the Windows version, storage device, and driver.<\/p>\n<p>This command queries sector information; it does not read a particular LBA&#8217;s raw contents or identify the physical location of a file. It is a useful way to verify an input needed for the calculation, not a complete disk-structure analysis.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-g4clw1b elementor-widget elementor-widget-heading\" data-id=\"g4clw1b\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">LBA Limitations and Common Misconceptions<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-vp8jzx4 elementor-widget elementor-widget-text-editor\" data-id=\"vp8jzx4\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>LBA provides a logical address, but several conclusions cannot be drawn from the address alone.<\/p>\n<ul><li><strong>An LBA does not identify a file.<\/strong> The file system&#8217;s metadata is needed to map files and their allocated clusters to the corresponding storage regions.<\/li><li><strong>An LBA is not a physical media address.<\/strong> On an SSD, for example, the device&#8217;s flash translation layer manages the mapping between host-visible logical addresses and internal flash storage.<\/li><li><strong>An LBA does not establish whether data is intact.<\/strong> A readable address, an I\/O error, or a partition-table inconsistency does not by itself prove that a file is recoverable or that a drive has physical damage.<\/li><li><strong>A byte offset depends on the correct logical block size.<\/strong> Using an assumed 512-byte size on a device exposing 4,096-byte logical blocks produces an incorrect result.<\/li><li><strong>Address origins must match.<\/strong> A partition-relative address cannot be treated as a disk-relative address without accounting for the partition&#8217;s starting position and confirming the tool&#8217;s addressing convention.<\/li><\/ul>\n<p>These distinctions are important when diagnosing partition layouts, interpreting disk utilities, or studying file-system structures. LBA supplies the address; additional metadata and device information are needed to interpret what is stored there.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-uwxeb1c elementor-widget elementor-widget-heading\" data-id=\"uwxeb1c\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Conclusion<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-v36hbrb elementor-widget elementor-widget-text-editor\" data-id=\"v36hbrb\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p><strong>Logical block addressing<\/strong> provides a linear way to identify logical storage blocks, but interpreting an LBA requires the correct logical block size and address-space origin. The distinction between logical and physical sectors, the differences between MBR and GPT fields, and the limitations of CHS compatibility values all affect how disk addresses should be understood. For reliable analysis, calculate offsets from verified parameters and interpret them alongside the relevant partition and file-system metadata.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-9gqufod elementor-widget elementor-widget-heading\" data-id=\"9gqufod\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">FAQs<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-tgtcxek faq-no-toc dtec-faq elementor-widget elementor-widget-elementskit-faq\" data-id=\"tgtcxek\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"elementskit-faq.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"ekit-wid-con\" >\n                <div class=\"elementskit-single-faq elementor-repeater-item-w45pn7v\">\n            <div class=\"elementskit-faq-header\">\n                <h3 class=\"elementskit-faq-title\">Is LBA the same as a sector number?<\/h3>\n            <\/div>\n            <div class=\"elementskit-faq-body\">\n                LBA is commonly used as a logical sector number in storage contexts. However, terminology depends on the interface and documentation. The key point is that an LBA identifies a logical block, and its byte offset depends on the block size and address-space origin.            <\/div>\n        <\/div>\n                <div class=\"elementskit-single-faq elementor-repeater-item-brvyrv9\">\n            <div class=\"elementskit-faq-header\">\n                <h3 class=\"elementskit-faq-title\">Does LBA numbering start at zero?<\/h3>\n            <\/div>\n            <div class=\"elementskit-faq-body\">\n                Yes. LBA 0 identifies the first logical block, LBA 1 the second, and so on. Therefore, a device exposing (N) logical blocks has a last valid LBA of <code>N \u2212 1<\/code>, not <code>N<\/code>.            <\/div>\n        <\/div>\n                <div class=\"elementskit-single-faq elementor-repeater-item-81d9vgf\">\n            <div class=\"elementskit-faq-header\">\n                <h3 class=\"elementskit-faq-title\">How do I calculate an LBA&#039;s byte offset?<\/h3>\n            <\/div>\n            <div class=\"elementskit-faq-body\">\n                Multiply the LBA by the logical block size: <code>Byte offset = LBA \u00d7 Logical block size<\/code>. For example, LBA 50 on a device with 512-byte logical blocks begins at byte offset 25,600. Confirm the logical block size before using the result.            <\/div>\n        <\/div>\n                <div class=\"elementskit-single-faq elementor-repeater-item-h9yw0fd\">\n            <div class=\"elementskit-faq-header\">\n                <h3 class=\"elementskit-faq-title\">Why can the same LBA have different byte offsets?<\/h3>\n            <\/div>\n            <div class=\"elementskit-faq-body\">\n                The logical block size may differ between devices or interfaces. LBA 50 begins at byte offset 25,600 with 512-byte blocks but at 204,800 with 4,096-byte blocks. The LBA number alone does not determine the byte position.            <\/div>\n        <\/div>\n                <div class=\"elementskit-single-faq elementor-repeater-item-luucn5g\">\n            <div class=\"elementskit-faq-header\">\n                <h3 class=\"elementskit-faq-title\">What is the difference between LBA and CHS?<\/h3>\n            <\/div>\n            <div class=\"elementskit-faq-body\">\n                LBA identifies a logical block with a linear number. CHS identifies a location using cylinder, head, and sector coordinates. CHS conversion requires geometry parameters, and modern compatibility values do not necessarily describe the drive's actual physical geometry.            <\/div>\n        <\/div>\n                <div class=\"elementskit-single-faq elementor-repeater-item-n5ia28c\">\n            <div class=\"elementskit-faq-header\">\n                <h3 class=\"elementskit-faq-title\">Does LBA identify a file&#039;s physical location?<\/h3>\n            <\/div>\n            <div class=\"elementskit-faq-body\">\n                No. LBA identifies a logical block in an address space, not a filename or a permanent physical media location. File-system metadata maps files to allocated storage regions, and a storage device may translate logical addresses internally.            <\/div>\n        <\/div>\n                <div class=\"elementskit-single-faq elementor-repeater-item-lc5emsj\">\n            <div class=\"elementskit-faq-header\">\n                <h3 class=\"elementskit-faq-title\">Why does MBR have a 2-TiB capacity limitation?<\/h3>\n            <\/div>\n            <div class=\"elementskit-faq-body\">\n                The common boundary arises from 32-bit sector-address fields combined with 512-byte logical sectors. The resulting address space contains 2\u00b3\u00b2 blocks, or 2 TiB. GPT uses wider LBA fields, allowing a much larger theoretical address space.            <\/div>\n        <\/div>\n                <div class=\"elementskit-single-faq elementor-repeater-item-y1fivh4\">\n            <div class=\"elementskit-faq-header\">\n                <h3 class=\"elementskit-faq-title\">Can Windows show the LBA of a specific file?<\/h3>\n            <\/div>\n            <div class=\"elementskit-faq-body\">\n                The <code>fsutil fsinfo sectorinfo<\/code> command reports sector information, not the LBA of a file. Locating file data requires interpreting the partition layout and file-system metadata, and the result may depend on fragmentation and the tool's address convention.            <\/div>\n        <\/div>\n                                <script type=\"application\/ld+json\">{\"@context\":\"https:\/\/schema.org\",\"@type\":\"FAQPage\",\"mainEntity\":[{\"@type\":\"Question\",\"name\":\"Is LBA the same as a sector number?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"LBA is commonly used as a logical sector number in storage contexts. However, terminology depends on the interface and documentation. The key point is that an LBA identifies a logical block, and its byte offset depends on the block size and address-space origin.\"}},{\"@type\":\"Question\",\"name\":\"Does LBA numbering start at zero?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Yes. LBA 0 identifies the first logical block, LBA 1 the second, and so on. Therefore, a device exposing (N) logical blocks has a last valid LBA of <code>N \u2212 1<\/code>, not <code>N<\/code>.\"}},{\"@type\":\"Question\",\"name\":\"How do I calculate an LBA&#039;s byte offset?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"Multiply the LBA by the logical block size: <code>Byte offset = LBA \u00d7 Logical block size<\/code>. For example, LBA 50 on a device with 512-byte logical blocks begins at byte offset 25,600. Confirm the logical block size before using the result.\"}},{\"@type\":\"Question\",\"name\":\"Why can the same LBA have different byte offsets?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"The logical block size may differ between devices or interfaces. LBA 50 begins at byte offset 25,600 with 512-byte blocks but at 204,800 with 4,096-byte blocks. The LBA number alone does not determine the byte position.\"}},{\"@type\":\"Question\",\"name\":\"What is the difference between LBA and CHS?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"LBA identifies a logical block with a linear number. CHS identifies a location using cylinder, head, and sector coordinates. CHS conversion requires geometry parameters, and modern compatibility values do not necessarily describe the drive's actual physical geometry.\"}},{\"@type\":\"Question\",\"name\":\"Does LBA identify a file&#039;s physical location?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"No. LBA identifies a logical block in an address space, not a filename or a permanent physical media location. File-system metadata maps files to allocated storage regions, and a storage device may translate logical addresses internally.\"}},{\"@type\":\"Question\",\"name\":\"Why does MBR have a 2-TiB capacity limitation?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"The common boundary arises from 32-bit sector-address fields combined with 512-byte logical sectors. The resulting address space contains 2\u00b3\u00b2 blocks, or 2 TiB. GPT uses wider LBA fields, allowing a much larger theoretical address space.\"}},{\"@type\":\"Question\",\"name\":\"Can Windows show the LBA of a specific file?\",\"acceptedAnswer\":{\"@type\":\"Answer\",\"text\":\"The <code>fsutil fsinfo sectorinfo<\/code> command reports sector information, not the LBA of a file. Locating file data requires interpreting the partition layout and file-system metadata, and the result may depend on fragmentation and the tool's address convention.\"}}]}<\/script>\n                \n    <\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Logical block addressing (LBA) is a method of identifying storage blocks with sequential numbers instead of cylinder, head, and sector coordinates. LBA 0 identifies the first logical block, LBA 1 identifies the second, and so on. However, an LBA number alone does not determine a byte offset: you also need the logical block size and [&hellip;]<\/p>\n","protected":false},"author":6,"featured_media":58021,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[842],"tags":[841],"class_list":["post-58020","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-disk-partition","tag-knowledge-base"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v25.0 (Yoast SEO v27.9) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Logical Block Addressing (LBA) Explained |Amagicsoft<\/title>\n<meta name=\"description\" content=\"Learn how logical block addressing maps LBA numbers to byte offsets, compare LBA vs. CHS, and understand its role in MBR, GPT, and Windows.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.amagicsoft.com\/pt\/kb\/disk-partition\/lba.html\" \/>\n<meta property=\"og:locale\" content=\"pt_BR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Logical Block Addressing (LBA): How Sector Numbers Work\" \/>\n<meta property=\"og:description\" content=\"Learn how logical block addressing maps LBA numbers to byte offsets, compare LBA vs. CHS, and understand its role in MBR, GPT, and Windows.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.amagicsoft.com\/pt\/kb\/disk-partition\/lba.html\" \/>\n<meta property=\"og:site_name\" content=\"Amagicsoft\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/amagicsoft.2024\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-10-30T06:59:50+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-30T09:03:32+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.amagicsoft.com\/wp-content\/uploads\/2026\/10\/Logical-Block-Addressing-LBA-Explained.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1350\" \/>\n\t<meta property=\"og:image:height\" content=\"760\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Vasilii\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@Amagicsoft\" \/>\n<meta name=\"twitter:site\" content=\"@Amagicsoft\" \/>\n<meta name=\"twitter:label1\" content=\"Escrito por\" \/>\n\t<meta name=\"twitter:data1\" content=\"Vasilii\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. tempo de leitura\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minutos\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html\"},\"author\":{\"name\":\"Vasilii\",\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/#\\\/schema\\\/person\\\/5cc725a7bfa9bc0e962db26a19dfb8c2\"},\"headline\":\"Logical Block Addressing (LBA): How Sector Numbers Work\",\"datePublished\":\"2026-10-30T06:59:50+00:00\",\"dateModified\":\"2026-10-30T09:03:32+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html\"},\"wordCount\":2550,\"publisher\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.amagicsoft.com\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Logical-Block-Addressing-LBA-Explained.webp\",\"keywords\":[\"Knowledge Base\"],\"articleSection\":[\"Disk &amp; Partition\"],\"inLanguage\":\"pt-BR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html\",\"url\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html\",\"name\":\"Logical Block Addressing (LBA) Explained |Amagicsoft\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.amagicsoft.com\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Logical-Block-Addressing-LBA-Explained.webp\",\"datePublished\":\"2026-10-30T06:59:50+00:00\",\"dateModified\":\"2026-10-30T09:03:32+00:00\",\"description\":\"Learn how logical block addressing maps LBA numbers to byte offsets, compare LBA vs. CHS, and understand its role in MBR, GPT, and Windows.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html#breadcrumb\"},\"inLanguage\":\"pt-BR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html#primaryimage\",\"url\":\"https:\\\/\\\/www.amagicsoft.com\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Logical-Block-Addressing-LBA-Explained.webp\",\"contentUrl\":\"https:\\\/\\\/www.amagicsoft.com\\\/wp-content\\\/uploads\\\/2026\\\/10\\\/Logical-Block-Addressing-LBA-Explained.webp\",\"width\":1350,\"height\":760,\"caption\":\"Logical Block Addressing (LBA) Explained\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/kb\\\/disk-partition\\\/lba.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.amagicsoft.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Logical Block Addressing (LBA): How Sector Numbers Work\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/#website\",\"url\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/\",\"name\":\"Amagicsoft\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pt-BR\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/#organization\",\"name\":\"Amagicsoft\",\"url\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.amagicsoft.com\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/cropped-logo_512x512-1.webp\",\"contentUrl\":\"https:\\\/\\\/www.amagicsoft.com\\\/wp-content\\\/uploads\\\/2025\\\/04\\\/cropped-logo_512x512-1.webp\",\"width\":512,\"height\":512,\"caption\":\"Amagicsoft\"},\"image\":{\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/amagicsoft.2024\\\/\",\"https:\\\/\\\/x.com\\\/Amagicsoft\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.amagicsoft.com\\\/zh\\\/#\\\/schema\\\/person\\\/5cc725a7bfa9bc0e962db26a19dfb8c2\",\"name\":\"Vasilii\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pt-BR\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/12fbd3cf5c3fd435565e0ee05fea6fb3ae89413aafdccfb30c0c821c69a44d12?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/12fbd3cf5c3fd435565e0ee05fea6fb3ae89413aafdccfb30c0c821c69a44d12?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/12fbd3cf5c3fd435565e0ee05fea6fb3ae89413aafdccfb30c0c821c69a44d12?s=96&d=mm&r=g\",\"caption\":\"Vasilii\"},\"description\":\"Vasilii is a data recovery specialist with around 10 years of hands-on experience in the field. Throughout his career, he has successfully solved thousands of complex cases involving deleted files, formatted drives, lost partitions, and RAW file systems. His expertise covers both manual recovery methods using professional tools like hex editors and advanced automated solutions with recovery software. Vasilii's mission is to make reliable data recovery knowledge accessible to both IT professionals and everyday users, helping them safeguard their valuable digital assets.\",\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/vasilii-zaitsev-65894b376\\\/\"],\"url\":\"https:\\\/\\\/www.amagicsoft.com\\\/pt\\\/author\\\/vasilii\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Explica\u00e7\u00e3o sobre o Endere\u00e7amento L\u00f3gico de Blocos (LBA) | Amagicsoft","description":"Aprenda como o endere\u00e7amento l\u00f3gico por blocos (LBA) mapeia os n\u00fameros LBA para deslocamentos em bytes, compare o LBA com o CHS e entenda seu papel no MBR, no GPT e no Windows.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.amagicsoft.com\/pt\/kb\/disk-partition\/lba.html","og_locale":"pt_BR","og_type":"article","og_title":"Logical Block Addressing (LBA): How Sector Numbers Work","og_description":"Learn how logical block addressing maps LBA numbers to byte offsets, compare LBA vs. CHS, and understand its role in MBR, GPT, and Windows.","og_url":"https:\/\/www.amagicsoft.com\/pt\/kb\/disk-partition\/lba.html","og_site_name":"Amagicsoft","article_publisher":"https:\/\/www.facebook.com\/amagicsoft.2024\/","article_published_time":"2026-10-30T06:59:50+00:00","article_modified_time":"2026-10-30T09:03:32+00:00","og_image":[{"width":1350,"height":760,"url":"https:\/\/www.amagicsoft.com\/wp-content\/uploads\/2026\/10\/Logical-Block-Addressing-LBA-Explained.webp","type":"image\/webp"}],"author":"Vasilii","twitter_card":"summary_large_image","twitter_creator":"@Amagicsoft","twitter_site":"@Amagicsoft","twitter_misc":{"Escrito por":"Vasilii","Est. tempo de leitura":"12 minutos"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html#article","isPartOf":{"@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html"},"author":{"name":"Vasilii","@id":"https:\/\/www.amagicsoft.com\/zh\/#\/schema\/person\/5cc725a7bfa9bc0e962db26a19dfb8c2"},"headline":"Logical Block Addressing (LBA): How Sector Numbers Work","datePublished":"2026-10-30T06:59:50+00:00","dateModified":"2026-10-30T09:03:32+00:00","mainEntityOfPage":{"@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html"},"wordCount":2550,"publisher":{"@id":"https:\/\/www.amagicsoft.com\/zh\/#organization"},"image":{"@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html#primaryimage"},"thumbnailUrl":"https:\/\/www.amagicsoft.com\/wp-content\/uploads\/2026\/10\/Logical-Block-Addressing-LBA-Explained.webp","keywords":["Knowledge Base"],"articleSection":["Disk &amp; Partition"],"inLanguage":"pt-BR"},{"@type":"WebPage","@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html","url":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html","name":"Explica\u00e7\u00e3o sobre o Endere\u00e7amento L\u00f3gico de Blocos (LBA) | Amagicsoft","isPartOf":{"@id":"https:\/\/www.amagicsoft.com\/zh\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html#primaryimage"},"image":{"@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html#primaryimage"},"thumbnailUrl":"https:\/\/www.amagicsoft.com\/wp-content\/uploads\/2026\/10\/Logical-Block-Addressing-LBA-Explained.webp","datePublished":"2026-10-30T06:59:50+00:00","dateModified":"2026-10-30T09:03:32+00:00","description":"Aprenda como o endere\u00e7amento l\u00f3gico por blocos (LBA) mapeia os n\u00fameros LBA para deslocamentos em bytes, compare o LBA com o CHS e entenda seu papel no MBR, no GPT e no Windows.","breadcrumb":{"@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html#breadcrumb"},"inLanguage":"pt-BR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html"]}]},{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html#primaryimage","url":"https:\/\/www.amagicsoft.com\/wp-content\/uploads\/2026\/10\/Logical-Block-Addressing-LBA-Explained.webp","contentUrl":"https:\/\/www.amagicsoft.com\/wp-content\/uploads\/2026\/10\/Logical-Block-Addressing-LBA-Explained.webp","width":1350,"height":760,"caption":"Logical Block Addressing (LBA) Explained"},{"@type":"BreadcrumbList","@id":"https:\/\/www.amagicsoft.com\/kb\/disk-partition\/lba.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.amagicsoft.com\/"},{"@type":"ListItem","position":2,"name":"Logical Block Addressing (LBA): How Sector Numbers Work"}]},{"@type":"WebSite","@id":"https:\/\/www.amagicsoft.com\/zh\/#website","url":"https:\/\/www.amagicsoft.com\/zh\/","name":"Amagicsoft","description":"","publisher":{"@id":"https:\/\/www.amagicsoft.com\/zh\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.amagicsoft.com\/zh\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pt-BR"},{"@type":"Organization","@id":"https:\/\/www.amagicsoft.com\/zh\/#organization","name":"Amagicsoft","url":"https:\/\/www.amagicsoft.com\/zh\/","logo":{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/www.amagicsoft.com\/zh\/#\/schema\/logo\/image\/","url":"https:\/\/www.amagicsoft.com\/wp-content\/uploads\/2025\/04\/cropped-logo_512x512-1.webp","contentUrl":"https:\/\/www.amagicsoft.com\/wp-content\/uploads\/2025\/04\/cropped-logo_512x512-1.webp","width":512,"height":512,"caption":"Amagicsoft"},"image":{"@id":"https:\/\/www.amagicsoft.com\/zh\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/amagicsoft.2024\/","https:\/\/x.com\/Amagicsoft"]},{"@type":"Person","@id":"https:\/\/www.amagicsoft.com\/zh\/#\/schema\/person\/5cc725a7bfa9bc0e962db26a19dfb8c2","name":"Vasilii","image":{"@type":"ImageObject","inLanguage":"pt-BR","@id":"https:\/\/secure.gravatar.com\/avatar\/12fbd3cf5c3fd435565e0ee05fea6fb3ae89413aafdccfb30c0c821c69a44d12?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/12fbd3cf5c3fd435565e0ee05fea6fb3ae89413aafdccfb30c0c821c69a44d12?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/12fbd3cf5c3fd435565e0ee05fea6fb3ae89413aafdccfb30c0c821c69a44d12?s=96&d=mm&r=g","caption":"Vasilii"},"description":"Vasilii \u00e9 um especialista em recupera\u00e7\u00e3o de dados com cerca de 10 anos de experi\u00eancia pr\u00e1tica na \u00e1rea. Ao longo de sua carreira, ele resolveu com sucesso milhares de casos complexos envolvendo arquivos exclu\u00eddos, unidades formatadas, parti\u00e7\u00f5es perdidas e sistemas de arquivos RAW. Sua experi\u00eancia abrange m\u00e9todos de recupera\u00e7\u00e3o manual usando ferramentas profissionais, como editores hexadecimais, e solu\u00e7\u00f5es automatizadas avan\u00e7adas com software de recupera\u00e7\u00e3o. A miss\u00e3o do Vasilii \u00e9 tornar o conhecimento confi\u00e1vel sobre recupera\u00e7\u00e3o de dados acess\u00edvel tanto para profissionais de TI quanto para usu\u00e1rios comuns, ajudando-os a proteger seus valiosos ativos digitais.","sameAs":["https:\/\/www.linkedin.com\/in\/vasilii-zaitsev-65894b376\/"],"url":"https:\/\/www.amagicsoft.com\/pt\/author\/vasilii"}]}},"_links":{"self":[{"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/posts\/58020","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/comments?post=58020"}],"version-history":[{"count":3,"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/posts\/58020\/revisions"}],"predecessor-version":[{"id":58035,"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/posts\/58020\/revisions\/58035"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/media\/58021"}],"wp:attachment":[{"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/media?parent=58020"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/categories?post=58020"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.amagicsoft.com\/pt\/wp-json\/wp\/v2\/tags?post=58020"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}