California Hard Disk Drive Data Recovery Services

DTI Data Recovery is a full service hard drive repair company. Unlike many of our competitors, DTI actually does run a class 100 clean room. We often get calls from people all over the world, but especially in the United States. Even though our primary clean room lab is located in Florida, many people send us their hard disk drives via Fed Ex, UPS, Postal Service and DHL.

California Data Recovery Services And Hard Disk Repair

There certainly are a few real data recovery companies in California, but unfortunately for most people they offer pricing that is quoted in a range. That means you will get a quote of $1,500 to $3,000 for data recovery. DTI on the other hand offers flat rate pricing for almost all data recovery except RAID Array Recovery, Exchange Server Recovery, or SQL repair. Any type of single hard drive recovery whether it is a laptop hard disk or an external TB drive, you will get an upfront quote.

Another significant difference between DTI and other California Data Recovery Companies is our no data no charge, no fix no fee data guarantee. This simply means that you won’t pay us a cent unless we recovery your data.

Check out these local California Data Recovery Pages for more information:

Los Angeles Data Recovery Services CA
San Diego Data Recovery Services CA
San Francisco Data Recovery Services CA
San Jose Data Recovery Services CA

24 Hour Hard Drive Recovery & Server/RAID Recovery Hotline:
Toll Free 1-866-438-6932 or direct 1-727-345-9665.

Extended Software Support:
8 AM to 11 PM EST 7days a week!

SNAP OS Data Recovery Super Block

SNAP Operating System File Recovery Through The Super Block

Recovering a single file from a SNAP OS Part 2

Last week we discussed how to find the file name on a SNAP OS file system. Using a sector editor we searched the hard disk drive for the file name. Once we found the file name I broke down the on disk data structure format for a directory/file entry.  Among the many elements of the structure the most important in determining where the data for the file is stored is the inode number. In this weeks installment we will discover how to use the on disk data structure called the super block. This is the key to the entire file system and is essential if we are to find the data related to this file name.

In order to find the super block, we must first understand how the SNAP OS positions itself on a drive. In windows the basic element of storage is a cluster. Standard cluster size for an NTFS drive is 4096 bytes, or eight (8) sectors. For SNAP OS the basic element of storage is a block. Standard block size for SNAP OS is 8192 bytes or sixteen 16 sectors. Using the block as a basis for storage, we then have groupings of blocks. These groupings of blocks are called cylinder groups. The on disk layout of a cylinder group is as follows.

Cylinder Group On Disk Layout

All blocks are relative to the beginning of the cylinder group.

• Super Block: Block 0: This block houses a copy of the on-disk structure of the super block
• Cylinder Group: Block 1:  On-disk structure of the cylinder group
• Inodes: Block 2 – (2 + n)  Inode StorageEach inode is 128 bytes, therefore 4 inodes per sector, or 64 inodes per block.
• Data Blocks: Blocks (2 + n)  - (end of cylinder group)  All remaining blocks to the end of the cylinder group are data blocks.

Applying real world numbers

In order to help illustrate how all of this works together, let’s take the 2003STEP.PDF example and apply it to our on disk definitions.

First of all, we must find the super block. The best way to do that, is to find the first cylinder group using the magic number I spoke of in my article “SNAP RAID Recovery Using SNAP OS”. The magic number for the cylinder group is 0×550209.  So, using WinHex as my sector editor, I plug that value into the “Hex Search” field and run the search.  In this case the Cylinder Group is stored at sector 48.  Now, we know that the Cylinder Group data structure is stored in relative block 1, and we also know that a copy of the super block is stored in relative block 0. The size of the blocks is 8K, so, we can count back 16 sectors, or 8K and find a copy of the super block.  

So, a copy of the super block is stored at sector 32.  There are some data elements within the super block that will help us identify the exact placement of the inode we are looking for. These elements are as follows: (Remember the numbers are for this real life situation only, your numbers may differ because of disk size, formatting flags etc.)

Super Block Offset:               2

Cylinder Block Offset:          3

Inode Block Offset                4

Data Block Offset                  16

The above numbers are relative to the beginning of the volume. Therefore we can find the beginning of the volume by using the Super Block offset.  The Super Block is stored on block two, or translated to sectors, sector 32. If we subtract 2 blocks, to find block zero, which is the beginning of the volume we will find the beginning of the drive.  This is important since many of the SNAP OS volumes I work on are RAID-ed. There is a great deal of extraneous data when dealing with RAIDs, however, using this formula, we can easily find the beginning of the drive on a destriped RAID set.

