On Mon, 10 Apr 2006, Marc L. de Bruin wrote:
dean gaudet wrote:
On Mon, 10 Apr 2006, Marc L. de Bruin wrote:
However, all preferred minors are correct, meaning that the output is in
sync with what I expected it to be from /etc/mdadm/mdadm.conf.
Any other ideas? Just adding
dean gaudet wrote:
On Sun, 9 Apr 2006, Marc L. de Bruin wrote:
...
Okay, just pressing Control-D continues the boot process and AFAIK the root
filesystemen actually isn't corrupt. Running e2fsck returns no errors and
booting 2.6.11 works just fine, but I have no clue why it picked the
On Mon, 10 Apr 2006, Marc L. de Bruin wrote:
dean gaudet wrote:
initramfs-tools generates an mdrun /dev which starts all the raids it can
find... but does not include the mdadm.conf in the initrd so i'm not sure it
will necessarily start them in the right minor devices. try doing an
dean gaudet wrote:
On Mon, 10 Apr 2006, Marc L. de Bruin wrote:
dean gaudet wrote:
initramfs-tools generates an mdrun /dev which starts all the raids it can
find... but does not include the mdadm.conf in the initrd so i'm not sure it
will necessarily start them in the right minor devices.
On Mon, 10 Apr 2006, Marc L. de Bruin wrote:
However, all preferred minors are correct, meaning that the output is in
sync with what I expected it to be from /etc/mdadm/mdadm.conf.
Any other ideas? Just adding /etc/mdadm/mdadm.conf to the initrd does not seem
to work, since mdrun seems to
On Sun, 9 Apr 2006, Marc L. de Bruin wrote:
...
Okay, just pressing Control-D continues the boot process and AFAIK the root
filesystemen actually isn't corrupt. Running e2fsck returns no errors and
booting 2.6.11 works just fine, but I have no clue why it picked the wrong
partitions to build
On Sun, Apr 09, 2006 at 02:35:53PM +0200, Marc L. de Bruin wrote:
Hi,
(I just subscribed, sorry if this is a dupe. I did try to match the
subject from the archives, but couldn't find any...)
I ran into trouble after upgrading a Debian Sarge system from 2.6.11 to
2.6.15. To be more precise,
