Bug 15645 - Both boot.iso's ( i586 & x86_64 ) are generating unbootable installs
Summary: Both boot.iso's ( i586 & x86_64 ) are generating unbootable installs
Status: RESOLVED DUPLICATE of bug 15640
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 5rc
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-07 18:09 CEST by William Kenney
Modified: 2015-04-08 08:56 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description William Kenney 2015-04-07 18:09:40 CEST
Description of problem:

M5RC i586 install from boot.iso
04/02/15 20:46
MD5SUM: 050b61aa950b06ae3c2c98dee8457cc0

I've installed this three times. Twice in Vbox and once
on real hardware. All three resulted in an unbootable
install. It never even got started. The computer saw
nothing to boot to. On Vbox it went back to the boot.iso
file and started all over thinking there was nothing
on the drive. I selected GRUB2.

In Vbox, GRUB2:

M5RC i585 install from boot.iso
04/07/15 00:04
MD5SUM: 5bdb33868c9b2a306a8f50bd1b701f7c
generates an unbootable install

M5RC x86_64 install from boot.iso
04/07/15 00:04
MD5SUM: 0137cc5b500286e7426334a453f026e3
generates an unbootable install


Reproducible: 

Steps to Reproduce:
William Kenney 2015-04-07 18:10:03 CEST

Whiteboard: (none) => 5rc

Comment 1 claire robinson 2015-04-07 18:18:42 CEST
This is likely to be a duplicate of bug 15640

Also see stormi's bug 13901
claire robinson 2015-04-07 18:20:48 CEST

CC: (none) => eeeemail

Comment 2 William Kenney 2015-04-07 19:39:14 CEST
(In reply to claire robinson from comment #1)

> This is likely to be a duplicate of bug 15640
> 
> Also see stormi's bug 13901

Ya, probably. I'll watch for the next updates of the boot.iso's
Latest M5RC i586 KDE Live-CD media installs from the boot menu just fine.
Comment 3 Marja Van Waes 2015-04-07 23:28:26 CEST
Just tried with boot-nonfree iso (32bits) from 2015-04-07 19:51
and used stage2 v. 16.79

install (choosing grub2 as bootloader) went fine and I had no problems booting into Mageia.

CC: (none) => marja11

Comment 4 William Kenney 2015-04-08 00:15:58 CEST
(In reply to Marja van Waes from comment #3)

> Just tried with boot-nonfree iso (32bits) from 2015-04-07 19:51
> and used stage2 v. 16.79
> 
> install (choosing grub2 as bootloader) went fine and I had no problems
> booting into Mageia.

Are you using the on-line repo or a local repo. Mine is:

192.168.1.2://~mageia/repo/distrib/5/i586
Comment 5 Marja Van Waes 2015-04-08 08:43:52 CEST
(In reply to William Kenney from comment #4)
> (In reply to Marja van Waes from comment #3)
> 
> > Just tried with boot-nonfree iso (32bits) from 2015-04-07 19:51
> > and used stage2 v. 16.79
> > 
> > install (choosing grub2 as bootloader) went fine and I had no problems
> > booting into Mageia.
> 
> Are you using the on-line repo or a local repo. Mine is:
> 
> 192.168.1.2://~mageia/repo/distrib/5/i586

local mirror on a USB disk. In stage1 I chose to use hard disk, then selected the USB drive, then set the path, for me that was:
mageia/distrib/cauldron/i586

I did not try "5" instead of "cauldron"...... I had thought that should work, because the "5" directory links to "cauldron", but in Monday's meeting I understood (or misunderstood?) from tmb that that wouldn't work, yet.
Comment 6 Marja Van Waes 2015-04-08 08:48:56 CEST
William, I understand the problem is not getting installer to run and finish, but booting into the just installed system. Is that correct?

If so, and if the problem persists, then please attach /drakx/report.bug.xz from your last install.

(Using "5" was OK, if it hadn't, you wouldn't have been able to install!)
Comment 7 Marja Van Waes 2015-04-08 08:50:56 CEST
oops
s!/drakx!/root/drakx!
Comment 8 Thierry Vignaud 2015-04-08 08:56:01 CEST
Closing

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

Status: NEW => RESOLVED
CC: (none) => thierry.vignaud
Resolution: (none) => DUPLICATE


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