Peter Ludikovsky schrieb:
> Udo Huebner wrote:
>> Hi all -
>>...
>> How can this labeling occur?
>> Partioning had been done by Acronis Partition Expert under WinXP.
> ...
> Could you please post the output of 'fdisk -l /dev/hdc'? Maybe the
> partitioning tool screwed something up.

Hi Peter -
Tom proposed to use CFdisk but I am using fdisk here because I am
familiar with it. Thus, here the output of 'fdisk -l /dev/hdc':

--------------
Disk /dev/hdc: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hdc2 1320 48641 380113965 f Win95 Ext'd (LBA)
/dev/hdc3 * 1 1319 10594836 c Win95 FAT32 (LBA)
/dev/hdc5 1320 48641 380113933+ b Win95 FAT32

Partition table entries are not in disk order
---------------

Hope it helps. Regards Udo

Udo Huebner wrote:
> Peter Ludikovsky schrieb:
>> Udo Huebner wrote:
>>> Hi all -
>>> ...
>>> How can this labeling occur?
>>> Partioning had been done by Acronis Partition Expert under WinXP.
>> ...
>> Could you please post the output of 'fdisk -l /dev/hdc'? Maybe the
>> partitioning tool screwed something up.
>
> Hi Peter -
> Tom proposed to use CFdisk but I am using fdisk here because I am
> familiar with it. Thus, here the output of 'fdisk -l /dev/hdc':
>
> --------------
> Disk /dev/hdc: 400.0 GB, 400088457216 bytes
> 255 heads, 63 sectors/track, 48641 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hdc2 1320 48641 380113965 f Win95 Ext'd (LBA)
> /dev/hdc3 * 1 1319 10594836 c Win95 FAT32 (LBA)
> /dev/hdc5 1320 48641 380113933+ b Win95 FAT32
>
> Partition table entries are not in disk order
> ---------------
>
> Hope it helps. Regards Udo

It helps indeed. Aparently Acronis screwed up the order in which the
partitions where created. You now have 2 options:

1) Fix with fdisk
Back up your data (if possible) since any work on the partition table
is risky. Then execute 'sudo fdisk /dev/hdc'. In fdisk press 'x' to
enter expert mode and then 'f' to fix the partition order & 'w' to write
the changes.

Again, _BACK UP YOUR DATA_ if possible before doing so.

2) Fix with fdisk/PartitonMagic
Again, back up your data first if possible, then clear all partitons
and re-create them using either PartitionMagic (Windows-Tool from
Symantec) or with fdisk.
PartitionMagic is pretty much self explaining, so here are the steps for
fdisk:
* Delete all partitions using the 'd' command
* Enter 'n' to create a new partition. You will be asked if you want a
'primary' or an 'extended' partition. Press p, 1, 1, 1319
* For the extended: n, e, 2, 1320, 48641
* For the logical: n, l, 1320, 48641
* Set the correct type: t, 1, c, t, 2, f, t, 5, b
* Activate the primary partition: a, 1
* Write & quit with w

I hope I was able to help you & that you didn't loose your interest in
Linux because of Tom. Sadly there will always be zealots like him
around, out on their personal crusade...

Regards
/peter

On 2008-02-08, Peter Ludikovsky <darthludi@gmail.com> wrote:
>
>
>
> I hope I was able to help you & that you didn't loose your interest in
> Linux because of Tom. Sadly there will always be zealots like him
> around, out on their personal crusade...

That's the sort of cheap shot that people take when they don't want
to honestly debate issues that someone raises.

Attack their worth as a human being by assigning a perjorative label
to them.

Thanks for affirming to everyone that I am on the right path.

Anyone reduced to such infantile and dishonest tactics is _obviously_
on the wrong path.

Tom

--
calhobbit (at)
gmail [DOT] com

On 2008-02-08, Tom Newton <tom@server.invalid> wrote:
>
> That's the sort of cheap shot that people take when they don't want
> to honestly debate issues that someone raises.
>
> Attack their worth as a human being by assigning a perjorative label
> to them.

Like "Windows Weenie"? I guess you don't want to honestly debate issues
that have been raised in this thread.

> Anyone reduced to such infantile and dishonest tactics is _obviously_
> on the wrong path.

By this definition you've been on the wrong path since you first started
trolling alt.os.linux.slackware.

Just so this post isn't completely useless, the old fdisk man page
suggested using the partitioning tools in this order: cfdisk, fdisk,
sfdisk, and suggests that the only reason to use fdisk before sfdisk is
that sfdisk's UI sucks (which is true), and otherwise it makes better
partition tables. More recent man pages suggest parted, fdisk, sfdisk,
presumably due to parted being the only common partitioner that supports
GPT.

