Bug 3671 - 2_a1: Unable to re-install boot loader with install dvd
Summary: 2_a1: Unable to re-install boot loader with install dvd
Status: RESOLVED DUPLICATE of bug 3327
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2011-12-08 20:13 CET by Bit Twister
Modified: 2012-01-26 17:09 CET (History)
0 users

See Also:
Source RPM: drakx-installer-rescue
CVE:
Status comment:


Attachments
results of blkid (1.15 KB, text/plain)
2012-01-26 16:37 CET, Bit Twister
Details
fstab (1.70 KB, text/plain)
2012-01-26 16:38 CET, Bit Twister
Details

Description Bit Twister 2011-12-08 20:13:07 CET
Description of problem:

Tried to re-install grub boot loader with install dvd

I navigated to reinstall, it looked ok for about 2 thirds of the way then it had a problem with cp commands for each of my partitions.

LABEL=cauldron on /mnt/cauldron type ext4 options default
cp: cannot create regular file '/mnt/etc/mtab': no such file or directory

After the above happened for each partition I get:

Your system is ready on /mnt.
Your root device isn't mounted on /mnt
<press Enter to return to Rescue menu>

Program exited abnormally (Return code 2)

Program 

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:

1. Use e2label /dev/XdYZ new-label-here to label all your partitions.
2. Modify fstab to use label partitions
3. Boot dvd
4. pick rescue
5. pick re-install bootloader
6. take first selection


Examaple fstab:

LABEL=cauldron / ext4 defaults 1 1
LABEL=cooker /cooker ext4 users,noauto,defaults 1 2
LABEL=2011_0_64 /2011_0_64 ext4 users,noauto,acl,relatime 1 2
LABEL=2010_2_64 /2010_2_64 ext4 users,noauto,defaults 1 2
Manuel Hiebel 2011-12-08 22:20:08 CET

Source RPM: (none) => drakx-installer-rescue

Comment 1 Manuel Hiebel 2011-12-08 22:23:17 CET
Hi, thanks for reporting this bug.
Assigned to the package maintainer.

Keywords: (none) => Triaged
Assignee: bugsquad => thierry.vignaud

Comment 2 Manuel Hiebel 2011-12-09 19:53:00 CET
maybe related to bug 3678
Comment 3 Thierry Vignaud 2012-01-25 17:40:48 CET
I would say it has been fixed along bug #3327
Just try cauldron rescue from your favorite mirror tomorrow or the day after
Comment 4 Bit Twister 2012-01-25 18:01:35 CET
(In reply to comment #3)
> I would say it has been fixed along bug #3327
> Just try cauldron rescue from your favorite mirror tomorrow or the day after

Do you mean a new dvd iso is being released?
Comment 5 Manuel Hiebel 2012-01-25 18:45:05 CET
(In reply to comment #4)
> 
> Do you mean a new dvd iso is being released?

No, only for the beta 1, but you can use the neinstall with the boot.iso [1]
and type 'rescue' at the prompt.

[1]: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/images/
Comment 6 Thierry Vignaud 2012-01-25 21:50:12 CET
which would load rescue.sqfs from http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/stage2/

Please test that boot.iso (or all.img on a USB key) and report if it's fixed
But I'm pretty confident this is the same bug as bug #3327 : rescue was jut not able to mount the root system anymore.

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

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

Comment 7 Bit Twister 2012-01-26 16:36:55 CET
(In reply to comment #6)
> which would load rescue.sqfs from
> http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/x86_64/install/stage2/
> 
> Please test that boot.iso (or all.img on a USB key) and report if it's fixed

Still broke.

Latest boot.iso test results
Entered rescue, picked hard drive Mageia-2-alpha3-x86_64-DVD.iso

Failed to open /dev/kmsg for logging: No such file or directory
Failed to mount /dev/shm: No such file or directory

Rebooted, selected network. Mirror contents of interest:
Index of ftp://mirrors.kernel.org/mageia/distrib/cauldron/x86_64/install/stage2/

Up to higher level directory
Name    Size    Last Modified
File:VERSION    1 KB    01/24/2012      09:02:00 PM
File:mdkinst.sqfs       46848 KB        01/24/2012      09:02:00 PM
File:rescue.sqfs        25064 KB        01/25/2012      07:53:00 PM


Grub> root (hd0,5)
Error 21: Selected disk does not exist
grub> setup --state2=/boot/grub/state2 (hd0)
Error 12: Invalid device requested

My recommendation, get grub to work on a running install, then work
the boot.iso problem. 

I have no idea how grub is to pick which partition will be used if
there are more than one installation. Example: cauldron, alpha2,
alpha3, beta1 and the user want to set alpha3 as the booting menu choice.

I lucked out that I happened to have cauldron alpha3 on hd0, and rest
of my installs on hd1.
Comment 8 Bit Twister 2012-01-26 16:37:46 CET
Created attachment 1435 [details]
results of blkid
Comment 9 Bit Twister 2012-01-26 16:38:14 CET
Created attachment 1436 [details]
fstab
Comment 10 Thierry Vignaud 2012-01-26 16:48:24 CET
This bug was about:

Your system is ready on /mnt.
Your root device isn't mounted on /mnt

which is now fixed.
Please don't mix issues and open a new bug report for this.
though I don't understand what you meant by "picked hard drive Mageia-2-alpha3-x86_64-DVD.iso"
Comment 11 Bit Twister 2012-01-26 17:09:42 CET
(In reply to comment #10)
> This bug was about:
> 
> Your system is ready on /mnt.
> Your root device isn't mounted on /mnt
> 
> which is now fixed.

Well since I tested today, I can not do a network (AS REQUESTED) or hard disk re-install of the the boot loader. So it is not fixed.

> Please don't mix issues 

Well, excuse me. Thought I would mention your new boot.iso would not
boot an iso from the hard drive.

> and open a new bug report for this.

That's ok, I'll let QA report it. Someone needs to modify the regression test procedure for boot.iso.

> though I don't understand what you meant by "picked hard drive
> Mageia-2-alpha3-x86_64-DVD.iso"

Does not matter now does it. 25-jan boot.iso is useless.

[

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