[Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
I can confirm this bug for Oneric. I've added a new 6th disk to md raid5 (grew it), several days later I've uprgaded the kernel (apt-get dist- upgrade), system was not rebooted between these two events. When grub was configured for a new kernel numerous error: found two disks with the index 5 for RAID md1. messages were diplayed (full /var/apt/term.log below). System functions properly after the reboot. root@server:/var/log/apt# cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10] md1 : active raid5 sdg1[1] sdf1[4] sde1[2] sdc1[0] sdd1[3] sda1[5] 9767559680 blocks level 5, 64k chunk, algorithm 2 [6/6] [UU] sda is the new disk. unused devices: none root@server:/var/log/apt# uname -a Linux server 3.0.0-24-generic-pae #40-Ubuntu SMP Tue Jul 24 15:55:26 UTC 2012 i686 athlon i386 GNU/Linux Log started: 2012-08-11 10:25:15 Selecting previously deselected package linux-image-3.0.0-24-generic-pae. (Reading database ... 252585 files and directories currently installed.) Unpacking linux-image-3.0.0-24-generic-pae (from .../linux-image-3.0.0-24-generic-pae_3.0.0-24.40_i386.deb) ... Done. Preparing to replace linux-generic-pae 3.0.0.23.27 (using .../linux-generic-pae_3.0.0.24.28_i386.deb) ... Unpacking replacement linux-generic-pae ... Preparing to replace linux-image-generic-pae 3.0.0.23.27 (using .../linux-image-generic-pae_3.0.0.24.28_i386.deb) ... Unpacking replacement linux-image-generic-pae ... Selecting previously deselected package linux-headers-3.0.0-24. Unpacking linux-headers-3.0.0-24 (from .../linux-headers-3.0.0-24_3.0.0-24.40_all.deb) ... Selecting previously deselected package linux-headers-3.0.0-24-generic-pae. Unpacking linux-headers-3.0.0-24-generic-pae (from .../linux-headers-3.0.0-24-generic-pae_3.0.0-24.40_i386.deb) ... Preparing to replace linux-headers-generic-pae 3.0.0.23.27 (using .../linux-headers-generic-pae_3.0.0.24.28_i386.deb) ... Unpacking replacement linux-headers-generic-pae ... Setting up linux-image-3.0.0-24-generic-pae (3.0.0-24.40) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/dkms 3.0.0-24-generic-pae /boot/vmlinuz-3.0.0-24-generic-pae run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.0.0-24-generic-pae /boot/vmlinuz-3.0.0-24-generic-pae update-initramfs: Generating /boot/initrd.img-3.0.0-24-generic-pae run-parts: executing /etc/kernel/postinst.d/pm-utils 3.0.0-24-generic-pae /boot/vmlinuz-3.0.0-24-generic-pae run-parts: executing /etc/kernel/postinst.d/update-notifier 3.0.0-24-generic-pae /boot/vmlinuz-3.0.0-24-generic-pae run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.0.0-24-generic-pae /boot/vmlinuz-3.0.0-24-generic-pae error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. Generating grub.cfg ... error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. Found linux image: /boot/vmlinuz-3.0.0-24-generic-pae Found initrd image: /boot/initrd.img-3.0.0-24-generic-pae error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. Found linux image: /boot/vmlinuz-3.0.0-23-generic-pae Found initrd image: /boot/initrd.img-3.0.0-23-generic-pae Found linux image: /boot/vmlinuz-3.0.0-22-generic-pae Found initrd image: /boot/initrd.img-3.0.0-22-generic-pae Found linux image: /boot/vmlinuz-3.0.0-21-generic-pae Found initrd image: /boot/initrd.img-3.0.0-21-generic-pae Found linux image: /boot/vmlinuz-2.6.38-11-generic-pae Found initrd image: /boot/initrd.img-2.6.38-11-generic-pae error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. error: found two disks with the index 5 for RAID md1. Found memtest86+ image: /memtest86+.bin done Setting up linux-image-generic-pae (3.0.0.24.28) ... Setting up linux-generic-pae (3.0.0.24.28) ... Setting up linux-headers-3.0.0-24 (3.0.0-24.40) ... Setting up linux-headers-3.0.0-24-generic-pae (3.0.0-24.40) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.0.0-24-generic-pae
Re: [Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
On 5/26/2011 5:24 PM, Jim Moseby wrote: I assume a fresh install of Natty on this server would result in a unbootable brick, everything else being equal. Or would a fresh install also fix the metadata? Yes, a totally fresh install ( and building a new raid array ) of Natty should work since the default metadata format is now 1.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776422 Title: [Natty] Grub no longer recognizes raid5 array -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
I have an ubuntu server that was nagging me to do a dist upgrade, and so I did. When I saw the error: Found two disks with the index 0 for RAID md0 I started searching and found this bug. I am now unsure how to proceed. - Is there any word on a resolution for this problem? - If my server restarts will it be unable to boot? - Is there any interim workaround? - Will reverting back to an older version of grub resolve this until a solution is found? Thanks. -Jim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776422 Title: [Natty] Grub no longer recognizes raid5 array -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
** Changed in: grub2 (Ubuntu) Status: Opinion = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776422 Title: [Natty] Grub no longer recognizes raid5 array -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
As I said before, the bug is in the bios reporting the size of the disk wrongly. Possible workarounds include reverting to the older version of grub, or upgrading the array to use a 1.x format metadata. Out of curiosity, what motherboard/bios is this? ** Changed in: grub2 (Ubuntu) Status: Confirmed = Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776422 Title: [Natty] Grub no longer recognizes raid5 array -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
This is an old HP Netserver E60. It has an Adaptec scsi controller in it. Its only job is as an httpd server, so nothing more powerful or modern is necessary. I don't want to reboot it at the moment or I'd tell you bios version, etc. I assume a fresh install of Natty on this server would result in a unbootable brick, everything else being equal. Or would a fresh install also fix the metadata? Do you think a bios flash would help, assuming it's not already the latest version? Failing that, I'm going to try to revert from Grub2 back to legacy grub, and see what happens. Worst case I'll just have to restore a backup image and ignore the Natty nags. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776422 Title: [Natty] Grub no longer recognizes raid5 array -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
It turns out that this is the result of several bugs, the first of which is a buggy bios that reports the size of the disk wrong, combined with mdadm superblock format 0.9 not containing enough information to tell if it belongs to the whole disk or the partition when the partition ends at the end of the disk. In the Maverick version of grub, it detects the superblock on the whole disk, and then again on the partition where it superceeds the disk. Grub was apparently intentionally changed to print an error and reject the partition superblock ( when it has already been found at the end of the whole disk ). The solution is to either use 1.x format superblocks ( 1.2 is now the default ) which do have enough information to not be ambiguous, or to leave some unpartitioned space at the end of the disk, which the Ubuntu installer does, but my buggy bios hid. ** Changed in: grub2 (Ubuntu) Status: Triaged = Invalid ** Changed in: grub2 (Ubuntu) Status: Invalid = Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776422 Title: [Natty] Grub no longer recognizes raid5 array -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
Something has gone wrong with the disk size detection. Grub thinks the size of the disk is 488396800 sectors instead of the 488397168 that fdisk reports. This shorter size causes the partition to appear to run right up to the end of the disk and thus, the raid superblock is found both at the end of the disk and the end of the partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776422 Title: [Natty] Grub no longer recognizes raid5 array -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
Also I tried reinstalling grub from the livecd to no avail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776422 Title: [Natty] Grub no longer recognizes raid5 array -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776422] Re: [Natty] Grub no longer recognizes raid5 array
After enabling raid debug messages and booting from a rescue cd, I can see the raid.c:699 scanning for RAID devices message, then the raid.c:639 Found array... messages for hd0, then the scanning repeats for hd0,msdos1 followed by the error: Found two disks... So it looks like it is recognizing the raid superblocks on both the whole disk, and the partition. There are 369 sectors between the end of the partition and the end of the disk, so it should not be finding the superblocks on (hdX). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776422 Title: [Natty] Grub no longer recognizes raid5 array -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
