Slashdot Mirror
Recovering Secret HD Space
An anonymous reader writes "Just browsing hardocp.com and noticed a link to this article.
'The Inquirer has posted a method of getting massive amounts of hard drive space from your current drive. Supposedly by following the steps outlined, they have gotten 150GB from an 80GB EIDE drive, 510GB from a 200GB SATA drive and so on.' Could this be true? I'm not about to try with my hard drive." Needless to say, this might be a time to avoid the bleeding edge. (See Jeff Garzik's warning in the letters page linked from the Register article.)
Sorry, but this is complete bullshit.
Did aureal density technology increase to 200GB/platter overnight? No.
Please refer to this thread on StorageReview.com for more information.
Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
Shenanigans.
No way in heck can you increase the amount of storage a HDD has so drastically. I mean, the physical disks can only hold so much, and no matter what you do, they arent going to magically double or triple.
These are physical disks, they have a set number of sectors. One size and one size only.
Unless you get into the whole mega vs. mibi byte but thats a whole nother can of worms!
http://www.freepokerchipset.info
I'm a Ghost developer.
This is just a method of corrupting your partition table so the same disk sectors appear more than once. If you try this, don't ask Symantec for help afterwards.
'A representative for large hard drive distributor Bell Micro said: "This is NOT undocumented and we have done this in the past to load an image of the original installation of the software. When the client corrupted the o/s we had a boot floppy thatopened the unseen partition and copied it to the active or seen partition. It is a not a new feature or discovery. We use it ourselves without any qualms' Which, having worked for a PC sales company, I can confirm is true. And certainly, while earlier models had partitions you could wipe with partition software, later PC builds had this hidden space. But the space was 1GB at most - there's no way there was the kind of 40GB plus hidden space the article claims.
Gain upto 300-600 more gigs. Your lover will be happy. Risk fre.....wait....lol.
Sorry.
http://www.freebsd.org
I think posting in the "letters" linked article sums it up pretty well:
About the "recover unused space on your drive" article:
Working for a data-recovery company I know a thing or two about harddisks....
One is that if the vendors would be able to double the capacity for just about nothing, they would.
All this probably does is to create an invailid partition table which ends up having:
|*** new partition ***|
|*** old partition ***|
overlapping partitions. So writing either partition will corrupt the other. It probably so happens that whatever situation people tried it, it just so happened that the (quick) format of the "new" partition didn't corrupt the other partition to make it unbootable.
And the 200G -> 510Gb "upgrade" probably has ended up with three overlapping partitions....
Roger
Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
THIS method is obviously BS (to put it mildly) but back when the dinosaurs roamed the earth we could double the size (or was that 1.5x, I can't remember) of a MFM hard drive by hooking it up an RLL controller. I remember putting a full-height IBM 10mb hard drive into my 386 and making it into either a 15mb or 20mb hard drive. I used that hard drive to store and rotate Fidonet echomail for several years, as I recall.
That worked because RLL encoded the data using a different method than MFM.
This, though, is smoke and mirrors.
If you're a zombie and you know it, bite your friend!
Not only do US programmer have to compete against programmers in other countries, but now we have to compete againts the Undead?
Ahhhhhhhhhhhhhhhhhhhhhh!!!!!
The old Linux IDE guy spoke of something like this a while back. Apparently the drive vendors got sick of stocking every drive model for warranty replacement, and implemented a scheme where they could "flash" a generic drive with a specific model number and capacity. Therefore it's possible that your "120GB" drive is really qualified for 160GB but was set that way for inventory reasons.
This was on the linux-kernel list a while back, too lazy too find it. (And it's possible I misunderstood -- Hedrick is a crackpot who is barely able to articulate what he is thinking.)
I saw the article title and I was very excited. I've bought many hard drives, and just recently I bought a 160 gig drive (was like $80 too after a mail in rebate, Fry's I love you...) and was about to buy a 250 ($110 after rebate, Fry's, still love you.) But then I figured, well if I do buy the 250, it's going to be able to hold around 200 gigs, and for some reason 50 gigs will be gone without a trace. I think there's 30 gigs missing on my 160 too, I've noticed this on a lot of drives (as drive sizes go up, so does the missing space.)
I thought this would actually let you use up that lost space somehow, you did buy the drive, it should contain the space, but it doesn't. RAM is just the opposite, you buy 512, it has 560 or so, well any ram I bought did. Anyway, is their a way to recover this lost space? Is their something I'm doing wrong? It seems to be worse in linux (but I heard that's cause it reserves space for root to access.)
In 1994 I bought a box of 720K single-density floppies by TDK. After discovering that making this extra hole could double the disk capacity, I crudely bashed the holes in them with the end of scissors.
These floppies were used almost daily for 3 years. (no hard disks available at that time). They were reformatted countless times.
Not single one of them ever failed. About a year ago, when failed to reformat and make a boot disk from several fresh-brought floppies I digged up one of them, reformatted again and succeeded in making a reliable boot disk.
Quality of todays media just makes me cry.
I'm suprised with all the comments from people who DON'T want to try it out. This is SLASHDOT! Come on don't we all have dozens of 512MB hard drives? Or even some old 10 gig drive that you found in some computer while you were dumpster diving?
(A.K.A The Song of Failing Disks)
Ten little gigabytes, waiting on line
one caught a virus, then there were nine.
Nine little gigabytes, holding just the date,
someone jammed a write protect, then there were eight.
Eight little gigabytes, should have been eleven,
then they cut the budget, now there are seven.
Seven little gigabytes, involved in mathematics
stored an even larger prime, now there are six.
Six little gigabytes, working like a hive,
one died of overwork, now there are five.
Five little gigabytes, trying to add more
plugged in the wrong lead, now there are four.
Four little gigabytes, failing frequently,
one used for spare parts, now there are three.
Three little gigabytes, have too much to do
service man on holiday, now there are two.
Two little gigabytes, badly overrun,
took the work elsewhere, now just need one.
One little gigabyte, systems far too small
shut the whole thing down, now there's none at all.
And not even I believe this one.
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
It seems to work by deliberately corrupting your partition tabes by overlapping your patitions:
Partition a from 0 to 200 GB
Partition b from 1 to 200 GB etc.
You could probably get it to say almost any amount, but it wouldn't be usable space.
Some drives may have a little extra space but not 70 GB on a 80GB drive. No sane company is going to sell a 150 GB drive as an 80 GB because they pay as much to manufacture platters and heads no matter how they're used. The cost of the unused parts would come right out of their profits. Also, sometimes there is "unused space" used for the hard drive's bios, or for relocating data from bad sectors.
"The price good men pay for indifference to public affairs is to be ruled by evil men." -Plato
In other news:
:P
Users report that 486to586.exe actually works.
"It works, it really works", "My machine feels much faster" was some of the comments from the happy users.
Karma whoring: But after some investigation, it was identified as a renamed copy of loadlin.exe
(I post this here because maybe you've been around long enough to remember when ARC vs. ZIP vs. LZH vs. some others was a big deal.)
.BOB.
.BOB extension, but hey, as they say, there's one born every minute.
Back in the days of the "archive format wars" somebody made a program called NaBob that was pretty funny. It made archives that were so perfectly compressed that they approached singularity. That is, every archive turned out to be one byte long.
The various compression methods, it was said, were named after different types of quarks. So, as the files were compressed, it would report, "upping," "downing", "charming," "stranging," etc.
The file extension was
When you ran the uncompress process, all your files would be mysteriously "extracted" from the archive again. Amazing! It really stored all that data in a single byte!
Of course, all it was really doing was setting the hidden file bit on all your files and creating a one-byte file with the
That program always cracked me up, so I just thought I'd share.
Breakfast served all day!
Disks of today have no direct mapping from head, cylinder and track number to physical location on the platter. Rather there is an internal table of the mapping with room for remapping potential weak sectors to unused space. When the head signal is getting close to be inconclusive the just read sector is written at a spare sector, the mapping table is updated, and the old one is marked as bad.
If this article had show how to manipulate the disk so a number of the spare sectors could be used for enlarging the disk it would have been interesting...
:-) = I am happy
:^) = I am happy with my big nose
C:\> = I am happy with my OS
No sane company is going to sell a 150 GB drive as an 80 GB because they pay as much to manufacture platters and heads no matter how they're used. The cost of the unused parts would come right out of their profits.
You'd be correct if there was just one HDD maker in the marketplace, but that isn't so.
First off, let me say that I think this whole isue is bunk. But let's pretend for a moment.
Company A and Company B are both in the business of making and selling HDDs. Company A makes only 200 GB HDDs which cost them about $100 each to manufacture and they then sell them for $200. Company B makes a 200GB HDD which costs them $100 to make and they then sell it for $200. Company B also does this, they modify the firmware of the drive to that only 150 GB are usable. They sell these "150 GB" HDDs for $150.
Company A gets the business of people who are willing to shell out $200 for a 200 GB HDD. Company A does not get the business who have a budget of less than $200 for their HDD purchase.
Company B get the business of people who are willing to shell out $200 for 200 GB HDD and the business of people who have a smaller budget.
By crippling the drive they protect the value of their "high end" product while at the same time making some money on the "mid range" as well
Company A's profits can be calculated like this profit = (X1xP1) whereas X=The number of units sold and P=The profit margin on the unit. #=The model of the HDD
Company B's profits can be calculated like this profit = (X1xP1)+(X2xP2).
This same business principle is a part of the reason why some 2.4 Ghz processors will run at 3 Ghz when overclocked.
I have no doubt that there could be a fair bit of space on a drive that is unavailable to the user, but double or triple capacity? Of course not!
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
CLV is constant linear velocity and is what the first generation CD players used. That meant the data passed under the head at a constant speed, 150kbytes/second. The further out on the disc the slower the disc turned as each turn had more data than close-in.
Once the speeds went up the manufacturers moved to CAV or constant angular velocity where the disc spins at a predetermined speed and the data comes in at different rates depending on the head position over the disc. What really happens is there's a table of different CAVs stored in the drive's firmware depending on the absolute position on the disc. Close into the hub the disc spins faster, further out it spins slower. If there are a lot of errors it will slow down to try and read the data better. On a 48x drive there might be as many as 12 different CAV speeds available to the firmware.
Er. Except that's not how it works.
Intel tests a sample from each batch of processors to determine which "bin" it goes into. That sample tested reliably at 2.4GHz? Okay, into the 2.4GHz pile. That sample tested at 2.8? Okay, into the 2.8 pile. The trick about processors running faster than labeled isn't because they're mislabeling processors, it's that they only test one processor out of the entire batch. Many processors within either batch could be capable of 3GHz, simply due to vagaries of production - you can give it a shot and find out, but don't be surprised when it develops unacceptable amounts of heat like the processor they tested.
HD manufacturers are quite different. When they release a new line of HDs, they are all based off common technologies, but over a wide range of hard drive sizes - because the NUMBER OF PLATTERS inside each model are different. Got a platter that can hold 100GB? Stick 1 inside, you've got a 100GB drive. 2 inside, 200GB. 3 inside, 300GB. There's three models (though drives typically contain substantially more platters). Now you stick 2 in heads for each platter (unless it's one of those old wacky Barracuda drives, which had 4 heads per platter), and firmware that is designed to control the hardware inside the sealed case - but usually even the controller is identical within a line.
One other important thing to remember is that they test the platters BEFORE the HD is fully assembled. This is very different from a processor, where you can't exact test individual components until the entire thing is built. That said, they certainly design in a certain amount of fudge room certainly, so they can remap bad sectors into the fudge room. No platter is perfect, so they need additional space to remap bad sectors. I would be very, very surprised if there's more than 10GB of available space on a 250GB drive...
Notice how they say an unpatched version of ghost is required:
Ghost 2003 Build 2003.775 (Be sure not to allow patching of this software)
That's because the patched version fixes A BUG that allowed the "ever expanding miracle".
Your information is off. Either you haven't used hard drives for about 15 years, or you are making the whole thing up.
The MBR does not store the bad block information. The MBR hasn't stored bad block information since IDE became popular and people stopped being able to low format your their hard drives (no a zero wipe is not a low level format, it simply gives the firmware a good time to reallocate developed bad sectors)
The bad block information is stored in areas of the drive that are completely unaccessable to the outside world, most probably near the servo information on the same track as the actual bad sector. It is only accessed by the LBA mapper in the drive firmware.
The drive actually keeps count of how many sectors it has had to reallocate in its life, and how many sectors it is waiting for a good moment to reallocate. You can get this info from most drives by inspecting the SMART values. Bad sectors do not ussually develop very often after the drive is shipped. You should not see this value be more then 1 or 2 in a young, properly working hard drive.
When the drive detects a sector is going bad, it does not automaticly reallocate it unless it can be correctly read. (or ECC corrected by the drive) This gives recovery software a slim chance of getting lucky and recoving the data from the bad block. The drive simply notes the sector is going bad. If it is read correctly at some late, the hard drive will automaticly reallocate it somewhere else. Alternatively, if a write is issued to a sector awaiting reallocation, then the drive will it perform then rather then wait for a good read.
Also, manufacturers still use aluminium platters in most drives. The embedded servo infomation is used to keep the drive tracking correctly regardless of the temperature of the drive (within specified limits)
Since you didn't read the article, nor any of the comments prevously written, you are completely wrong about this magical utility. It is simply an exploitation of a bug in Norton Ghost that makes your hard drive look larger then it is by overlapping partitions. Attempt to write data to one partition and you will trash the data on the other.
What probably happens here is: ghost creates a special file, or at least writes to an empty part of your filesystem. Then, it writes a complete mini-os to this 8 MB region.
It backs up the original MBR (which is the bootsector, it also hold the partition table) and writes its own MBR. This MBR has a partition table which includes an 8 MB partion. The boundaries of the partition are the boundaries of the special file.
Since this MBR isn't meant to be used in any normal operation environment, it's not quite legal. Some (not all, the MBR can only hold 4) of the original partitions still show up in the new MBR. Therefore, the 8 MB partition lies inside a much larger partition.
This probably confuses fdisk, which lets you create a partition directly after the 8 MB partition, but inside your original partition.
When you subsequently delete the 8 MB partition, fdisk is probably confused again. The end of the original partition is probably obscured by the new, overlapping partition. So it lets you create yet another partition, from the beginning of the disk to the start of the overlapping partition.
The end result is: one large partition holding two small partitions inside it. This will exactly double your diskspace. Just don't try to use it :-)
This is your sig. There are thousands more, but this one is yours.
I can't possibly see how this would work. They're reporting a (more than?) 2x size increase on the largest harddrive they alledgedly did this trick on.
If it works at all, all it really accomplishes is trick windows into thinking the partition really is bigger than it is. There's NO WAY it could get any bigger in reality, since drive capacity is based on the number of sectors the drive reports to the computer, and that is a fixed, hard-coded number that can't be changed by Norton Ghost or any other utility. If you try to address sector maxcapacity+1, you'll just get an error message back from the drive, it won't actually do anything.
This is just a case of someone making sh** up in order to appear on the front page of hardware websites... A bit like participating in a 'reality show' on TV.
You're joking right?
On the subject of the Inquirer article.
The 200JB, or BB or whatever is clearly impossible. There is no hidden space on them to recover at all, let alone 310GB! I can't imagine what kind of idiocy provoked someone to believe that was even possible. Western Digital doesn't make drives with more than 3 platters! The 200GB Western Digitals are only available with 80GB/platters. They only have 5 heads. It's therfore impossible to recover any capacity from them at all (5*40GB=200GB).
Some of the other drives are known to short stroke their platters. This raises the more serious problem of this idiocy... The problem is modern drives store important information on those hidden inner areas of their platters (firmware, disk information, reallocated bad sectors), who knows what you could be overwriting whenever you use that space. Put something down in the wrong place and the drive will never start again or corrupt data at certain sectors. It's a lottery ticket everytime you write data in that partition. That's not what I call useable capacity.
Also, if this was working properly, the 80GB deskstar would yield:
either 90GB (+10GB) if it was a 180GXP (three heads on 60GB platters)
or 80GB (+0GB) if it was a 7K250 (2 heads on 80GB platters)
Anyone with most basic knowledge of hard drives should know that most of the numbers up there are simply impossible, not to mention simply ridiculous.
It's not that there aren't hard drives which are short stroked and sold at a capacity below that available for access in theory, but that something is clearly wrong with this method in that it is simply inventing space that physically can't be there. Perhaps hard drive manufacturers are shortstroking disks to the point that they are formatted with the capacity of drives with fewer platters or heads, but this could never justify the failure of this method on the 200GB Western Digital drive. This drive is a known quantity. No matter what, even if they got a disk that was a shortstroked 6 head drive (which would make no sense), the maximum capacity is 250GB, not 510GB. You would need 7 platters to get that capacity with todays technology!
I would carry your analysis a step further and note that chip and drive manufacturers don't make money by downgrading their product.
I daresay they've a statistical model that has them doing enough sampling to maximize profit, and the means minimizing the amount of irritated customers calling in about problems.
This is not like highway engineering, where they have to figure in weather, vehicles, and Aunt Tillie before posting a speed sign for a curve, so they lowball it heavily.
Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
The Host Protected Area is space on your hard drive that your bios, your operating system or even your applications can be set aside for certain management information. I take it that some backup programs (ab)use it to "hide" compressed boot images on hard drives. I wouldn't be very surprised if companies like Dell or IBM stole some of your hard disk so you can restore a windows installation.The "Host Protected Area" has nothing at all to do with the drive-internal handling of bad sectors or other drive-interal.Drive-internal information as well as sectors used for replacing sectors gone bad are not accessible through the ATAPI commandset for accessing the HPA.
The ANSI T13 Standard Document for ATAPI-6 (current) are overprized at $18.00 but you can download a draft of upcoming ATAPI-7 from the T13 working group's site at http://www.t13.org. There you will find in Section 4.9 of the document: "A reserved area for data storage outside the normal operating system file system is required for several specialized applications". Systems may wish to store configuration data or save memory to the device in a location that the operating system cannot change. The optional Host Protected Area feature set allows a portion of the device to be reserved for such an area when the device is initially configured. A device that implements the Host Protected Area feature set shall implement the following minimum set of commands:"
READ NATIVE MAX ADDRESS
SET MAX ADDRESS ... ...
I take it that READ NATIVE MAX ADDRESS tells you how many sectors of user addressable space have been configured on the drive and SET MAX ADDRESS lets you adjust that.
The way I see it there may be a lot of preinstalled hard drives out there with a compressed windows installation images on them "hidden" in the HPA. Maybe a new version of hdparm will allow linux users to reclaim that dead space.
I happen to work in the processor inducstry, and your statement is untrue. Every processor gets tested. The 'bins' are chosen due to 2 factors:
1) The processor passes testing under extreme conditions at this speed. This gaurantees that the part has a high probability of never being returned as a defect (as silicon is used it ages due to electron-igration, which effectively makes it work slower/stop working eventually). The testing gaurantees that the user won't ever see this impact. In this case, a 2.4GHz binned part may work fine for you at 2.8GHz, but perhaps it will die in 3 years. Or perhaps a single instruction in SSE will return the wrong value 1 time in 100,000. Who knows.
2) Parts are binned to meet supply. The company says it will supply 10,000 2.8GHz parts, and 100,000 2.4GHz parts. However of the 110,000 parts, 40,000 ran at 2.8GHz, and the rest at 2.4GHz. To keep the price scale (and meet the contract) 30,000 oparts which are perfectly good at 2.8GHz will get sold as 2.4
The downside: There is no way to tell (1) from (2) as a consumer, so overclocking is all a game of craps.
Also remember that the tests are done under 'extreme' conditions, which means that all parts will likely work slightly faster than the bin they were assigned to.
Caveat: When a new frequency/design is released, it may be very difficult to get to the desired frequency, and the testing is relaxed somewhat to meet the quota (in which case very few parts will be overclockable)
Lastly, no testing is done above the top bin, so if 3.2 GHz is the current fastest sold, some percentage of those may run at 3.4 or 3.6, and they won't have been tested that far.
The parent post is incorrect in regards to chip testing.
Manufacturers test every single chip pretty much identically. Different companies differ in how they determine speed of parts (run some patterns at full speed, measure the delay of some known circuits, etc.) but each part is tested. There is too much variation across the wafer to do much else.
It's always possible to run a chip faster than a manufacturer's testing especially if it is kept cooler than the max spec, voltage is within tighter tolerance than spec, or if the user doesn't care about correct answers. I find the last point is what usually allows the greatest overclocking.
Also, some large manufacturers (Intel, AMD) have marketing needs to sell certain speed grades. So if all parts run at 3.0GHz, but users are demanding the cheaper 2.8GHz parts, then they'll sell some faster parts marked at 2.8GHz. In general, this is a temporary situation since re-pricing to reflect the increased yield will probably move the 3.0GHz price down shortly to increase pressure on the competition.
I followed the directions to the letter. I ended up with a 1GB drive! (On a supposedly 540MB drive. In the end, FDISK claimed 965 MB.) I filled up the first partition (with mp3s, naturally.) I then started filling up the second partition...
Surprise, surprise. It crashed halfway through copying the mp3s. Reboot? BZZZT! Windows 98 crashed a quarter of the way through loading. Starting up from a DOS disk, and my directory structure is all frooed up on the C partition. Filenames with random ASCII characters in them, inaccessible directories, all sorts of data corruption goodness. The D partition had correct names, though. (So my second batch of mp3s was probably fine.)
(Or, more specifically, do not try this on a hard drive you want to keep, or with data you want to keep.)
Another non-functioning site was "uncertainty.microsoft.com."
The purpose of that site was not known.