Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
with 2.6.39.1 I think so, but as said very seldom and my complete system freezes with those errors so I need to hard reset my machine (and as far as I can see the logging is also broken at that time cause I don't find it in messages back)
My idea (but without logs it's hard to say) this kind of...
I am running this card for quite a while
OS: debian squeeze x64 (with custom kernel, see below)
setup: 5x seagate ST31500341AS 1.5TB in soft raid 6
kernels:
3.0.3
seen no real issues yet, but running it only a couple of weeks
2.6.39.1
I got a complete system freeze very rarely (~ once...
As I -perhaps not so explicitly- mentioned in the post:
I did not notice it at the time ... so my raid functions properly and the file transfer did not stop as far as I know ... performance could have been down any level at that moment but I did not notice it in any case ...
errors are still not 100 percent solved it seems ... but not really noticed this one during the copy process (probably during a copy of ~ 500GB of files to my raid 6)
Dec 5 21:13:11 fileserver kernel: ata15.00: device reported invalid CHS sector 0
Dec 5 21:13:11 fileserver kernel: ata15...
running a linux softraid setup for more then a year now, have seen several disk failures due to bad connectors / kernel issues (at least in the beginning) with my previous motherboard
Never lost a single bit, rebuilds always worked out fine (but I sometimes had to intervene by hand, but again...
I have been following this thread passively waiting for some advice on how to get it working on linux. From kernel 2.6.36 (also rc) it looked quite good but I still had timeouts (also still saw NCQ errors in the log, but not every error seemed to be related to a timeout) for example when...