Secondly, and more importantly, we can determine the total inodes per cylinder group.  As defined before, we know that there are 64 inodes per block.   In our real world example we can see that the inode block starts at relative block 4, and the data block starts at relative block 16.  If we subtract 4 from 16 we know that there are 12 blocks of storage per cylinder group.   We know that there are 64 inodes per block, times12 blocks, or 768 inodes per cylinder group.  There is a data element in the super block that tells us the inodes per cylinder group.  If we take our previous calculation, and it matches the super block data element, then we know that our file system is aligned.  In this case they both match.

Now, if we know that we have 768 inodes per cylinder group, and the current inode we are looking for is 1015297, we can divide the inode we are looking for, by total inodes per cylinder group to find the cylinder group which house our inode. That value 1322.   We then do the mod of the same values to tell us which inode within the cylinder group is the one we are looking for.  That value is 1.  So, we can say in cylinder group, 1322, inode 1, we have the inode we are looking for.

Lastly, how do we find Cylinder Group 1322?  The size of the Cylinder Group is the size of the data group plus 64 sectors.  So, in my case, the data group was 1024 blocks, or 16,384 sectors.  You add 64 sectors to that and you have each cylinder at 16,448 sectors.  One note, every 16 cylinder groups is an adjustment of 1024 sectors.   So the 16th cylinder group is only 15,424 sectors.

That’s, it!  Now that we have a method for finding the inode, we can actually start pulling data off.  I will cover direct disk blocks and the formula for pulling data off of the drive in my next installment.

Florida Hard Drive Data Recovery Services

DTI Data’s primary clean room lab is located in South Pasadena Florida, on the Gulf Coast just outside of St Petersburg. We often get in hard drives for repair from all over the world, but many a Floridian will drive to our lab to drop off their hard disk. When a visitor arrives at DTI Data the first thing they see is a look into our bio-metrically secured laboratory.

People would be amazed at how many companies that call themselves Data Recovery Labs don’t actually have a real lab, let alone a clean room. If you are determined to drop your hard drive off at a location locally, and you’re not in New York or Florida, make sure your local lab actually does have a clean room!

All the major companies allow lab visitors to see their clean rooms. There is nothing to hide, in fact a true lab will have rows and rows of work benches that lead up to the secure and dust free clean room entryway. There is no reason to restrict hard disk owners seeking data recovery from verifying that the lab they are depending upon actually has a clean room.

If you happen to be reading this and you own or work for a computer repair company, contact Jon Moxley by email: sales@dtidata.com or phone: Toll Free: 1-866-438-6932 Direct: 1-727-345-9665. Feel free to look at our Value Added Reseller Plan as well.

If you live in or around Tampa you can get Driving Directions To DTI Data Recovery here. Our data recovery services are worldwide because we are only a day away from just about anywhere with Fed-Ex or UPS.

24 Hour Hard Drive Recovery & Server/RAID Recovery Hotline:
Toll Free 1-866-438-6932 or direct 1-727-345-9665.

Extended Software Support:
8 AM to 11 PM EST 7days a week!

Florida Hard Drive Data Recovery Service Areas

Feel free to visit any of these Florida Data Recovery pages for more information:

• Boca Raton Data Recovery Services
• Miami Data Recovery Services
• Orlando Data Recovery Services
• Miami Beach Data Recovery Services
• Clearwater Data Recovery Services FL
• Tampa Data Recovery Services
• St Petersburg Data Recovery
• Fort Lauderdale Data Recovery Services
• Tallahassee Data Recovery FL
• Gainesville Data Recovery FL
• West Palm Beach Data Recovery Services FL
• Palm Bay Data Recovery FL
• Hialeah Data Recovery Services FL
• Hollywood Data Recovery FL

Data Recovery is often the difference between a company surviving a disaster or going out of business. Be sure to check out the data recovery company you are staking your data on!

Building a Boot Sector With Recover It All Professional

Use Data Recovery Software To Build a Boot Sector

NOTE: This walk through is good for a SINGLE partition hard disk, running an NTFS operation system. You will need to contact technical support for situations out side of that.

The boot record is one of the keys to initializing the operating system. If this cornerstone has somehow been corrupted, or you are receiving error messages such as “No operating system found.” “NTLDR is missing.” “A disk read error occurred” , then this little utility may be the answer to your problem.

