News for hackers. Stuff that matters.
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by randombits0 on Thursday August 17, 2023 @01:27PM (#37165212)
I did this many years ago when I was a bench tech at a PC shop. It was an old Connor 40 meg drive running DOS. If I squeezed it just right, it would work. Too much? Failure, Abort/retry/ignore. Not enough? Same. So I stood there, squeezing the drive, and hitting ‘r’ for retry, over and over. It worked!

Boss walked by. “What the heck are you doing?”

“I’m milking the data out of this drive!”

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by placesalt on Thursday August 17, 2023 @01:53PM (#37165548)
I did the same sort of thing with a broken iPod hard drive. If it was squeezed, it would work; the fix was to put a folded business card in-between the exterior back plate and the drive. That would squeeze it enough that it'd work. Never heated up enough to start a fire, either, so it was safe!
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by dendrite9 on Thursday August 17, 2023 @04:59PM (#37167972)
Oh man I remember doing that to eke out a little more life from several mp3 players, one or two Creatives and an Sansa e200. There was also one with a sliding door over an SD card with 32MB that I had to pop open and try to fix. I think that was around 2003? I'm pretty sure I upgraded to a 64MB card at some point.

Shims were plastic cards, subway tickets, and occasionally toothpicks as an adjustable clamp while I was trying to figure out where the failure was.

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by toast0 on Thursday August 17, 2023 @05:35PM (#37168446)
I've had to do that to make batteries stay connected in various devices; I've also made shims out of folded aluminum foil when battery contacts are just too far apart; and used a penny (with the edges coated) to shim a light socket where the end of the fixture made it impossible to screw the proper bulb in all the way. Good times :D
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by throwaheyy on Thursday August 17, 2023 @03:14PM (#37166551)
I had this happen once but the force that would cause the drive to work seemed to be gyroscopic rather that pressure on the casing. So I had to hold the laptop at an angle and turn myself around on the spot while I copied the data off. If I stopped spinning around the drive would grind/crash and the OS would hang.
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by Agingcoder on Thursday August 17, 2023 @05:25PM (#37168331)
You didn’t get sick ?
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by throwaheyy on Thursday August 17, 2023 @07:51PM (#37169863)
I only had to do it for several minutes, long enough to have it boot up successfully and copy off the most important data over wifi. I do remember getting a bit dizzy during the procedure. The laptop was a pretty light PowerBook G4 from 2003.

My theory (based on the sound the drive had been making, which prompted me to try imposing different kinds of sideways acceleration on the laptop until I could hear the drive spinning ”freely”) is that it wasn’t a problem with the disks/heads but a messed up bearing in the spindle motor.

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by samwillis on Thursday August 17, 2023 @07:24PM (#37169637)
Using a centrifuge to separate valuable data from low value redundant components is inspired!
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by randombits0 on Friday August 18, 2023 @11:26PM (#37185191)
The ones sink because they’re heavier.
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by heleninboodler on Thursday August 17, 2023 @04:03PM (#37167190)
> old Connor 40 meg drive

I would like to call out to the younger readers that this is not a typo. Think about how minuscule the capacity of this hard drive is, and also that it's entirely possible it was a full height 5.25" drive, which is 3.25" tall!

Here is a fun tour of old drive technology that goes into just how amazingly simple some of it is: https://www.youtube.com/watch?v=8LbFKV_pPAE

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by Agingcoder on Thursday August 17, 2023 @05:27PM (#37168360)
Yep I owned a 40 meg drive. I remember when very large applications appeared (50 megs) wondering how it was even at all possible, and whether it made sense.

It also meant lots of highly unreliable floppies !

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by lowestprimate on Thursday August 17, 2023 @06:02PM (#37168786)
I worked on this drive. It's a 3.5 drive. A long time ago. Time for my daily nap and Centrum shot.
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by jacquesm on Thursday August 17, 2023 @08:11PM (#37170001)
Wait in line, and give me back those 8" floppies that you borrowed.

Seriously though: the amount of miniaturization in storage is something I'll never get used to. From punch cards and papertape via cassette to floppies, harddrives (in various incarnations and densities) and now to solid state so compact that you could store all of the data that I've created in my whole life in something about the size of your smallest fingernail. Incredible.

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by marcus0x62 on Thursday August 17, 2023 @08:13PM (#37170016)
Yep, I had a Seagate 40MB IDE hard drive, which I considered quite compact at 3.5” full height. It replaced 20MB full-height 5.25” MFM drives.

The MFM drives were… fun… in that if you connected one of the two data cables upside down, you’d crash the armature and destroy the hard drive.

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by qingcharles on Friday August 18, 2023 @01:34AM (#37171681)
Ah, you young'uns with your 40MB drives. My first was a full-height 10MB drive on my Sirius 1. That thing was life-changing.

Someone gave me a 30GB drive the other day. I still haven't figured a use for it?

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by gruturo on Friday August 18, 2023 @08:27AM (#37174719)
>> old Connor 40 meg drive >I would like to call out to the younger readers that this is not a typo.

Actually there is a typo there, it's Conner. But yeah, 40MB was even a luxurious capacity, my first HDD was 20 (later reformatted to 30 with an RLL controller)

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by randombits0 on Friday August 18, 2023 @11:30PM (#37185216)
Cheater! I used pirated ROMs to make my USR HST a dual standard.
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by yencabulator on Friday August 18, 2023 @10:40AM (#37176299)
[delayed]
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by randombits0 on Friday August 18, 2023 @11:32PM (#37185232)
A:>debug

-g=c800:5

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by 300bps on Thursday August 17, 2023 @04:51PM (#37167875)
Same. In 1990 was a field service engineer at a PC shop. We used to use circuit cooler or "cold spray" as we used to call it.

We had three levels of hard drive data recovery that we did in order. Usually didn't have to get past #2.

1. Put it into another computer

2. Cold spray the heck out of it and see if it works for an hour

3. Remove the circuit board of the drive and replace it with the circuit board from a matching known working drive

If it didn't work after that and they 100% needed the data we sent it out to Ontrack. They'd put it in their clean room, remove the platters and read the data directly.

Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by jacquesm on Thursday August 17, 2023 @08:12PM (#37170009)
That last trick no longer works. Too much trickery with NV storage on the board. The last time I did this successfully is about a decade ago.
Re:Retrieving 1TB of data from a bad Seagate Firecuda drive ... by blarg1 on Friday August 18, 2023 @11:36AM (#37177074)
Reminds me of one I had where it would start clicking and file access froze, so I would turn it side ways and bang it against the table, it seemed to unstick it.