Your message dated Sun, 13 Jan 2013 10:40:36 +0800
with message-id <[email protected]>
and subject line Re: Bug#606168: Bug #606168 - Parted complains about MBR 
modified by gptsync
has caused the Debian Bug report #606168,
regarding Parted complains about MBR modified by gptsync
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
606168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606168
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: parted
Version: 1.8.8.git.2008.03.24-11.1

disk0label attached is the first 40 blocks (20480 B) of GPT with MBR
modified by gptsync.

$ /sbin/parted -s disk0label print
Warning: Unable to open /home/andrewb/disk0label read-write (Permission
denied).  /home/andrewb/disk0label has been opened read-only. Warning:
Unable to open /home/andrewb/disk0label read-write (Permission
denied).  /home/andrewb/disk0label has been opened read-only. Error:
Can't have the end before the start! Error: Can't have overlapping
partitions. Error: Can't have overlapping partitions. Backtrace has 9
calls on stack: 9: /lib/libparted-1.8.so.10(ped_assert+0xb0) [0xff7ca60]
  8: /lib/libparted-1.8.so.10 [0xffc07a8]
  7: /lib/libparted-1.8.so.10(ped_disk_new+0xc4) [0xff86c44]
  6: /sbin/parted [0x100077f0]
  5: /sbin/parted(command_run+0x1c) [0x1000583c]
  4: /sbin/parted(non_interactive_mode+0xb4) [0x1000d994]
  3: /sbin/parted(main+0x80) [0x1000b910]
  2: /lib/libc.so.6 [0xfd49704]
  1: /lib/libc.so.6 [0xfd498c0]


You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

        http://ftp.gnu.org/gnu/parted/

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

        http://www.gnu.org/software/parted

for further information.

Your report should contain the version of this release (1.8.8)
along with the error message below, the output of

        parted DEVICE unit co print unit s print

and the following history of commands you entered.
Also include any additional information about your setup you
consider important.

Assertion ((PedSector) PED_LE64_TO_CPU (gpt->AlternateLBA) <=
disk->dev->length - 1) at ../../../libparted/labels/gpt.c:828 in
function gpt_read() failed.

Error: Can't have overlapping partitions.

The MBR itself.

$/sbin/sfdisk -d disk0label

WARNING: GPT (GUID Partition Table) detected on 'disk0label'! The util
sfdisk doesn't support GPT. Use GNU Parted.

# partition table of disk0label
unit: sectors

disk0label1 : start=        1, size=   409639, Id=ee
disk0label2 : start=   409640, size=456713104, Id=af
disk0label3 : start=457384888, size=453190728, Id=83, bootable
disk0label4 : start=910575616, size= 32966656, Id=83

Attachment: disk0label
Description: Binary data


--- End Message ---
--- Begin Message ---
Package: parted
Version: 2.3-5

On Sat, 12 Jan 2013 10:08:24 -0500
Phillip Susi <[email protected]> wrote:

> On 01/12/2013 08:05 AM, Andrew Buckeridge wrote:
> > Parted expects protective MBR to have a single entry for GPT (the
> > GPT itself contains the partitions). However, gptsync also has MBR
> > point to partitions after the GPT. Note that partitions are off by
> > one as MBR still has entry for GPT. The GPT does not have an entry
> > itself.
> 
> When you originally filed this report it was for version 1.8.  Are you
> still using that or have you upgraded?  2.3-11 in wheezy seems to work
> fine for me.

Only looking with parted and sfdisk as this disc is in use. 2.3-5 did
not die like before. Disc has not been touched.

PeeCee LBA is another annoyance, but should not be an issue if you
create a new one to PeeCee LBA. What is logical about 255 heads, 63
sectors or 512 byte blocks? Ran without crashing or complaint this time
so fixed.

Intel Macs and PeeCees are very entertaining. Rest is info only.

On a dual boot Mac use Mac diskutil and then gptsync. Gptsync is
available inside rEFIt. Pot luck whether Linux counts MBR or GPT
numbers. MBRs parts are +1 as first must be protective 0xee.
My root is /dev/sda3 (GPT) where as before it was /dev/sda4 (MBR).
I label volumes boot, root, var, swap, etc. so can mount by LABEL.
Remembering and typing UUIDs during rescue is a bit tricky.

Parted and also sfdisk get confused and presumes PeeCee "Logical" Block
Addressing with CHSB */255/63/512. Kernel probably guesses this.

On SD cards I clip H to 128 and S to 32 to make alignment with 64kiB BU
easier using sfdisk and mkfs.msdos -s .. -S 512 or mkfs.ext2 -E
stride=..,stripe-width=.. Note that SDHC require alignment with 4MiB BU!

Obviously Mac don't use PeeCee CHS and LBA crappage. What's boundary
unit of SATA SSDs? They are "logical" 512B or 4096B, but internally
they are read modify write to physical BU. (Btrfs devs may know this
and disc label work arounds or must /var be a superfloppy SSD?)

Guessing CHS crappage from MBR presumes they start on track boundaries
and end on cylinder boundaries. You can not do this if want to align
data on SSDs. However, on rotating discs you can align 4kiB of first
volume on next track only by hiding first 512B "logical" block and then
using PeeCee CHSB */255/63/512. Ending entry must also be clipped if
larger than CHS.

Its all a mess, but its working so not touching my disc.

> andrewb@andrewbi:~$ sudo parted /dev/sda unit chs print quit
> Model: ATA Hitachi HTS54505 (scsi)
> Disk /dev/sda: 60801,80,62
> Sector size (logical/physical): 512B/512B
> BIOS cylinder,head,sector geometry: 60801,255,63.  Each cylinder is 8225kB.
> Partition Table: gpt
> 
> Number  Start         End           File system     Name                  
> Flags
>  1      0,0,40        25,127,13     fat32           EFI System Partition
>  2      25,127,14     28454,146,35  hfs+            NotQuiteMaxDisk
>  3      28470,227,37  56680,181,12  ext3            root
>  4      56697,7,14    60801,80,14   linux-swap(v1)  swap

CHS are always funny. These are worked out from 512B "logical" blocks
and kernel guess as no CHS crappage in GPT. Also none in simpler type
0x88, but have to mount on loop in my kernel. What about 4kiB blocks?

> andrewb@andrewbi:~$ sudo sfdisk -l /dev/sda
> 
> WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util sfdisk 
> doesn't support GPT. Use GNU Parted.

Ah, but sfdisk and shell printf|dd run on RISC powerpc.
That's another bug.
> 
> 
> Disk /dev/sda: 60801 cylinders, 255 heads, 63 sectors/track
> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
> 
>    Device Boot Start     End   #cyls    #blocks   Id  System
> /dev/sda1          0+      0-      1-        19+  ee  GPT
>                 start: (c,h,s) expected (0,0,2) found (1023,254,63)
>                 end: (c,h,s) expected (0,0,40) found (1023,254,63)
> /dev/sda2          0+     25-     26-    204800    c  W95 FAT32 (LBA)
>                 start: (c,h,s) expected (0,0,41) found (1023,254,63)
>                 end: (c,h,s) expected (25,127,14) found (1023,254,63)
> /dev/sda3         25+  28454-  28430- 228356552   af  HFS / HFS+
>                 start: (c,h,s) expected (25,127,15) found (1023,254,63)
> /dev/sda4   *  28470+  56680-  28210- 226595364   83  Linux
May have tried to read the CHS junk!?

--- End Message ---

Reply via email to