This bug still exist in 18.04... Ubuntu installer always fails at the
end when installing on RAID (in my case, RAID 1 and UEFI) and have to
manually reinstall GRUB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
I see the same bug on lucid 10.04.3 LTS
Because I install system using FAI system , I just changed the default
settings in /etc/mdadm/mdadm.conf , so mdadm uses metadata version 1.0
after that grub installs correctly and I can boot from the raid1 device
metadata 0.9 also works .
but with me
I opened bug 701351 to track the nearly-identical problem, as it occurs
for mdraid version(s) 1.0, 1.1 and 1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527401
Title:
grub-installer fails to ins
Oh, btw, I'm running mdraid version 1.0, not 0.9 and according to
comment #9 above, this may be the reason I've got a problem. Am opening
a new bug, to report this, as the above history is a bit long and
confusing ...
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm hitting this bug, as described in comment #43 and comment 51
Running Lucid, on 64-bit,
grub-probe -t fs /boot
grub-probe: error: no mapping exists for `md1'.
grub-install --recheck --modules="mdraid raid" /dev/md1
/usr/sbin/grub-probe: error: no mapping exists for `md1'.
/usr/sbin/grub-probe
Hi, I'm trying to install 10.04.1 64 bit, and this bug is still open.
Any plans to fix it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527401
Title:
grub-installer fails to install on a raid1 arra
I think you should file a new bug and attach full installation logs
(/var/log/syslog and /var/log/partman; use "save debug logs" from the
main menu to extract them, or they're saved in /var/log/installer/syslog
and /var/log/installer/partman on the installed system). Your problem
may not have the
I am still experiencing this bug. I tried to install Ubuntu 10.04 server
on three discs sda, sdb, sdc. They were all partitioned into two primary
partition, 2GB and "rest". I run a boot partition raid1 on the 2GB and a
raid5->encrypted-. >logical volumes on the "rest"-parts.
Everything goes smooth
So fine, bug fixed! I'm using the last LTS and it works well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/527401
Title:
grub-installer fails to install on a raid1 array
--
ubuntu-bugs mailing li
(My install is 10.04)
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
I've got this same problem, it seems.
I originally installed to /dev/sda. I later added 2 new disks. I
manually (with the Ubuntu GUI, anyway) made a RAID1 of them, and have
copied everything over to them.
Trying to install grub yields:
r...@thdesktop:/# grub-install --modules="mdraid raid" /d
Oh, I see Colin's worked on it (http://www.listware.net/201007/grub-
devel/64403-patch-mdadm-1x-metadata-support.html). Now to see if there's
an accessible way to build/install and use.
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bu
I'm seeing this bug in an install of 10.04.1, although this may be
related to my creating the RAID 1 array before hand, since with the
WD20EARS drives otherwise the cylinder alignment isn't right - or at
least I can't see how to make it so.
Is there a work-around? Or do I have to entirely reinstal
** Changed in: grub2 (Ubuntu Lucid)
Assignee: Colin Watson (cjwatson) => (unassigned)
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
The installer fails if there are already superblocks on your disks.
They get set (partly) assembled and the installer is not capable of
showing or handling these.
Try writing zeros to your disk or mdadm --stop and --zero-superblock
from another console.
--
grub-installer fails to install on a r
The partman in the server installer from the daily distribution
20100419.1 is even more erroneous.
I decided to simplify matters by installing a small extra IDE/ATA disk for the
system
keeping the 3 x 2TB SATA disks for manual configuration (as soon as partman is
raid
ignorant and buggy).
The i
I'm sorry, but I can't handle further comments in this bug; it is much
too difficult to keep track. Could you please file a new bug report, as
I requested in comment 34?
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification
The server still does not reboot, saying a few times:
init: unreadahed-other main process (number) terminated with status 4
and freezing
Faulty everywhere...
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because yo
Another ugly thing: fdisk -l complains "/dev/mdX does not contain a
valid partition table" (see the attachment) about partitions created by
partman. The system is nevertheless operational.
** Attachment added: "fdisk -l output"
http://launchpadlibrarian.net/44699156/err-1.txt
--
grub-installe
Once again, the simple recipe in message #30 above allowed me to boot an
unbootable system (forgotten grub-install error?)
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which i
syslog attachment to the previous message (this system cannot even take
>1 attachments ;-)
** Attachment added: "syslog"
http://launchpadlibrarian.net/44694787/syslog
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification
I repeated the installation experiment twice, this time with 3 SATA disks on
AHCI (yesterday
they were on IDE):
1. with 10.04-beta2-server-amd64
2. with the daily server-amd64 (18/4/2010)
getting basically the same results for /boot on raid1.
After 1) the system booted once but stopped booting
One of the issues ("too large" 2.7gb raid the installer refuses to
create) is related to/same as
https://bugs.launchpad.net/bugs/543838
I stupidly made a remote update (kernel included) with reboot, and the system
did not come up.
Apparently, kernel updates modify MBR. Now I am locked from my
Sergei, could you please file a new bug about this (just in case it's
different from the original, which it might well be - it's easier to
mark it as a duplicate later than to try to split it up) and attach the
'syslog' and 'partman' installer logs - you can extract them using "Save
debug logs" fro
I did it manually, using ext4, first on raid1 (2 active + 1 spare), which
failed to boot, after
several attempts. Rescue would not help.
Then I destructed raid1 and manually (see above) grub-installed on /sda1,
/sdb1, sdc1.
Doing the same with raid1 does not worth the time to load a bunch of mo
Just to re-iterate, I succesfully installed ubuntu 10.04 lts beta2 to a
RAID1 config without any problems after the initial bug identified here
was fixed. The grub installer also seemed to install copies of itself to
both drives which is a plus (I've been manually doing that in the past).
Keep
Filesystems used?
Are you doing it by hand or preseeding?
I just use the generic recipe from the README contained in the
partman-auto-raid and it works (as I described earlier, it bombed once
afterwards but was fine after that).
--
grub-installer fails to install on a raid1 array
https://bugs.lau
1. Ubuntu 10.04 beta2 x64 server (installed from CD) would not boot from raid1;
see above.
2. It would not boot even if you destruct your RAID1 (into 3 pieces in my case)
and ask it to install on a simple non-raid ext4 partitions that result.
Workaround:
a) boot from any LiveCD, or rescue CD
b
moreover, the "Rescue/repair" option on the server disk is buggy.
1. Asks the name of the system
2. Asks to select a timezone from a mile-long list
3. Suggests to select a root filesystem, with no apparent effect
4. When you pick up "install grub" it leads you through the whole disk
partitioning
buggy as hell: after installation finished OK (with grub installed to
mbr of /sda, /sdb), the system cannot boot:
Grub loading stage 1.5
Grub loading, please wait...
Error 17
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notifi
Another nasty feature:
it keeps creating "unusable" spaces after every raid /md*, between 100-200KB,
not a big deal, but nevertheless...
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubunt
Another error :-(
In the end of the partitioning it says
ERROR!!!
partition length 5655133440 exceeds the loop-partition-table
imposed maximum of 4294967295
which is strange. The 3 disks I have are just 2TB each, and I am just
trying to create a RAID 0 of three 967GB partitions /sd{a,b,c}8 on
Looks like I found a remedy (which may also indicate where the error
is):
1. Create RAIDs one at a time, finish after each one.
2. It says "Starting the partitioner" (apparently it writes and rereads tables)
3. Select "Configure SW RAID", etc.
Takes more time (each "Starting ..." takes a minute)
Confirmed: I retried it erasing all the partitions of the previous installation
and recreated
all the partitions from scratch, all of the same size and primary:
/sda1 /sda2 ...
/sdb1 /sdb2 ...
/sdc1 /sdc2 ...
with the intention to build raids1 on /md0 (/sda1, /sdb1, /sdc1 - spare) and
/md1 (/s
Still (in server x64 beta2) partitioning & raid building do not work correctly
during installation.
I had 3 identical HDs, with identical /sda1 /sdb1 /sdc1 of 100MB each in the
beginning of the corresp. disk. Trying to build RAID1 with 2 active mirrors
/sda1 and /sdb1
and spare /sdc1, the partiti
@Mark Foster.
What happens if you reboot the server a few times. Does it always work,
or do you sometimes get the busybox? (i'm asking because this might be a
separate bug.)
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notificat
Installed Lucid 10.04 beta 2 from Alternate CD. I was able to mirror
(RAID 1) /boot on 2 TB drives via the installer. I noticed a quick grub
install message flash on the screen to show that grub was being
installed to both /dev/sda and /dev/sdb.
System appears to boot normally.
--
grub-install
I just installed Lucid Beta2 Server with separated Raid1 for /boot. Grub
has been installed on both hard disks.
While creating the md devices, the newly added superblocks are available
as free raid devices. To avoid faulty configurations please hide them.
--
grub-installer fails to install on a
Addendum to my last comment... after rebooting from busybox the system
did come up. So it looks as though the grub-install problem is fixed
here.
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member
Following up on comments in 532729
Tried this (again) on Lucid Beta2 and it gets much further - the grub-install
step does not FAIL like it had before.
However on subsequent boot of the machine it brings up a busybox prompt
as shown in the attachment
** Attachment added: "20100409a.png"
http
Scratch my earlier comment. I've seen so many strange things this week
during installation procedures, that my conclusion is not at all
reliable.
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member
I can confirm that the updates work.
I have installed a RAID1 system up to the point that GRUB errors out.
Then I executed a shell, chrooted to the target system and updated the packages
(including grub).
After the updates were installed, I exited back to the installer, installed the
Grub bootlo
I've reverted the incorrect duplication; see my comment in bug 549258.
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
The error messages I get are not the same and apparently, it's before it
even starts copying any files!
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Objection. Not the exact bug! My problem is before I even get to the
GRUB installation stage!
It's the partitioning.
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
That could be what I fixed, or could be something else. Please try
10.04 LTS Beta 2 when it's released, and if it still fails then please
file a new bug report.
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because y
I have a server Raid1 with 2 Seagate Hard disks, I installed Karmic on
them, stable release, it didn't finish installation because it says grub
won't install, is this fixed now on 10.04 LTS? Should I install now when
it's released? I'm still using Jaunty on my server.
--
grub-installer fails to i
This bug was fixed in the package partman-base - 139ubuntu2
---
partman-base (139ubuntu2) lucid; urgency=low
* Always leave a small gap at the end of the disk (except on device-mapper
devices), to avoid confusing mdadm by leaving the MD 0.90 superblock at
the end of the disk
The problem with mdadm in the initramfs was as follows:
The MD 0.90 metadata format operates by putting a superblock at the
*end* of the physical volume. (This is arguably a little silly and the
1.x formats work differently, but GRUB doesn't support them yet so
they're not an option.) This means
Wow - great work!
Verified that grub now installs on RAID1 system without errors.
Have not yet verified that it boots correctly as I'm running into some
graphics issues at boot-time but I suspect this is unrelated.
Thanks,
-stephen
--
Stephen Mulcahy Atlantic Linux http://www.atl
** Changed in: mdadm (Ubuntu Lucid)
Assignee: (unassigned) => Colin Watson (cjwatson)
** Changed in: mdadm (Ubuntu Lucid)
Importance: Undecided => High
** Changed in: mdadm (Ubuntu Lucid)
Milestone: None => ubuntu-10.04-beta-2
--
grub-installer fails to install on a raid1 array
http
** Branch linked: lp:ubuntu/grub2
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
This bug was fixed in the package grub2 - 1.98-1ubuntu2
---
grub2 (1.98-1ubuntu2) lucid; urgency=low
* Fix LVM/RAID probing in the absence of /boot/grub/device.map
(LP: #525085, #527401).
* Backport my upstream patch to copy .mo files from /usr/share/locale to
match where
** Branch linked: lp:~ubuntu-core-dev/ubuntu/lucid/grub2/lucid
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
I found that after I'd fixed this the initramfs failed to load md
modules reliably before trying to bring up the array. I'm creating a
bug task for this, and will have a look after I've uploaded the grub2
fix (at which point it will be easier to debug this sort of thing).
** Also affects: mdadm (
Yes, it is the very top thing on my list and it will be fixed.
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Just ran into this this morning when test installing a server with beta1
- would be very nice to have this fixed for this release
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: grub2 (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Lucid)
Status: New => Triaged
** Changed in: grub2 (Ubuntu Lucid)
Importance: Undecided => High
** Changed in: grub2 (Ubuntu Lucid)
Milestone: None => ubuntu-10.04-beta-2
** Package changed: grub-installer (Ubuntu) => grub2 (Ubuntu)
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
** Tags added: iso-testing
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
** Attachment added: "installation preseed file"
http://launchpadlibrarian.net/39747248/raid5.preseed
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Attachment added: "syslog.gz"
http://launchpadlibrarian.net/39747219/syslog.gz
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Attachment added: "Partman log of the installation"
http://launchpadlibrarian.net/39747241/partman.gz
--
grub-installer fails to install on a raid1 array
https://bugs.launchpad.net/bugs/527401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
63 matches
Mail list logo
