Hey guys, first post here. Been a long-time lurker, thought it'd finally be time for me to join everyone else. Unfortunately, it's not on a light note...
One year ago when I first bought my computer, I decided to install a program my motherboard manufacturer (GIGABYTE) provided, which allowed me to image my operating system into a special partition on the hard drive. Not too long after, I decided to stop using it, thinking buying Ghost would be a better option. Now, when I tried to search for the partition where XpressRecovery2 (the program) installed itself, I couldn't find anything. Windows reported the hard drive as having a much lower capacity than it should have!
Doing some further research (and attempting to create a partition in the free space using a LiveCD), I found out that the missing space was related to a DCO lockout. Did a test using hdparm on the LiveCD to see if it was an HPA that was causing it, but hdparm gave me a negative on that (process of elimination is what led me to the DCO conclusion). I then downloaded a tool called HDD Capacity Restore, and it reported missing space on the drive; however, when I attempted to use it to restore the space, it stated that it encountered an error. SpinRite came right after this, and it gave me a shocking (not really...) report: the BIOS itself may be enforcing the DCO, as it could not read the entire sector span of the partition.
I am, well, disappointed...at GIGABYTE. Why they would use this method to install their imaging software is strange, but meh. Interestingly enough, when I tried to format the partition as FAT32 under Windows, it reported 137K (!) bad sectors on the partition, which I know for sure isn't bad because I haven't had a single bad sector occur on the drive yet.
Anyone have any thoughts? It seems I'm at a wall.
Removing a BIOS-enforced DCO partition
Moderator: Thanas
-
- Youngling
- Posts: 67
- Joined: 2008-12-29 05:26pm
- DesertFly
- has been designed to act as a flotation device
- Posts: 1381
- Joined: 2005-10-18 11:35pm
- Location: The Emerald City
Re: Removing a BIOS-enforced DCO partition
Backup, do an fdisk and a complete reinstall from disc?
I'm sure people with more expertise will come along with better ideas, but that's what I got now.
I'm sure people with more expertise will come along with better ideas, but that's what I got now.
Proud member of the no sigs club.
-
- Youngling
- Posts: 67
- Joined: 2008-12-29 05:26pm
Re: Removing a BIOS-enforced DCO partition
Linux's fdisk won't work due to the aforementioned bad-sector issue, and Windows wouldn't even see that section anyway. Just recently attempted flashing the BIOS to a newer version to see if that would reset anything; no go.
Oh well, I've more or less given up on trying to reclaim the space. It's 133MB worth, but still...133MB...
You could put so many Maya files there. Damn you GIGABYTE!
Oh well, I've more or less given up on trying to reclaim the space. It's 133MB worth, but still...133MB...
You could put so many Maya files there. Damn you GIGABYTE!
Re: Removing a BIOS-enforced DCO partition
How much is 'much lower'? Are we talking about a sizable percentage of the drive, or just a few hundred meg?
-
- Youngling
- Posts: 67
- Joined: 2008-12-29 05:26pm
Re: Removing a BIOS-enforced DCO partition
Just a few hundred megs, but as I said, I like having all my space available.
I guess "much lower" was an exaggeration of sorts, but these days I literally use all the hard drive space I can muster.
I guess "much lower" was an exaggeration of sorts, but these days I literally use all the hard drive space I can muster.