error loading os

[David Cockram]

Hi,
I have 2 SATA drives, and I've been struggling to do a simple clone of my
Seagate C: partiton to a Maxtor F: partition.
I've tried Ghost 9.0, Acronis True Image 8.0 and other trial software. In
most cases I got as far as a login screen and it reverted to a plain blue
screen with cursor. I always remove Seagate before trying to boot with the
cloned Maxtor. The only thing that did consistently work was Acronis Migrate
Easy, but the problem is that you need to copy the entire disk. That means
overwriting the other Maxtor partitions. But it proves that it did work. Now
why did it, and not the others?

Now whilst playing around with all this I noticed that I was getting 'error
loading os' when trying to boot. When I went back to Acronis, that was also
giving this message, and not even attempting to boot as it had previosly
done. I tried using sysprep with the same result.

Then I tried removing partitions completely from the Maxtor, using fdisk and
dos to format, using Max Blast to format, using the
XP repair tool, fixmbr, fixboot. You name it I tried it I think.

So I then thought I'd see if I could install XP on this drive. No, I get the
same message when it gets to the booting from disk stage.

Firstly, any ideas what could have caused this, and secondly do I need to do
a low level format to get this drive back to normal shipping condition. If
so, could someone tell me how, and what software to use, as I've done this
before.

I've now done a fair bit of reading about cloning. For a lot of people it
seems to be a completely painless process using Ghost or Acronis. For many
others including me, it just doesn't seem to work, and I've seen the same
issues reported over and over with no workable solutions.

Ah well, I'll get there in the end. Maybe sooner with your help. Thanks,

Dave Cockram

 

[Yves Leclerc]

On your Seagate drive, did you add the SATA drivers?? The SATA drivers may
need to be installed before you clone the drive??

 

[Guest]

David,

Try using the Maxtor as a SLAVE, first. Install the Maxtor software, from
CD to the Master HD. ONce done you have XP on the master with the necessary
files to enable reading of the Maxtor HD. Format the Maxtor to a single
Partition and then when complete use the ghost to copy from Master to SLave.
Now remove the Master, set the jumpers on the slave for Master and reboot. If
this doesn't work, ignore what I said, have a couple of shots of J.D. and
start over. Good Luck.

 

[Jeff]

Another thing that you might check is in your Bios to make sure that the
SATA drive is still set as the boot drive. My system will periodically drop
the Sata drive as the boot drive and I have to go into the Bios and reset it
as the boot drive. I have not found an answer as to why that happens but so
far everytime that I have recieved the error loading os that has been the
problem. Just a thought.

Jeff

 

[Cycle]

Another thing that you might check is in your Bios to make sure that the
SATA drive is still set as the boot drive. My system will periodically
drop
the Sata drive as the boot drive and I have to go into the Bios and reset
it
as the boot drive. I have not found an answer as to why that happens but
so
far everytime that I have recieved the error loading os that has been the
problem. Just a thought.

Jeff

I seem to have found a cure for my particular “Error loading OS” problem.



I have two Maxtor SATA hard disc drives. These show up in my BIOS as
PM-Maxtor, and underneath SM-Maxtor (i.e. Primary and Secondary). The first
drive in this list, PM-Maxtor, is the boot drive containing the operating
system.



On boot-up, the BIOS looks for an operating system on the first drive in the
list only. Thus it looks on PM-Maxtor, finds the operating system, and boots
up.



However, about once a week on boot-up I got the “Error loading OS” message.
I noticed that in the BIOS, PM-Maxtor and SM-Maxtor had changed places. So
SM-Maxtor was being searched for the operating system – and it did not have
one of course.



I think I may have found out why this changeover was happening. The SATA
lead connecting the PM-Maxtor drive to the motherboard fitted very loosely
on the pins on the drive. At boot-up, with the metal cold, it was as though
the PM drive was not making good enough contact with the motherboard and was
not being properly detected by the BIOS.



I replaced the SATA connecting lead with one of a better quality that
gripped the connecting pins on the drive more firmly, and have not had the
“Error loading OS” message in four months. As it was happening weekly in the
two months prior to changing the lead, I think there is a strong possibility
that the problem, in my case at least, was caused by poor electrical
connections. (Once I suspected what was happening, I pushed the original
lead onto the drive tightly, where it lasted about a week before giving
trouble again.)



I should be interested to know what make of drive and SATA lead is being
used by anyone else with this problem.



Cycle.

 

[David Cockram]

OK, we're making some progress here. I can now make and restore a clone copy
in Acronis 8.0.

I need to follow these steps EXACTLY.

1. Don't format or give a drive letter to the recipient drive (Maxtor first
partition here)
2. Use Acronis from boot CD not XP
3. Swap SATA cables before rebooting so Maxtor drive is now on same cable as
original Seagate

