The "diskdrake" program crashed. Drakbug-17.88.3 caught it. I cannot read the partition table of device sdd, it's too corrupted for me :( I can try to go on, erasing over bad partitions (ALL DATA will be lost!). The other solution is to not allow DrakX to modify the partition table. (the error is unknown partition table format on disk /dev/sdd. ) Do you agree to lose all the partitions? Can't locate partition_table/loop.pm in @INC (you may need to install the partition_table::loop module) (@INC contains: /usr/lib/libDrakX /usr/lib/perl5/site_perl/5.22.3/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.22.3 /usr/lib/perl5/vendor_perl/5.22.3/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.22.3 /usr/lib/perl5/5.22.3/x86_64-linux-thread-multi /usr/lib/perl5/5.22.3 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.22.2 /usr/lib/perl5/vendor_perl/5.22.2/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.22.0 /usr/lib/perl5/vendor_perl/5.20.1 /usr/lib/perl5/vendor_perl .) at /usr/lib/libDrakX/partition_table.pm line 279. Perl's trace: drakbug::bug_handler() called from /usr/lib/libDrakX/partition_table.pm:279 partition_table::initialize() called from /usr/lib/libDrakX/partition_table/raw.pm:227 partition_table::raw::zero_MBR() called from /usr/lib/libDrakX/fsedit.pm:261 fsedit::get_hds() called from /usr/libexec/diskdrake:74 Theme name: oxygen-gtk Kernel version = 4.14.70-desktop-2.mga6 Distribution=Mageia release 6 (Official) for x86_64 CPU=Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Summary: diskdrake crashed => diskdrake crashed [Can't locate partition_table/loop.pm in @INC (you may need to install the partition_table::loop module)]Assignee: bugsquad => mageiatoolsCC: (none) => marja11, pterjan
Is this still valid in Mageia 7? Cauldron?
CC: (none) => ouaurelien
Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of our distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Resolution: (none) => OLDStatus: NEW => RESOLVED