SandForce is not SanDisk (SanForce has been acquired by LSI, anyway). I’m not sure who manufactured for SandForce – they are described as a fabless manufacturing <http://en.wikipedia.org/wiki/Fabless_semiconductor_company> company. (that’s not fabulous J )
Look them up on Wikipedia. I don’t know where the components for your particular SanDisk SSD were made. It is interesting that the latest supercomputers, just funded by US government bodies, have been designed to use massive amounts of RAM (SSD) rather than an ever-increasing CPU count. It seems to indicate that there are SSDs and SSDs (and probably, controllers). _____ Ian Thomas Victoria Park, Western Australia From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Tuesday, March 25, 2014 12:16 PM To: ozDotNet Subject: Re: [OT] Weird symptoms and SSD Chaps, it's a SanDisk 240MB, which is suspicious regarding your comments! I just went up to MSY and got a replacement, a Kingston this time, not another SanDisk. The shop guy said they'll send the SSD back to be analysed and either repaired or replaced. I told him it was my C: drive so I'll have to reinstall before I can give him the old one. After reading some technical stuff on SSDs several weeks ago and how they work and wear-levelling and the like I became a bit worried and moved the swap file to a HDD in an attempt to cut down the writes. It's actually a bit worrying how SSDs work when you look into them. If the C: drive can stay on life support until the weekend I'll be happy. Luckily the main work I'm on at the moment is inside a VM on a HDD D: drive. Greg On 25 March 2014 14:50, <ben.robb...@jlta.com.au> wrote: My guess is a drive based on a SandForce controller. You’ve described the symptoms I had before my SandForce SDD died a couple of years ago. I was going to replace it with a newer SandForce drive until I Googled a bit and then opted to go with an Intel 510 which used a Marvell controller and have had no problems with it. I’d back up everything you want to keep that is on that drive ASAP. Ben From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of GregAtGregLowDotCom Sent: Tuesday, 25 March 2014 11:26 AM To: ozDotNet Subject: RE: [OT] Weird symptoms and SSD Hi Greg, Always horrible to hear that. What sort of drive was it? Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: <http://www.sqldownunder.com/> www.sqldownunder.com From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Greg Keogh Sent: Tuesday, 25 March 2014 2:00 PM To: ozDotNet Subject: [OT] Weird symptoms and SSD Folks, I have a warning post: Since I installed a fresh Windows 7 on an SSD as Xmas I've been suspicious of how one time in 20 it will stop and say "Bad boot drive" and I have to power off and on again and then it always starts okay. No other symptoms have been observed. Well today, I was shutting down my PC when it blue screened on the way down, it said SERVICE_EXCEPTION. Just to be safe I rebooted it normally to check it was okay. First problem. IE 32-bit shortcut says it's invalid, but I can see the iexplore.exe in the correct place. Double-clicking it does nothing. The 64-bit iexplore.exe tells me "The file or directory is corrupted and unreadable." Then I notice most of my Start menu All Programs are gone. The Administrative Tools menu is empty. I searched for an hour but none of the advice is relevant or useful. Last known good config recover did nothing. I even thought I had a virus, but found no evidence. Finally I did a chkdsk C: /F and rebooted and I saw about 20 repairs (including iexplore.exe) and now it seems to be back to normal. However I suspect the SSD is about to die unpredictably and all of my mysterious symptoms were side effects. I'm just posting this in case it might be useful for someone in a similar situation. Now I'm going to the shops to get a new SSD and psych myself up for a possible Windows reinstall over the whole weekend. At Xmas it took 4 x 12 hour days to get to a satisfactory working state. Greg K This email is intended for the named recipient only. The information it contains may be confidential or commercially sensitive. If you are not the intended recipient you must not reproduce or distribute any part of this email, disclose its contents to any other party, or take any action in reliance on it. If you have received this email in error, please contact the sender immediately and delete the message from your computer.