Worst hard drive crash I've seen


Recommended Posts

Not bad.

Here's my similar drive crash from work back in 2006..

100_2745.jpg

100_2746.jpg

100_2747.jpg

100_2748.jpg

100_2749.jpg

100_2750.jpg

100_2751.jpg

100_2752.jpg

100_2753.jpg

100_2754.jpg

It was part of a RAID 1 array that had been degraded for a few months..

The server wasn't important so I just ignored it until one day when I had to reboot the server and it wouldn't boot with the drive installed.

I took it out and opened it and thats the damage I found. I still have it.

I see this type of thing all the time at work. We actually researched why we were getting drives like this. Here is a crude explination, it was subjected to a jarring motion while powered off. This creates a small pit on the platter where the heads are parked and very slightly bends the heads. When you power up the drive, the head jumps when it gets to the pit, in turn creating another pit, and another, and another.... As the metallic dust builds up in the drive, it helps eat at the drive, like sandpaper. Eventually you get a pretty nasty groove, although I have never seen one that has eaten itself completely through the platter. Also the distance between the ridges in the groove and the resulting pattern in the dust is directly related to the speed of the platter. I wouldn't breathe or touch the dust in the drive. as it contains a lubricant for the heads. So the next time you are handling hard drives, treat them with respect, or they will turn out like this.

Not bad.

Here's my similar drive crash from work back in 2006..

...snip...

It was part of a RAID 1 array that had been degraded for a few months..

The server wasn't important so I just ignored it until one day when I had to reboot the server and it wouldn't boot with the drive installed.

I took it out and opened it and thats the damage I found. I still have it.

This is a very smooth cut. The original is a very rough, uneven cut- in fact it almost looks like it was ground down with a dremel. There are large broad strokes tha would apear to have been gouged out at one time...

Anyways, impressive nonetheless but I really don't like the uneven nature of the first one. The fact that the first drive was brought in in an unknown state, just 'found' to be that way with a valid security sticker says someone has been had with a nice practical joke.

Not bad.

Here's my similar drive crash from work back in 2006..

That's also an older drive, right?

I wonder what havoc a headcrash of epic proportions will cause inside the newer IBM/Hitachi drives, since they have platters made out of glass substrate.

Can you hook it back up and record the sounds it makes as it screams? I love the sound of cutting wood in the background. That must have sounded like a tablesaw cutting through a coffee can full of nails.

If you contact the manufacturer, maybe they will be interested in looking at it for you. I think the warranty is up though. By like 10 years.

This is a very smooth cut. The original is a very rough, uneven cut- in fact it almost looks like it was ground down with a dremel. There are large broad strokes tha would apear to have been gouged out at one time...

Anyways, impressive nonetheless but I really don't like the uneven nature of the first one. The fact that the first drive was brought in in an unknown state, just 'found' to be that way with a valid security sticker says someone has been had with a nice practical joke.

I'm not even going to try and argue with you to "prove" to you that the drive was not tampered with. I'll just say this, I stake my reputation as an IT professional and as a staff member of this site on it.

I'm not even going to try and argue with you to "prove" to you that the drive was not tampered with. I'll just say this, I stake my reputation as an IT professional and as a staff member of this site on it.

ha ha i will

i took the pics and finished disassembly of the hard drive

this harddrive was out of a gateway e4200 at a college. it was either part of our defunct test domain or linux lab.

if we have obsenly old equipment or a damaged drive we pull the HD set it aside and get rid of the rest. (at one point i had a stack of 30 HDs behind my desk, i still have sevral old 286 5 1/4 hds some caviar 17000s and several 5-20 gig drives that have been sitting for 3+ years now from pcs we find in random closets).

my best guess is the drive failed over a vacation and sat there unnoticed for days then was removed and set aside. there was no indication of the amount of damage on the outside other than our other network admin said "shake this thing, it sounds like a plater came loose" to witch we replied "no way in hell" so we took the cover off and found what you see in the first pic.