NOTE: This function will WRITE data to sectors of the hard drive.

Anytime that a write is performed there is a possibility for more corruption, so use this function only in emergencies. You can also avoid causing further damage to the hard disk by using speed clone first to be sure you have a back up of your data before you go rooting around in a system area of the hard drive. See our post: How to Slave a Hard Drive

Under the ‘Utilities’ menu option click on the menu item which displays ‘Build Boot Record’. You will be presented with a dialog box, very similar to the one below.

 
There are several fields that need some explanation. They are as follows.

LBA Sector:
This box contains the sector where the boot record is to reside.
On a single partitioned hard drive that is normally 63, however placement of the boot record depends upon how the drive has been partitioned.

NOTE: Diagnostic partitions are very common in all computers being built today. Because of the 2-3 gig off set due to the diagnostic partition, the actual boot sector for your primary working drive is further down the hard drive.

Total Sectors:
In order to figure out if you have the correct total sectors you will need to get out your trusty calculator and do a little math. To properly report the total sectors on a drive partition you multiply the heads, times the sectors, times the cylinders minus the reserved sectors and minus 1 sector for the Back up MBR (master boot record)  You can find this information but clicking the little plus sign next to physical data and then the plus sign next to geometry.

I am running the software on a Maxtor 6Y120P0 (120 gigabyte) hard drive the heads are 255, the sectors are 63 and the cylinders are 14946. That gives you 240107490 sectors, minus the 63 reserved sectors and minus the 1 sector for the MBR for a final tally of 240107426 sectors for a single partitioned drive.

NOTE: You will notice that the software reports the total sectors with out removing the reserve sectors; you must make sure you remove the reserve sectors.

Start Cluster:
On an NTFS file system the values could either be ‘4′ or ‘786432′. With older NTFS (i.e. NT4 and Server 2000) using the 4. Newer NTFS (i.e. Windows XP Professional, Sever 2003, and Windows Vista) using 786432.

Sectors Per FAT:
You will not need to fill in this information on an NTFS file system.

Sectors Per Cluster:

Under an NTFS file system this value is almost always 8, unless the file system was converted from FAT32, then the value is usually ‘1′.

Now that we have all of the fields filled in, we can send our boot record to the hard drive. Just click on the ‘Write’ button.

You will receive a warning telling you that you are writing to the hard. Ignore said warning if you TRULY want to write the boot record. If you have any questions, please feel free to call technical support. If you require hard drive recovery please read the information below:

If you are here you need data recovery, more than likely, internal hard disk repair. Call Toll Free: 1-866-438-6932 or fill out an online quote form if you need hard drive recovery.

Data Recovery Tutorial: How to Slave a Hard Drive

This is a tutorial from Jacqui Best about the proper procedure for slaving your hard drive prior to running data recovery software on it. This would also be the procedure to follow if you were to run speed clone to sector clone a noisy drive or if you have a partition problem and need to repair or recover data from a partition or if you need to restore or undelete a file.

It is very important to not download data recovery software directly to the effected hard drive. If you don’t have a second drive or don’t have either a USB drive or USB capable data recovery software, then you must hook the drive up as a slave to run the software.

Hard Drive Recovery Video Series - How to Slave A Hard Disk

Watch the video below to see how to slave a desktop IDE hard drive. If you have any questions post a comment at the bottom of the page. We answer all comments that are legitimate questions!

Get the latest Flash Player to see this player.

Case Study: How to “Slave” your Hard Drive

In data recovery it is NEVER a good idea to install, copy, surf the Internet, reboot the machine, or do ANYTHING on the hard drive you are now trying to recover the data from. I often tell customer they need to Slave the hard disk to another computer, or put it in a USB chassis. What is difficult is the fact that the average home user has no idea how to do this, and it can be a very daunting task.

The following is a step by step walk through, with pictures on how to remove a hard drive from a computer, slave it to another and then be able to do a safe recovery of the hard drive. If the hard drive isn’t seen in the BIOS or is making noises you more than likely need hard drive recovery.

Tools needed: Phillips head screwdriver and a marker.

Step 1: Shut the PC down and unplug the power.

Step 2: Let’s take a look at the back of the computer and see that we need to unscrew and do in order to get the case open. It varies from model to model, so I am showing you on a standard tower case. You will see that there are screws holding on the side panels of the computer. You will need to remove both sides of the tower in order to free the hard drive.

After you remove the sides you will have a front and a back so to speak.

