Bug 12719 - drakinstall fails to detect the right disks
Summary: drakinstall fails to detect the right disks
Status: RESOLVED DUPLICATE of bug 12718
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (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: 2014-02-11 10:56 CET by André DESMOTTES
Modified: 2014-02-11 16:35 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description André DESMOTTES 2014-02-11 10:56:55 CET
Description of problem:
In order to install Cauldron (x86_64 DVD KDE before Mageia 4 release) from a USB stick on an old PC (2008) I had to enter the BIOS to declare the USB stick as the first HD to boot from. 
The first steps went fine until the partionning. There, the USB stick was called sde and the HD sdf. With sdf selected, I checked "Use existing partitions", "next", suggested partitions were sdf5 for / and sdf7 for /home. OK
Formating: sdf5 only, OK, then an error message: "An error ocurred, the swap format for sde5 failed" (French retranslated in English).
It was really sd*e*5, of course sde is in read only mode. I steped back and tried again, same result.
Workaround I tried: "customized partitions", partionning of sdf5, back, "Use existing partitions", uncheck sdf5 for no partitionning -> same result.
Back, sde selected, "customized partitions", delete sde5 (created after the place taken by the image), back, sdf selected, "existing partitions", uncheck sdf5 for no partitionning, and the following went fine.

Version-Release number of selected component (if applicable):
Mageia Cauldron 2 weeks before the release

How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2014-02-11 16:35:21 CET
one is enough

*** This bug has been marked as a duplicate of bug 12718 ***

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


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