[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (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.net/bugs/1309639
Wow! This is going back somewhat. My recollection is as follows:
Home-built PC:
PROBABLY based on Asus M4A89TD PRO MoBo, with 8GB Kingston RAM,
nVidia Graphics with Quadro NVS285 GPU, AMD Phenom II X4 960T CPU, and
TWO-off Western Digital 1TB HDDs in RAID-1 configuration for most of the
I think for this we should simply figure out a way to reproduce this
issue in the smallest; more reduced way possible in virtual machines,
and test 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?
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (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/1309639
Title:
grub
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
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!
**
Odd, everything seems fine there.
--
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 notifications about this bug go to:
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
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
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
Looks like a different problem now. Do you have a /boot partition?
What does grub-probe /target/boot show?
--
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
11 matches
Mail list logo
