Hot answers tagged data-recovery
Ok - something was bugging me about your issue, so I fired up a VM to dive into the behavior that should be expected. I'll get to what was bugging me in a minute; first let me say this: Back up these drives before attempting anything!! You may have already done damage beyond what the resync did; can you clarify what you meant when you said: Per ...
I almost cringe to do this, but if you're serious about recovering your data, and you don't have backups, you'll need a higher-end data recovery service. Watch out for fly-by-nights shops that will be peddling/scamming in your area, and go with an actual top-tier data recovery service. (And be prepared to pay $$$$ for it.) Here's a list of what to look at: ...
There are already many companies providing services for this, for example 24HourData (their site has a list of drives they support). While you figure out your next steps keep these things in mind (from Top Tips for Liquid Damaged Data Storage Devices) Do not try to power on a flood damaged hard drive bad things happen to good hard drives when this ...
http://www.storagesearch.com/disklabs-art3-floods.html Do NOT attempt to recover the data yourself. This will do more damage to your data and makes it more difficult to recover when it eventually gets to a data recovery specialist. When hard disk drives get wet, the 'heads' can get stuck to the platters. When the hard drive is powered ...
I know @HopelessN00b already mentioned this, and I'm not affiliated with them, but try this: Kroll Ontrack From what I can tell, they handle some of the most difficult data recovery cases, including server, RAID, and forensic data recovery. Given that this is one of the leading data recovery companies, expect to pay dearly for their services. More ...
Ha - my (un)favorite question I get asked (as I wrote DBCC CHECKDB). Here you go: There's only one time when you should be trying to work out how long a CHECKDB is going to take - when you're planning your regular database maintenance. If you're faced with a corrupt (or suspected corrupt) database and you're only just starting to think about how long a ...
If you've lost two drives then you've lost your data. The only recourse is to restore from backup if one exists or, as you stated, send the drives off to a data recovery company to try and recover the data.
The problem was that the new motherboard created a host protected area (HPA) on some of the drives, a small section used by OEMs for system recovery purposes, usually located at the end of the harddrive. ZFS maintains 4 labels with partition meta information and the HPA prevents ZFS from seeing the upper two. Solution: Boot Linux, use hdparm to inspect and ...
Old NeXT hardware. SWOON! Getting a SCSI2 -> SCSI 1 adapter should be trivial. There were both internal and external varieties. Google is your friend. For some reason I thought the "newer" slabs should be SCSI2 but it's been a long time. You still have to terminate the scsi chain. Keep to addresses 0-7. Further just Googling for "scsi-2 pci card" comes up ...
Is it possible for each platter in a multi-platter drive to be separated, cleaned, imaged, and merged into a new virtual drive for data recovery? As you would have read in other articles, the answer to this question is "yes". What you would not have read yet is that it is not an unconditional "yes". Data recovery companies would do what is called a ...
Try this tutorial Basically you can use the commandline tool ext3grep to search through sections of the filesystem. I have not tried this myself YMMV.
The software RAID solution is Windows itself: SFS refers to a "dynamic disk" in Windows 2000 or later, and software RAID volumes in Windows must be built on dynamic disks. What I would do: Capture offline images of all drives before attempting to boot, to ensure that we do not make anything worse than it already is. Put the bootable NTFS drive on the ...
The solution you want (and this should work) is to run mysql_install_db as root. or dpkg-reconfigure mysql if you're a deb/ubu user. Manpage description: mysql_install_db initializes the MySQL data directory and creates the system tables that it contains, if they do not exist.
How valuable is the data? If your business depends on it, disconnect it and call a professional recovery service. If it's not so valuable, this is a pretty good summary of steps you can take yourself. It includes the controller board changing idea Dentrasi mentioned and also everyone's favourite, the freezer trick.
All my data in this 6 years is gone and they will just extend the hosting expired date to another 90 days That is very generous of them. Seriously. Is there any other way to retrieve the data from the crashed harddisk? Get the disc, send it to a recovery lab. Cost is some US$ PER GIGABYTE OF DISC SIZE. Are you willing to pay that? See: All ...
Send 'em to Kroll Ontrack (or another professional data recovery company). Your restore efforts are much more likely to further damage the tapes than doing anything productive.
Look at the /etc/rc?.d directories. You will find symlinks in those that point to the scripts that were in /etc/init.d. You will know what startup scripts you will need to restore to /etc/init.d. So, something like: $ ls -l /etc/rc?.d and you will see something like: /etc/rc2.d: total 4 -rw-r--r-- 1 root root 556 2009-01-23 15:01 README lrwxrwxrwx 1 ...
F2 is typically the right option to choose... Otherwise the ESXi server would not have booted. My concern is what happened leading up to this incident... Did you receive any errors? Any indicators on the hard drive LEDs? Typically, an HP server's disks won't just crap-out on you. Considering you're using 750GB disks in RAID5, the chances are that the ...
I see two options in your future. Call PSS and open a ticket. It'll take a while to get anywhere with them. Call SQLskills (Paul to be specific) and see what he can do. I know that Paul has successfully hacked a database back to life using a hex editor before. Paul isn't cheap, but he'll get the job done. Good luck.
First and foremost, boot off a live CD or recovery disk and back up your data. You may want to include system configurations from /etc, too. You can try doing a reinstall over what you have, leaving your partitions you want to keep untouched. As long as you weren't keeping your good data in any system partitions (and let's hope not under /usr), you should ...
If you still have the current log file it may be possible to recovery the data using a 3rd party tool. UPDATE statements are fully logged in most cases. Here are a couple of tools to look for: Apex SQL Log by ApexSQL SQL Log Rescue by RedGate If you were running in simple recovery model with no backups, then ran your UPDATE statement, and then took a ...
Your best bet would be taking the drive to a data recovery company who would, in most cases, be able to remove the disk's platters and extract the remaining data from them. However, this process is quite risky and there are no guarantees that your data can be recovered either partially (as a result of a head crash) or at all (as a result of having taken an ...
Assuming a battery backed controller, the data should be flushed out to disk and you would be fine. Power supply failure isn't really any different from shutting of the machine unless there was some massive surge. That being said, raid isn't backup, you must have backup. Also, if you can afford it, two power supplies on two different power sources ("A/B" ...
If these files are critical to your client and critical to your keeping them as a client then: STOP NOW. SHUT DOWN THE SERVER AND STOP ACCESSING THE HARD DRIVES. NOW. Then start looking for a data recovery company who can recover the data from the hard drives.
Michael Hampton's answer is most correct, though I've posted about this before. The easiest way of moving the files over to the new mountpoint is: # cd /var/www # vi /etc/fstab # (add the new disk to the fstab now so you don't forget!) # mount /var/www # mv * /var/www
Listing the directories does not mean that the filesystem is ok, you're just viewing metadata (which is a small percent of a filesystem). Create a backup of everything you can Run a filesystem check (fsck) Create another backup (in case fsck managed to save some more files) Replace the disk
Looks like the filesystem was hosed and the fsck didn't fully repair it. At this point I'd be tempted to check the logs to see if the disks are all physically working (noises? SMART status? errors in the logs regarding resets? etc.) and restore from backup rather than spend more time trying to straighten out the results of the fsck.
It's not available for download yet and we don't deal with unreleased code on serverfault. Come back, or better yet read the documentation, once it's released rather than announced. That said basically you just upgrade your VC and hosts to 5.1 and deploy the VDP .ovf like you did for VDR, the process is the same.
Only top voted, non community-wiki answers of a minimum length are eligible