Front

Back

Step 3: While looking in the front we are going to locate and remove the hard drive. You will see below that the hard disk is located near the bottom of the drive chassis in side (the pink area I have highlighted). This is usually the case for most computers.

Step 4: We are going to need to remove the screws from the front and then go around the back of the pc and remove the screws on that side also.

Front Screws

Back Screws

NOTE: there is USUALLY a way to access these screws from the back. If there is not, I would contact, you local computer store fro help as it can become an issue of having to remove the motherboard and other peripherals.

Step 5: Now I want you to remove the power from the Hard Disk. This is a small cable with one red wire two black wires and a yellow wire running into a white connector. Be gentle and slowly pull the cable out, it may be a tight fit so usually slowly rocking it left and right will help remove it.

After you have unplugged it, take a marker and put a mark on it, this will help you to know which one to use when you put the drive back later.

Step 6: Here comes one of the hardest parts, removing the hard drive from the chassis. You are going to want to try and push, any cables in the way of the rear of the drive, up and out of the way. Firmly grab the back and top of the hard drive and pull back to free it.

PLEASE do this gingerly as you do not want to damage any other internal components.

Step 7: Now that the hard drive is free, Flip the hard drive over so that you are looking at the “green board” take you marker and make an arrow that is pointing to the power. This will help you to know which connector to use and which way it is supposed to be plugged into the drive.

Step 8: Holding the hard drive firmly, grab the cable and pull it out. This is another one of those tight cables. Be patient and careful, you don’t want to snap any of the pins off or break the cable.

Step 9: Ok so now we have the hard drive free from the computer, we need to set it to be a slave in the computer you are moving it to. If you take a look at the back of the hard drive there will be a set of pins usually located between the power and hard drive cables.
Now here is the tricky part.

Since Seagate owns Maxtor and Western Digital is the next most popular hard drive I will cover a Maxtor and Western Digital drives for how to set jumpers. (Almost all manufactures keep the jumper setting on the top of the drive on the label) Western Digital: If you look at the green board you will see that near those pins there are labels CS SLAVE MASTER PM2. You are going to want to put the jumper (which should be there already) on SLAVE.

Seagate/Maxtor: This manufacturer is the exact opposite of Western Digital. When you want to make a drive a slave you must make sure there is no jumper on the first set of pins next to the hard drive cable. Maxtor/Seagate have a very clear diagram on the top of their hard drives to explain how to set up as slave.

Step 10: Now that you have made the drive a slave, you can now move it to another computer, to attempt recovery. To do so please start by repeating steps 1 and 2 from above.

Step 11: Ok now another tricky part, putting the drive into the other computer. (for the sake of this walkthrough I am just re-inserting the drive into the same computer)What we need to do is now put the drive into an empty bay in the computer. And put one screw into the side. This is just to hold it in place while you do the recovery.

Step 12: Now find the hard drive cable coming off the hard drive that was already in the machine. To avoid a very lengthy explanation, I am just going to have you disconnect the cable from the hard drive. While looking at the cable you are going to want to connect the very end to the drive you are attempting to recover and the second from the end to original hard drive in the machine.

Step 13: Now connect a free power connector to the hard drive.

NOTE: if you do not have a free power plug you may need to buy a power splitter from your local PC Company.

The image below is what everything should look like when you have connected all the cables.

Step 14: Now replace the sides of the computer, and plug it back in. You should be able to boot into Windows now and attempt recovery.

SNAP Server Data Recovery Of A Single File

Recovering a single file from a SNAP OS

As we know SNAP Appliance used a proprietary Unix File System (UFS) handler in order to run there Network Attached Storage (NAS) product. This particular OS ran a Berkley Software Distribution (BSD) flavor of UFS. Although there are many similarities to the original file system, there are also enough changes to make file recovery extremely difficult. In the following paragraphs, and articles we will explore the arithmetic and methodology of recovering a single file from a UFS volume.

In order to recover the file we must use the on-disk data structures that give the OS its road map to the file name, inode, and finally data block placement. Normally I would start with the coarsest data structure, but in order to facilitate an understanding of the file hierarchy I will start from the smallest granularity. That data structure being the directory entry.

To illustrate the data elements and their use I chose a PDF file for recovery. The file name is “2003STEP.PDF”. Using you favorite sector editor, do a scan and search for the file name that you want to recover. The tool I use is a wonderful product called “WinHex”. Figure A is a capture of my sector search.

