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
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
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
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
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
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
** 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.
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,
** 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)'
** 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
** 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.
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
** 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
13 matches
Mail list logo
