out of the box install crashes. works fine on developer's machine. nice QA as usual.

Bug #1696184 reported by Andrey Lelikov
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
New
Undecided
Unassigned

Bug Description

hello,world

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CasperVersion: 1.376.2
Date: Tue Jun 6 10:15:26 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu-gnome.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
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
Andrey Lelikov (lagnchpad) wrote :
Revision history for this message
Phillip Susi (psusi) wrote :

Please run the following commands and post the output:

sudo mdadm -D /dev/md0
sudo grub-probe -vvv -d /dev/md0

Changed in grub-installer (Ubuntu):
status: New → Incomplete
Revision history for this message
Andrey Lelikov (lagnchpad) wrote :
Revision history for this message
Andrey Lelikov (lagnchpad) wrote :
Revision history for this message
Andrey Lelikov (lagnchpad) wrote :

this is likely not your bug. apparently ubiquity does not install mdadm into target install dir at all.

Changed in grub-installer (Ubuntu):
status: Incomplete → New
Revision history for this message
Andrey Lelikov (lagnchpad) wrote :

this is ubiquity not installing mdadm onto target

affects: grub-installer (Ubuntu) → ubiquity (Ubuntu)
Revision history for this message
Andrey Lelikov (lagnchpad) wrote :
Download full text (6.7 KiB)

confirmed. a true dup of #880766 from 2011. Today is 2017 and installing ubuntu on software raid is still unsupported scenario. this is ubuntu...

workaround:

1. install w/o the bootloader (undocumented switch!)
sudo ubiquity -b

2. chroot into target system, install mdadm, switch grub-pc to grub-efi, profit.

root@ubuntu-gnome:/root/tsta# mount /dev/mapper/root_crypt /tgt
root@ubuntu-gnome:/root/tsta# mount -o bind /dev /tgt/dev
root@ubuntu-gnome:/root/tsta# mount -o bind /dev/pts /tgt/dev/pts
root@ubuntu-gnome:/root/tsta# mount -o bind /sys /tgt/sys
root@ubuntu-gnome:/root/tsta# mount -o bind /proc /tgt/proc
root@ubuntu-gnome:/root/tsta# cat /etc/resolv.conf > /tgt/etc/resolv.conf
root@ubuntu-gnome:/root/tsta# mount /dev/md0 /tgt/boot
root@ubuntu-gnome:/root/tsta# chroot /tgt
root@ubuntu-gnome:/# mount /dev/sda1 /boot/efi

root@ubuntu-gnome:/# apt-get install mdadm
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  default-mta | mail-transport-agent
The following NEW packages will be installed:
  mdadm
0 upgraded, 1 newly installed, 0 to remove and 194 not upgraded.
Need to get 393 kB of archives.
After this operation, 1,203 kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 mdadm amd64 3.3-2ubuntu7.2 [393 kB]
Fetched 393 kB in 0s (778 kB/s)
Preconfiguring packages ...
Selecting previously unselected package mdadm.
(Reading database ... 188668 files and directories currently installed.)
Preparing to unpack .../mdadm_3.3-2ubuntu7.2_amd64.deb ...
Unpacking mdadm (3.3-2ubuntu7.2) ...
Processing triggers for systemd (229-4ubuntu16) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up mdadm (3.3-2ubuntu7.2) ...
Generating mdadm.conf... done.
update-initramfs: deferring update (trigger activated)
/usr/sbin/grub-mkconfig: 250: /usr/sbin/grub-mkconfig: cannot create /boot/grub/grub.cfg.new: Directory nonexistent
Running in chroot, ignoring request.
update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
Processing triggers for systemd (229-4ubuntu16) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
update-initramfs: Generating /boot/initrd.img-4.8.0-54-generic

root@ubuntu-gnome:/# grub-install /dev/sda
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for RAID and LVM install.

root@ubuntu-gnome:/# apt-get install grub-efi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  grub-common grub-efi-amd64 grub-efi-amd64-bin grub-pc-bin grub2-common
Suggested packages:
  multiboot-doc grub-emu xorriso desktop-base
The following packages will be REMOVED:
  grub-gfxpayload-lists grub-pc
The following NEW packages will be installed:
  grub-efi grub-efi-amd64 grub-efi-amd64-bin
The following packages will be upgr...

Read more...

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

Grub should not need mdadm for grub-probe to work. Whenever I install on raid, I never have the boot loader fail to install; just have to remember to chroot in after and install mdadm before rebooting or the installed system won't boot past the initramfs.

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

It looks like it is finding the array, but doesn't find anything inside it. What does blkid say is in /dev/md0?

Revision history for this message
Andrey Lelikov (lagnchpad) wrote :

root@lelikusa:~# blkid /dev/md0
/dev/md0: UUID="35233d76-cfd5-4608-a347-adc92b104f78" TYPE="ext2"
root@lelikusa:~# cat /proc/mounts | grep md0
/dev/md0 /boot ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 0

I'm pretty sure blkid was working on md0 from rescue disc.

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

Oh, I missed it in the log the first time; grub-probe did detect ext2 on /dev/md0. But that was on the installed system right? Can you run it from the livecd?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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