Thanks, that looks like it did the trick. Yes, I was already aware
that sdc needs to be replaced at some point, just not during my OS
upgrade.
root@jowahome:~# mdadm --assemble --update=name --name=md0 /dev/md0
/dev/sdb1 /dev/sdc1
mdadm: /dev/md0 has been started with 2 drives.
root@jowahome:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
[raid4] [raid10]
md0 : active (auto-read-only) raid1 sdc1[0] sdb1[2]
2930133824 blocks super 1.2 [2/2] [UU]
unused devices: <none>
On Thu, Aug 31, 2017 at 7:22 AM, Andreas Klauer
<Andreas.Klauer@xxxxxxxxxxxxxx> wrote:
> On Thu, Aug 31, 2017 at 06:06:42AM -0600, Joel Walberg wrote:
>> ## root@jowahome:~# mdadm -A /dev/md2014 /dev/sdc1 /dev/sdb1
>> ## mdadm: unexpected failure opening /dev/md2014
>> ## root@jowahome:~# mdadm -A /dev/md/md2014 /dev/sdc1 /dev/sdb1
>> ## mdadm: unexpected failure opening /dev/md2014
>
> Could be related to the name. Try assembling it as /dev/md0.
>
> If that works, change the name to something that isn't md<number>.
>
> (--assemble --update=name --name=xyz I guess)
>
>> ## SMART Extended Self-test Log Version: 1 (1 sectors)
>> ## Num Test_Description Status Remaining
>> LifeTime(hours) LBA_of_first_error
>> ## # 1 Short offline Completed without error 00%
>> 21086 -
>
> This is a personal preference... but you should run self tests
> more regularly (automated, smartd) to detect HDD errors in time.
>
>> ## 5 Reallocated_Sector_Ct PO--CK 097 097 010 - 3344
>
> That's quite a lot of reallocated sectors already.
> This is the kind of drive that will make your rebuilds fail.
>
> I would consider replacing such a drive / putting it to some use
> where data loss is acceptable.
>
> Regards
> Andreas Klauer
--
___________________________
Joel A. Walberg
joel.walberg@xxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
