| 2007-10-31 04:12:33 |
PaulSchulz |
bug |
|
|
added bug |
| 2007-10-31 04:32:27 |
PaulSchulz |
bug |
|
|
added attachment 'initrd.diff' (Difference in initrd's after installation.) |
| 2009-10-14 19:40:05 |
xteejx |
mdadm (Ubuntu): status |
New |
Invalid |
|
| 2010-01-29 20:37:51 |
xteejx |
mdadm (Ubuntu): status |
Invalid |
Incomplete |
|
| 2010-02-03 03:27:36 |
Craig Rae |
attachment added |
|
BootDmesg.txt http://launchpadlibrarian.net/38688403/BootDmesg.txt |
|
| 2010-02-03 03:27:39 |
Craig Rae |
attachment added |
|
CurrentDmesg.txt http://launchpadlibrarian.net/38688405/CurrentDmesg.txt |
|
| 2010-02-03 03:27:41 |
Craig Rae |
attachment added |
|
Dependencies.txt http://launchpadlibrarian.net/38688407/Dependencies.txt |
|
| 2010-02-03 03:27:43 |
Craig Rae |
attachment added |
|
Lspci.txt http://launchpadlibrarian.net/38688419/Lspci.txt |
|
| 2010-02-03 03:27:45 |
Craig Rae |
attachment added |
|
Lsusb.txt http://launchpadlibrarian.net/38688435/Lsusb.txt |
|
| 2010-02-03 03:27:48 |
Craig Rae |
attachment added |
|
MDadmExamine.dev.sda.txt http://launchpadlibrarian.net/38688437/MDadmExamine.dev.sda.txt |
|
| 2010-02-03 03:27:51 |
Craig Rae |
attachment added |
|
MDadmExamine.dev.sda2.txt http://launchpadlibrarian.net/38688439/MDadmExamine.dev.sda2.txt |
|
| 2010-02-03 03:27:53 |
Craig Rae |
attachment added |
|
MDadmExamine.dev.sdb.txt http://launchpadlibrarian.net/38688440/MDadmExamine.dev.sdb.txt |
|
| 2010-02-03 03:27:55 |
Craig Rae |
attachment added |
|
MDadmExamine.dev.sdb2.txt http://launchpadlibrarian.net/38688441/MDadmExamine.dev.sdb2.txt |
|
| 2010-02-03 03:27:57 |
Craig Rae |
attachment added |
|
ProcCpuinfo.txt http://launchpadlibrarian.net/38688444/ProcCpuinfo.txt |
|
| 2010-02-03 03:28:01 |
Craig Rae |
attachment added |
|
ProcInterrupts.txt http://launchpadlibrarian.net/38688446/ProcInterrupts.txt |
|
| 2010-02-03 03:28:04 |
Craig Rae |
attachment added |
|
ProcModules.txt http://launchpadlibrarian.net/38688447/ProcModules.txt |
|
| 2010-02-03 03:28:07 |
Craig Rae |
attachment added |
|
ProcMounts.txt http://launchpadlibrarian.net/38688448/ProcMounts.txt |
|
| 2010-02-03 03:28:11 |
Craig Rae |
attachment added |
|
ProcPartitions.txt http://launchpadlibrarian.net/38688450/ProcPartitions.txt |
|
| 2010-02-03 03:28:14 |
Craig Rae |
attachment added |
|
UdevDb.txt http://launchpadlibrarian.net/38688451/UdevDb.txt |
|
| 2010-02-03 03:28:18 |
Craig Rae |
attachment added |
|
UdevLog.txt http://launchpadlibrarian.net/38688453/UdevLog.txt |
|
| 2010-02-03 03:28:22 |
Craig Rae |
attachment added |
|
mdadm.conf.txt http://launchpadlibrarian.net/38688458/mdadm.conf.txt |
|
| 2010-02-03 03:28:25 |
Craig Rae |
mdadm (Ubuntu): status |
Incomplete |
New |
|
| 2010-02-03 03:28:29 |
Craig Rae |
tags |
|
apport-collected |
|
| 2010-02-03 14:49:50 |
xteejx |
mdadm (Ubuntu): importance |
Undecided |
High |
|
| 2010-02-03 14:49:50 |
xteejx |
mdadm (Ubuntu): status |
New |
Triaged |
|
| 2010-03-28 15:20:14 |
ceg |
summary |
Installing mdadm package breaks bootup. |
Installing mdadm package breaks bootup (with old superblocks around). |
|
| 2010-03-28 19:53:23 |
ceg |
summary |
Installing mdadm package breaks bootup (with old superblocks around). |
Installing mdadm or outdated mdadm.conf breaks bootup |
|
| 2010-03-28 20:09:06 |
ceg |
description |
Binary package hint: mdadm
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:
- 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 |
Binary package hint: mdadm
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:
- 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.
Cure:
Systematically preventing conflicts from arising instead of relying on mdadm.conf maintanance. -> comment #33 |
|
| 2010-03-28 20:09:27 |
ceg |
summary |
Installing mdadm or outdated mdadm.conf breaks bootup |
Installing mdadm (or outdated mdadm.conf) breaks bootup |
|
| 2010-03-28 21:56:29 |
ceg |
summary |
Installing mdadm (or outdated mdadm.conf) breaks bootup |
[->UUIDudev] installing mdadm (or outdated mdadm.conf) breaks bootup |
|
| 2010-03-28 23:02:22 |
ceg |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-03-30 10:17:07 |
ceg |
description |
Binary package hint: mdadm
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:
- 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.
Cure:
Systematically preventing conflicts from arising instead of relying on mdadm.conf maintanance. -> comment #33 |
(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
|
|
| 2010-03-30 10:18:40 |
ceg |
description |
(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
|
(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 prevent any conflicts from arising instead of relying on mdadm.conf maintanance. -> UUID-based raid assembly described in comment #33
|
|
| 2010-03-30 10:29:14 |
ceg |
description |
(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 prevent any conflicts from arising instead of relying on mdadm.conf maintanance. -> UUID-based raid assembly described in comment #33
|
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.
Cure:
Systematically prevent conflicts from arising instead of relying on mdadm.conf maintanance. -> UUID-based array assembly as described in comment #33
|
|
| 2010-03-30 10:43:52 |
ceg |
description |
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.
Cure:
Systematically prevent conflicts from arising instead of relying on mdadm.conf maintanance. -> UUID-based array assembly as described in comment #33
|
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.
Cure:
Systematically prevent conflicts from arising instead of relying on mdadm.conf maintanance. -> UUID-based array assembly as described in comment #33
|
|
| 2010-04-06 11:09:33 |
xteejx |
removed subscriber Teej |
|
|
|
| 2010-06-09 14:45:08 |
ceg |
description |
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.
Cure:
Systematically prevent conflicts from arising instead of relying on mdadm.conf maintanance. -> UUID-based array assembly as described in comment #33
|
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 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. -> Do not depend on mdadm.conf definitions but use UUID-based array assembly as described in comment #33
|
|
| 2013-01-14 18:05:37 |
Hans Deragon |
bug |
|
|
added subscriber Hans Deragon |
