graphical installer crashed.

Bug #1721317 reported by HankB
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub-installer (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Installing to /dev/sdb with /boot/efi on an MD RAID1 partition. Booted to live environment, apt upgrade/update, install mdadm (and gparted) brought up the RAID and started the install. Selected /dev/md0 for EFI partition and /dev/sdb2 for '/' (formatted as EXT4) Selected /dev/sdb for GRUB installation.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4 [modified: lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
Date: Wed Oct 4 12:52:56 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
HankB (hbarta) wrote :
Revision history for this message
HankB (hbarta) wrote :

Without rebooting I followed directions at https://askubuntu.com/questions/83037/how-do-i-reinstall-grub2, mounted / and /boot/efi:

root@ubuntu:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 16421252 0 16421252 0% /dev
tmpfs 3287460 9792 3277668 1% /run
/dev/sdc 1550400 1550400 0 100% /cdrom
/dev/loop0 1496320 1496320 0 100% /rofs
aufs 16437292 2260244 14177048 14% /
tmpfs 16437292 18012 16419280 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 16437292 0 16437292 0% /sys/fs/cgroup
tmpfs 16437292 524 16436768 1% /tmp
tmpfs 3287460 84 3287376 1% /run/user/999
/dev/sdb2 50264772 53072 47635316 1% /mnt
/dev/md0 523248 3496 519752 1% /mnt/boot/efi
root@ubuntu:~# ls /mnt/boot/efi
EFI
root@ubuntu:~# ls /mnt/boot/efi/EFI/
Dell ubuntu
root@ubuntu:~# grub-install --root-directory=/mnt /dev/sdb
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
grub-install: error: will not proceed with blocklists.
root@ubuntu:~# grub-install --force --root-directory=/mnt /dev/sdb
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged..
Installation finished. No error reported.
root@ubuntu:~# update-grub
/usr/sbin/grub-probe: error: failed to get canonical path of `aufs'.
root@ubuntu:~#

Tried to boot from BIOS (UEFI boot manager) selecting "integrated RAID Controller 1: ubuntu" and got a "GRUB>" prompt. Seems like no way to boot from second drive via the UEFI BIOS. Swapped drives with same result.

or similar hoping

Revision history for this message
Phillip Susi (psusi) wrote :

Can you post the output of mdadm -D /dev/md0?

Changed in grub-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
HankB (hbarta) wrote : Re: [Bug 1721317] Re: graphical installer crashed.

I needed to get the install done so I went ahead and did a more normal
install with '/boot/efi' in an normal partition on the first disk. After
the install, I created a matching partition on the second drive, copied the
/boot/efi partition to that and then created a (degraded RAID) on the first
drive. (At this point I had destroyed /dev/md0 and recreated it.) I then
copied the data back to the RAID partition on the first drive, unmounted
the partition on the second and added it to complete the RAID1. The
partition was created as /dev/md0 (using 0.90 metadata) and after reboot
came up as /dev/md127. Other than that, it seems to work. Surprisingly the
block ID for /dev/md127 and the original EXT4 /boot/efi matched. But this
is all after the crash that triggered the bug report.

The command used to create the RAID device would have used the same
parameters as

root@androidlx01:~# mdadm --create /dev/md0 --metadata=0.90 -l raid1 -f -n
1 /dev/sda1

mdadm: /dev/sda1 appears to be part of a raid array:

      level=raid0 devices=0 ctime=Wed Dec 31 19:00:00 1969

Continue creating array? y

mdadm: array /dev/md0 started.

root@androidlx01:~# cat /proc/mdstat

Personalities : [raid1]

md0 : active raid1 sda1[0]

     524224 blocks [1/1] [U]

unused devices: <none>

The existing RAID is

androidadmin@androidlx01:~$ sudo mdadm -D /dev/md127
/dev/md127:
        Version : 0.90
  Creation Time : Tue Oct 31 15:55:49 2017
     Raid Level : raid1
     Array Size : 524224 (512.02 MiB 536.81 MB)
  Used Dev Size : 524224 (512.02 MiB 536.81 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 127
    Persistence : Superblock is persistent

    Update Time : Fri Nov 10 15:33:49 2017
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : 498041b2:09e636ad:d8fca355:d4d345d0 (local to host
androidlx01)
         Events : 0.40

    Number Major Minor RaidDevice State
       0 8 1 0 active sync /dev/sda1
       1 8 17 1 active sync /dev/sdb1
androidadmin@androidlx01:~$

On Tue, Oct 17, 2017 at 8:36 AM, Phillip Susi <email address hidden> wrote:

> Can you post the output of mdadm -D /dev/md0?
>
>
> ** Changed in: grub-installer (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721317
>
> Title:
> graphical installer crashed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/
> +bug/1721317/+subscriptions
>

--
'03 BMW F650CS - hers
'98 Dakar K12RS - "BABY K" grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - "OUR LC"
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois

Revision history for this message
Phillip Susi (psusi) wrote :

Can you run sudo grub-probe /boot/efi?

Revision history for this message
HankB (hbarta) wrote :

I have handed this off to another user and no longer have access to it.

On Thu, Nov 30, 2017 at 12:24 PM, Phillip Susi <email address hidden> wrote:

> Can you run sudo grub-probe /boot/efi?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721317
>
> Title:
> graphical installer crashed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/
> +bug/1721317/+subscriptions
>

--
'03 BMW F650CS - hers
'98 Dakar K12RS - "BABY K" grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - "OUR LC"
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for grub-installer (Ubuntu) because there has been no activity for 60 days.]

Changed in grub-installer (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.