<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>To follow up on how i managed to solve this...  The original
      failed drive was a WD 4T.  I tried two different Toshiba drives
      (8T and 4T) and neither were recognized by the Dell BIOS.   So I
      tried WD.   Their 8T was recognized by the BIOS, but its size was
      misidentified as 0T and the kernel refused to recognize it as a
      valid disk.   WD 6T, however, worked fine.  So I've build a new
      array with 6T WD.  Why the WD works and Toshiba didn't will remain
      a mystery.  I don't see anything significant in their spec sheets.<br>
    </p>
    <p>In any case, Hurray for RAID1 - I didn't lose any data and didn't
      have to resort to backups.</p>
    <p>Steve</p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 2023-10-15 8:50 PM, Steve Tynor via
      Ale wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:0100018b35f68f44-5d69f0ab-6200-4156-8c23-a5965d1a7573-000000@email.amazonses.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p>Thanks Jim.    It's a software RAID via mdadm.   The array was
        originally built with Ubuntu 18 - have kept it going through
        various system upgrades - now on Ubuntu 22.  And you are right -
        I misspoke when calling it LVM RAID - if my notes are right from
        back then, I created it via the "full disk" partitions:</p>
      <p>    mdadm --create --verbose /dev/md0 --level=1
        --raid-devices=2 /dev/sdb1 /dev/sdc1<br>
      </p>
      <p>When these errors start happening, it brings the machine to its
        knees.    Anything I can do to "repair" the array to avoid those
        segments?  Even when the errors are happening, mdstat looks
        healthy:</p>
      <p>   ricotta:~> cat /proc/mdstat <br>
           Personalities : [raid1] [linear] [multipath] [raid0] [raid6]
        [raid5] [raid4] [raid10] <br>
           md0 : active raid1 sdc1[0] sdb1[1]<br>
                 3906884608 blocks super 1.2 [2/2] [UU]<br>
                 bitmap: 10/30 pages [40KB], 65536KB chunk<br>
        <br>
           unused devices: <none><br>
      </p>
      <p>For now I've just removed the errant disk from the array again
        pending inspiration...<br>
      </p>
      <p>Steve</p>
      <p><br>
      </p>
      <div class="moz-cite-prefix">On 2023-10-15 5:47 PM, Jim Kinney
        wrote:<br>
      </div>
      <blockquote type="cite"
cite="mid:CAEo=5Pyx8uqv6OqLuCKuywEXTChM7rkkx1=h1Jrndam3yJHiYQ@mail.gmail.com">
        <meta http-equiv="content-type"
          content="text/html; charset=UTF-8">
        <div dir="auto">The Errors look like the raid recognized a
          block/segment failure on sdb and handled it by redirects to a
          new location and copied in the data from the mirror.
          <div dir="auto"><br>
          </div>
          <div dir="auto">Is the the drive bad? Not yet. Sectors do fail
            in time. </div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">But raid system specified sdb, not sdb1, so
            the raid subsystem is either using the entire drive for sdb
            or there's a raid controlling hardware or software that is
            doing the low level hardware management and that layer needs
            to be worked on to recognize the new drive. It really sounds
            like there's a raid controller in there somewhere.</div>
        </div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Sun, Oct 15, 2023, 2:40
            PM Steve Tynor via Ale <<a href="mailto:ale@ale.org"
              moz-do-not-send="true" class="moz-txt-link-freetext">ale@ale.org</a>>
            wrote:<br>
          </div>
          <blockquote class="gmail_quote"
