1 |
On Thu, Mar 3, 2022 at 1:38 PM Dale <rdalek1967@×××××.com> wrote: |
2 |
> |
3 |
> Julien Roy wrote: |
4 |
> > This is exactly what happened to me. I unknowingly bought SMR drives |
5 |
> > (I didn't know the difference, but the drives were "RAID" rated, |
6 |
> > whatever that means. SMR drives obviously aren't "RAID" anything.) |
7 |
> > Well, when was the time to expand my RAID, it wouldn't work. |
8 |
> > Needless to say, I will not be buying any product from WD anymore. |
9 |
> > |
10 |
> > Julien |
11 |
> > |
12 |
> > |
13 |
> |
14 |
> From my understanding, it wasn't just WD. I don't think any of them |
15 |
> alerted people as to what they were getting. I recently bought a WD and |
16 |
> will again because I could have easily bought a Seagate or any other |
17 |
> brand that was SMR without knowing it. WD just so happened to be the |
18 |
> first one I found with a good price is all. |
19 |
> |
20 |
> Still, I don't like that any of them pulled this stealth release tho. |
21 |
> For most, it most likely didn't matter but for some, it was a disaster. |
22 |
> Possibly a costly disaster at that. |
23 |
> |
24 |
> We learned tho. |
25 |
> |
26 |
> Dale |
27 |
|
28 |
Truthfully I don't think WD or the others understood the problem early |
29 |
on. At first they denied there was a problem, and actually I don't think |
30 |
there really is a problem setting up a RAID system using an SMR drive. |
31 |
Where the problem showed up was during resivering which isn't |
32 |
something everyone does every day. It was during resilvering that |
33 |
the SMR drives failed, and once WD (and others) saw the data |
34 |
WD rebranded the Red series in Red and Red Plus, with the Plus |
35 |
version being CMR. I've resilvered using a couple of Red Plus 4TB |
36 |
drives and everything is good so far. |
37 |
|
38 |
My 2 cents, |
39 |
Mark |