the carbon filter was in tact and there was no sign of moisture intrusion. the ground down jagged edge is from it slipping under and over the center ring of the plater witch as you see in in the first and second pic is sticking out as far as the ground down edge. what you cant see is the marks left on the side of the plater where it was thrown around in the casing and bound up aginst the side. it ground the center section smooth and the outer to a sharp edge

the platers had no real damage other than the inside and outside edge and had a mirror finish after i wiped the aluminum dust off and are now hanging on the wall in my office

my bet is neilgx is right about what happend to cause it. you wouldn't belive how many time we walk into office where there is a bad noise or smell of burnt electronics and they say we ment to call you about that a few days ago but it is still working so we thought it was ok.

That's also an older drive, right?

I wonder what havoc a headcrash of epic proportions will cause inside the newer IBM/Hitachi drives, since they have platters made out of glass substrate.

It's a Quantum Viking II 3.5 Series PX09J011 SCSI drive. 9.1 GB. I forget how old it is, but the other drive in the RAID 1 array (same model drive) is still running in the server hehe

you wouldn't belive how many time we walk into office where there is a bad noise or smell of burnt electronics and they say we ment to call you about that a few days ago but it is still working so we thought it was ok.

So true. So very, very true.

  • 1 month later...

I've seen something similar before. The hard drive in our CEO's PC crashed, making a scraping noise any time it was powered up. I pulled the drive apart out of curiosity and was amazed at what I found.

There were two platters in the drive, and at first glance they looked very odd. The mirror surface I expected to see was hazy. After touching the top platter I realized it was covered in a think layer of dust. I didn't take any photos of the tear down, but I saved the platters.

Blame the poor pictures on my camera phone and the poor lighting in my office.

The top of the first platter after being removed and wiped down. As you can see, it looks normal.

aV20PNgi.jpg

The opposite side of the top platter. It's obviously suffered from a failed head impacting the surface, and at first glance it just looks as though it's been scratched. That's not the case however...

aV20QiH9.jpg

The bottom platter, after being removed and wiped down. It's COMPLETELY CLEAR.

aV20QA99.jpg

The heads on both sides of the bottom platter failed, impacting the surface while the drive continued to spin. This caused the heads to act like sand paper and completely removed the magnetic material on the platter, which was what also happened to the bottom of the top platter. The same material is gone and you're looking at the top layer, THROUGH the bottom of the platter. This also explained the dust that was coating every square inch of the the drive. It was the tiny bits of the magnetic material that was scraped off of the platters.

