1 |
On 05/02/2022 22:16, Julien Roy wrote: |
2 |
> I didn't - I typically use the Gentoo and Arch wiki when I need |
3 |
> information, but will keep that in mind. |
4 |
> I noticed, on that page, that there's a big bold warning about using |
5 |
> post-2019 WD Red drives. Sadly, that's exactly what I am doing, my array |
6 |
> is 4xWD60EFAX. I don't know whether that's the cause of the problem. It |
7 |
> does say on the wiki that these drives can't be added to existing |
8 |
> arrays, so it would make sense. Oh well, lesson learned. |
9 |
|
10 |
Ouch. EFAX drives are the new SMR version it seems. You might have |
11 |
been lucky, it might have added okay. |
12 |
|
13 |
The problem with these drives, basically, is you cannot stream data to |
14 |
them. They'll accept so much, fill up their CMR buffers, and then stall |
15 |
while they do an internal re-organisation. And by the time they start |
16 |
responding again, the OS thinks the drive has failed ... |
17 |
|
18 |
I've just bought a Toshiba N300 8TB for £165 as my backup drive. As far |
19 |
as I know that's an okay drive for raid - I haven't heard any bad |
20 |
stories about SMR being sneaked in ... I've basically split it in 2, 3TB |
21 |
as a spare partition for my raid, and 5TB as backup for my 6TB (3x3) |
22 |
raid array. |
23 |
|
24 |
Look at creating a raid-10 from your WDs, or if you create a new raid-5 |
25 |
array from scratch using --assume-clean then format it, you're probably |
26 |
okay. Replacing SMRs with CMRs will probably work fine so if one of your |
27 |
WDs fail, you should be okay replacing it, so long as it's not another |
28 |
SMR :-) (If you do a scrub, expects loads of parity errors first time |
29 |
:-) but you will probably get away with it if you're careful. |
30 |
|
31 |
Cheers, |
32 |
Wol |