Dell Notebook Disk Upgrade problem; need help!
Rusty Williamson
Re: Disk upgrade on Dell Inspiron E1505; Intel CoreTM Duo Proc T2050; XP
Professional SP2
I've just got done upgrading the hard disk on my notebook from a 60GB drive
to a 250GB drive. Rather then reinstall everything I used Apricorn's EZ
Upgrade Sata Notebook Hard Drive Upgrade Kit which creates a 'clone' of your
current disk on the new disk drive.
It worked to a degree: the new 250 hard disk is in the PC and the PC boots
but. only the partition that was cloned over shows up. I expected to see
the other 190GB in Computer Management under Disk Management and be able to
create a partition on it but, its not there. I've rebooted, had the PC scan
for HW changes. In the Bios the drive is listed as a 60GB drive and, as far
as I can see (and I've looked and looked) there is no way to change this! I
checked the Device Manager and the disk seems listed correctly with 'WD' and
'250'.
Anyone have any ideas?
Thanks!
Rusty
--
-------------------------------------------------------
Rusty Williamson
Owner, Technical Director, Lead Animator
Virtualmedia Studios
www.virtualmediastudios.com
S.Lewis
"Rusty Williamson" <ru...@uno.sd.znet.com> wrote in message
news:472935fb$0$16534$4c36...@roadrunner.com...
> Hi,
>
>
>
<snip>
You're absolutely *sure* that BIOS sees only 60gb while Windows sees the
entire 250gb?
I've never seen that.
I have seen it just the opposite, though.
Jay B
it could have written data into the bios to force the size.
also could have written a boot manager on the front of the drive to mask
the size.
the entire 250gb should be listed in disk management and you should be
able to partition to rest of it.
what happened to the dell utility partition at the start of the drive?
Brian K
I understand the HD shows as 60 GB in the BIOS. Does it also show as 60 GB
in Disk Management?
That is, the partitions add to around 60 GB and there is NO unallocated
space. If so, it's fixable.
Rusty Williamson
>
> You're absolutely *sure* that BIOS sees only 60gb while Windows sees the
> entire 250gb?
No... windows sees only the 60gb -- the Device Manager just shows the plug
and play device name I think which indicates 250 GB.
Rusty Williamson
> never heard of that program.
> it could have written data into the bios to force the size.
Well its the old size so I doubt that (if it wrote to the bios it would have
written the new drive data)
> also could have written a boot manager on the front of the drive to mask
> the size.
> the entire 250gb should be listed in disk management and you should be
> able to partition to rest of it.
> what happened to the dell utility partition at the start of the drive?
It seems to be there. The hidden Media Center partitiion is not there (it's
the final partition on the original disk).
In my experience you can usually change the bios to "Auto" (it detects the
drive) or you can spell out the drive specs. Not here. There's something
called 'boot options'... I wonder...?
Ben Myers
disk space. Two solutions. One is to use software like Partition Magic to
increase the 60GB partition to use entire 250GB. The other is to use Windows'
built-in storage management (Administrative Tools) to partition and format the
currently unpartitioned disk space... Ben Myers
On Wed, 31 Oct 2007 20:20:13 -0700, "Rusty Williamson" <ru...@uno.sd.znet.com>
wrote:
Jay B
you can also contact apricorn at their website and see if they know what
happened.
Brian K
OK. It's a Dell issue and not related to the software that you used. Dell
MediaDirect 2 is installed in a Host Protected Area at the end of the HD
and this can't be seen from Disk Management or by partitioning software. It's
commencing sector is controlled by code in LBA-3. (LBA-0 is the "Master boot
record"). Say the HPA commences at the 57 GB mark of your HD. When you
clone your HD to a larger HD then LBA-3 creates a HPA starting at the 57 GB
mark and you "lose" the rest of your HD.
The fix is to zero LBA-3 and then to remove the HPA. Your MediaDirect will
no longer work of course.
This is a procedure to fix your HD so that it shows full size.
You will need to download two files. The first is Roadkil's Sector Editor.
http://www.roadkil.net/diskutils.html
Unzip the file and copy sectedit.exe to a folder in your HD.
The second file to download is Magic Boot Disk
http://hddguru.com/download/software/Magic-Boot-Disk/Magic_Boot_Disk_ISO_v2.0.zip
The main page is
http://hddguru.com/content/en/software/2006.02.10-Magic-Boot-Disk/
but you needn't look at this page .
Unzip the file and burn the .iso as an image. Not as a data CD. For example,
in Nero close the initial window and choose Recorder, Burn Image. Or better
still, use ImgBurn.
Double click sectedit.exe. In the Select Disk box choose Physical 0 and
click Open. (DON'T choose any of the drive letters). Use the arrows at the
bottom right to find LBA-3. It should take 3 clicks. Here is mine which is
already zeroed. Your sector should have code.
http://i16.photobucket.com/albums/b16/bjkdegree/LBA-3.gif
Here is a typical Dell LBA-3
http://i16.photobucket.com/albums/b16/bjkdegree/lba-3_dan.gif
Your sector may look slightly different but if you find the "[XLDR]" string
in the lower right, that's a good clue that you are looking at the right
sector.
Click Edit, Zero Data. Now you should see all zeroes. Click File, Save
Sector. Close Roadkil. Double click sectedit.exe again and confirm that
LBA-3 has been zeroed.
Now shutdown Windows and boot to the Magic Boot Disk CD. Accept the
defaults.
At C:\MHDD> type MHDD and press Enter.
Type the number of your HD (it should be 1) and press Enter.
Now the prompt is MHDD>
Type RHPA and press Enter. Make a note of your Native Maximum LBA address.
You will also see your reduced HD size.
Type NHPA and press Enter. Type Y for "Do you want to set Native LBA
address". Type Y for "Continue".
Type RHPA and press Enter. Your HD should be full size.
Type exit
Remove the CD and boot to Windows. The HD should be fixed.
Rusty, how did it go?
Jay B
space. it only reports the full size at 60gb which is completely weird.
Rusty Williamson
http://www.virtualmediastudios.com/Doc2.htm
--
-------------------------------------------------------
Rusty Williamson
Owner, Technical Director, Lead Animator
Virtualmedia Studios
www.virtualmediastudios.com
"Brian K" <remov...@hotmail.com> wrote in message
news:nBbWi.7407$CN4....@news-server.bigpond.net.au...
Brian K
> I've posted images here:
No image there, Rusty. You are not alone. Many people with Dell laptops have
reported this problem.
Jay B
never showing more than 60gb.
i didnt doubt you.
you can try what Brian suggested.
but, i think it still should show the full amount in disk manager.
i would download and run the bootable partition software and see what it
shows you.
you should be able to resize it.
if you cant see it from a bootable disk, then you have to alter the bios
to change the size.
i think what i said first -- that somehow their software tricked the
system into forcing the size somehow. you can also try clearing cmos.
if not that, then the hard drive could be bad or its really a 60gb drive
in a 250 package...
Rusty Williamson
I've just read through your post -- thank you for all the time you put into
this! My motto is 'there's always an answer'.
Just before reading your post I had just resolved myself to doing it the
right way... I reviewed all that would have to be done (booting the recovery
disk, going through the windows q&a and setup, installing and setting up my
software, etc.) which, I will have to do anyway... damn it.
Your method sounds a tad scary... it goes a layer deeper then I usually go.
I'm going to have to think about this. But regardless of which way I go,
thank you for your effort!!! I'll post what I decide and how it goes.
Cheers,
Rusty
--
-------------------------------------------------------
Rusty Williamson
Owner, Technical Director, Lead Animator
Virtualmedia Studios
www.virtualmediastudios.com
"Brian K" <remov...@hotmail.com> wrote in message
news:tlcWi.7426$CN4....@news-server.bigpond.net.au...
Brian K
"Jay B" <ja...@audiman.net> wrote in message
news:AJcWi.1029$8u...@newsfe09.lga...
>i saw the pics. it only shows the model of the drive. the size is never
>showing more than 60gb.
> i didnt doubt you.
> you can try what Brian suggested.
> but, i think it still should show the full amount in disk manager.
>
> i would download and run the bootable partition software and see what it
> shows you.
> you should be able to resize it.
> if you cant see it from a bootable disk, then you have to alter the bios
> to change the size.
>
> i think what i said first -- that somehow their software tricked the
> system into forcing the size somehow. you can also try clearing cmos.
>
> if not that, then the hard drive could be bad or its really a 60gb drive
> in a 250 package...
Jay, my procedure does work and I'm not surprised that you are dubious.
That's OK. It is the accepted way to fix this problem. This is a fascinating
problem confined to Dell laptops with MediaDirect 2.
Brian K
reference.
http://www.wilderssecurity.com/showthread.php?t=167401
RnR
wrote:
Brian, I don't know about this procedure but if his program really
manipulated the bios into thinking this was a 60gb drive then you
basically have to low level it such that you set the correct
parameters and based on your description I think your procedure does
this. I know about low leveling because back in the old days I used
to purposely crash my drives to learn how to fix them. In those days
you could easily low level them (perhaps I'm being modest here) but
you had to know what to input and then the drive would come back to
normal. That said usually the drive mfgrs. have their own utilities
to fix and clone their own drives. He should check the WD site for
such utilities. I'm not convinced that his device manager will be of
any help to him if the bios is really messed up with the wrong
settings for the drive.
RnR
<ru...@uno.sd.znet.com> wrote:
>Hi,
>
>
>
>Re: Disk upgrade on Dell Inspiron E1505; Intel CoreTM Duo Proc T2050; XP
>Professional SP2
>
>
>
>I've just got done upgrading the hard disk on my notebook from a 60GB drive
>to a 250GB drive. Rather then reinstall everything I used Apricorn's EZ
>Upgrade Sata Notebook Hard Drive Upgrade Kit which creates a 'clone' of your
>current disk on the new disk drive.
>
>
>
>It worked to a degree: the new 250 hard disk is in the PC and the PC boots
>but. only the partition that was cloned over shows up. I expected to see
>the other 190GB in Computer Management under Disk Management and be able to
>create a partition on it but, its not there. I've rebooted, had the PC scan
>for HW changes. In the Bios the drive is listed as a 60GB drive and, as far
>as I can see (and I've looked and looked) there is no way to change this! I
>checked the Device Manager and the disk seems listed correctly with 'WD' and
>'250'.
>
>
>
>Anyone have any ideas?
>
>
>
>Thanks!
>
>Rusty
Yes, go to the WD site and use their utilities to fix your drive.
This stuff is usually provided free. They probably also have cloning
software and I'd use their stuff this time around.
Brian K
See http://www.wilderssecurity.com/showthread.php?t=167401
Correct. There are several tools apart from MHDD that can remove the HPA.
Using the Hitachi Feature Tool and HDAT2 is described in that thread.
An easy way to see if you have a HPA is to use Dan Goodell's DSRFix.
http://www.goodells.net/dellrestore/fixes.htm
Brian K
With Dan's tool, if the 48-bit user sectors doesn't match the 48-bit maximum
sectors then you have a HPA.
Rusty Williamson
YES! It worked like a charm. THANK YOU! Where do you learn this stuff
(really, I want to know)?
For 20 years I was... an Application Programmer/Systems Programmer/Manager
of QC/System and Network Administrator/MIS/Software Architect (what a
title) -- I guess at one time I was a UNIX mini-God in the land of Main
Frames and certainly an UML/RUP/OOP/C++/Rational Rose/Design Pattern God (or
they paid me like one) but, I do not know the PC or Windows as well as I
wish I did. And, LOL, truth told, I don't want to learn! I make virtual
movies now and its too much fun.
However, I will ask you one thing... just because I've been asking everyone
and no one knows, no Google searches have hit anything... my main
development system is a Boxx 3206 AMD Athlon 64 X2 Dual running XP
Professional SP2. Everyday, usually after I've taken a break, explorer.exe
starts doing something that takes up one full core (50% of my CPU) and the
only thing that stops it is a reboot. Its the real explorer.exe, not the
Trojan Horse (or at least it lives in the correct place).
Any ideas?
Thanks again!
Rusty
---------------------------------------------------------
Brian K
"> YES! It worked like a charm.
Rusty,
It's been a pleasure to help you and I can understand why most folks were
dubious. I was fortunate to be involved in that Acronis thread from the
early phase.
Regarding your explorer.exe problem, I have seen this, a few years ago on my
computer. I read some threads about stopping a few services that weren't
needed. It really did fix the problem but I can't remember which services I
stopped.
dg1261
"RnR" <rnrt...@gmail.com> wrote in message
news:knnii3p9pi7045anh...@4ax.com...
> Brian, I don't know about this procedure but if his program really
> manipulated the bios into thinking this was a 60gb drive then you
> basically have to low level it such that you set the correct
> I'm not convinced that his device manager will be of any help to him
> if the bios is really messed up with the wrong settings for the drive.
Really, guys, if you're skeptical of what Brian's telling you, please read
the Wilders link he provided. The problem is known, predictable, and
reproducible. Although it occurs only in Dells with MediaDirect 2, it's not
exactly rare--more and more users are discovering the problem as they get to
the point where they want to upgrade to a larger hard disk. For those who
don't want to wade through the complete and very detailed information in the
Wilders link, I've posted a one-page recap of the issue on my website at
www.goodells.net/dellrestore/hpa-issues.htm.
This is not a bios issue, low-level formatting won't help, and the WD
utilities (or anyone else's, for that matter) won't prevent the problem from
recurring. It is caused by the Dell MBR for MediaDirect 2, and will happen
anytime Dell's MBR is copied to the new disk as part of the cloning process.
In a nutshell, the fix Brian provided is to break the Dell MBR so it doesn't
do what Dell intended.
BTW, Brian wasn't suggesting Device Manager would fix anything, it was
merely a diagnostic step to confirm the system thinks the entire hard disk
is truncated and smaller than it really is. This is to eliminate the common
newbie mistake of looking only at the size of the C: partition rather than
the entire disk.
Dan Goodell
RnR
wrote:
Not to pick hairs but I didn't say " he " said it would help. I said
it wouldn't help because it just lists the drivers installed and is
not necessarily what the peripherals really are tho most of the time
they are the same. I'm not familiar with the bug described so
perhaps you and Brian are correct about cloning a Dell MBR but if you
low level the drive and then format it (high level) it will rewrite
the MBR thus restoring the drive back to it's original state before
any cloning begun.
And I wasn't skeptical of what Brian was saying. I just said I don't
know of the procedure which isn't meant to say it does not work.
RnR
Brian's post is correct about the services. I'll suggest you go to
"blackviper.com" as he describes each service and whether you really
need it. I've heard there are other sites as well but I don't recall
their names. I suppose you could google on "services" as well.
Brian K
I think Dan's Device Manager was a typo and he meant Disk Manager.
If you were aware of this problem before cloning your old HD to a new HD
then you would zero LBA-3 on the old HD prior to the clone procedure.
Another way is to create images of the old HD partitions and restore these
images to the new HD but don't choose the option to restore the MBR and
Track 0. A generic MBR will be written to the new HD so the OS will boot but
the Dell LBA-3 will not be present on the new HD so the HPA will not be
created on the first boot.
But in reality, most people will not be aware of the problem and will get
caught.
RnR
wrote:
>RnR,
Brian, just for the record I don't/didn't doubt your procedure to fix
the OP's problem. I think some may have misinterpreted my words.
Right about that ... I was not aware of the problem and your solution
(and tried to say that earlier without implying anything else) so I'd
probably fall back on my experiences and try to low/high level the
drive if possible or searching for another fix.
In any case, your post is good info.
Brian K
> Brian, just for the record I don't/didn't doubt your procedure to fix
> the OP's problem. I think some may have misinterpreted my words.
> Right about that ... I was not aware of the problem and your solution
> (and tried to say that earlier without implying anything else) so I'd
> probably fall back on my experiences and try to low/high level the
> drive if possible or searching for another fix.
>
> In any case, your post is good info.
I understand and I also understand anyone being skeptical of the procedure.
It does seem weird and we do see a lot of strange posts.
dg1261
> I'm not familiar with the bug described so perhaps you and
> Brian are correct about cloning a Dell MBR but if you low
> level the drive and then format it (high level) it will rewrite
> the MBR thus restoring the drive back to it's original state
> before any cloning begun.
Unfortunately, that won't be enough if you've already fallen victim to the
bug. That won't reverse the HPA. You'll need to take additonal steps, as
detailed in the Wilders thread.