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

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      594
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      74
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!