Re: [Bug 1309639] Re: grub confused by named md raid arrays

2015-05-08 Thread PMOverfield
t it carefully. > > @PMOverfield; what kind of system are you using? Are there only two > disks being mirrored, or are you using a different kind of setup? > > ** Changed in: grub2 (Ubuntu) > Status: Confirmed => Incomplete > > ** Changed in: grub2 (Ubuntu) >

[Bug 1309639] [NEW] Installer locks after failing to install GRUB onto RAID array

2014-04-18 Thread PMOverfield
Public bug reported: Am installing Trusty (AMD-64 Desktop), with /boot as a RAID-1 set (ext2fs) under mdadm on a GPT partition, with a separate, non-RAID, unformatted partition for BIOS-grub. At the stage of attempting to install GRUB it fails, reporting fatal error. I get the window offering the

[Bug 1309639] Re: Installer locks after failing to install GRUB onto RAID array

2014-04-19 Thread PMOverfield
Thank you, Philip. After the "AskUbuntu" editing mechanism de-formatted my response there I feared you might abandon this one in disgust at the garbage. I've attached "grubprobe.out" with the response you requested. I'm puzzled by the conflict beteen lines 116 and 392: md/root and /dev/md5 are the

[Bug 1309639] Re: grub confused by named md raid arrays

2014-04-21 Thread PMOverfield
Thank you for this insight, Philip. I know you didn't ask for it, but I've wiped the HDs (DBAN) and rebuilt the system from scratch, but OMITTING the "-N" option from mdadm, so that the RAID sets don't get the confusing optional names. Unfortunately GRUB still fails to install, producing exactly

[Bug 1309639] Re: grub confused by named md raid arrays

2014-04-21 Thread PMOverfield
As suspected, so here's the second attachment ** Attachment added: "Contents of /var/log/syslog" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1309639/+attachment/4090903/+files/noname.syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subsc

[Bug 1309639] Re: grub confused by named md raid arrays

2014-04-22 Thread PMOverfield
Yes, I do. FYI the setup is: GPT, 1st partition starts at sector 2048 1MiB NOT RAID, NOT formatted, BIOS-grub 200MiB RAID-1, ext2, /boot 2GiB RAID-1, swapfs 5GiB RAID-1, ext4, /var 5GiB RAID-1, ext4, /tmp 6GiB RAID-1, ext4, / 22GiB RAID-1, ext4, /usr >900GiB RAID-1, ext4, /home (remainder of

[Bug 1309639] Re: grub confused by named md raid arrays

2014-04-22 Thread PMOverfield
Philip, I apologise: I didn't do exactly what you asked. I chrooted to /target, then executed sudo grub-probe /boot. I've now found that if I stay at /, and execute grub-probe /target/boot, I get different output. So herewith target.boot.grub-probe.out to give you that information. Sorry! ** Attac

[Bug 1309639] Re: grub confused by named md raid arrays

2014-04-22 Thread PMOverfield
Well, the rig is still set up: feel free to ask for any further investigations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309639 Title: grub confused by named md raid arrays To manage notifica

[Bug 577678] Re: nm-applet does not show in indicator applet after reboot

2010-12-01 Thread PMOverfield
*** This bug is a duplicate of bug 589362 *** https://bugs.launchpad.net/bugs/589362 Got this problem when building RAID array on 10.04.1 No problem when creating and configuring the array with Live CD for AMD64: nm-applet present and correct, fully functioning. To install Linux have to s