Bug 24055 - Attempt to create a GUID partition table creates one onremoveable partition
Summary: Attempt to create a GUID partition table creates one onremoveable partition
Status: RESOLVED INVALID
Alias: None
Product: udisks
Classification: Unclassified
Component: operations (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: David Zeuthen (not reading bugmail)
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-20 17:10 UTC by maximlevitsky
Modified: 2010-01-22 03:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description maximlevitsky 2009-09-20 17:10:08 UTC 
Just after creation of the partition table, it creates a single partition that spans all the device (which is wrong), then an attempt to delete it fails:

Error erasing: helper exited with exit code 1: In part_del_partition: device_file=/dev/mmcblk0, offset=512
Entering MS-DOS parser (offset=0, size=1015808000)
MSDOS_MAGIC found
found partition type 0xee => protective MBR for GPT
Exiting MS-DOS parser
Entering EFI GPT parser
No GPT_MAGIC found
Leaving EFI GPT parser
Entering Apple parser
No MAC_MAGIC found
Leaving Apple parser
No known partition table found
got it
Error: /dev/mmcblk0: unrecognised disk label
ped_disk_new() failed
Comment 1 David Zeuthen (not reading bugmail) 2009-10-16 13:28:25 UTC 
(In reply to comment #0)
> device_file=/dev/mmcblk0

IIRC, SD media only support MBR so that's probably why you are seeing this bug. Yes, it's crazy, but that's part of the spec IIRC. Not all SD readers may enforce this restriction. Does it work on other kinds of devices?
Comment 2 maximlevitsky 2009-10-16 22:10:39 UTC 
very well could be, a usb on disk keys doesn't have this limitation?
Comment 3 maximlevitsky 2009-10-22 15:27:18 UTC 
Unfortunately, exactly same behavior is seen on an usb disk-on-key.
Comment 4 maximlevitsky 2010-01-22 03:28:31 UTC 
Just like I explained in bug #24056, everything works fine now.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.