So far I am getting the impression that it is not.
One of my users brought me her laptop that was getting the above error. I pulled the drive out of the laptop to see if I could do anything and so far nothing. I can't even see the drive when I plug it in to my desktop using an Apricorn Drivewire, and I have been able to recover data from damaged hard drives using it and Recuva before with no problems.
And before anyone asks, this user had not backed up any of her data or done anything else that may have prevented this. That is a tale for another time. In the meantime I am just trying to save what I can. User education will come later.
I am open to any suggestions that might allow me to recover some of this user's data. Anyone that has dealt with this specific error message has my attention.
11 Replies
I have not personally dealt with this, but it looks like a firmware update may be the answer. Your exact model laptop number isn't listed, but maybe the drive is.
Sorry for not adding this with my above comment - I should have mentioned that most of what I have found so far on this issue speaks of solid state drives (which this is not, it's a Hitachi z7k500-500) and also of various other model Lenovos, as LarryG mentioned. The only person I have found so far who had my exact issue and the exact same laptop, etc., was unable to recover anything. He was told to 1) reseat the drive (I have tried that many times) 2) replace the motherboard (the machine itself seems to be fine, as I can get into the BIOS and whatnot with no issues, so probably not the problem) and 3) replace the hard drive, which I will certainly do.
But I would like to recover something, anything off this drive.
Sorry for not adding this with my above comment - I should have mentioned that most of what I have found so far on this issue speaks of solid state drives (which this is not, it's a Hitachi z7k500-500) and also of various other model Lenovos, as LarryG mentioned. The only person I have found so far who had my exact issue and the exact same laptop, etc., was unable to recover anything. He was told to 1) reseat the drive (I have tried that many times) 2) replace the motherboard (the machine itself seems to be fine, as I can get into the BIOS and whatnot with no issues, so probably not the problem) and 3) replace the hard drive, which I will certainly do.
But I would like to recover something, anything off this drive.
If you can't get anything to read the drive, then it's probably toast. But if you can get it to read, but not actually recognize correctly, reformat it and try and recover data. It's better than sitting around and doing nothing.
I have the Lenovo Thinkpad Edge E540. Same Error. I don't have an SSD, too.
I started Linux Live USB and tried GParted; No HD in there. But when I started the 'disks' tool, it appeared. I was able to right-click and to (I don't know the exact words) 'wake from sleep'(??? or something like this..)
Unfortunately this did work only once. Next time I started again, I got the Error again and Linux didn't help anymore.
Good thing: I always backup everything. So no recovery issue for me.
Bad thing: Because I live abroad at the moment, it is not so easy to go to the shop, where I bought the machine, and hand it in -.- So; no computer for me :X
i got these problem too in mine T430. my instant solution is.
1. on power button . click f1 go to setup menu
2. got to 2nd Tab. goto to ATA. change from AHCI to compatiblity. then save & restart
3.during restart .hdd already detect
4.click f1 again. change back from compatiblity to AHCI
5. restart n success login to windows
But need to doing all these if shut down. for fast login. just use Sleep not shutdown
P/S: you may recover all data or clone hdd to new hdd
Noor Effendi's solution worked for me - thanks!
My issue was on a T420 with a SSD, newly upgraded from Windows 8 to Windows 10. When the machine was powered off then powered on it booted as expected. However when I did a Restart from Windows I got the 2100 HDD0 error.
After doing Noor's procedure the problem no longer occurs.
FWIW the problem started several months before when the machine was running Windows 7 and my company enabled BitLocker.