I'm not sure why but it seems that a number of people have piled onto
this bug report with unrelated issues. The original issue here was
simply that grub won't install to a raid without mdadm installed. Since
that isn't a bug, I'm closing this report.
** Changed in: grub-installer (Ubuntu)
I can confirm this bug for Ubuntu server 16.04.3 AMD64. The problem
seems to be related to the drive size or/and the interface. grub-install
fails with two 2 TB Samsung 960 Pro m2 SSDs. With Intel 180 GB SATA
SSDs, it works just fine. Mainboard: ASUS Prime X399-A
** Changed in: grub-installer (Ubu
[Expired for grub-installer (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
You might want to install grub to all of the drives in the server (
dpkg-reconfigure grub-pc ). That way if one fails and it boots from
another, it can boot too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Doh! In my case the issue was that I had replaced one of the disks on
the server. In the process the server had decided it was going to boot
from disk #3... Changed that and it all seems to have worked. Trying a
full RAID install now.
--
You received this bug notification because you are a member
Booted again off of fob - which a rescue boot had installed grub onto. I
had removed it the last time when it booted and I ran grub-install
/dev/sda. Will now try to run grub-install /dev/sdb.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I can report the exact same issue with a fresh 16.04 install.
I did manual partitioning, left the requisite 1MB+1MB free for grub and
it now boots to grub-rescue with a message about an unknown filesystem.
I booted into rescue mode and ran grub-install /dev/sda which annoyingly
installed on my usb
Wonder if the issue is installing off a usb drive. Is something confused
by device order?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315344
Title:
Grub install failed on disks with software RAID
Hi,
I wondered about this as there are docs about it and it is not like "everybody
complains".
Docs:
- https://help.ubuntu.com/lts/serverguide/advanced-installation.html
- https://help.ubuntu.com/community/Installation/SoftwareRAID
I tested that with a virtual guest for that I set up 3x20GB Disks
After so long time this bug is still present. I gave up with Ubuntu server
14.04 and in 16.04 I encountered the same bug. You can't install Ubuntu server
with RAID setup from installer.
After spending hours and tried to find what was the difference I made with
Gentoo setup that worked perfectly
Adding the grub probe output requested from other reporters.
** Attachment added: "more grub probe output"
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1315344/+attachment/4164163/+files/grub-probe.txt
--
You received this bug notification because you are a member of Ubuntu
In my case it also failed. I had a precreated series of /dev/md devices
I set up using gdisk.
/dev/md0 for swap, /dev/md1 for root (/), and /dev/md2 for home (/home).
The install died during the grub installation. Now, there is no longer
an Alternate Ubuntu CD with the Debian Installer (which, sa
so, I just hit this issue using a custom install script running from a
custom live CD, however I've managed to find where my issue was, just
somehow happened to end up finding this page.
The issue was when I ran the grub install command, it would fail with
the message that it can't find the md1 de
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub-installer (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315344
Titl
Yes, indeed - grub-probe -d /dev/md1 worked fine when running from my
previous 13.10 system as well as from the USB stick (Trusty 64bit desktop,
mdadm installed), but not after chroot to the /dev/md1 target.
I found that mdadm was not installed on /dev/md1, I installed it (and
Postfix) by hand, af
So sudo grub-probe -d /dev/md1 works ( prints "ext2 ) when run from the
live cd. Does it work if you run it after the chroot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315344
Title:
Grub insta
Thanks, did all that, but it doesn't resolve the problem:
> ...
> /# grub-install /dev/sda
Installing for i386-pc platform.
(after a few seconds wait)
grub-install: error: disk `md1' not found.
I looked at /target/boot/grub - no grub.cfg. /target/etc/default/grub
and /target/etc/grub.d/* all lo
Try this:
sudo -s
mount /dev/md1 /target
for f in proc sys dev dev/pts ; do mount --bind /$f /target/$f ; done
chroot /target
grub-install /dev/sda
I assumed here that /dev/md1 is your root partition; if it is not,
change it accordingly.
--
You received this bug notification because you are a m
Here is the output of the command (run under Ubuntu 13.10 booted from
/dev/md0):
$ sudo mdadm -D /dev/md1
/dev/md1:
Version : 1.2
Creation Time : Wed Nov 6 16:18:54 2013
Raid Level : raid1
Array Size : 19514240 (18.61 GiB 19.98 GB)
Used Dev Size : 19514240 (18.61 GiB 19
Thanks for your swift reply. The machine is in my office; it is
currently running Saucy, I can't reboot Trusty before Monday. Are these
commands run under Saucy (with its root on md0) useful?
Cheers,
Helge
Helge MEI
Can you post the output of sudo mdadm -D /dev/md1, and sudo grub-probe
-v -d /dev/md1?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315344
Title:
Grub install failed on disks with software RAID
T
21 matches
Mail list logo
