Hello everybody!
(I hope this is the right list to post this...) I've installed Debian
sarge from the current
testing on 29/03/2005 with Kernel 2.6 using four Raid1 partitions. I
didn't install any
additional tasks with base-config at first. Everything went fine, I
was able to reboot into
the system and to access the raid partitions. The root directory is on
a raid partition and
even that works!
But: I started base-config and installed the desktop environment. The
install went fine.
But after the next reboot the system was broken. The first raid
partition with root on it
still worked, so I was able to boot into a minimal system. But the
other three raid
partitions notably with /var and /home on it didn't work, so I got
lots of error messages.
And now it becomes really funny: I was able to recreate the missing
raid arrays
manually using mdadm --create and to mount them. It worked, I could
use them. Yet
after another reboot they had vanished again. If I don't use
base-config to install the
desktop environment but fetch the packages manually with aptitude
everything is fine.
And if I make an install with Kernel 2.4 instead of 2.6 I can use
base-config to install and
it works, too.
So it seems that using base-config after an install with Kernel 2.6 on
raid partitions
breaks all raid partitions except the first. As there is a simple
workaround, i. e. installing
the packages manually, it's not a big problem. But it took me two days
to figure that out.
What was I doing wrong or might it be that there is a bug in
base-config?
If anyone has encountered similar problems I'd be interested to hear
about that.
Browsing the mailing lists I see that this problem already appeared in
September 2004
and was supposed to be fixed a long time ago. But apparently it isn't,
at least in my
case.
Thanks
Hans-Joerg v. Mettenheim
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org