A
Andreas
Hi all,
I'm using a (preinstalled) Windwos 2000 system at my office that had
the following (unusual) partitioning (disk geometry: 9729 cylinders,
255 heads, 63 sectors)
-Primary(&active) "System", NTFS, 0/1/1 - 1017/254/63 (7985.4MB) ->
Drive C:
-Primary unnamed unassigned, 1018/0/1 - 1018/254/63 (7.8MB)
-Primary Extended (type 0f), 1019/0/1 - 9727/254/63
* Log. "Data", NTFS, 1019/1/1 - 9725/254/63 (68299.8MB)
-> Drive D:
* Log. unnamed unassigned, 9726/0/1 - 9727/254/63 (15.7MB)
-Primary unnamed unassigned, 9728/0/1 - 9728/254/63 (7.8MB)
For one thing, I don't understand why they added the 2 unassigned
primary partitions and the one unassigned logical one (each precisely
one or two heads long). But my problem was that I wanted to increase
space on drive C, so I started Acronis Partitionexpert 2003 (build
286) and first decreased logical partition D to 55GB and pushed it to
the right. Funnily I was not able to increase partition C, it only
complained its maximum size was already reached (maybe because the
extended partition would otherwise start outside 2035 cylinder limit,
but I thought that's no problem if you only want to boot from one OS
in the first primary partition). The decrease of partition D seemed to
work fine though and I had 11GB unused space between C and D.
So I tried out PartitionMagic 8.0 (buil 1242)instead, but it only
reported me the whole disk as "bad" (yellow border). I did not have
any data problem on the disk though. Using the partition table tool, I
found that the logical drive did nto start at a head boundary
anymore... well I don't have teh details anymore, because after that I
started Acronis Partitionexpert once more and extended drive D to its
maximum size, in the hope I could then use Partitionmagic.
But Partitionmagic still reports the same problem. This is the
information reported by Powerwuests PartitionInfo 8.0:
===========================================================================================================
Disk Geometry Information for Disk 1: 9729 Cylinders, 255 Heads,
63 Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head
Sect StartSect NumSects
===========================================================================================================
0 0 80 0 1 1 07 1017 254
63 63 16,354,107
0 1 00 1018 0 1 05 1023 254
63 16,354,170 139,942,215
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 1018 0 1 05 9728 254 63 16354170
139942215
16,354,170 0 00 1018 1 2 07 1023 254
63 16,354,234 139,942,151
Info: End C,H,S values were large drive placeholders.
Actual values are:
16354170 0 00 1018 1 2 07 9728 254 63 16354234
139942151
Error #106: Partition didn't begin on head boundary.
ucBeginSector expected to be 1, not 2.
===========================================================================================================
Partition Information for Disk 1: 76,316.6 Megabytes
Volume PartType Status Size MB PartSect #
StartSect TotalSects
===========================================================================================================
C: NTFS Pri,Boot 7,985.4 0 0
63 16,354,107
Extended Pri 68,331.2 0 1
16,354,170 139,942,215
EPBR Log 68,331.2 None --
16,354,170 139,942,215
D: NTFS Log 68,331.1 16,354,170 0
16,354,234 139,942,151
Error #114: Logical starting at 16354234 is not one head away from
EPBR.
The problem seems to be at the starting sector of the second NTFS
partition. The surrounding extended partition starts at sector
16354170 (that is 1018/0/1 if you start counting at sectornumber 1), a
head boundary, the logical partition (D
inside is starting 64
sectors after that (16354234-16354170), this is one head plus one
sector (1018/1/2). Partitionmagics error message "Error #114" above
seems to indicate that logical drives must always start at head
boundaries - Acronis didn't follow this (actually, after the first
resize action the logical start position was even 7 sectors off a head
boundary).
So, either Partitionmagics assumption that logical drives must be at
head boundaries is wrong, or Acronis somehow miscalculated disk
geometry. Mainly I'm now worried if there's a risk of data loss with
the D partition starting at the current position? I don't have any
indication yet that data is lost on drive D, all seems to be fine...
but I'd like to understand the problem, and if there really is a
problem.
I was considering using Partitionexpert and resize D until by
coincidence the logical drive starts at an even position. But this can
take very long, statisticalls I need 64 tries... and a lot of nerves.
Or I can image both drives to another disk and start completely from
scratch. Still, if there's an easier solution, I would naturally
prefer it Any help would be highly welcome!
And of course... is this a bug in Partitionexpert or in
Partitionmagic?
Thanks in advance, Andy
I'm using a (preinstalled) Windwos 2000 system at my office that had
the following (unusual) partitioning (disk geometry: 9729 cylinders,
255 heads, 63 sectors)
-Primary(&active) "System", NTFS, 0/1/1 - 1017/254/63 (7985.4MB) ->
Drive C:
-Primary unnamed unassigned, 1018/0/1 - 1018/254/63 (7.8MB)
-Primary Extended (type 0f), 1019/0/1 - 9727/254/63
* Log. "Data", NTFS, 1019/1/1 - 9725/254/63 (68299.8MB)
-> Drive D:
* Log. unnamed unassigned, 9726/0/1 - 9727/254/63 (15.7MB)
-Primary unnamed unassigned, 9728/0/1 - 9728/254/63 (7.8MB)
For one thing, I don't understand why they added the 2 unassigned
primary partitions and the one unassigned logical one (each precisely
one or two heads long). But my problem was that I wanted to increase
space on drive C, so I started Acronis Partitionexpert 2003 (build
286) and first decreased logical partition D to 55GB and pushed it to
the right. Funnily I was not able to increase partition C, it only
complained its maximum size was already reached (maybe because the
extended partition would otherwise start outside 2035 cylinder limit,
but I thought that's no problem if you only want to boot from one OS
in the first primary partition). The decrease of partition D seemed to
work fine though and I had 11GB unused space between C and D.
So I tried out PartitionMagic 8.0 (buil 1242)instead, but it only
reported me the whole disk as "bad" (yellow border). I did not have
any data problem on the disk though. Using the partition table tool, I
found that the logical drive did nto start at a head boundary
anymore... well I don't have teh details anymore, because after that I
started Acronis Partitionexpert once more and extended drive D to its
maximum size, in the hope I could then use Partitionmagic.
But Partitionmagic still reports the same problem. This is the
information reported by Powerwuests PartitionInfo 8.0:
===========================================================================================================
Disk Geometry Information for Disk 1: 9729 Cylinders, 255 Heads,
63 Sectors/Track
System PartSect # Boot BCyl Head Sect FS ECyl Head
Sect StartSect NumSects
===========================================================================================================
0 0 80 0 1 1 07 1017 254
63 63 16,354,107
0 1 00 1018 0 1 05 1023 254
63 16,354,170 139,942,215
Info: End C,H,S values were large drive placeholders.
Actual values are:
0 1 00 1018 0 1 05 9728 254 63 16354170
139942215
16,354,170 0 00 1018 1 2 07 1023 254
63 16,354,234 139,942,151
Info: End C,H,S values were large drive placeholders.
Actual values are:
16354170 0 00 1018 1 2 07 9728 254 63 16354234
139942151
Error #106: Partition didn't begin on head boundary.
ucBeginSector expected to be 1, not 2.
===========================================================================================================
Partition Information for Disk 1: 76,316.6 Megabytes
Volume PartType Status Size MB PartSect #
StartSect TotalSects
===========================================================================================================
C: NTFS Pri,Boot 7,985.4 0 0
63 16,354,107
Extended Pri 68,331.2 0 1
16,354,170 139,942,215
EPBR Log 68,331.2 None --
16,354,170 139,942,215
D: NTFS Log 68,331.1 16,354,170 0
16,354,234 139,942,151
Error #114: Logical starting at 16354234 is not one head away from
EPBR.
The problem seems to be at the starting sector of the second NTFS
partition. The surrounding extended partition starts at sector
16354170 (that is 1018/0/1 if you start counting at sectornumber 1), a
head boundary, the logical partition (D
inside is starting 64sectors after that (16354234-16354170), this is one head plus one
sector (1018/1/2). Partitionmagics error message "Error #114" above
seems to indicate that logical drives must always start at head
boundaries - Acronis didn't follow this (actually, after the first
resize action the logical start position was even 7 sectors off a head
boundary).
So, either Partitionmagics assumption that logical drives must be at
head boundaries is wrong, or Acronis somehow miscalculated disk
geometry. Mainly I'm now worried if there's a risk of data loss with
the D partition starting at the current position? I don't have any
indication yet that data is lost on drive D, all seems to be fine...
but I'd like to understand the problem, and if there really is a
problem.
I was considering using Partitionexpert and resize D until by
coincidence the logical drive starts at an even position. But this can
take very long, statisticalls I need 64 tries... and a lot of nerves.
Or I can image both drives to another disk and start completely from
scratch. Still, if there's an easier solution, I would naturally
prefer it
Any help would be highly welcome!And of course... is this a bug in Partitionexpert or in
Partitionmagic?
Thanks in advance, Andy