[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
This is still a problem in 12.04.1 Server AMD64. OS is installed on a single drive and the machine also contains 6 drives that I want to configure as RAID0. Installed and configured OS fine, installed mdadm and now can't boot. The 6 drives destined for the array are brand new so have never been part of a RAID array. The OS drive was previously part of a RAID array, but obviously was formatted during installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/158918 Title: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/158918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
You might want to use the original debian on your server instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/158918 Title: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/158918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
I run into the same exact issue described by Roy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/158918 Title: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/158918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
This bug has bugged me for a while now. It started in 10.10 and is still there in 11.04. Fresh install of Natty, 11.04 AMD64. All updates performed. - Reboot works fine. Install MDADM - reboot fails mount: mounting /dev/disk/by-uuid/ on /root failed: Device or resource busy ... ... No init found. Try passing init=bootarg. Remove MDADM (boot on live-CD) - reboot works fine System has 7 disks. /dev/sda as boot disk. /dev/sd[bcdefg] are used as raid members. Error occurs both when a raid is properly set up, and when all raid members have the superblock zeroed. Error occurs both when mdadm.conf is correct or blank, or missing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/158918 Title: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/158918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
Does affect me as well - here are the steps to reproduce: Fresh install of Ubuntu Desktop 10.10, performing all online updates - reboot works fine. Then install mdadm the system does not boot any more: mount: mounting /dev/disk/by-uuid/ on /root failed: Device or resource busy ... ... No init found. Try passing init=bootarg. See also: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/591696 -- [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup https://bugs.launchpad.net/bugs/158918 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
I had problems with the release version of Lucid Desktop on AMD64. A clean install is brought up to date and rebooted. The mdadm package is installed and rebooted. System becomes unbootable in the same manner. Disks had been previously used in nv-raids and maybe md-raid (cannot confirm). Single disk install with new partition table on disk. No raid arrays or partitions present anywere on system. System was rebooted immediately after installing mdadm. Tried to repeat this on a factory fresh disk, however it installs and reboots without problems. -- [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup https://bugs.launchpad.net/bugs/158918 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
** Description changed: Original Report (also confirmed with 9.10 and 10.04 beta1): On a freshly installed ubuntu-7.10-alternate, with latest apt-get update. When the 'mdadm' package is installed, the system fails to boot successfully, and ends up at the initrd '(busybox)' prompt. Hardware: DELL 1950 - 1RU Server HDD: SAS To get the server booting again you need to revert to the old initramfs: - Boot with ubuntu-7.10-alternate, and go through install steps up to 'partitioning'. - ALT-F2 to start other shell - 'fdisk -l' to see details of available drives. - mkdir /mnt/disk - mount -t ext3 /dev/sdb1 /mnt/disk - cd /mnt/disk/boot - mv initrd-version.img initrd-version.img-new - cp initrd-version.img.bak initrd-version.img - sync - reboot --- Diagnose: - This is mdadm setting up arrays according to unreliable superblock information (device minor numbers, labels, hostnames) combined with the idea of fixing the unreliability by limiting array assembly with information from mdadm.conf (PARTITIONS, ARRAY, HOMEHOST lines) which just reassigns the unsolvable conflict handling problem to setup tools, admins and installers. It forces them to create mdadm.conf files. And of course they fail. - In these cases the initramfs ends up with an ARRAY definition (that - really shouldn't need to be there) the system can not assemble at all or - in that state of booting. + In cases where old superblocks are found on the disks during mdadm + install, they are added to ARRAY definitions (that really shouldn't + need to be there at all) in mdadm.conf, and copied over into the + initramfs. During next boot the system can not assemble these + (incomplete) arrays. Cure: Systematically prevent conflicts from arising instead of relying on - mdadm.conf maintanance. - UUID-based array assembly as described in - comment #33 + mdadm.conf maintanance. - Do not depend on mdadm.conf definitions but + use UUID-based array assembly as described in comment #33 -- [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup https://bugs.launchpad.net/bugs/158918 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
Current mdadm versions support AUTO lines in mdadm.conf, that may supersede dynamic mdadm.conf rewriting. -- [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup https://bugs.launchpad.net/bugs/158918 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
** Description changed: - Binary package hint: mdadm + (also confirmed for 9.10 and 10.04) On a freshly installed ubuntu-7.10-alternate, with latest apt-get update. When the 'mdadm' package is installed, the system fails to boot successfully, and ends up at the initrd '(busybox)' prompt. Hardware: DELL 1950 - 1RU Server HDD: SAS - To get server booting again: + To get server booting again you need to restore the old initramfs: - Boot with ubuntu-7.10-alternate, and go through install steps up to 'partitioning'. - ALT-F2 to start other shell - 'fdisk -l' to see details of available drives. - mkdir /mnt/disk - mount -t ext3 /dev/sdb1 /mnt/disk - cd /mnt/disk/boot - mv initrd-version.img initrd-version.img-new - cp initrd-version.img.bak initrd-version.img - sync - reboot --- Diagnose: - This is mdadm setting up arrays according to unreliable superblock information (device minor numbers, labels, hostnames) combined with the idea of fixing the unreliability by limiting array assembly with information from mdadm.conf (PARTITIONS, ARRAY, HOMEHOST lines) which just reassigns the unsolvable conflict handling problem to setup tools, admins and installers that have to creating the mdadm.conf files. And of course they fail. + In this case the initramfs ends up containing invalid ARRAY definitions + that disturbs the boot. + + Cure: Systematically preventing conflicts from arising instead of relying on mdadm.conf maintanance. - comment #33 ** Description changed: (also confirmed for 9.10 and 10.04) On a freshly installed ubuntu-7.10-alternate, with latest apt-get update. When the 'mdadm' package is installed, the system fails to boot successfully, and ends up at the initrd '(busybox)' prompt. Hardware: DELL 1950 - 1RU Server HDD: SAS To get server booting again you need to restore the old initramfs: - Boot with ubuntu-7.10-alternate, and go through install steps up to 'partitioning'. - ALT-F2 to start other shell - 'fdisk -l' to see details of available drives. - mkdir /mnt/disk - mount -t ext3 /dev/sdb1 /mnt/disk - cd /mnt/disk/boot - mv initrd-version.img initrd-version.img-new - cp initrd-version.img.bak initrd-version.img - sync - reboot --- Diagnose: - This is mdadm setting up arrays according to unreliable superblock information (device minor numbers, labels, hostnames) combined with the idea of fixing the unreliability by limiting array assembly with information from mdadm.conf (PARTITIONS, ARRAY, HOMEHOST lines) which just reassigns the unsolvable conflict handling problem to setup tools, admins and installers that have to creating the mdadm.conf files. And of course they fail. In this case the initramfs ends up containing invalid ARRAY definitions that disturbs the boot. - Cure: - Systematically preventing conflicts from arising instead of relying on - mdadm.conf maintanance. - comment #33 + Systematically prevent any conflicts from arising instead of relying on + mdadm.conf maintanance. - UUID-based raid assembly described in comment + #33 -- [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup https://bugs.launchpad.net/bugs/158918 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
** Description changed: - (also confirmed for 9.10 and 10.04) + Original Report (also confirmed with 9.10 and 10.04 beta1): On a freshly installed ubuntu-7.10-alternate, with latest apt-get update. When the 'mdadm' package is installed, the system fails to boot successfully, and ends up at the initrd '(busybox)' prompt. Hardware: DELL 1950 - 1RU Server HDD: SAS - To get server booting again you need to restore the old initramfs: + To get the server booting again you need to revert to the old initramfs: + - Boot with ubuntu-7.10-alternate, and go through install steps up to 'partitioning'. - ALT-F2 to start other shell - 'fdisk -l' to see details of available drives. - mkdir /mnt/disk - mount -t ext3 /dev/sdb1 /mnt/disk - cd /mnt/disk/boot - mv initrd-version.img initrd-version.img-new - cp initrd-version.img.bak initrd-version.img - sync - reboot --- Diagnose: - This is mdadm setting up arrays according to unreliable superblock information (device minor numbers, labels, hostnames) combined with the idea of fixing the unreliability by limiting array assembly with information from mdadm.conf (PARTITIONS, ARRAY, HOMEHOST lines) which just reassigns the unsolvable conflict handling problem to setup tools, - admins and installers that have to creating the mdadm.conf files. And of + admins and installers. It forces them to create mdadm.conf files. And of course they fail. - In this case the initramfs ends up containing invalid ARRAY definitions - that disturbs the boot. + In this case the initramfs ends up with invalid ARRAY definitions that + stop the system from booting. Cure: - Systematically prevent any conflicts from arising instead of relying on - mdadm.conf maintanance. - UUID-based raid assembly described in comment - #33 + Systematically prevent conflicts from arising instead of relying on + mdadm.conf maintanance. - UUID-based array assembly as described in + comment #33 -- [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup https://bugs.launchpad.net/bugs/158918 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
** Description changed: Original Report (also confirmed with 9.10 and 10.04 beta1): On a freshly installed ubuntu-7.10-alternate, with latest apt-get update. When the 'mdadm' package is installed, the system fails to boot successfully, and ends up at the initrd '(busybox)' prompt. Hardware: DELL 1950 - 1RU Server HDD: SAS To get the server booting again you need to revert to the old initramfs: - Boot with ubuntu-7.10-alternate, and go through install steps up to 'partitioning'. - ALT-F2 to start other shell - 'fdisk -l' to see details of available drives. - mkdir /mnt/disk - mount -t ext3 /dev/sdb1 /mnt/disk - cd /mnt/disk/boot - mv initrd-version.img initrd-version.img-new - cp initrd-version.img.bak initrd-version.img - sync - reboot --- Diagnose: - This is mdadm setting up arrays according to unreliable superblock information (device minor numbers, labels, hostnames) combined with the idea of fixing the unreliability by limiting array assembly with information from mdadm.conf (PARTITIONS, ARRAY, HOMEHOST lines) which just reassigns the unsolvable conflict handling problem to setup tools, admins and installers. It forces them to create mdadm.conf files. And of course they fail. - In this case the initramfs ends up with invalid ARRAY definitions that - stop the system from booting. + In these cases the initramfs ends up with an ARRAY definition (that + really shouldn't need to be there) the system can not assemble at all or + in that state of booting. Cure: Systematically prevent conflicts from arising instead of relying on mdadm.conf maintanance. - UUID-based array assembly as described in comment #33 -- [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup https://bugs.launchpad.net/bugs/158918 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
A note for /etc/mdadm/mdadm.conf: # ARRAY definitions you make here will be honored only when executing mdadm manually. # The mdadm calls executed on udev events do use this file replacing all lines containing ARRAY. -- [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup https://bugs.launchpad.net/bugs/158918 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158918] Re: [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup
** Summary changed: - Installing mdadm (or outdated mdadm.conf) breaks bootup + [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup -- [-UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup https://bugs.launchpad.net/bugs/158918 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.ubuntu.com/mailman/listinfo/ubuntu-bugs