Figure A

There are many elements in a directory entry structure; however there are actually five key elements.

1. File Name: This is the actual name of the directory/file. In Figure A this is defined as “2003STEP.PDF”
2. File Name length: This data element is self explanatory as it defines the length of the name. In Figure A the name length is defined as 0×0C, or 12 in decimal.
3. File Type: In this case we are only concerned about two types. First 0×04 which is a directory entry and 0×08, which is a standard file name entry. In Figure A this file entry is regular file name.
4. Record length: This defines the entire length of this particular directory/file name record. In variable length records there is always a record length. In Figure A you can see the record length is 0×00000028 in hex, or 40 in decimal.
5. Inode number: The name, and name length are important, however the inode number holds the key to the data block placement. In Figure A this is defined as 0×000F7E01, or 1015297 in decimal.

Next installment I will describe the ‘cylinder group’ data structure and how we can use that to find our inode element.

Recover Deleted Partition With DART XP

Unlike a lot of software companies, DTI does NOT outsource their tech support. My staff answer the software support calls from 8:00 AM to 11:00 PM 7 DAYS A WEEK. That’s right we really answer the phones at night and on weekends to help clients use our software to recover their data.

The following case study is an actual response to a tech support call. (The names have been changed to protect the innocent!)

PROBLEM: User accidentally deleted partition with the “Disk Management Utility”

SOFTWARE USED FOR RECOVERY: DART XP Partition Repair Software for NTFS

“Bob called and had already downloaded the DART XP Demo, and needed help on how exactly to go about getting his data back.I asked what had happened to the drive and he informed me he had accidentally deleted the partition with the disk management utility. He also let me know that the drive was a slave drive in the machine.I directed him to click the Physical drive and click next in the software. DART immediately rebuilt the lost partition in memory. We allowed the software to complete the fast scan which took less the 90 seconds. We then clicked on the found partition and clicked next. When we did, the drive treed up in exactly the way it looked before the partition was lost.

He could see all his files and directories including the ones he had deleted before the partition wipe. I told him he could now purchase the software and copy the files off.I Instructed Bob on how to use the disk management utility to put a new partition on the drive and reformat it, so that he would be able to put his data back the way it was be for the partition delete.”To Recap the data recovery software used was DART XP which is $69.00, but will Show you the files recovered before you pay for it! Here is a screenshot of that feature:

Exchange Server Dirty Shutdown Error

24 Hour Exchange Server Support

I run DTI Data’s 24 hour Microsoft Exchange Support Hotline. While I often jokingly refer to it as our “suicide hotline”, that is close to the truth. When that phone rings at 2 AM I know someone is having a serious Microsoft Exchange problem. I am often asked why we offer free phone support for Exchange. Most people expect there to be a hidden charge or some other hitch, in fact last night I got a call from the UK and the gentleman asked if the number was a premium line, one that costs money to call.

I explained to him like I explain to everyone that our business model is simple. In our experience (which is pretty vast) most Exchange errors are fatal. If you have had a dirty shutdown, jet engine errors or problems with transaction logs being corrupted or out of order, chances are you will have to restore from backup. ESEUTIL and ISINTEG do not really repair anything, they truncate parts of the database that appear to be in error, whether it is duplicate or illegal keys, page file header corruption, etc.

That is why we are so adamant about backing up the priv, priv1 edb and stm files before running any Microsoft Utilities!

So if most Exchange issues that are serious enough for a system engineer to call us are going to require a restoration of backup, how does that benefit us? Well unfortunately not all Exchange backup programs work all the time. After all Exchange is a database that is almost always active and there is always a chance that the backup will fail. That is why it is critical for users to check the backups at least monthly.

Now we get to the heart of the matter. Most engineers that call have had a serious Exchange issue, they have run utilities and that hasn’t worked, I’d say that at least 70% of the calls I get also have tried to restore from backup and it failed. SO if an admin is in need of Exchange Server Data Recovery, who are they going to send it to? Probably the company that answered the phone in the middle of the night and helped him get back up and running! That is why we offer free support, it’s a good business plan to spread good will and brand your company name as being customer oriented. DTI is very serious about customer service. Whether its a laptop hard drive recovery or a multiple hard disk RAID array, everyone is going to know that we are giving them the best we can.

The Most Common Exchange Server Failure Support Calls

