[Bug 1655836] [NEW] Ubuntu 17.04 installation with "Guided - use entire disk and set up LVM" fails

Launchpad Bug Tracker 1655836 at bugs.launchpad.net
Thu Jan 12 06:19:36 UTC 2017


You have been subscribed to a public bug:

---Problem Description---
Ubuntu 17.04 Guided - use entire disk and set up LVM  and Guided - use entire disk and set up encrypted LVM does not create separate partition for /boot and so fails to complete the installation.


Comment 3
Looking into the logs ,this error will come if someone is using some external media (ex :USB stick ).Suppose it is /dev/sda and our hard disk is /dev/sdb .. then installation should occur on /dev/sdb, but it is trying to install on /dev/sda.. so workaround is to remove external media and continue. 

But, here they are doing virtual dvd install on LPAR.


Comment 6

System drops to (initramfs) prompt after following errors:

Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
done.
Begin: Running /scripts/local-block ... mdadm: No arrays found in config file or automatically
mdadm: error opening /dev/md?*: No such file or directory
mdadm: No arrays found in config file or automatically
done.
done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  UUID=4209e2c0-aa8e-4d53-b572-382e5d3a88de does not exist.  Dropping to a shell!


BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) 
 
(initramfs) ls -l /dev/[hs]d*
ls: /dev/[hs]d*: No such file or directory

(initramfs) cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-4.9.0-11-generic root=UUID=4209e2c0-aa8e-4d53-b572-382e5d3a88de ro

(initramfs) cat /proc/modules
(initramfs) 


Can you try to recreate this problem with today's daily build. 

Comment 7 
(In reply to comment #6)

I was able to recreate this problem with today's build as well.

** Affects: grub-installer (Ubuntu)
     Importance: Undecided
     Assignee: Taco Screen team (taco-screen-team)
         Status: New


** Tags: architecture-ppc64le bugnameltc-150138 severity-high targetmilestone-inin1704
-- 
Ubuntu 17.04  installation with "Guided - use entire disk and set up LVM" fails
https://bugs.launchpad.net/bugs/1655836
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to grub-installer in Ubuntu.



More information about the foundations-bugs mailing list