Shoot, my brain is fried. Three months, not two. /:
On 10/17/21 9:21 AM, Phil Turmel wrote:
Hi Romulo,
On 10/16/21 9:11 PM, Romulo Albuquerque wrote:
Hi All,
I've 5 disks array 3TB each, but one of the disks /dev/sdb can't be
recognized.
Using mdadm - v3.4 - 28th January 2016 on Debian GNU/Linux 9.11
(stretch).
So, I tried to assemble the array with 4 disks, but it didn't work,
see below >
sudo mdadm --assemble --verbose /dev/md0 /dev/sd[acde]
mdadm: looking for devices for /dev/md0
mdadm: /dev/sda is identified as a member of /dev/md0, slot 0.
mdadm: /dev/sdc is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdd is identified as a member of /dev/md0, slot 3.
mdadm: /dev/sde is identified as a member of /dev/md0, slot 4.
mdadm: ignoring /dev/sdc as it reports /dev/sda as failed
mdadm: ignoring /dev/sdd as it reports /dev/sda as failed
mdadm: ignoring /dev/sde as it reports /dev/sda as failed
mdadm: no uptodate device for slot 1 of /dev/md0
mdadm: no uptodate device for slot 2 of /dev/md0
mdadm: no uptodate device for slot 3 of /dev/md0
mdadm: no uptodate device for slot 4 of /dev/md0
mdadm: added /dev/sda to /dev/md0 as 0
mdadm: /dev/md0 assembled from 1 drive - not enough to start the array.
[trim /]
This didn't work because /dev/sda dropped out of your array back in the
middle of July. You were running degraded for two months before
/dev/sdb dropped out.
If /dev/sdb is totally dead, you will have to use a two-month-old device
to revive your array, with data corruption for anything written in the
past two months. Add a --force to your assemble command to do so.
I recommend trying harder to recover /dev/sdb onto another device. Then
assemble that replacement with the other three, leaving out /dev/sda.
Also using --force.
Finally, investigate why /dev/sda dropped out in July, and why you
didn't get an email from mdmon. (Timeout mismatch for the former,
perhaps, and incomplete configuration for the latter, likely.)
Phil
