Package: gdisk Version: 0.7.2-1 Severity: normal It appears that the new gdisk release confuses itself when it needs to write a protective MBR:
=== # gdisk /dev/sde GPT fdisk (gdisk) version 0.7.2 Partition table scan: MBR: not present BSD: not present APM: not present GPT: present Found valid GPT with corrupt MBR; using GPT and will write new protective MBR on save. Command (? for help): p Disk /dev/sde: 3907029168 sectors, 1.8 TiB Logical sector size: 512 bytes Disk identifier (GUID): BA0107F2-D774-4FF5-BCB7-9DD1F6874523 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 3907029134 Partitions will be aligned on 8-sector boundaries Total free space is 6 sectors (3.0 KiB) Number Start (sector) End (sector) Size Code Name 1 40 131111 64.0 MiB 8200 Linux swap 2 131112 8650791 4.1 GiB 8E00 Linux LVM 3 8650792 2930277127 1.4 TiB FD00 Linux RAID 4 2930277128 3907029134 465.8 GiB FD00 Linux RAID Command (? for help): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed? (Y/N): y OK; writing new GUID partition table (GPT). Warning: 0xEE partition doesn't start on sector 1. This can cause problems in some OSes. Warning! An error was reported when writing the partition table! This error MIGHT be harmless, but you may have trashed the disk! Command (? for help): q === In particular, note the absence of the "operation completed succesfully" message. Trying to rebuild the protective MBR gives the following: === # gdisk /dev/sde GPT fdisk (gdisk) version 0.7.2 [..] Command (? for help): x [..] Expert command (? for help): n Expert command (? for help): o Disk size is 3907029168 sectors (1.8 TiB) MBR disk identifier: 0x00000000 MBR partitions: Number Boot Start Sector End Sector Status Code 1 1 100527 omitted 0xEE === After downgrading to 0.6.14-1 (yay snapshots.d.o :), I get this: === # gdisk /dev/sde GPT fdisk (gdisk) version 0.6.14 Partition table scan: MBR: not present BSD: not present APM: not present GPT: present Found valid GPT with corrupt MBR; using GPT and will write new protective MBR on save. Command (? for help): v No problems found. 6 free sectors (3.0 KiB) available in 1 segments, the largest of which is 6 (3.0 KiB) in size. Command (? for help): w Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING PARTITIONS!! Do you want to proceed, possibly destroying your data? (Y/N): y OK; writing new GUID partition table (GPT). The operation has completed successfully. === And the protective MBR data: === Command (? for help): x Expert command (? for help): o MBR disk identifier: 0x00000000 MBR partitions: Number Boot Start (sector) Length (sectors) Type 1 1 3907029167 0xEE Disk size is 3907029168 sectors (1.8 TiB) === I have done the same test on a 1.5TB disk with similar results (results are the same before and after issuing 'n'-create a new protective MBR): 0.7.2: Number Boot Start Sector End Sector Status Code 1 1 97071 omitted 0xEE 0.6.14: Number Boot Start (sector) Length (sectors) Type 1 1 2930277167 0xEE I have not tried to write a new partition table to other disks -- they're very much in use. But given the sector number mismatches, I would expect similar failures on those disks. Thanks, Arno Information: Debian Release: 6.0.2 APT prefers stable APT policy: (990, 'stable'), (600, 'testing'), (200, 'stable-updates') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-5-kirkwood Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdisk depends on: ii groff-base 1.20.1-10 GNU troff text-formatting system ( ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libpopt0 1.16-1 lib for parsing cmdline parameters ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libuuid1 2.17.2-9 Universally Unique ID library gdisk recommends no packages. gdisk suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
