Mailinglist Archive: opensuse-bugs (5295 mails)

< Previous Next >
[Bug 848655] New: Fail to install grub2 during installation
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 1 Nov 2013 16:06:53 +0000
  • Message-id: <>

Summary: Fail to install grub2 during installation
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: x86-64
OS/Version: SUSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: nrickert@xxxxxxxxxxxxx
QAContact: jsrain@xxxxxxxx
Found By: ---
Blocker: ---

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101

This is for 13.1RC2. I've listed this as an install problem, rather than a
grub2 problem.

Background: Install is to an encrypted LVM. There is a separate "/boot".

During the install, I imported partitioning from my prior install (prior was
13.1RC1). However, I changed the root file system to use "ext4". I had used
"btrfs" for RC1.

The error message indicated that grub2 could not be found, because
"/boot/grub2" could not be located. I continued with the install anyway, to
have an unbootable system.

Examining from another system, here is what I could see:

"/boot" was completely empty (except for the "lost+found" directory).

If I unmounted "/boot", then the "/boot" directory on the root file system did
contain all of the normal stuff. Not helpful for booting, since that file
system use encryption.

It looks to me as if "/boot" (or "/dev/sda1") was properly formatted during the
install, but was never mounted.

Note: I was able to recover the system, which is now working fine.

Second problem: this looks unrelated, but I suspect it is actually related
(the same install failure). The partitioning include "/dev/sda3", to be
mounted as "/windows/C" with NTFS. It was supposed to not be mounted by
default. The "/etc/fstab" entry for this was correct. However, when I tried
to manually mount, it turned out that the mount point "/windows/C" had never
been created.

Attachment: I will, shortly, attach YaST logs for the install.

Wild guess: Here's a completely wild guess. I think this is due to my
changing the root file system to use "ext4" rather than "btrfs" previously used
on the same volume. It's my understanding that with "btrfs", something is done
with snapshots, instead of a completer reinstall. So presumably Yast has to
handle it differently. I'm guessing that Yast made that decision too early, so
did not adapt to the fact that I changed to using "ext4" for that volume.

Reproducible: Didn't try

Steps to Reproduce:

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >