Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Imaging OS from a 20GB IDE Drive and moving it to a 40GB SATA Drive

  • 06-07-2005 9:39am
    #1
    Registered Users, Registered Users 2 Posts: 68,190 ✭✭✭✭


    This could belong in either Windows or here, so hopefully someone can help.

    I've never used ghosting software before, which is probably where the bulk of my confusion is.

    I have Windows 2003 on a server. The primary HDD (IDE-0, master) is 20GB, which is where the OS lies, with a 200GB (IDE-0, slave) drive for data. Performance is poor from the 20GB, it's an oldish drive. So I want to replace the primary HDD with a smallish SATA drive - this one seems like a candidate.

    Now obviously, I could reinstall the OS, but that's far from ideal. I have a lot of services set up just the way I want them.

    So, could anyone recommend a plan of action here? Getting the necessary software is not a problem. Should it be possible to install the Sata drivers for the motherboard, ghost the 20GB, install that image to the 40GB, then boot straight off the 40GB?
    Will the existing IDE drive cause hassle, i.e. will it be first in boot priority? Motherboards is Abit VA-20.

    Cheers


Comments

  • Registered Users, Registered Users 2 Posts: 1,268 ✭✭✭Zapho


    I did a clone of a drive recently enough from a 10gb to a 20gb, but both were IDE and it was a clone of an XP partition. I used Partition Magic and just copied the 10gb partition to the 20gb drive. Its an exact image so one I did the clone and replaced the 10gb with the 20gb the 20gb drive booted up just fine. Then I just resized the primary partition on the 20gb drive because it was on 10 gb in size.
    I think you should install the sata drivers onto your 20gb drive first otherwise the sata drive won't boot.
    The only annoying thing about all this was that when I booted windows for the first time it said that there was "significant hardware changes" and that I would have to reactivate Xp within 3 days. Hope this helps!


  • Registered Users, Registered Users 2 Posts: 68,190 ✭✭✭✭seamus


    Zapho wrote:
    I did a clone of a drive recently enough from a 10gb to a 20gb, but both were IDE and it was a clone of an XP partition. I used Partition Magic and just copied the 10gb partition to the 20gb drive. Its an exact image so one I did the clone and replaced the 10gb with the 20gb the 20gb drive booted up just fine. Then I just resized the primary partition on the 20gb drive because it was on 10 gb in size.
    I think you should install the sata drivers onto your 20gb drive first otherwise the sata drive won't boot.
    The only annoying thing about all this was that when I booted windows for the first time it said that there was "significant hardware changes" and that I would have to reactivate Xp within 3 days. Hope this helps!
    Excellent, cheers helps clear it up a bit alright. The only difference with my setup is the mixed SATA/IDE environment, but I'm sure Google can help answer that one.


  • Registered Users, Registered Users 2 Posts: 5,333 ✭✭✭Cake Fiend


    seamus wrote:
    Should it be possible to install the Sata drivers for the motherboard, ghost the 20GB, install that image to the 40GB, then boot straight off the 40GB?
    Will the existing IDE drive cause hassle, i.e. will it be first in boot priority? Motherboards is Abit VA-20.

    Cheers

    This is worth a shot first, but usually problems arise with imaging XP/2003 installations because of differences in HD controllers (e.g. if you move a drive from one motherboard to another). As you mentioned, it seems that XP/2003 use their usual controller drivers as 'priority', so they panic when the controller changes (in fact, I think it may make major customizations to the HAL on first install). If just having the drivers installed doesn't work, there is a way of kind of resetting the OS to re-install its first-priority controller drivers, providing you have the new drivers installed. You can do this through a registry hack (google, I can't remember off-hand what you should search for, but it's out there, I've used it successfully myself) and possibly through sysprep (if available for 2003). I'll have a quick shufty, if I find a link I'll post it.

    Edit: hmm, can't seem to find what I was talking about, the only workaround I can find is the old repair-installation trick. This is a pretty inconvenient way of doing things (have to reinstall all updates, rollups, etc), so try to find the reg-hack way first if you can. That's if you even need to do it in the first place - I don't know much about SATA, but it's possible that your current chipset drivers will let you interface with the SATA controllers just as easily as the IDE.


  • Moderators, Recreation & Hobbies Moderators, Science, Health & Environment Moderators, Technology & Internet Moderators Posts: 94,288 Mod ✭✭✭✭Capt'n Midnight


    If it's going into a different machine then sysprep sure sounds like the best way because of all the outer hardware changes.

    Other options - could you get an IDE to SATA conveter so you still use the original IDE controller ?

    Does SATA require you to press F6 and then load a driver ?

    BTW:
    Also is there any way of "disabling" the IDE controller in 32 bit windows or selecting generic EIDE / IDE / ST-506 so it doesn't care - a bit like the way DOS does or selecting VGA instead of a more specific video driver ? Have gone through the pain of NT blue screening on a different revision of the Intel PIIX4 chipset so out of curiousity I'd like to know how to turn them things off.


Advertisement