Hi,

I have a notebook (an old thinkpad T-20) with a 20Gb disk from IBM
(model  IBM-DJSA-220).   I changed the disk for bigger one : 120GB from
western digital (model WDC WD1200BEVE-0).  Each disk was about 60% full.

I did take an image of 2 partitions (each of 9GB) of my original disk.
I then installed the new disk, partition with bigger size (each 20GB)
and then restored the saved image on my new disk.  The new disk has 255
heads in a cylinder but the old one had 16 cylinders.  The do no have
the same geometry.

Now if I check free space on the disk it still show that the disk is 56%
empty even if I doubled it's size.  The total count of blocks seem not
to be correct.

Here is the partition table from fdisk for my new disk in blocks (sorry
it's in french):
-------------------------------------------
Périphérique Amorce    Début         Fin      Blocs    Id  Système
/dev/sda1   *          63    40017914    20008926   83  Linux
/dev/sda2        40017915    41528024      755055   82  Linux swap /
Solaris
/dev/sda3        41528025    81545939    20008957+  83  Linux
/dev/sda4        81545940   234436544    76445302+   5  Extended
/dev/sda5        81546003    83554064     1004031   83  Linux
/dev/sda6        83554128   123571979    20008926   83  Linux
/dev/sda7       123572043   234436544    55432251   83  Linux
------------------------------------------------------------------

How can fdisk tell that the disk sda1  has 20008926 blocks when it
really has 40017132 blocks ???  In fact if you make the calculation from
the difference between the starting block and the ending one, no
partitions seems to show the correct count ???  But if I take Gparted
instead, it shows the correct numbers of blocks but it still show me
that I use 14G on the 20G partition ???  Strange it's from an image of a
10G partition ???  I do no understand anymore.

Is there anything that I can do to fix this. I was thinking about taking
a tar of the whole disk on a bigger partition, reformatting the disk and
restore the archive on the disk.  Would it correct the geometry problem
?  I'm totally puzzled.

I still have my original data on the old disk on my desk, nothing is
lost for now.


Regards,

   Bernard Tremblay



-- 
  Bernard Tremblay
  [EMAIL PROTECTED] 
-- 
  Bernard Tremblay
  [EMAIL PROTECTED]

--- Begin Message ---
Hi,

I have a notebook (an old thinkpad T-20) with a 20Gb disk from IBM
(model  IBM-DJSA-220).   I changed the disk for bigger one : 120GB from
western digital (model WDC WD1200BEVE-0).  Each disk was about 60% full.

I did take an image of 2 partitions (each of 9GB) of my original disk. 
I then installed the new disk, partition with bigger size (each 20GB)
and then restored the saved image on my new disk.  The new disk has 255
heads in a cylinder but the old one had 16 cylinders.  The do no have
the same geometry.

Now if I check free space on the disk it still show that the disk is 56%
empty even if I doubled it's size.  The total count of blocks seem not
to be correct.

Here is the partition table from fdisk for my new disk in blocks (sorry
it's in french):
-------------------------------------------
Périphérique Amorce    Début         Fin      Blocs    Id  Système
/dev/sda1   *          63    40017914    20008926   83  Linux
/dev/sda2        40017915    41528024      755055   82  Linux swap /
Solaris
/dev/sda3        41528025    81545939    20008957+  83  Linux
/dev/sda4        81545940   234436544    76445302+   5  Extended
/dev/sda5        81546003    83554064     1004031   83  Linux
/dev/sda6        83554128   123571979    20008926   83  Linux
/dev/sda7       123572043   234436544    55432251   83  Linux
------------------------------------------------------------------

How can fdisk tell that the disk sda1  has 20008926 blocks when it
really has 40017132 blocks ???  In fact if you make the calculation from
the difference between the starting block and the ending one, no
partitions seems to show the correct count ???  But if I take Gparted
instead, it shows the correct numbers of blocks but it still show me
that I use 14G on the 20G partition ???  Strange it's from an image of a
10G partition ???  I do no understand anymore.

Is there anything that I can do to fix this. I was thinking about taking
a tar of the whole disk on a bigger partition, reformatting the disk and
restore the archive on the disk.  Would it correct the geometry problem
?  I'm totally puzzled.

I still have my original data on the old disk on my desk, nothing is
lost for now.


Regards,

   Bernard Tremblay



-- 
  Bernard Tremblay
  [EMAIL PROTECTED]



--- End Message ---
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
g4u-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/g4u-help

Reply via email to