Adding below an interesting comment from Curtis H (2009-11-12 21:56:03 CET) at Mandriva bug 53090, with steps to reproduce.


I agree.  This isn't the first time that I've received an error.  In the most
recent case, here's how it came up.

I want to delete all the partitions on a drive.
- Clicked delete on a partition somewhere in the middle of the layout and a
notice popped up that the drives will be renumbered.  
- Then I deleted the remaining partitions starting with the drive furthest to
the right (in the diskdrake layout)
- Clicked "Done" and a note popped up that the new partition table will be
written
- Click the OK button and received the following error:

INTERNAL ERROR: unknown device sdb9
MDK::Common::Various::internal_error() called from
/usr/lib/libDrakX/bootloader.pm:1554
bootloader::device_string2grub() called from
/usr/lib/libDrakX/bootloader.pm:1993
bootloader::update_for_renumbered_partitions() called from
/usr/lib/libDrakX/diskdrake/interactive.pm:1452
diskdrake::interactive::update_bootloader_for_renumbered_partitions() called
from /usr/lib/libDrakX/diskdrake/interactive.pm:298
diskdrake::interactive::Done() called from
/usr/lib/libDrakX/diskdrake/hd_gtk.pm:126
(eval)() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:126
diskdrake::hd_gtk::try_() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:121
diskdrake::hd_gtk::try() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:192
diskdrake::hd_gtk::__ANON__() called from /usr/lib/libDrakX/mygtk2.pm:1424
(eval)() called from /usr/lib/libDrakX/mygtk2.pm:1424
mygtk2::main() called from /usr/lib/libDrakX/ugtk2.pm:767
ugtk2::main() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:115
diskdrake::hd_gtk::main() called from /usr/sbin/diskdrake:93

CC: (none) => stormi
QA Contact: (none) => bugsquad
Assignee: bugsquad => pterjan

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

I experienced the same bug when using diskdrake in Mageia 3 (a fully upgraded Mageia 2, i586):

INTERNAL ERROR: unknown device sda8
MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/bootloader.pm:1660
bootloader::device_string2grub() called from /usr/lib/libDrakX/bootloader.pm:2238
bootloader::update_for_renumbered_partitions() called from /usr/lib/libDrakX/diskdrake/interactive.pm:1541
diskdrake::interactive::update_bootloader_for_renumbered_partitions() called from /usr/lib/libDrakX/diskdrake/interactive.pm:298
diskdrake::interactive::Done() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:133
(eval)() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:133
diskdrake::hd_gtk::try_() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:127
diskdrake::hd_gtk::try() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:208
diskdrake::hd_gtk::__ANON__() called from /usr/lib/libDrakX/mygtk2.pm:1449
(eval)() called from /usr/lib/libDrakX/mygtk2.pm:1449
mygtk2::main() called from /usr/lib/libDrakX/ugtk2.pm:767
ugtk2::main() called from /usr/lib/libDrakX/diskdrake/hd_gtk.pm:121
diskdrake::hd_gtk::main() called from /sbin/diskdrake:93


What I did:
I first removed my sda8 NTFS partition. Diskdrake told something about renumbering one of the partition, but I can't remember the exact message. Then I deleted my sda2 NTFS partition.

Some background: Between those are ext4 partitions numbered respectively sda5, sda6, sda7. sda1 is a swap partition, and I have no sda3 in /dev/. There is a sda4 but I have no idea what that is.

I did not do anything more than deleting those two NTFS partition, then apply the changes and said I wanted it written to /etc/fstab, then comes the error message.

CC: (none) => remi
Source RPM: (none) => diskdrake

*** Bug 8868 has been marked as a duplicate of this bug. ***

CC: (none) => jaanus.ojangu

Addendum: I could not exit diskdrake properly because of this error, so I created a new sda8 partition in the same place as the previous one. The error then disappears.

Output of fdisk -l (after the changes):

Disk /dev/sda: 160.0 GB, 160041885696 bytes, 312581808 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000a516

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63     2040254     1020096   82  Linux swap / Solaris
/dev/sda4        44021754   312576704   134277475+   5  Extended
/dev/sda5        44021760    85995944    20987092+  83  Linux
/dev/sda6        85996008   207479474    60741733+  83  Linux
/dev/sda7       207482880   228139064    10328092+  83  Linux
/dev/sda8       228143104   312576704    42216800+   7  HPFS/NTFS/exFAT

Didn't this get fixed?

CC: (none) => marja11

It can still happens in some cases

Yes still happens, 8b2 64 bit Classic Installer

Create some paritions, delete, make new.

Related or not, on next try I got into a lock; changed my mind and attempted to try F2FS in encrypted LVM, so in LVM I deleted the ext4 i made, created a F2FS, and diskdrake *stopped responding* at all.  Ctrl-AltF3(3) and i saw it had issued some LVM command, forgot which.

Power off, restarted from scratch again without any delete and it is now past that point, installing currently.

Hardware: i586 => All

That doesn't appear to be the same bug Morgan.

I think this bug would have been fixed by the work I did on diskdrake in 2017 (bug 20074).

CC: (none) => mageia

I think you are correct.

Lets close this for now at least

Next time it bombs weirdly, should i grab log and open new bug?

Install.log, dmesg, or more?  dd dump of MBR?

Status: ASSIGNED => RESOLVED
Resolution: (none) => OLD