1 |
On 07/29/2015 08:34 AM, Volker Armin Hemmann wrote: |
2 |
> Am 29.07.2015 um 16:52 schrieb Daniel Frey: |
3 |
>> On 07/28/2015 12:04 AM, Volker Armin Hemmann wrote: |
4 |
>>> you know - this does not sound like ssd failure. Most SSDs bomb out by |
5 |
>>> just becoming completely unacessible. |
6 |
>>> |
7 |
>>> dmesg errors? |
8 |
>> Filled with /dev/sda errors when it "failed". |
9 |
> |
10 |
> oh the joy. |
11 |
|
12 |
Yeah. I don't remember what the exact error message was, other than it |
13 |
was filled with "can't read" and "can't write" in the messages. |
14 |
|
15 |
Booting from USB worked fine. Compiling while booted from USB worked |
16 |
until I chroot'ed to the failed SSD. Then a bunch of segfaults and other |
17 |
weird errors. |
18 |
|
19 |
I've seen this before both at home and work, where SSDs do this with no |
20 |
warning. IMO they're way too unreliable. I don't have one in my server |
21 |
or workstation at home. I had one in my server and it lasted two years |
22 |
before similar issues above. It (server SSD) was replaced with a |
23 |
spinning disk 3 years ago and it's still running today. I'm pretty sure |
24 |
if I replaced it with another SSD it would've failed already. |
25 |
|
26 |
> |
27 |
>> |
28 |
>>> are you using ecc ram? |
29 |
>> Nope. |
30 |
>> |
31 |
>>> if not - maybe, just maybe it is your ram at fault. The stuff the kernel |
32 |
>>> sends and the stuff that end on the ssd might not be identical. |
33 |
>>> |
34 |
>> Ran memtest overnight on it, no errors. |
35 |
>> |
36 |
>> Dan |
37 |
>> |
38 |
>> |
39 |
>> |
40 |
> |
41 |
> I had ram that passed memtest - and zfs detected errors. Went ecc ram, |
42 |
> no more errors. |
43 |
> |
44 |
> With ram hammer as latest attack vector, ecc is even more worth its money. |
45 |
> |
46 |
|
47 |
ECC is fine and dandy, but this motherboard doesn't support it. It's a |
48 |
desktop board from 2008. All it does is a frontend for mythtv, nothing else. |
49 |
|
50 |
|
51 |
|
52 |
Dan |