• Content count

  • Joined

  • Last visited

Everything posted by JaredDM

  1. Reliability of ST2000LM007

    Run away, RUN AWAY!!!! That model is a Rosewood series of hard drive from Seagate. They are as cheap junk as cheap can be. They are so cheap they didn't even put a full metal top cover on there. The only thing keeping the dirty outside air out from contaminating the drive is the sticker on the top. Plus, these are an absolute nightmare for data recovery. They seem to have soft platter surfaces that scratch very easily, and they rarely work after heads are replaced even by professionals. We see a lot of them already coming in for data recovery. Most just have the heads stuck to the platters, so those are easy enough recoveries, but when the heads fail it could be a total loss of data. If you did buy one of these, I'd recommend you have two backups.
  2. I'm working on a project to deconstruct how a number of common RAID controllers write metadata to the disks to keep track of the RAID config. Working in pro data recovery, I'm doing this to try to speed up our work when various array types come in and we have to reverse engineer them. So I'm just curious what you all think are the most common controllers out there. Currently, I've got the full spread of Areca cards figured out, as well as Perc 6, Perc H710, HP Smart Array cards, a number of Adaptec cards, LSI MegaRAID, etc.. I'm just looking for other common ones typically used in small to medium business servers. I'm not so concerned about big enterprise stuff, as they usually are smart enough to have a backup. I just figure it's better to reverse engineer them now than have to race against the clock when 20 drives show up for recovery and it needs to be done in two days. So what cards have you seen used a lot?
  3. Most Common RAID Controllers

    Thanks, I added those to my list of cards to bring in and analyze. If anyone else has other common ones to suggest, please let me know.
  4. RAID using WD Velocity Raptor HD's:

    All HDDs and all SSDs can be used in RAID. The only reason some drives are "recommended" for RAID when others aren't recommended has to do with their ability to handle vibration. They assume you'll be putting a bunch of them into an enclosure or rack together where the vibration might build up. That and you should never use Green drives in a RAID as the power saving functions can cause chaos. For a two drive array vibration is really a moot point. There's no reason not to use a couple Velociraptors in RAID, but unless you use an actual hardware controller there's also not going to be much benefit. Honestly you'd be 100x better off just investing the money into a good SSD. As to doing a RAID of SSDs you're unlikely to see much benefit to a RAID 0 or RAID 5 as far as speed is concerned. Most likely the extra latency the controller would negate any benefit of the RAID. It might even end up slower than a single SSD in some cases. RAID 1 is good for redundancy in case one fails (however you still need a backup in case of logical corruption), so if uptime is important you might consider that.
  5. If you look at David Johnson's posts, nearly half are spamming Stellar's software. So this isn't an "unbiased" opinion, it's just SPAM from some clown who either works for Stellar or is getting paid to SPAM for them. Flagging it now. The only thing Stellar is "stellar" at, in my opinion, is lying to people while spamming every forum on the planet.
  6. Deleted accidental duplicate post.
  7. I've seen issues at times where USB controllers (even ones built into the motherboard) start to go unstable and occasionally will disconnect for a split second. This can cause errors in the data if it was currently writing to the disk. Especially, it would cause such issues if it was only modifying a large file such as a database. Doing nothing but data recovery work, we actually tend to wear out USB controllers and always keep a few add-in cards handy for when they go. So I've seen them act quite strange when they are on the way out.
  8. In that case, perhaps you can try this company: http://www.chandigarhdatarecovery.com/ I've had quite a few conversations with Amarbir, the owner, on various chat forums. He seems to know his stuff.
  9. They are ripping you off. I've seen plenty of $2K+ cases quoted by Kroll and Drivesavers that we recovered for under $1,000. A few of which they had deemed "unrecoverable" and given up on. The problem is they are big companies with lots of employees. And of all these employees only about 1/4 are actually doing data recovery work. The rest are all just marketing, sales, customer service, SEO, advertising, etc. You're much better off using a smaller company with only a handful of employees and most are all are actually the technicians.
  10. Here at our data recovery lab for a dropped WD you can pretty much bet that the price will be $650 + cost of donor parts. If the drive isn't clicking it's possible that the cost could even be a bit less. Just to give you a baseline. From the way you spell "centre" I'd assume you're in the UK (we spell it center here in the USA)? If so I'd recommend you try out this company: http://www.pcimage.co.uk I've had discussions with the lead technician there and he's very good. Well respected even among data recovery pros.
  11. HGST's consumer grade drives are rock solid for reliability, and their enterprise drives are really reliable. Working in pro data recovery we strain our drives to the max with constantly moving around full HDD's worth of customer data, image files, etc. For our high-speed RAID arrays which we use to store and process all this data, HGST enterprise drives are all we use because we'll kill pretty much anything else in a matter of months. As to their helium filled drives, we generally don't use those. While I'm sure they are reliable, part of the reason they went with the helium is so they could stack more platters and thinner ones in there. More platters = more read/write heads = more chances one will fail. But, even most enterprise customers aren't going to strain drives like we do here. We move Tb's of data around every single day.
  12. First off, full disclaimer: I work in professional data recovery, so I'm not really looking for a company to use. I'm also not looking to SPAM or give a shout out to my company here. I find that I'm constantly amazed how people will spend thousands of dollars at companies (I won't name them here, but I'm sure you've heard of them) who in my opinion are sub-par at actually performing data recovery. Yet more affordable companies, who do better work and regularly recover cases the big companies gave up on, can't seem to compete well on a national scale. I've generally just attributed it to the marketing budget of these few larger companies, but maybe it's something else. I'm just trying to understand why IT professionals, such as yourselves, choose one company over the others. Is it their pricing, discount or referral commissions, reputation, years in business, or something else? I welcome any feedback here.
  13. Who do you use for data recovery, and why?

    OK, that doesn't exactly answer my question about what makes you choose them over other companies. Is it because it's not your decision that you mention the contract?
  14. Not too long ago I recovered a failed 2.1Gb Quantum Fireball that was still in operation in a manufacturing environment. Amazingly enough I found another working one on ebay to replace the failed read/write heads and recover all the data.
  15. Basically how the SSD part of the SSHD works is twofold. First, it acts as a write buffer temporarily storing data write operations and queuing them for later writing to the platters. Then it acts as a commonly accessed sector cache for faster read operations from commonly accessed files such as those used by the OS. How exactly the drive decides which sectors are stored in the cache will vary by manufacturer, model, firmware, etc. and it's not exactly publically posted anywhere. But, suffice to say the read cache on the SSD starts out empty and initially will operate around the same speed as a normal HDD. After some time, it'll begin to mark off blocks of sectors that are being regularly accessed and a duplicate of these sectors will be cached in the SSD side for faster accessing. It basically learns your behavior. So as already mentioned, there's no way to separate the SSD portion or even to make the system treat it any differently than a standard HDD. The hybrid functions are all internal to the drive and completely automatic.