Write Bits Directly Onto a Hard Drive Platter? 578
kidcharles writes "I'm working on a project that requires writing bits to a magnetic hard drive platter in a completely controlled fashion. I need to be able to control exactly where 1s and 0s will appear physically on the platter. Normally when data is written to a drive the actual bits that get written are determined by the file system being used, as modified by whatever kind of error handling the drive itself is using (e.g. Reed-Solomon). All of the modern innovations in file systems and error handling are great for reliable and efficient data storage, but they are making my particular task quite daunting. My question for Slashdot: is there a way to get down to the 'bare metal' and write these bits? Any good utilities out there to do this? Obviously a free and open source solution would be preferable, but I'm open to anything at this point."
magic marker (Score:5, Funny)
May I suggest (Score:2, Funny)
Be careful! (Score:5, Funny)
I can't help directly, but can give one important advice - careful how you distribute the bits! If too many ones get on the same side of the platter this will destabilize it, causing it to wobble due to the weight difference ( a one weighs quite a bit more than a zero, you know!) and potentially tearing the platter in two!
I tried it once (Score:5, Funny)
Got myself a disk editor, and wrote something on the very first sector.
After that I can't use the HD anymore.
The computer can't even recognize it anymore.
There is a real possibility to do this. (Score:2, Funny)
>Any good utilities out there to do this?
Yes. My solution involves a screwdriver and a sharpie. And you can write bits of information to the bare metal, like "this drive is broken, dont waste your time trying to fix it".
My colleague was not happy finding the drive on his desk and told me its a low level joke. Well, yes.
Re:Be careful! (Score:5, Funny)
I can attest that improper bit stacking is a very real danger - one that almost cost me my life.
It was in 1999 in Sierra Leone, and my last assignment before I left for Sydney was to punt three hundred reams of bit-printed A4 four kilometres up the Moa to a nearby monastery.
It had been a hectic week and the crew the boss had assigned to load the raft had already worked a double shift. Subsequently, they failed to read the job sheet properly and loaded the raft with the all the paper with the zero-bit set on one side and the one-bit set on the other.
I got about three hundred meters from the dock when I was startled by a large black snake swimming past. I quickly moved from where I was sitting on the zero-bit stack to the one-bit stack, and of course the raft immediately capsized.
I was told when I reached the shore that the snake had most probably been a mamba - one of the deadliest snakes in Africa. If I had been bitten I would have been dead within minutes.
I hope this serves as a warning to anyone involved in any kind of data stacking. In short, always properly disperse your bits - your life may depend on it!
Re:too late? (Score:1, Funny)
Re:Data Recovery (Score:2, Funny)
Re:Data Recovery (Score:3, Funny)
Good. Go write "Paulatz wuz here" next to the HOLLYWOOD sign.
That's nothing! (Score:5, Funny)
Re:That's nothing! (Score:5, Funny)
"transmute lead into gold in a cost-effective manner"
Rob a bank with a gun?
Are you sure that's your requirement? (Score:5, Funny)
"I'm working on a project that requires writing bits to a magnetic hard drive platter in a completely controlled fashion."
Are you sure?
The reason I ask is I'm working on a project that requires me to move data faster than light. At least that's what I spent last Monday working up the math to prove that data replication between our different data centers has an upper bound enforced by the fabric of the universe and that it was impossible for me to achieve the project's stated goals without essentially inventing warp drive. As it turns out after a meeting it was determined that the goal was just a stated guideline. It also turns out the price of faster data transfer rates is prohibitive and after a further meeting the stated project goal was total baloney. Yes. Baloney. We had sandwiches. It was a nice meeting.
Re:That is gonna be hard (Score:1, Funny)
... parametrize ... influence ... situation ... position ...
You sound like a corporate buzzword generator [andrewdavidson.com].
Re:Be careful! (Score:1, Funny)
Virus: Let me trim the FAT off your hard disk. (Also works for solid state drives that support TRIM operation.)
By the way, compression makes your data occupy less space, by converting all the bits from 0 to 1. Because 1 weighs less. Also, it makes the hard drive faster (after defrag) because 1 is more aerodynamic than 0.
One more possibility... (Score:3, Funny)
It CAN be done! (Score:4, Funny)
Re:Wrong. (Score:2, Funny)
No, its only that his writing algorithm a word.
Re:ob XKCD reference (Score:3, Funny)
Re:Wrong. (Score:2, Funny)
But how can be sure?
Re:One more possibility... (Score:3, Funny)
Re:Wrong. (Score:1, Funny)
Your sentence is wrong, sorry.
Your sentience is wrong, sorry.
Re:Sure (Score:2, Funny)
Re:Slashdot trolled (Score:3, Funny)
gives new meaning to "my 2 cents worth" [google.com]
Re:DRM? (Score:4, Funny)
The romantic in me wonders if he is trying to create a piece of art. Next week's front-page headlines are like "Hard-Drive Hacker Recreates 'Starry Night' Directly On Platter".
Re:Be careful! (Score:4, Funny)
Oh, hell yeah. Sometimes on a slow day, when there's little wind and a crowd outside the building, my colleagues will send around a bunch of emails full of ones. The cables outside twist and swing, and people look around for the source of wind.
Those recent communication satellite crashes? Too many ones got in their relay buffers, weighing them down and destabilizing their orbits.
Re:Sure (Score:1, Funny)
> Not to mention that disks haven't actually written "zeros and ones" as such for at least 15 years
Roight--modern drives go to ELEVEN!
Re:Are you sure that's your requirement? (Score:4, Funny)
The reason I ask is I'm working on a project that requires me to move data faster than light. At least that's what I spent last Monday working up the math to prove that data replication between our different data centers has an upper bound enforced by the fabric of the universe and that it was impossible for me to achieve the project's stated goals without essentially inventing warp drive.
I have a solution for your problem:
1. Declare your main data center King. This requires a coronation ceremony and a crown.
2. Declare your backup data center Crown Prince. This does not require a ceremony.
3. Push the big red button that kills your King (the main data center).
Thus, by the laws of royal succession, your backup data center will instantly become King with all the knowledge of its predecessor. And that is how you to move data faster than light without violating the laws of physics.
Re:Slashdot trolled (Score:5, Funny)
Find a drive with characteristics similar to what you want, and contract with the manufacturer to modify the drive to do what you want. The manufacturer has the tools and engineers to alter the existing firmware. It won't be cheap. If the manufacturer refuses the proposal, buy the company.