Bug 14830 - "INTERNAL ERROR: unknown device sdb1" late in network install if boot media removed
Summary: "INTERNAL ERROR: unknown device sdb1" late in network install if boot media r...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
: Normal normal
Target Milestone: Mageia 6
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
: 15316 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-18 01:41 CET by Morgan Leijström
Modified: 2016-10-10 23:13 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
report.bug.tar.gz (367.52 KB, application/octet-stream)
2014-12-18 01:43 CET, Morgan Leijström
Details

Description Morgan Leijström 2014-12-18 01:41:21 CET
1) I installed using network install, using boot.nonfree on a USB stick.
2) During install while it was installing packages i removed it.
3) after having set root pwd etc it should install the boot loader and i got this message:

* error: INTERNAL ERROR: unknown device sdb1
MDK::Common::Various::internal_error() called from /usr/lib/libDrakX/devices.pm:130
devices::entry() called from /usr/lib/libDrakX/devices.pm:145
devices::make() called from /usr/lib/libDrakX/fs/type.pm:256
fs::type::call_blkid() called from /usr/lib/libDrakX/fs/type.pm:264
fs::type::type_subpart_from_magic() called from /usr/lib/libDrakX/fs/type.pm:246
fs::type::fs_type_from_magic() called from /usr/lib/libDrakX/bootloader.pm:1165
bootloader::suggest() called from /usr/lib/libDrakX/any.pm:205
any::setupBootloaderBefore() called from /usr/lib/libDrakX/install/steps.pm:767
install::steps::setupBootloaderBefore() called from /usr/lib/libDrakX/install/steps_interactive.pm:1043
install::steps_interactive::setupBootloaderBefore() called from /usr/lib/libDrakX/install/install2.pm:111
install::install2::installStepsCall() called from /usr/lib/libDrakX/install/install2.pm:313
install::install2::setupBootloader() called from /usr/lib/libDrakX/install/install2.pm:805
(eval)() called from /usr/lib/libDrakX/install/install2.pm:804
install::install2::real_main() called from /usr/lib/libDrakX/install/install2.pm:789
install::install2::main() called from /usr/bin/runinstall2:30
 
I think it is a bug that it tries to do *anything* on sdb.
- the network install boot device.
Logically, i should be able to remove it anytime after it loaded, at least after it started stage2 ?

I am positive i did not set a mount point for it during partitioning.

md5sum of 64 bit boot.nonfree.iso = 0cc0244dfe5b740acf6b0ef3df23d12f
drakX v 16.48

4) I executed "bug" and will attach the file to this bug.

5) I put in the USB stick and pressed the OK button on the dialog and it proceeded with the graphis driver install

Reproducible: yes

Reproducible: 

Steps to Reproduce:
Comment 1 Morgan Leijström 2014-12-18 01:43:00 CET
Created attachment 5720 [details]
report.bug.tar.gz
Comment 2 Morgan Leijström 2014-12-18 10:34:59 CET
After this I did annother install attempt and kept the stick plugged in, so i did not see this message.

But other problem happened... So, booted on same usb stick again for yet another trial, and *now* the installer say the partition on sdb is to corrupted to be useable.

Anyhow, it apparently booted on it, and i intend not to install on it...

What the heck did it do to it and when?

Logs on the install before when sdb was found corrupt, see https://bugs.mageia.org/show_bug.cgi?id=12027#c7
Comment 3 Thierry Vignaud 2015-02-18 11:29:27 CET
Should be fixed by this morning installer (was probably bug #14435).

For original report, well, removing the usb stick was a bad idea :-)
Though ideally this should be made to work as it's no more needed.
Comment 4 Morgan Leijström 2015-02-18 14:16:20 CET
Thanks.
For removing usb after network installer booted i now made bug #15316
Comment 5 Thierry Vignaud 2015-05-29 13:18:43 CEST
*** Bug 15316 has been marked as a duplicate of this bug. ***
Comment 6 Thierry Vignaud 2015-05-29 13:21:38 CEST
It would have worked if you've removed it before the graphical installer starts (ie when stage1 is loaded and look for stage2).

We could alter install::steps::setupBootloaderBefore() so that it refresh $all_hds but really there's more places where the installer isn't ready to cope with removed hds.

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