And this is the killer - if I don't do one of these and the cloning process
fails, than it will ALWAYS fail UNTIL I do a disk copy with Acronis. This
overwrites my entire drive and it's not entirely convenient to ship out
100GB of data to somewhere else. (Andrew mentions earlier in the thread a
method using recovery console which I'll try if I need to in future.) And
bizarrely this not only clones the drive correctly, but it puts it back to
normal such that I can now successfully clone a partition.

So, what on earth is going on here? Why did the boot sector get screwed up
( I assume that's what it was) and why did none of the standard fixes for
this type of problem not work - fixboot /fixmbr?

I gather at least some of this is caused by me using SATA drives. Perhaps
there will be no such problems with Ghost 10.0 and Acronis 9.0?

Dave

 

[Walter Clayton]

Prior to the clone, delete all but the default value from
HKLM\system\mounteddevices.

 

[David Cockram]

Presumably XP will just rebuild this from scratch again? Do you think that
is what stopped the clone booting when it almost got to the login screen and
then reverted to a plain blue screen with cursor?

Dave

 

[Walter Clayton]

Yes it will get rebuilt and yes, if that's not deleted then cloning just the
partition image itself can cause some less than desirable results. In fact
if you check
HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore MS back
up / restore tools don't restore that key.

 

[David Cockram]

Walter, HELP! ! !

I deleted that key as suggested, HKLM\system\mounteddevices (except default
value).
Before restoring the clone onto the other drive I decided to just check the
values in the key after rebooting and supposedly rebuilding.

After entering my password at the log in screen, it immediately reverts to
logging off . . .
I have tried everything I can think of, safe mode, boot disk but can't log
on any more.

I then tried restoring the saved cloned partition to the other drive and got
NTLDR is missing. So now I don't have any bootable drives.Back to Acronis
boot CD to restore an earlier clone that worked and restored. The first
partition, E: on the Maxtor was greyed out so I couldn't access it. I
eventually used MaxBlast to repartition and then Acronis restore worked, and
I'm now back to using an earlier saved clone that I've restored on the
Maxtor. I haven't touched the Seagate C: so if there's a way of accessing
and putting back this registry key (which I stupidly didn't feel the need to
save) maybe I can get back to normal.

I swear once this is over, I won't touch any of this software for a long,
long time. There are just too many issues and problems here. Restoring all
my programs in an emergency pales to insignificance compared with the time
and hassle spent so far.

Thanks in anticipation,

Dave


----- Original Message -----
From: "Walter Clayton" <[email protected]>
Newsgroups:
microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
Sent: Sunday, April 24, 2005 1:28 AM
Subject: Re: error loading os

 

[Walter Clayton]

I assume you're up and running on the problematic platform? If so, go to
http://www.bootitng.com/utilities.html and download Partinfo. Unzip it and
run partinfW (yes, that W not O) from a command prompt as follows:

partinfw >partinfo.txt
start notepad partinfo.txt

Then copy and paste the contents back here. Also, do start->run->c:\boot.ini
and copy and paste the contents of boot.ini back here as well.


I think I know what your issue is now and it's going to revolve around
boot.ini and the mbr code and now that I've taken a really fast look at
Acronis, it may be the tool isn't the right tool for what you're attempting.
Or you may be using it wrong.

 

[David Cockram]

Thanks Walter,

I'll do it now, but in the meantime, I'm only up and running on my second
hard drive, the Maxtor. The Seagate which has the problem is inaccessable. I
don't know if that affects things. Let me know if it does.

Dave

 

[David Cockram]

The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
missing. I don't know if that's because I'm now bootiing from the other
drive.

boot.ini from the Maxtor drive I'm now using - SATA 2

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect /NoExecute=OptOut


PARTINFO 1.09
Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.

Run date: 04/24/2005 16:06

====================================================================
MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
+====+====+=============+====+=============+===========+===========+
Volume Information
+----+----+-------------+----+-------------+-----------+-----------+
| 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x04E1AF2A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x04E1AF2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x22F802A6F8027875
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 81915435
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xD400C167C150E2
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 333991350
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xA478DD6678DD382E
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
====================================================================
MBR Partition Information (HD1):
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x024C1258
MFT LCN: 0x0B42FF
MFT Mirr LCN: 0x03D54EA
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x4228D79E28D78EF3
Checksum: 0x0
Boot Flag: 0xAA55

 

[David Cockram]

I also just noticed that my drive letter asignments are all screwed up.

The Seagate (SATA 1) should be C,D,E with C being active. It is now F,D,E
with D being active (OS is on F).
The Maxtor (SATA 2) should be F, active. It is now C, active.

Dave

The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
missing. I don't know if that's because I'm now bootiing from the other
drive.

boot.ini from the Maxtor drive I'm now using - SATA 2

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect /NoExecute=OptOut


PARTINFO 1.09
Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.

Run date: 04/24/2005 16:06

====================================================================
MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
+====+====+=============+====+=============+===========+===========+
Volume Information
+----+----+-------------+----+-------------+-----------+-----------+
| 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x04E1AF2A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x04E1AF2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x22F802A6F8027875
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 81915435
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xD400C167C150E2
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 333991350
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xA478DD6678DD382E
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
====================================================================
MBR Partition Information (HD1):
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x024C1258
MFT LCN: 0x0B42FF
MFT Mirr LCN: 0x03D54EA
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x4228D79E28D78EF3
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------

Thanks Walter,

I'll do it now, but in the meantime, I'm only up and running on my second
hard drive, the Maxtor. The Seagate which has the problem is
inaccessable. I don't know if that affects things. Let me know if it
does.

Dave

 

[Walter Clayton]

The partition structure is a bit weird. You have a logical with what appears
to be a single volume followed by a couple of standard bootable primaries.
In fact, the second partition is currently flagged as active.

MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |

The boot strap code would have to be in the second partition. That includes
boot.ini, ntldr, ntdetect.com. The arc statement for that partition will be
tricky, that depends on from where you're loading the OS. If you're loading
the OS from the same partition, using the current partition and volume
tables, the arc statement should read

default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

although the partition number might need be three depending on how things
are counted (and I get really fuzzy on how the boot strap code counts
logical partitions and volumes; I avoid placing logicals in front of
non-logical volumes like the plague).

Exactly what are you attempting to accomplish? One thing that sticks out is
to move the logical higher in the partition table and drop the bootable
primary in front of that.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.

The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
missing. I don't know if that's because I'm now bootiing from the other
drive.

boot.ini from the Maxtor drive I'm now using - SATA 2

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect /NoExecute=OptOut


PARTINFO 1.09
Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.

Run date: 04/24/2005 16:06

====================================================================
MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
+====+====+=============+====+=============+===========+===========+
Volume Information
+----+----+-------------+----+-------------+-----------+-----------+
| 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x04E1AF2A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x04E1AF2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x22F802A6F8027875
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 81915435
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xD400C167C150E2
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 333991350
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xA478DD6678DD382E
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
====================================================================
MBR Partition Information (HD1):
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x024C1258
MFT LCN: 0x0B42FF
MFT Mirr LCN: 0x03D54EA
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x4228D79E28D78EF3
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------

Thanks Walter,

I'll do it now, but in the meantime, I'm only up and running on my second
hard drive, the Maxtor. The Seagate which has the problem is
inaccessable. I don't know if that affects things. Let me know if it
does.

Dave

 

[Walter Clayton]

First rule when dealing with multiple partitions is that drive lettering is
fluid and meaningless.

See other post since it's time to figure out exactly where you think you are
and where you're going.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.

I also just noticed that my drive letter asignments are all screwed up.

The Seagate (SATA 1) should be C,D,E with C being active. It is now F,D,E
with D being active (OS is on F).
The Maxtor (SATA 2) should be F, active. It is now C, active.

Dave

The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
missing. I don't know if that's because I'm now bootiing from the other
drive.

boot.ini from the Maxtor drive I'm now using - SATA 2

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect /NoExecute=OptOut


PARTINFO 1.09
Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.

Run date: 04/24/2005 16:06

====================================================================
MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
+====+====+=============+====+=============+===========+===========+
Volume Information
+----+----+-------------+----+-------------+-----------+-----------+
| 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x04E1AF2A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x04E1AF2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x22F802A6F8027875
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 81915435
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xD400C167C150E2
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 333991350
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xA478DD6678DD382E
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
====================================================================
MBR Partition Information (HD1):
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x024C1258
MFT LCN: 0x0B42FF
MFT Mirr LCN: 0x03D54EA
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x4228D79E28D78EF3
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------

Thanks Walter,

I'll do it now, but in the meantime, I'm only up and running on my
second hard drive, the Maxtor. The Seagate which has the problem is
inaccessable. I don't know if that affects things. Let me know if it
does.

Dave


I assume you're up and running on the problematic platform? If so, go to
http://www.bootitng.com/utilities.html and download Partinfo. Unzip it
and run partinfW (yes, that W not O) from a command prompt as follows:

partinfw >partinfo.txt
start notepad partinfo.txt

Then copy and paste the contents back here. Also, do
start->run->c:\boot.ini and copy and paste the contents of boot.ini
back here as well.


I think I know what your issue is now and it's going to revolve around
boot.ini and the mbr code and now that I've taken a really fast look at
Acronis, it may be the tool isn't the right tool for what you're
attempting. Or you may be using it wrong.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


Walter, HELP! ! !

I deleted that key as suggested, HKLM\system\mounteddevices (except
default
value).
Before restoring the clone onto the other drive I decided to just
check the
values in the key after rebooting and supposedly rebuilding.

After entering my password at the log in screen, it immediately
reverts to
logging off . . .
I have tried everything I can think of, safe mode, boot disk but can't
log
on any more.

I then tried restoring the saved cloned partition to the other drive
and got
NTLDR is missing. So now I don't have any bootable drives.Back to
Acronis
boot CD to restore an earlier clone that worked and restored. The
first
partition, E: on the Maxtor was greyed out so I couldn't access it. I
eventually used MaxBlast to repartition and then Acronis restore
worked, and
I'm now back to using an earlier saved clone that I've restored on the
Maxtor. I haven't touched the Seagate C: so if there's a way of
accessing
and putting back this registry key (which I stupidly didn't feel the
need to
save) maybe I can get back to normal.

I swear once this is over, I won't touch any of this software for a
long,
long time. There are just too many issues and problems here. Restoring
all
my programs in an emergency pales to insignificance compared with the
time
and hassle spent so far.

Thanks in anticipation,

Dave


----- Original Message -----
From: "Walter Clayton" <[email protected]>
Newsgroups:
microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
Sent: Sunday, April 24, 2005 1:28 AM
Subject: Re: error loading os


Yes it will get rebuilt and yes, if that's not deleted then cloning
just the partition image itself can cause some less than desirable
results. In fact if you check
HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
MS back up / restore tools don't restore that key.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


Presumably XP will just rebuild this from scratch again? Do you
think that is what stopped the clone booting when it almost got to
the login screen and then reverted to a plain blue screen with
cursor?

Dave
Prior to the clone, delete all but the default value from
HKLM\system\mounteddevices.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently
advanced.


OK, we're making some progress here. I can now make and restore a
clone copy in Acronis 8.0.

I need to follow these steps EXACTLY.

1. Don't format or give a drive letter to the recipient drive
(Maxtor first partition here)
2. Use Acronis from boot CD not XP
3. Swap SATA cables before rebooting so Maxtor drive is now on
same cable as original Seagate

And this is the killer - if I don't do one of these and the
cloning process fails, than it will ALWAYS fail UNTIL I do a disk
copy with Acronis. This overwrites my entire drive and it's not
entirely convenient to ship out 100GB of data to somewhere else.
(Andrew mentions earlier in the thread a method using recovery
console which I'll try if I need to in future.) And bizarrely this
not only clones the drive correctly, but it puts it back to normal
such that I can now successfully clone a partition.

So, what on earth is going on here? Why did the boot sector get
screwed up ( I assume that's what it was) and why did none of the
standard fixes for this type of problem not work - fixboot
/fixmbr?

I gather at least some of this is caused by me using SATA drives.
Perhaps there will be no such problems with Ghost 10.0 and Acronis
9.0?

Dave


Hi,
I have 2 SATA drives, and I've been struggling to do a simple
clone of my Seagate C: partiton to a Maxtor F: partition.
I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
software. In most cases I got as far as a login screen and it
reverted to a plain blue screen with cursor. I always remove
Seagate before trying to boot with the cloned Maxtor. The only
thing that did consistently work was Acronis Migrate Easy, but
the problem is that you need to copy the entire disk. That means
overwriting the other Maxtor partitions. But it proves that it
did work. Now why did it, and not the others?

Now whilst playing around with all this I noticed that I was
getting 'error loading os' when trying to boot. When I went back
to Acronis, that was also giving this message, and not even
attempting to boot as it had previosly done. I tried using
sysprep with the same result.

Then I tried removing partitions completely from the Maxtor,
using fdisk and dos to format, using Max Blast to format, using
the
XP repair tool, fixmbr, fixboot. You name it I tried it I think.

So I then thought I'd see if I could install XP on this drive.
No, I get the same message when it gets to the booting from disk
stage.

Firstly, any ideas what could have caused this, and secondly do I
need to do a low level format to get this drive back to normal
shipping condition. If so, could someone tell me how, and what
software to use, as I've done this before.

I've now done a fair bit of reading about cloning. For a lot of
people it seems to be a completely painless process using Ghost
or Acronis. For many others including me, it just doesn't seem to
work, and I've seen the same issues reported over and over with
no workable solutions.

Ah well, I'll get there in the end. Maybe sooner with your help.
Thanks,

Dave Cockram

 

[David Cockram]

Walter,

Very simply, I'm just trying to undo the problems caused by deleting that
key.

Perhaps under most circumstances it can be deleted and it will rebuild, but
this is not what has happened here.

So I would like to get back to being able to boot from the first partition
(where the OS is) on the Seagate. The second partition is marked active at
the moment.

As for the wider picture, I had sorted out a method of cloning that worked
as long as I rigidly followed the steps I mentioned earlier. Otherwise I
never managed to boot the clone. I assumed that deleting that key would
answer that particular issue

Thanks,

Dave

The partition structure is a bit weird. You have a logical with what
appears to be a single volume followed by a couple of standard bootable
primaries. In fact, the second partition is currently flagged as active.

MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |

The boot strap code would have to be in the second partition. That
includes boot.ini, ntldr, ntdetect.com. The arc statement for that
partition will be tricky, that depends on from where you're loading the
OS. If you're loading the OS from the same partition, using the current
partition and volume tables, the arc statement should read

default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

although the partition number might need be three depending on how things
are counted (and I get really fuzzy on how the boot strap code counts
logical partitions and volumes; I avoid placing logicals in front of
non-logical volumes like the plague).

Exactly what are you attempting to accomplish? One thing that sticks out
is to move the logical higher in the partition table and drop the bootable
primary in front of that.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.

The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
missing. I don't know if that's because I'm now bootiing from the other
drive.

boot.ini from the Maxtor drive I'm now using - SATA 2

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect /NoExecute=OptOut


PARTINFO 1.09
Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.

Run date: 04/24/2005 16:06

====================================================================
MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
+====+====+=============+====+=============+===========+===========+
Volume Information
+----+----+-------------+----+-------------+-----------+-----------+
| 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x04E1AF2A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x04E1AF2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x22F802A6F8027875
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 81915435
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xD400C167C150E2
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 333991350
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xA478DD6678DD382E
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
====================================================================
MBR Partition Information (HD1):
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x024C1258
MFT LCN: 0x0B42FF
MFT Mirr LCN: 0x03D54EA
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x4228D79E28D78EF3
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------

Thanks Walter,

I'll do it now, but in the meantime, I'm only up and running on my
second hard drive, the Maxtor. The Seagate which has the problem is
inaccessable. I don't know if that affects things. Let me know if it
does.

Dave


I assume you're up and running on the problematic platform? If so, go to
http://www.bootitng.com/utilities.html and download Partinfo. Unzip it
and run partinfW (yes, that W not O) from a command prompt as follows:

partinfw >partinfo.txt
start notepad partinfo.txt

Then copy and paste the contents back here. Also, do
start->run->c:\boot.ini and copy and paste the contents of boot.ini
back here as well.


I think I know what your issue is now and it's going to revolve around
boot.ini and the mbr code and now that I've taken a really fast look at
Acronis, it may be the tool isn't the right tool for what you're
attempting. Or you may be using it wrong.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


Walter, HELP! ! !

I deleted that key as suggested, HKLM\system\mounteddevices (except
default
value).
Before restoring the clone onto the other drive I decided to just
check the
values in the key after rebooting and supposedly rebuilding.

After entering my password at the log in screen, it immediately
reverts to
logging off . . .
I have tried everything I can think of, safe mode, boot disk but can't
log
on any more.

I then tried restoring the saved cloned partition to the other drive
and got
NTLDR is missing. So now I don't have any bootable drives.Back to
Acronis
boot CD to restore an earlier clone that worked and restored. The
first
partition, E: on the Maxtor was greyed out so I couldn't access it. I
eventually used MaxBlast to repartition and then Acronis restore
worked, and
I'm now back to using an earlier saved clone that I've restored on the
Maxtor. I haven't touched the Seagate C: so if there's a way of
accessing
and putting back this registry key (which I stupidly didn't feel the
need to
save) maybe I can get back to normal.

I swear once this is over, I won't touch any of this software for a
long,
long time. There are just too many issues and problems here. Restoring
all
my programs in an emergency pales to insignificance compared with the
time
and hassle spent so far.

Thanks in anticipation,

Dave


----- Original Message -----
From: "Walter Clayton" <[email protected]>
Newsgroups:
microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
Sent: Sunday, April 24, 2005 1:28 AM
Subject: Re: error loading os


Yes it will get rebuilt and yes, if that's not deleted then cloning
just the partition image itself can cause some less than desirable
results. In fact if you check
HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
MS back up / restore tools don't restore that key.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


Presumably XP will just rebuild this from scratch again? Do you
think that is what stopped the clone booting when it almost got to
the login screen and then reverted to a plain blue screen with
cursor?

Dave
Prior to the clone, delete all but the default value from
HKLM\system\mounteddevices.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently
advanced.


OK, we're making some progress here. I can now make and restore a
clone copy in Acronis 8.0.

I need to follow these steps EXACTLY.

1. Don't format or give a drive letter to the recipient drive
(Maxtor first partition here)
2. Use Acronis from boot CD not XP
3. Swap SATA cables before rebooting so Maxtor drive is now on
same cable as original Seagate

And this is the killer - if I don't do one of these and the
cloning process fails, than it will ALWAYS fail UNTIL I do a disk
copy with Acronis. This overwrites my entire drive and it's not
entirely convenient to ship out 100GB of data to somewhere else.
(Andrew mentions earlier in the thread a method using recovery
console which I'll try if I need to in future.) And bizarrely this
not only clones the drive correctly, but it puts it back to normal
such that I can now successfully clone a partition.

So, what on earth is going on here? Why did the boot sector get
screwed up ( I assume that's what it was) and why did none of the
standard fixes for this type of problem not work - fixboot
/fixmbr?

I gather at least some of this is caused by me using SATA drives.
Perhaps there will be no such problems with Ghost 10.0 and Acronis
9.0?

Dave


Hi,
I have 2 SATA drives, and I've been struggling to do a simple
clone of my Seagate C: partiton to a Maxtor F: partition.
I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
software. In most cases I got as far as a login screen and it
reverted to a plain blue screen with cursor. I always remove
Seagate before trying to boot with the cloned Maxtor. The only
thing that did consistently work was Acronis Migrate Easy, but
the problem is that you need to copy the entire disk. That means
overwriting the other Maxtor partitions. But it proves that it
did work. Now why did it, and not the others?

Now whilst playing around with all this I noticed that I was
getting 'error loading os' when trying to boot. When I went back
to Acronis, that was also giving this message, and not even
attempting to boot as it had previosly done. I tried using
sysprep with the same result.

Then I tried removing partitions completely from the Maxtor,
using fdisk and dos to format, using Max Blast to format, using
the
XP repair tool, fixmbr, fixboot. You name it I tried it I think.

So I then thought I'd see if I could install XP on this drive.
No, I get the same message when it gets to the booting from disk
stage.

Firstly, any ideas what could have caused this, and secondly do I
need to do a low level format to get this drive back to normal
shipping condition. If so, could someone tell me how, and what
software to use, as I've done this before.

I've now done a fair bit of reading about cloning. For a lot of
people it seems to be a completely painless process using Ghost
or Acronis. For many others including me, it just doesn't seem to
work, and I've seen the same issues reported over and over with
no workable solutions.

Ah well, I'll get there in the end. Maybe sooner with your help.
Thanks,

Dave Cockram

 

[David Cockram]

Yes, those files are now all on the second (Non OS) partition.

boot.ini

[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect /NoExecute=OptIn

Can I perhaps copy them across and try rebooting? If so, exactly which
files?

Dave

The partition structure is a bit weird. You have a logical with what
appears to be a single volume followed by a couple of standard bootable
primaries. In fact, the second partition is currently flagged as active.

MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |

The boot strap code would have to be in the second partition. That
includes boot.ini, ntldr, ntdetect.com. The arc statement for that
partition will be tricky, that depends on from where you're loading the
OS. If you're loading the OS from the same partition, using the current
partition and volume tables, the arc statement should read

default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS

although the partition number might need be three depending on how things
are counted (and I get really fuzzy on how the boot strap code counts
logical partitions and volumes; I avoid placing logicals in front of
non-logical volumes like the plague).

Exactly what are you attempting to accomplish? One thing that sticks out
is to move the logical higher in the partition table and drop the bootable
primary in front of that.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.

The boot.ini file drom the Seagate (problem drive - SATA 1) appears to be
missing. I don't know if that's because I'm now bootiing from the other
drive.

boot.ini from the Maxtor drive I'm now using - SATA 2

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect /NoExecute=OptOut


PARTINFO 1.09
Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.

Run date: 04/24/2005 16:06

====================================================================
MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 0 | 1 0 1 | f | 1023 254 63 | 16065 | 81899370 |
+====+====+=============+====+=============+===========+===========+
Volume Information
+----+----+-------------+----+-------------+-----------+-----------+
| 0: | 0 | 1 1 1 | 7 | 1023 254 63 | 63 | 81899307 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
MBR Partition Information (HD0) Continued:
+====+====+=============+====+=============+===========+===========+
| 1: | 80 | 1023 0 1 | 7 | 1023 254 63 | 81915435 | 252075915 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 333991350 | 252075915 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 16128 Total Sectors: 81899307
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x04E1AF2A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x04E1AF2
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x22F802A6F8027875
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 81915435 Total Sectors: 252075915 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 81915435
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xD400C167C150E2
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 333991350 Total Sectors: 252075915 ID: 0x3
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 333991350
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0F065F8A
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0F065F8
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xA478DD6678DD382E
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
====================================================================
MBR Partition Information (HD1):
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
| 1: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x024C1258
MFT LCN: 0x0B42FF
MFT Mirr LCN: 0x03D54EA
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x4228D79E28D78EF3
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------

Thanks Walter,

I'll do it now, but in the meantime, I'm only up and running on my
second hard drive, the Maxtor. The Seagate which has the problem is
inaccessable. I don't know if that affects things. Let me know if it
does.

Dave


I assume you're up and running on the problematic platform? If so, go to
http://www.bootitng.com/utilities.html and download Partinfo. Unzip it
and run partinfW (yes, that W not O) from a command prompt as follows:

partinfw >partinfo.txt
start notepad partinfo.txt

Then copy and paste the contents back here. Also, do
start->run->c:\boot.ini and copy and paste the contents of boot.ini
back here as well.


I think I know what your issue is now and it's going to revolve around
boot.ini and the mbr code and now that I've taken a really fast look at
Acronis, it may be the tool isn't the right tool for what you're
attempting. Or you may be using it wrong.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


Walter, HELP! ! !

I deleted that key as suggested, HKLM\system\mounteddevices (except
default
value).
Before restoring the clone onto the other drive I decided to just
check the
values in the key after rebooting and supposedly rebuilding.

After entering my password at the log in screen, it immediately
reverts to
logging off . . .
I have tried everything I can think of, safe mode, boot disk but can't
log
on any more.

I then tried restoring the saved cloned partition to the other drive
and got
NTLDR is missing. So now I don't have any bootable drives.Back to
Acronis
boot CD to restore an earlier clone that worked and restored. The
first
partition, E: on the Maxtor was greyed out so I couldn't access it. I
eventually used MaxBlast to repartition and then Acronis restore
worked, and
I'm now back to using an earlier saved clone that I've restored on the
Maxtor. I haven't touched the Seagate C: so if there's a way of
accessing
and putting back this registry key (which I stupidly didn't feel the
need to
save) maybe I can get back to normal.

I swear once this is over, I won't touch any of this software for a
long,
long time. There are just too many issues and problems here. Restoring
all
my programs in an emergency pales to insignificance compared with the
time
and hassle spent so far.

Thanks in anticipation,

Dave


----- Original Message -----
From: "Walter Clayton" <[email protected]>
Newsgroups:
microsoft.public.windowsxp,microsoft.public.windowsxp.basics,microsoft.public.windowsxp.general,microsoft.public.windowsxp.newusers
Sent: Sunday, April 24, 2005 1:28 AM
Subject: Re: error loading os


Yes it will get rebuilt and yes, if that's not deleted then cloning
just the partition image itself can cause some less than desirable
results. In fact if you check
HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore\KeysNotToRestore
MS back up / restore tools don't restore that key.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


Presumably XP will just rebuild this from scratch again? Do you
think that is what stopped the clone booting when it almost got to
the login screen and then reverted to a plain blue screen with
cursor?

Dave
Prior to the clone, delete all but the default value from
HKLM\system\mounteddevices.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently
advanced.


OK, we're making some progress here. I can now make and restore a
clone copy in Acronis 8.0.

I need to follow these steps EXACTLY.

1. Don't format or give a drive letter to the recipient drive
(Maxtor first partition here)
2. Use Acronis from boot CD not XP
3. Swap SATA cables before rebooting so Maxtor drive is now on
same cable as original Seagate

And this is the killer - if I don't do one of these and the
cloning process fails, than it will ALWAYS fail UNTIL I do a disk
copy with Acronis. This overwrites my entire drive and it's not
entirely convenient to ship out 100GB of data to somewhere else.
(Andrew mentions earlier in the thread a method using recovery
console which I'll try if I need to in future.) And bizarrely this
not only clones the drive correctly, but it puts it back to normal
such that I can now successfully clone a partition.

So, what on earth is going on here? Why did the boot sector get
screwed up ( I assume that's what it was) and why did none of the
standard fixes for this type of problem not work - fixboot
/fixmbr?

I gather at least some of this is caused by me using SATA drives.
Perhaps there will be no such problems with Ghost 10.0 and Acronis
9.0?

Dave


Hi,
I have 2 SATA drives, and I've been struggling to do a simple
clone of my Seagate C: partiton to a Maxtor F: partition.
I've tried Ghost 9.0, Acronis True Image 8.0 and other trial
software. In most cases I got as far as a login screen and it
reverted to a plain blue screen with cursor. I always remove
Seagate before trying to boot with the cloned Maxtor. The only
thing that did consistently work was Acronis Migrate Easy, but
the problem is that you need to copy the entire disk. That means
overwriting the other Maxtor partitions. But it proves that it
did work. Now why did it, and not the others?

Now whilst playing around with all this I noticed that I was
getting 'error loading os' when trying to boot. When I went back
to Acronis, that was also giving this message, and not even
attempting to boot as it had previosly done. I tried using
sysprep with the same result.

Then I tried removing partitions completely from the Maxtor,
using fdisk and dos to format, using Max Blast to format, using
the
XP repair tool, fixmbr, fixboot. You name it I tried it I think.

So I then thought I'd see if I could install XP on this drive.
No, I get the same message when it gets to the booting from disk
stage.

Firstly, any ideas what could have caused this, and secondly do I
need to do a low level format to get this drive back to normal
shipping condition. If so, could someone tell me how, and what
software to use, as I've done this before.

I've now done a fair bit of reading about cloning. For a lot of
people it seems to be a completely painless process using Ghost
or Acronis. For many others including me, it just doesn't seem to
work, and I've seen the same issues reported over and over with
no workable solutions.

Ah well, I'll get there in the end. Maybe sooner with your help.
Thanks,

Dave Cockram

 

[Walter Clayton]

Walter,

Very simply, I'm just trying to undo the problems caused by deleting that
key.

Perhaps under most circumstances it can be deleted and it will rebuild,
but this is not what has happened here.

There are exceptions. I have such my self since I don't enumerate partitions
in default order, however this is, I'll have to admit, the first time I've
seen some one park a logical volume in front the boot partition. There are
some other reasons why this is going to be problematic on going other than
you're inability to do a simple partition clone of the system...

So I would like to get back to being able to boot from the first partition
(where the OS is) on the Seagate. The second partition is marked active at
the moment.

OK. It's time to be *extremely* specific.
The first partition on your Segate is a logical volume. No BIOS can initiate
boot strap on that partition. The second partition in the partition table is
the active primary. That is the partition the BIOS will bootstrap. That is
the partition that must contain boot.init, ntldr and ntdetect.com. In turn
boot.ini must point to the partition from which the OS will loaded.
Depending on exactly how you got into the partition table layout you have,
specifically the timing therein, things may get a bit interesting since the
mounteddevices key has been clipped. The key is what was the OS partition
enumerated as when you set it up. Once boot.ini is straightened out, you may
have to use "last known good configuration' to get the mounteddevices values
back. As an aside, if you alter the physical layout of the Seagate now, you
could save your self a lot of grief and would not have to worry about the
old mounteddevices key.

One 'long' term issue I *think* you're going to have, is if you drop another
volume into the logical partition, it's going to hose the arc statement.

As for the wider picture, I had sorted out a method of cloning that worked
as long as I rigidly followed the steps I mentioned earlier. Otherwise I
never managed to boot the clone. I assumed that deleting that key would
answer that particular issue

I can get you back to where you want to go at present, but due to the
partition layout you have on the Seagate you're going to continue to have
some extreme difficulty in partition cloning of the OS instance. I can
understand exactly why you're having to jump through the hoops you are
though.

Pulling in the other post:

Yes, those files are now all on the second (Non OS) partition.

boot.ini

[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect /NoExecute=OptIn

Can I perhaps copy them across and try rebooting? If so, exactly which
files?

Yes, but I'd go a bit further since you're in hunt and peck mode at the
moment.
Modify the boot.ini as follows and note the change on the time out value.
You need the time to be able to select a different arc path.

[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition 1" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home
Edition 2" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Home
Edition 3" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(4)\WINDOWS="Microsoft Windows XP Home
Edition 4" /fastdetect /NoExecute=OptIn

In this way you can attempt to load each of the partitions. Also, bring the
image up in safe mode initially. Do not bring the machine up in normal mode
directly. Once up in safemode, use diskmgmt.msc to correct any drive letter
assignment problems you may have.

The other two files you need are ntldr and ntdetect.com.

Once you get where you want, you can delete the extraneous [operating
systems] statements from boot.ini.

 

[David Cockram]

Walter,
I had a play around with all this, but gave up in the end, and reinstalled
XP.

Could you have a look at this and tell me if it now seems 'normal'.

At this stage I would like to take regular backup images, (ideally using
Acronis, as I have that), and restore them to the Maxtor (HD1) for checking.
Can you forsee any problems now?

Finally, I believe it would be relatively easy to restore images to any of
the other partitions on say the Maxtor (there are three). Do I need to
modify boot.ini in order to access them. My BIOS has a boot loader if I
press F8 so would they then appear on it's menu?

Thanks,

Dave

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /fastdetect /NoExecute=OptIn


PARTINFO 1.09
Copyright (C) 1996-2003, TeraByte Unlimited. All rights reserved.

Run date: 04/26/2005 0:36

====================================================================
MBR Partition Information (HD0):
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 61432497 |
| 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 61432560 | 262309320 |
| 2: | 0 | 1023 0 1 | 7 | 1023 254 63 | 323741880 | 262325385 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 63 Total Sectors: 61432497 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x03A962B0
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x03A962B
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x844C0F974C0F8362
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 61432560 Total Sectors: 262309320 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 61432560
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0FA285C7
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0FA285C
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0xF2281E1A281DDF03
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 323741880 Total Sectors: 262325385 ID: 0x3
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 323741880
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x0FA2C488
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x0FA2C48
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x7AB4DECCB4DE89D1
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
====================================================================
MBR Partition Information (HD1):
+====+====+=============+====+=============+===========+===========+
| 0: | 80 | 0 1 1 | 7 | 1023 254 63 | 63 | 38539872 |
| 1: | 0 | 1023 0 1 | 7 | 1023 254 63 | 38539935 | 274036770 |
| 2: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
| 3: | 0 | 0 0 0 | 0 | 0 0 0 | 0 | 0 |
+====+====+=============+====+=============+===========+===========+
BOOT SECTOR INFORMATION
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 63 Total Sectors: 38539872 ID: 0x1
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 63
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x024C1258
MFT LCN: 0x0B42FF
MFT Mirr LCN: 0x03D54EA
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x4228D79E28D78EF3
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------
File System ID: 0x7 LBA: 38539935 Total Sectors: 274036770 ID: 0x2
Jump: EB 52 90
OEM Name: NTFS
Bytes Per Sec: 512
Sec Per Clust: 8
Res Sectors: 0
Zero 1: 0x0
Zero 2: 0x0
NA 1: 0x0
Media: 0xF8
Zero 3: 0x0
Sec Per Track: 63
Heads: 255
Hidden Secs: 38539935
NA 2: 0x0
NA 3: 0x800080
Total Sectors: 0x010557821
MFT LCN: 0x0C0000
MFT Mirr LCN: 0x01055782
Clust Per FRS: 0xF6
Clust Per IBlock: 0x1
Volume SN: 0x7E38F7BF38F7750D
Checksum: 0x0
Boot Flag: 0xAA55
-------------------------------------------------------------------------------