-- Initial header ---
From : martin f krafft [EMAIL PROTECTED]
To : Cyrille Bollu [EMAIL PROTECTED]
CC : [EMAIL PROTECTED]
Date : Wed, 13 Sep 2006 12:46:48 +0200
Subject : Re: Bug#386468: mdadm: cannot mount root filesystem after upgrade
(system
also sprach Cyrille Bollu [EMAIL PROTECTED] [2006.09.09.1121 +0200]:
thanks for the help: It is working now!
...
But, still with /dev/md3 as root filesystem and not /dev/md2
(my debian stable is on /dev/md1)... ;-)
Please give me exact details about which array is used how. /dev/md1
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
martin f krafft wrote:
I think it's all due to your chroot. What happens is that mdadm
decides that /dev/md3 (which probably is your stable root
filesystem) holds the root filesystem, so it decides to bring it up
during boot. Your grub
Hi Cyrille,
Sorry that you're experiencing troubles with mdadm. From what I can
tell right now, I don't think it's serious, so don't panic or
stress, we'll work it out.
also sprach Cyrille Bollu [EMAIL PROTECTED] [2006.09.07.2227 +0200]:
If I wait long enough for the boot process to give up and
retitle 386468 initramfs creation from chroot renders system unbootable
thanks
also sprach martin f krafft [EMAIL PROTECTED] [2006.09.08.1011 +0200]:
That's because you cannot just mount to /.
What do you have in your grub configuration as the root= parameter?
I think it's all due to your
Package: mdadm
Version: 2.5.2-7
Followup-For: Bug #383727
Hi,
I've seen quite a few bugs related to this matter on the BTS, and
have seen that a new version of mdadm is already in unstable, but,
as none of the bug reported apply exactly to my case, I decided to open
mine.
HISTORY
---
6 matches
Mail list logo
