All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: "Tuc at T-B-O-H.NET" <ml@t-b-o-h.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: Correct partition table geometry?(Story included)
Date: Sat, 31 May 2008 08:39:11 -0400	[thread overview]
Message-ID: <484146EF.7090302@rtr.ca> (raw)
In-Reply-To: <200805310238.m4V2chKZ034543@himinbjorg.tucs-beachin-obx-house.com>

Tuc at T-B-O-H.NET wrote:
>
> Disk /dev/hdb: 500.1 GB, 500107862016 bytes
> 255 heads, 63 sectors/track, 60801 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/hda1   *           1         127     1020096   83  Linux
> /dev/hda2             128         185      465885   82  Linux swap
> /dev/hda3             186         312     1020127+  83  Linux
> /dev/hda4             313        9729    75642052+   5  Extended
> /dev/hda5             313         439     1020096   83  Linux
> /dev/hda6             440        1714    10241406   83  Linux
..

You could fire up fdisk, delete hda6, hda5, hda4,
then recreate hda4 extending over the entire free space,
then recreate hda5, hda6 *exactly* as before (above),
and then hda7 with the remaining free space.
And only *then* commit the changes to disk.

No need to reformat hda5,hda6 this way, their contents will
survive the repartitioning if they are recreated exactly
as before.

Done.  Entire disk now accessible.

But personally, I wouldn't do this.  I'd just create a new
partition scheme that makes more sense, and then file-copy
everything over from the old 80GB drive to the new scheme,
re-run grub-install on the new drive, and be done with it.

Cheers


  reply	other threads:[~2008-05-31 12:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31  2:38 Correct partition table geometry?(Story included) Tuc at T-B-O-H.NET
2008-05-31 12:39 ` Mark Lord [this message]
2008-05-31 21:28   ` Tuc at T-B-O-H.NET

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=484146EF.7090302@rtr.ca \
    --to=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=ml@t-b-o-h.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.