Creative Data Loss
lewiz writes "An interesting article from the BBC about the crazy things people do when they accidentally delete files. Amazingly one guy froze his hard disk in an effort to retrieve files. Real men don't make backups... but, hell, who needs to if you can resurrect them from the dead ;)"
I'm surprised to see this - a friend did this successfully to get his hard drive working for a while, and I've seen a fair amount of other people reporting success with it on the internet.
Anyone else?
I actually did that on a WD scsii hard drive last year. It failed on me and had important data on it. I wasn't willing to shill out a few hundred to a few grand to get it fixed, so I found a few articles commenting about how the clicking noise I was hearing was problems related to the mechanics of the drive and there was a chance I could salvage my hard drive by placing in the freezer.
I thought, "Well, the data is lost anyway, so why not?" I put it in a ziplock bag, so not to get the platters all frosty, and left it in overnight. I woke up the next morning and put it back into my computer, and wouldn't you know it, absolutly nothing except for the same clicking errors I heard the day before.
Thanks Internet, you've once again provided me with more information that I really needed.
I once lost a year's worth of gnucash xml data, including all the backups (and gnucash makes plenty--a new one every time you use it!). I promptly used dd /dev/hda1|grep to search for markers that I knew would be in a gnucash file, and with a little shell scripting found the original and every single backup file in deleted space. After determining with a little more fancier grepping which blocks represented my most recently updated file, I recovered that, trimmed off a bit of the filesystem cruft around the edges, and had my file back.
:-)
Then I promptly set up a system to encrypt and email myself the most recent file, every day.
(Yes, I'm aware that there are programs that will do the same thing for me.)
It's rare that you're presented with a knob whose only two positions are Make History and Flee Your Glorious Destiny.
A good colleague - Hi Ryan :) - who builds computers in his spare time left a brand new 80GB
hard drive on the roof nd drove off. It bounced a couple of times and got driven over. His mistake was to attempt to send it back for a warranty refund :) Not just women - it happens to all sorts
of people for all sorts of reasons :)
I had two IBM death-stars and a Maxtor fail on me last year. The IBM's made that horrible clicky sound they are famous for, and the Maxtor just stopped spinning. I discovered by accident with the first IBM that if I turned it upside down and powered up the machine, I was able to access my data! It worked for the replacement IBM drive a few months later after it failed (bleh), and a Maxtor that had stopped spinning completly.
Doesn't work all the time, but worth a try. Anyone have any idea why it works at all?
One thing of interest is that the article specifically highlighted the female user - whereas, for men, it was just a user.
The gender of the user in the list was already specified by the 'his/her', so I have no idea why they needed to specifically point out when the user was female.
I've attached my Amiga harddrive to a PC at work. For a few days I've been succesfully using my home system by mounting the drive under linux as AFFS and then using the mounted directories as volumes under UAE, emulating Amiga just like the one I had at home. Then I got that idea of looking how does Windows see it.
I booted NT, Disk Manager and it displayed a requester with something along this lines:
"The drive contains invalid/corrupt signature and can't be read. Windows is about to write a correct signature. This is an absolutely safe operation and won't change the way of accessing the disk by other operating systems in any way. Do you wish to proceed?".
So, I clicked yes.
Result: 6 hours of recovering of erased Amiga partition table. Absolutely safe my ass, fucking Microsoft liars.
45 5F E1 04 22 CA 29 C4 93 3F 95 05 2B 79 2A B2
In any modern hard drive the R/W head is automatically retracted to a safe area during powerdown and never contacts the platter anyway even when the drive is running (i.e. the Winchester flying head.) If the head ever does touch the platter you've just destroyed part of the platter and maybe the head as well. However, if the drive has seized up, cooling it causes the bearings and spindle shaft to contract and move away from each other to reduce friction. If it's enough that the motor can start turning again you may be able to use the drive for a while.
The higher the technology, the sharper that two-edged sword.
What about this?.
meh
Ain't that the truth: I just put back in my SB Live and am selling my brand new audigy 2 zs. The zs sounds nice enough, but it just won't wake up after standby. And that's pretty important seeing as I use my computer as an alarm clock.
And you should check out the Creative forums for a brilliant example of how a company acts when they're product is buggy as hell.
-- Waht? Tehr's a preveiw buottn?
...when answering the phone in support years ago, I took a call from a user who wanted help replacing her hard drive. After 5-10 minutes of roundabout conversation, she finally admitted that the guys doing work in her building had dropped a cinder block through the ceiling and smashed her server.
No joke.
...if I wanted to read garbage like that, I'd go to \.
I had three failed drives back in the heyday of Fujitsu timebombs and IBM deathstars. One we had to send off to data recovery because it failed while it was being reconnected to my backup server. This is true. It was the first time the machine had been power cycled in six months, and when restarted in the location where I had it connected to my backup server, it never spun up. Most of the data from that drive was smeered around the network in various forms and locations, but it was simpler (though somewhat expensive) just to send if off for recovery.
A friend brought me a drive that wouldn't spin up that I managed to spin up just barely long enough to recover the data by power cycling a number of times with different power supplies. The death rattle was noticably increasing as I raced to copy off the files. There was only a few gigs that mattered so I won the race by a few minutes.
The third drive really wanted to spin up. You could feel the platter quiver momentarily on each power cycle. I put it in the fridge wrapped in a thick dishtowel for about four hours. When I took it out of the fridge I had to race to get it installed in the rescue machine before it warmed up too much. It started up. Woohoo! Then it was fine as far as I could tell, but it never started again after that.
I also had a few other Fujitsu's that were rotated out of important functions before they predictably failed. And there was one deathstar drive I installed in a friends machine just before it became widespread knowledge that deathstars sucked, and that drive has never so much as burped. Just as dangerous as the Fuji bombs, a little less predictable.
We had one drive at work that failed within 30 days of being installed. Wasn't either type of notoriously crappy drive, it was just a lemon.
Since that batch in rapid succession, I haven't witnessed a drive failure in two years over some two dozen spindles. Some of those drives in firewalls were from the old less than 10GB era. They made so much spindle noise we recently decided on a mercy killing.
Here's hoping the Seagate 7200.7s are one of the good batches. I've got a lot of them now.
I've had the same thing happen. Actually all the work for that entire semester of school was on the drive and I almost didn't graduate because of it. (now I'm a bit more careful).
Anyway, I noticed that the deathstar would have problems at certain points and give the well known 4 scrapes and two clicks. After some hard though and a lot of research (a lot pointing to freezing) I ended up waiting till it was having trouble reading and then I twisted it with a decent amount of force. My hypothesis was that if I did this, the drive would realize that the heads were misaligned and reset them. Luckily, it did the trick and after some fsck'ng I was able to get all the data off the drive.
Yup, good, but I got them beat for the temperature part, and I was in the freezer myself...
Non-Linux Penguins ?