Bug 15960 - Deleting a GPT partition during classic install results in "I cannot read the partition table of device sda, it's too corrupted for me"
Summary: Deleting a GPT partition during classic install results in "I cannot read the...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-16 15:41 CEST by Martin Whitaker
Modified: 2015-06-02 15:48 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Stage 2 log showing failure (20.73 KB, text/plain)
2015-05-16 15:41 CEST, Martin Whitaker
Details

Description Martin Whitaker 2015-05-16 15:41:24 CEST
Created attachment 6560 [details]
Stage 2 log showing failure

Using the round 1 M5 final classic x86_64 DVD (from USB stick). Selected custom partitioning, and whilst setting up the partitions, deleted an unwanted partition left over from a previous trial. After clicking on "Next", the "I cannot read the partition table of device sda, it's too corrupted for me" was displayed, along with the error trace:

INTERNAL ERROR: unknown device sda1
MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/devices.pm:131
devices::entry() called from /usr/lib/libDrakX/devices.pm:146
devices::make() called from /usr/lib/libDrakX/fs/type.pm:254
fs::type::call_blkid() called from /usr/lib/libDrakX/fs/type.pm:262
fs::type::type_subpart_from_magic() called from /usr/lib/libDrakX/fsedit.pm:281
fsedit::get_hds() called from /usr/lib/libDrakX/fs/any.pm:14
fs::any::get_hds() called from /usr/sbin/draklive-install:135
(eval)() called from /usr/sbin/draklive-install:135
main::init_hds() called from /usr/sbin/draklive-install:65
main::install_live() called from /usr/sbin/draklive-install:42

Clicking on "OK" brings you back to the same message, and the only way out is to reboot.

Looking in ddebug.log, it claims

* error: failed to del partition #13 on /dev/sda at /usr/lib/libDrakX/partition_table/gpt.pm line 168.

but after reboot, fdisk showed the partition was deleted.
Samuel Verschelde 2015-05-16 17:41:06 CEST

CC: (none) => thierry.vignaud, tmb

Comment 1 Thierry Vignaud 2015-05-17 11:10:04 CEST
Actually it might have failed b/c it failed to tell the kernel to reread the partition table b/c one of /dev/sda partition was busy (eg: mounted)

Which is confirmed by this error message:
* error: /proc/partitions does not agree with drakx 12 != 13:

That means the kernel failed to reread the partition table
Comment 2 Samuel Verschelde 2015-05-17 16:54:34 CEST
Is that something we can still fix or should we make it an ERRATA entry?

Severity: normal => major

Martin Whitaker 2015-06-02 00:39:58 CEST

Whiteboard: (none) => IN_ERRATA

Comment 3 Samuel Verschelde 2015-06-02 09:27:38 CEST
According to the following Errata entry, it's not possible to delete a GPT partition and then to continue with the installation.

Could you test in order to make the report more precise? If it's truly deleting any GPT partition that makes the install fail, could be a blocker. Otherwise please update the Errata.
Comment 4 Samuel Verschelde 2015-06-02 09:28:21 CEST
Setting FOR_ERRATA back until we are sure the Errata entry is ok and/or we make it blocker (although it's very very late)

Whiteboard: IN_ERRATA => FOR_ERRATA

Comment 5 Tony Blackwell 2015-06-02 13:27:35 CEST
Without specifically testing this now, I doubt this is still true.  I've been able to resize or delete existing MSWin-created partitions, even on RAID0, with Classic install and to create and delete and re-create GPT partitions entirely within Mageia without problems using current media. (except for the 5th-partition bug which is in errata) 
Tony

CC: (none) => tablackwell

Comment 6 André DESMOTTES 2015-06-02 15:43:59 CEST
I confirm what Tony said. I could create and delete GPT partitions with Mageia Classic installer since Mageia 5 RC.

CC: (none) => lebarhon

Comment 7 Thierry Vignaud 2015-06-02 15:45:33 CEST
Closing then

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 8 Samuel Verschelde 2015-06-02 15:48:48 CEST
Ok, I'll remove the Errata entry that had been written.

Whiteboard: FOR_ERRATA => (none)


Note You need to log in before you can comment on or make changes to this bug.