From: Curtis Gedak <gedakc@gmail.com>
To: Phillip Susi <psusi@ubuntu.com>, Karel Zak <kzak@redhat.com>
Cc: Marc MERLIN <marc@merlins.org>, util-linux@vger.kernel.org
Subject: Re: Severe fdisk problem leading to data loss?
Date: Wed, 27 Nov 2013 12:58:11 -0700 [thread overview]
Message-ID: <52964ED3.8030504@gmail.com> (raw)
In-Reply-To: <52963910.60800@ubuntu.com>
On 13-11-27 11:25 AM, Phillip Susi wrote:
> On 11/27/2013 9:58 AM, Karel Zak wrote:
>> After 20 years it's feature ;-) as I'm almost sure that we cannot
>> fix it and disable all partition where is no the ID.
> While that's cute and all, I think we both know it isn't really true ;)
Unfortunately at least one company produces devices that have partitions
with ID set to 0, yet these same partitions contain data.
An Apple iPod Shuffle is such an example as shown in the following fdisk
output:
user@debian:~$ sudo fdisk -l /dev/sde
Note: sector size is 2048 (not 512)
Disk /dev/sde: 8120 MB, 8120172544 bytes
250 heads, 62 sectors/track, 255 cylinders
Units = cylinders of 15500 * 2048 = 31744000 bytes
Device Boot Start End Blocks Id System
/dev/sde1 1 3 92876 0 Empty
/dev/sde2 4 255 7812000 b W95 FAT32
This has lead some people, who wish to re-partition such a device, to
use fdisk to temporarily set the ID to a non-zero value. Then they can
edit the partitions. When the partitioning tasks are complete they use
fdisk to set the ID back to zero again.
By doing this work-around, data loss can be avoided.
As such this "feature" of fdisk has been used and described on the
Internet. For example see the following post:
http://dreamlayers.blogspot.ca/2012/01/editing-ipod-partitions-with-gparted.html
Regards,
Curtis
next prev parent reply other threads:[~2013-11-27 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131118102051.GA31813@merlins.org>
2013-11-24 13:52 ` Severe fdisk problem leading to data loss? Marc MERLIN
2013-11-25 10:31 ` Karel Zak
2013-11-25 11:59 ` Marc MERLIN
2013-11-27 14:46 ` Phillip Susi
2013-11-27 14:58 ` Karel Zak
2013-11-27 18:25 ` Phillip Susi
2013-11-27 19:58 ` Curtis Gedak [this message]
2013-11-27 20:08 ` Phillip Susi
2013-11-27 20:23 ` Curtis Gedak
2013-11-27 21:05 ` Phillip Susi
2013-11-27 21:07 ` Curtis Gedak
2013-11-27 23:02 ` Ángel González
2013-11-27 20:07 ` Karel Zak
2013-11-27 20:19 ` Phillip Susi
2013-11-27 21:09 ` Karel Zak
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=52964ED3.8030504@gmail.com \
--to=gedakc@gmail.com \
--cc=kzak@redhat.com \
--cc=marc@merlins.org \
--cc=psusi@ubuntu.com \
--cc=util-linux@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