style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div>
              <p>And I guess one more question...  I was not able to
                learn much about these errors from the interwebs, but
                perhaps they don't necessarily suggest an actual drive
                failure but some sort of soft problem with the array -
                perhaps repartition the bad drive and add it back to the
                array and hope the errors don't come back?   The errors
                look scary to me, but most people on this list have a
                lot more sysadm chops than I do...</p>
              <p><font face="monospace">Oct 13 21:11:48 ricotta kernel:
                  [714090.323895] md/raid1:md0: read error correct</font><br>
                <font face="monospace">ed (8 sectors at 7339070832 on
                  sdb1)</font><br>
                <font face="monospace">Oct 13 21:12:01 ricotta kernel:
                  [714104.108320] md/raid1:md0: redirecting sector</font><br>
                <font face="monospace"> 7338806424 to other mirror: sdb1</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.347389] ata2.00: exception Emask 0x0 SAc</font><br>
                <font face="monospace">t 0x140000 SErr 0x0 action 0x0</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.347501] ata2.00: irq_stat 0x40000008</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.347558] ata2.00: failed command: READ FP</font><br>
                <font face="monospace">DMA QUEUED</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.347621] ata2.00: cmd 60/78:90:98:5c:71/0</font><br>
                <font face="monospace">1:00:b5:01:00/40 tag 18 ncq dma
                  192512 in</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.347621]          res 41/40:00:88:5d:71/0</font><br>
                <font face="monospace">0:00:b5:01:00/00 Emask 0x409
                  (media error) <F></font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.347809] ata2.00: status: { DRDY ERR }</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.347860] ata2.00: error: { UNC }</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.350759] ata2.00: configured for UDMA/133</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.350801] sd 1:0:0:0: [sdb] tag#18 FAILED </font><br>
                <font face="monospace">Result: hostbyte=DID_OK
                  driverbyte=DRIVER_OK cmd_age=7s</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.350811] sd 1:0:0:0: [sdb] tag#18 Sense K</font><br>
                <font face="monospace">ey : Medium Error [current] </font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.350817] sd 1:0:0:0: [sdb] tag#18 Add. Se</font><br>
                <font face="monospace">nse: Unrecovered read error -
                  auto reallocate failed</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.350824] sd 1:0:0:0: [sdb] tag#18 CDB: Re</font><br>
                <font face="monospace">ad(16) 88 00 00 00 00 01 b5 71 5c
                  98 00 00 01 78 00 00</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.350827] blk_update_request: I/O error, d</font><br>
                <font face="monospace">ev sdb, sector 7339072664 op
                  0x0:(READ) flags 0x0 phys_seg 47 prio class 0</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.351018] md/raid1:md0: sdb1: rescheduling</font><br>
                <font face="monospace"> sector 7338806424</font><br>
                <font face="monospace">Oct 13 21:12:09 ricotta kernel:
                  [714111.351111] ata2: EH complete</font><br>
                <font face="monospace">Oct 13 21:12:20 ricotta kernel:
                  [714122.174015] md/raid1:md0: redirecting sector</font><br>
                <font face="monospace"> 7338806424 to other mirror: sdb1</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.594981] ata2.00: exception Emask 0x0 SAc</font><br>
                <font face="monospace">t 0x1000 SErr 0x0 action 0x0</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.595089] ata2.00: irq_stat 0x40000008</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.595146] ata2.00: failed command: READ FP</font><br>
                <font face="monospace">DMA QUEUED</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.595209] ata2.00: cmd 60/78:60:98:5c:71/0</font><br>
                <font face="monospace">1:00:b5:01:00/40 tag 12 ncq dma
                  192512 in</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.595209]          res 41/40:00:78:5d:71/0</font><br>
                <font face="monospace">0:00:b5:01:00/00 Emask 0x409
                  (media error) <F></font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.603898] ata2.00: status: { DRDY ERR }</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.608263] ata2.00: error: { UNC }</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.615103] ata2.00: configured for UDMA/133</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.615136] sd 1:0:0:0: [sdb] tag#12 FAILED </font><br>
                <font face="monospace">Result: hostbyte=DID_OK
                  driverbyte=DRIVER_OK cmd_age=4s</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.615145] sd 1:0:0:0: [sdb] tag#12 Sense K</font><br>
                <font face="monospace">ey : Medium Error [current] </font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.615151] sd 1:0:0:0: [sdb] tag#12 Add. Se</font><br>
                <font face="monospace">nse: Unrecovered read error -
                  auto reallocate failed</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.615158] sd 1:0:0:0: [sdb] tag#12 CDB: Re</font><br>
                <font face="monospace">ad(16) 88 00 00 00 00 01 b5 71 5c
                  98 00 00 01 78 00 00</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.615162] blk_update_request: I/O error, d</font><br>
                <font face="monospace">ev sdb, sector 7339072664 op
                  0x0:(READ) flags 0x0 phys_seg 47 prio class 0</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.619470] md/raid1:md0: sdb1: rescheduling</font><br>
                <font face="monospace"> sector 7338806424</font><br>
                <font face="monospace">Oct 13 21:12:24 ricotta kernel:
                  [714126.623671] ata2: EH complete</font><br>
                <br>
              </p>
              <div>On 2023-10-15 3:01 PM, Steve Tynor via Ale wrote:<br>
              </div>
              <blockquote type="cite">
                <p>Forgot to include: the original WD drives are also
                  "AF", so I think that rules out sector size
                  incompatibility.</p>
                <p>Steve</p>
                <p><br>
                </p>
                <div>On 2023-10-15 2:16 PM, Steve Tynor via Ale wrote:<br>
                </div>
                <blockquote type="cite">
                  <p>I'm not certain how to be sure.  A quick duckduckgo
                    search suggests that 4k native sector also being
                    marketed as "Advanced Format" - is that right?  
                    Looking at the Toshiba spec page, I see AF listed as
                    "Yes" for the 8T (the first drive I tried) and "No"
                    for the 4T (which also didn't work).</p>
                  <p>    <a
href="https://storage.toshiba.com/docs/support-docs/toshiba_n300_salessheet_english_07-27-21.pdf?Status=Master"
                      target="_blank" rel="noreferrer"
                      moz-do-not-send="true"
                      class="moz-txt-link-freetext">https://storage.toshiba.com/docs/support-docs/toshiba_n300_salessheet_english_07-27-21.pdf?Status=Master</a><br>
                  </p>
                  <p>Steve<br>
                  </p>
                  <div>On 2023-10-15 2:08 PM, Robert Tweedy via Ale
                    wrote:<br>
                  </div>
                  <blockquote type="cite"> <font size="2" face="Arial">Hi
                      Steve,<br>
                      <br>
                      Out of curiosity, are the new drives "4K native"
                      sector drives, and is this the same as the old
                      drives you're replacing? If the system's old
                      enough its BIOS might not support that & is
                      expecting to have "512n" (512-native) or "512e"
                      (512-emulated) sector-size drives.<br>
                      <br>
                      Other than that, I'm not sure what it could be
                      beyond being Toshiba brand (which I've personally
                      never had good experience with, but that's only
                      anecdotal).<br>
                      <br>
                      -Robert<br>
                    </font><br>
                  </blockquote>
                  <br>
                  <fieldset></fieldset>
                  <pre>_______________________________________________
Ale mailing list
<a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer"
                  moz-do-not-send="true" class="moz-txt-link-freetext">Ale@ale.org</a>
<a href="https://mail.ale.org/mailman/listinfo/ale" target="_blank"
                  rel="noreferrer" moz-do-not-send="true"
                  class="moz-txt-link-freetext">https://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a href="http://mail.ale.org/mailman/listinfo" target="_blank"
                  rel="noreferrer" moz-do-not-send="true"
                  class="moz-txt-link-freetext">http://mail.ale.org/mailman/listinfo</a>
</pre>
                </blockquote>
                <br>
                <fieldset></fieldset>
                <pre>_______________________________________________
Ale mailing list
<a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer"
                moz-do-not-send="true" class="moz-txt-link-freetext">Ale@ale.org</a>
<a href="https://mail.ale.org/mailman/listinfo/ale" target="_blank"
                rel="noreferrer" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a href="http://mail.ale.org/mailman/listinfo" target="_blank"
                rel="noreferrer" moz-do-not-send="true"
                class="moz-txt-link-freetext">http://mail.ale.org/mailman/listinfo</a>
</pre>
              </blockquote>
            </div>
            _______________________________________________<br>
            Ale mailing list<br>
            <a href="mailto:Ale@ale.org" target="_blank"
              rel="noreferrer" moz-do-not-send="true"
              class="moz-txt-link-freetext">Ale@ale.org</a><br>
            <a href="https://mail.ale.org/mailman/listinfo/ale"
              rel="noreferrer noreferrer" target="_blank"
              moz-do-not-send="true" class="moz-txt-link-freetext">https://mail.ale.org/mailman/listinfo/ale</a><br>
            See JOBS, ANNOUNCE and SCHOOLS lists at<br>
            <a href="http://mail.ale.org/mailman/listinfo"
              rel="noreferrer
            noreferrer" target="_blank" moz-do-not-send="true"
              class="moz-txt-link-freetext">http://mail.ale.org/mailman/listinfo</a><br>
          </blockquote>
        </div>
      </blockquote>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Ale mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ale@ale.org">Ale@ale.org</a>
<a class="moz-txt-link-freetext" href="https://mail.ale.org/mailman/listinfo/ale">https://mail.ale.org/mailman/listinfo/ale</a>
See JOBS, ANNOUNCE and SCHOOLS lists at
<a class="moz-txt-link-freetext" href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a>
</pre>
    </blockquote>
  </body>
</html>