From: Christian Ohm <chr.ohm@gmx.net>
To: linux-ext4@vger.kernel.org
Subject: Re: How to recover a damaged ext4 file system?
Date: Thu, 12 Feb 2009 22:36:24 +0100 [thread overview]
Message-ID: <20090212213624.GA17744@moongate.localnet> (raw)
In-Reply-To: <498DDB26.3080102@redhat.com>
On Saturday, 7 February 2009 at 13:04, Eric Sandeen wrote:
> that's counting "cylinders" - try "fdisk -u" to be able to display (or
> specify) geometry in sectors, which is not a unit open to interpretation...
Corrupted disk:
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xaaaaaaaa
Device Boot Start End Blocks Id System
/dev/sdc1 1 1953520064 976760032 83 Linux
New partition:
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xaaaaaaaa
Device Boot Start End Blocks Id System
/dev/sdc1 63 1953520064 976760001 83 Linux
Both disks show the exact same size in sectors (in the kernel messages as
well), so the new partition on the new drive should be exactly the same as the
one on the old drive. For some reason the new partition starts at sector 63,
while the old one starts at sector 1 - but that could be a difference in
creating the partitions (unless sector 1 is an invalid starting sector?).
Best regards,
Christian Ohm
prev parent reply other threads:[~2009-02-12 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 13:53 How to recover a damaged ext4 file system? Christian Ohm
2009-01-06 12:05 ` Andreas Dilger
2009-01-06 19:34 ` Theodore Tso
2009-01-07 21:42 ` Christian Ohm
2009-01-08 10:11 ` Andreas Dilger
2009-02-07 16:27 ` Christian Ohm
2009-02-07 19:04 ` Eric Sandeen
2009-02-12 21:36 ` Christian Ohm [this message]
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=20090212213624.GA17744@moongate.localnet \
--to=chr.ohm@gmx.net \
--cc=linux-ext4@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).