What I found odd was that the platters are actually made of glass. I had always thought they were metal.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft: Windows 11 KB5094126, KB5093998 finally stops trusting a critical system threat by Sayan Sen This week Microsoft released the Patch Tuesday updates for June 2026 with KB5094126 on Windows 11 25H2, 24H2, and KB5093998 on Windows 11 23H2. On Windows 10 22H2 it's under KB5094127. Alongside the announced release notes for the new builds, Microsoft has revealed another change that is coming to Windows with these new releases. It has been confirmed that custom folders are getting a significant change with the June 2026 updates as such folders or folder names defined by desktop.ini will no longer appear after this update is successfully installed. While you may inititally think this is a bug with the new release, Microsoft has stated that this is in fact "expected behaviour" in its new support article regarding this which Neowin spotted today while browsing. Essentially it's a security hardening measure such that custom folder presentations are treated as potentially unsafe whenever Windows is not sure about their origin and whether that desktop.ini folder can be trusted or not. Here is list of such untrusted files and folders: Files downloaded from the internet that carry Mark-of-the-Web (MOTW). Files copied from certain remote locations, such as some WebDAV or HTTP-based locations. Files on network paths that are not classified as intranet or trusted by zone policy. For those who may not be familiar, Desktop.ini is a special configuration file used by Windows to customize the appearance and behavior of individual folders. Basically Windows can read specific instructions stored in Desktop.ini instead of displaying every folder with the same default settings. This can be used to apply custom icons, thumbnail images, localized folder names, and such informational tooltips (infotip). The file can also influence certain folder-specific behaviors and properties. It is typically stored as a hidden system file within a folder that has been designated to support Desktop.ini customization. However, because Windows Shell automatically reads and applies these attributes whenever a customized folder is opened, they have historically (since the Windows XP days) presented an attack surface as a result of an unchecked buffer in the Shell component responsible for extracting custom attributes from Desktop.ini files. As such an attacker could create a specially crafted Desktop.ini containing a malicious or corrupted attributes and place it on a network share. So if a user were to browse that folder, Windows would automatically process the file, potentially triggering a buffer overflow. This could allow arbitrary code to run with the same permissions as the logged-in user. Hence a seemingly harmless folder could become a security risk when their contents are not properly validated. For admins and users alike looking to manage this behaviour, Microsoft has shared a few ways. One of them is to assign a trusted mark on the folder in case you are sure of its source. Secondly a policy can be used to revert back to the previous state. Finally, the MOTW can be removed too to indicate to Windows that this is a safe file. The company explains: Option 1: Add the source to Trusted Sites (Recommended) If the affected content is stored on a known internal or managed source, add that source to the Trusted Sites list. Once the source is treated as trusted, Windows processes desktop.ini from that source normally. This keeps the protection in place for other locations and is the lower-risk option. Option 2: Use policy to restore previous behavior Organizations that need broader compatibility can enable the policy Allow the use of remote paths in file shortcut icons.Enabling this policy restores the pre-June 2026 behavior for affected remote or untrusted scenarios. Option 3: Check for and remove the Mark of the Web (MotW) If the desktop.ini file has a Mark of the Web (MotW), Windows may treat it as coming from an untrusted source and block customization. Verify whether MotW is present and, if appropriate, remove it from the desktop.ini file. This can restore expected behavior, but should only be done for trusted content, as it removes the associated security protection. To remove the MotW tag, open PowerShell and run one of the following commands: For a single desktop.ini file: Unblock-File "C:\Your\Folder\Path\desktop.ini" For all desktop.ini files in a folder: Get-ChildItem "C:\Your\Folder\Path" -Recurse -Filter desktop.ini -Force | Unblock-File Microsoft has warned though against using a broad opt-out using the provided policy as it reduces protection against potentially malicious remote folder-customization content. As such the tech giant recommends trusting only controlled internal sources and keeping trust settings as strict as possible. You can check out the official support article here on Microsoft's website.
    • LAV Filters 0.82.0 by Razvan Serea LAVFSplitter is a multi-format media splitter that uses libavformat (the demuxing library from ffmpeg) to demux all sorts of media files. LAV Splitter is a Souce Filter/Splitter required to demux the files into their separate elementary streams. LAV Audio and Video Decoder are powerful decoders with a focus on quality and performance, without any compromises. Supported Formats: MKV/WebM, AVI, MP4/MOV, MPEG-TS/PS (including basic EVO support), FLV, OGG, and many more that are supported by ffmpeg! LAV Filters are based on ffmpeg and libbluray and is aimed to offer a all-around solution to perfect playback of file-based Media as well as Blu-rays. LAV Filters 0.82.0 changelog: LAV Splitter NEW: Support for demuxing Dolby Vision Enhancement Layer streams NEW: Support for Animated WebP images Changed: When demuxing Blu-ray discs, Dolby Vision metadata is available on the primary video stream LAV Video NEW: Support for Animated WebP images Changed: Hardware decoding support for DVDs has been removed Download: LAV Filters 0.82.0 | 15.5 MB (Open Source) View: LAV Filters Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • For some reason when EU forced Microsoft to allow users to change the default browser and search provider in Windows (also no ads for Office and the likes) - it was good. But when it comes to Apple - then it's bad. BTW, Apple would have gone out of business if Microsoft wasn't pressed by US government several decades ago. 😉
  • Recent Achievements

    • One Month Later
      Sopa flores earned a badge
      One Month Later
    • First Post
      StaticMatrix earned a badge
      First Post
    • Week One Done
      StaticMatrix earned a badge
      Week One Done
    • Rookie
      lamborghiniv10 went up a rank
      Rookie
    • One Month Later
      pinnclepd earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      506
    2. 2
      PsYcHoKiLLa
      207
    3. 3
      +Edouard
      156
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      79
  • Tell a friend

    Love Neowin? Tell a friend!