--keith

--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

Udo Huebner wrote:

> Device Boot Start End Blocks Id System
> /dev/hdc2 1320 48641 380113965 f Win95 Ext'd (LBA)
> /dev/hdc3 * 1 1319 10594836 c Win95 FAT32 (LBA)
> /dev/hdc5 1320 48641 380113933+ b Win95 FAT32
>
> Partition table entries are not in disk order

Right :-(

At your own risk, you can use dskprobe.exe from the NT resource kit to
repair the partition table, by shuffling the entries into the desired
order. Make a copy of the sector, before writing it back. This procedure
may not work when you actually run a system from that disk, because then
the disk is locked against low-level access. Afterwards you may have to
edit boot.ini, to reflect the new numbering.

DoDi

Peter Ludikovsky schrieb:
> Udo Huebner wrote:
>> Peter Ludikovsky schrieb:
>>> Udo Huebner wrote:
>>>> Hi all -
>>>> ...
>> --------------
>> Disk /dev/hdc: 400.0 GB, 400088457216 bytes
>> 255 heads, 63 sectors/track, 48641 cylinders
>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>
>> Device Boot Start End Blocks Id System
>> /dev/hdc2 1320 48641 380113965 f Win95 Ext'd (LBA)
>> /dev/hdc3 * 1 1319 10594836 c Win95 FAT32 (LBA)
>> /dev/hdc5 1320 48641 380113933+ b Win95 FAT32
>>
>> Partition table entries are not in disk order
>> ---------------
>>
>> Hope it helps. Regards Udo
>
> It helps indeed. Aparently Acronis screwed up the order in which the
> partitions where created. You now have 2 options:
>
> 1) Fix with fdisk
> ...
> 2) Fix with fdisk/PartitonMagic
> ...

Thank you very much, Peter, for your detailed hints. I will certainly
try these but it needs some time because - as said - the system is
already again running with _lots_ of GBs collected on both partitions
which have to be backed up. I will report on it soon.

> I hope I was able to help you & that you didn't loose your interest in
> Linux because of Tom. Sadly there will always be zealots like him
> around, out on their personal crusade...

No, I will not loose the interest in Linux. I am coming from the
Win-GUI and therefore indeed started with KDE against Tom's puristic
opinion. :-)
It is easier for me to get in and, hopefully, I can later transfer my
partly free german Win-C++ programs to english and the pertinent C++
language for Linux.

Regards Udo

Hans-Peter Diettrich schrieb:
> Udo Huebner wrote:
> ...
>> Partition table entries are not in disk order
>
> Right :-(
>
> At your own risk, you can use dskprobe.exe from the NT resource kit to
> repair the partition table, by shuffling the entries into the desired
> order. Make a copy of the sector, before writing it back. This procedure
> may not work when you actually run a system from that disk, because then
> the disk is locked against low-level access. Afterwards you may have to
> edit boot.ini, to reflect the new numbering.

Thank you too, Hans-Peter. I don't know if dskprobe.exe is contained in
my XP but, at first, I will check the hints of Peter Ludikovski.

Regards Udo

Udo Huebner wrote:
> Peter Ludikovsky schrieb:
>> Udo Huebner wrote:
>>> Peter Ludikovsky schrieb:
>>>> Udo Huebner wrote:
>>>>> Hi all -
>>>>> ...
>>> --------------
>>> Disk /dev/hdc: 400.0 GB, 400088457216 bytes
>>> 255 heads, 63 sectors/track, 48641 cylinders
>>> Units = cylinders of 16065 * 512 = 8225280 bytes
>>>
>>> Device Boot Start End Blocks Id System
>>> /dev/hdc2 1320 48641 380113965 f Win95 Ext'd (LBA)
>>> /dev/hdc3 * 1 1319 10594836 c Win95 FAT32 (LBA)
>>> /dev/hdc5 1320 48641 380113933+ b Win95 FAT32
>>>
>>> Partition table entries are not in disk order
>>> ---------------
>>>
>>> Hope it helps. Regards Udo
>>
>> It helps indeed. Aparently Acronis screwed up the order in which the
>> partitions where created. You now have 2 options:
>>
>> 1) Fix with fdisk
>> ... 2) Fix with fdisk/PartitonMagic
>> ...
>
> Thank you very much, Peter, for your detailed hints. I will certainly
> try these but it needs some time because - as said - the system is
> already again running with _lots_ of GBs collected on both partitions
> which have to be backed up. I will report on it soon.

Fixing with fdisk will destroy your partition tables. Been there, done that. You need to squeeze out the misplaced partition, with its contents saved, then stretch and migrate your other partitoins back into order.

Partition Magic is awful about this and doesn't report re-arranging things.