The late XV105
16th Jun 2011, 21:11
What is "Access Mode" in the BIOS of my ASUS P5N32-SLI motherboard, please?
I ask because I have just cloned the HDD that runs the XP operating system and Program Files of my media server. Initially, swapping out the original o/s HDD and replacing it with the cloned one gave rise to boot failing with "Error loading operating system". I was puzzled because the cloned HDD is a box new and identical Seagate Barracuda (apart from slightly later firmware I see) and I was careful to write the MBR, the boot sector, and the boot.ini.
After logical trial and error I found that I could solve the problem and successfully boot from the clone so long as I followed this process (some details are irrelevant but I include them all to give continuity):
Mount target HDD in external enclosure and connect to PC (I used eSATA)
Switch on media server and enter BIOS
For the target HDD, change Access Mode from AUTO to LARGE
Save changes and boot
Perform a full format of the target HDD
Clone HDD yadda yadda yadda
Shut down media server
Open enclosure and remove cloned o/s HDD
Swap o/s HDD for cloned o/s HDD (in the same bay as it happens)
Restart PC and enter BIOS
For the boot HDD, change access mode from AUTO to LARGE
Save changes and boot
Observe successful boot; all is cushty
If I formatted and cloned the target HDD having booted beforehand as Access Mode AUTO, the cloned result wouldn't work whether set to either AUTO or LARGE when booted for use. Neither would it work if formatted and cloned as LARGE but then booted for use as AUTO. I have to use Access Mode LARGE both before formatting & cloning and for runtime usage.
Why, please, since the donor HDD works just fine with Access Mode AUTO (but I now know won't boot if left as LARGE)?
It's no big deal, and I have a working clone now locked safely away in my employer's backup facility, but I'm curious.
I ask because I have just cloned the HDD that runs the XP operating system and Program Files of my media server. Initially, swapping out the original o/s HDD and replacing it with the cloned one gave rise to boot failing with "Error loading operating system". I was puzzled because the cloned HDD is a box new and identical Seagate Barracuda (apart from slightly later firmware I see) and I was careful to write the MBR, the boot sector, and the boot.ini.
After logical trial and error I found that I could solve the problem and successfully boot from the clone so long as I followed this process (some details are irrelevant but I include them all to give continuity):
Mount target HDD in external enclosure and connect to PC (I used eSATA)
Switch on media server and enter BIOS
For the target HDD, change Access Mode from AUTO to LARGE
Save changes and boot
Perform a full format of the target HDD
Clone HDD yadda yadda yadda
Shut down media server
Open enclosure and remove cloned o/s HDD
Swap o/s HDD for cloned o/s HDD (in the same bay as it happens)
Restart PC and enter BIOS
For the boot HDD, change access mode from AUTO to LARGE
Save changes and boot
Observe successful boot; all is cushty
If I formatted and cloned the target HDD having booted beforehand as Access Mode AUTO, the cloned result wouldn't work whether set to either AUTO or LARGE when booted for use. Neither would it work if formatted and cloned as LARGE but then booted for use as AUTO. I have to use Access Mode LARGE both before formatting & cloning and for runtime usage.
Why, please, since the donor HDD works just fine with Access Mode AUTO (but I now know won't boot if left as LARGE)?
It's no big deal, and I have a working clone now locked safely away in my employer's backup facility, but I'm curious.