Bug 15630 - Partitioner (drakdisk) crashes in presence of firmware raid
Summary: Partitioner (drakdisk) crashes in presence of firmware raid
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-06 03:10 CEST by Vladimir Zawalinski
Modified: 2015-04-07 01:34 CEST (History)
2 users (show)

See Also:
Source RPM: Mageia Control Centre
CVE:
Status comment:


Attachments
syslog after drakdisk crash (275.80 KB, text/plain)
2015-04-06 03:12 CEST, Vladimir Zawalinski
Details
drakdebug report for drakdisk crash (411.63 KB, application/zip)
2015-04-06 03:20 CEST, Vladimir Zawalinski
Details

Description Vladimir Zawalinski 2015-04-06 03:10:22 CEST
Description of problem:
Partitioner, whether invoked from control centre or console, crashes immediately

Version-Release number of selected component (if applicable):
Mageia 5 (Cauldron, RC Round 5 distribution 64 bit, classical installer, KDE)

How reproducible:
Every Time

Steps to Reproduce:
1. UEFI system
2. Define motherboard firmware raid
3.Boot and invoke MCC partitioner tool

This seems to be a leftover after the changes for firmware raid support, with the common symptom "unknown partition table  ..  /dev/sdb". Appears similar to diskdrake failure that was occuring in 14330.
Please find syslog and drakbugreport attachments

Reproducible: 

Steps to Reproduce:
Comment 1 Vladimir Zawalinski 2015-04-06 03:12:33 CEST
Created attachment 6191 [details]
syslog after drakdisk crash
Comment 2 Vladimir Zawalinski 2015-04-06 03:20:03 CEST
Created attachment 6192 [details]
drakdebug report for drakdisk crash
Vladimir Zawalinski 2015-04-06 03:20:46 CEST

CC: (none) => vzawalin1

Thomas Backlund 2015-04-06 14:38:44 CEST

CC: (none) => tmb
Attachment 6191 mime type: application/octet-stream => text/plain

Comment 3 Vladimir Zawalinski 2015-04-07 01:34:20 CEST
This problem does not happen if the system is booted with the noiswmd kerenel parameter added in grub. AS Megeia 5 will be released with this parameter as default, I am closing ths bug.

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


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