Answering the emergency line for all these years has given me a lot of insight into common Exchange problems. While there certainly are plenty of things that can go wrong with an Exchange server, you would be surprised at how often I hear the same scenario of Exchange Server failure. Below are the most common calls that I receive from the support line.

Anti-Virus Deleted or Quarantined a Transaction Log

By far the most common call over the years has been the transaction log was quarantined by Norton, AVG or Panda. Lately this problem hasn’t been so apparent since there is so much good information about Exchange and anti-virus, but looking at the last 3 years this is by far the most predominant failure. The fact is you shouldn’t let any program have the ability to modify any component of Microsoft Exchange Server.

Information Store Has Reached The 16 GB Limit

Another historically rampant problem that has smoothed over recently is the priv or priv1 edb file size limitation. The Internet has also helped by educating admins about the 16 GB limit. Many didn’t know that the file size incorporated both the priv1 edb AND the priv1 stm file in its limitations. Once the size gets hit, the Information Stores can’t be mounted. There are plenty of websites (including our Exchange Forum) that posted the 1 GB temporary fix to the problem. This and Microsoft increasing the size to 72 GB has made this scenario less prevalent than say a year ago.

And now for the worst problem of them all…

Exchange Server Has Had A Dirty Shutdown

The big daddy problem of them all, a dirty shutdown is a very bad situation. This is the problem that I hear more than any other Exchange failure. A dirty shutdown happens whenever the Information Stores have not been closed in the normal manner. During the winter this is usually due to power surges or outages. Last week I took close to fifty calls from the Ohio area that had power problems leading to data recovery.

It is critical that your servers have UPS systems, battery backups, whatever you can do to help shut the Information Stores down properly during a power crises. If your server has had a dirty shutdown, exchange data recovery will be in your future if you don’t have a solid Exchange disaster recovery plan in place. A dirty shutdown is a disaster by definition. It often leads to jet engine errors, duplicate or illegal keys or worse. Keep your files backed up, and just as important: test your backups and recovery plan often!

Hard Disk Recovery of My Own Computer!

Lost Data… It has happened to all of us. Just last week my computer was acting weird. I’ve been computing since 1995 and thought I had seen it all; however this was a new one on me. I though at first it was my sound card, because there was a horrible distorted digital scream coming from my computer. I restarted and the machine would get through the Windows (XP PRO) login screen, start loading applications, then restart.

After a couple of times I knew enough to stop trying and called my buddy Rich who is DTI’s network Manager. He dropped by and told me my hard disk was dead. I though no problem I backed up just about every day with Ghost. So he replaced my disk and loaded the last full image of my system.

Everything was going smooth until I started testing my incremental data, you know the stuff like My Documents that I back up every night. Well I opened a spreadsheet and it was corrupt. My pst file was shot, ell my Word and Open Office documents were also crap.

I immediately called Rich and told him that I just turned into a data recovery customer. He gave the drive to Malcolm Jamieson DTI’s head data recovery engineer. He had to completely swap the platters because the drive wasn’t able to communicate any more to the micro-code modules on the platters.

I found out that this is a very common problem with high capacity hard disks. The fact is a 250GB hard drive has the exact same size platters that a 40GB drive had, the drive manufactures are stuffing more and more info onto the platters using proprietary compression called micro-code.

Fortunately Malcolm knows what he is doing and was able to recover 100% of my lost data.

The lesson to be learned here is its not enough to just back up your data, you have to verify the data that is being backed up.

Over the next couple of weeks Rich and his cohort in crime John Best DTI’s Exchange and network expert are going to be implementing a bullet proof back up and restoration system. I will be documenting all of it here so everyone can benefit from my suffering and aviod hard disk recovery.

Data Recovery Services Nationwide

Nationwide Data Recovery Services

DTI Data Recovery offers nationwide data recovery services. We have found that most people feel more comfortable sending their hard drive to a local company for data recovery , the problem for clients is there are only a few legitimate data recovery companies scattered across the country and most of them are in large population centers like Tampa Florida, Los Angeles California, etc.

What we tell clients when they call is we are only a day away with Fed Ex or UPS. As long as the hard drive is packaged properly there is little risk of further damage. Here is a link to a page about hard drive recovery packaging shipping.

DTI has labs in New York and outside of St Petersburg Florida. If you are elsewhere give us a call and we can help you package your hard drive for data recovery.

If you are here you need data recovery, more than likely, internal hard disk repair. Call Toll Free: 1-866-438-6932 or fill out an online quote form if you need hard drive recovery.

Next Page »