Bug#386468: mdadm: cannot mount root filesystem after upgrade (system unbootable)

[martin f krafft]

also sprach Cyrille Bollu <cyrille.bollu at scarlet.be> [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 your stable root, /dev/md3 is your unstable root? what's
/dev/md2? Any others?

> Do you have any clue as why the name of my RAID arrays were
> changed during the upgrade?

What were they before?

> Also, there is still this problem that "mdadm --examine --scan"
> reports 2 /dev/md4 array:

See #386315

> Also, what is the difference between "update-initramfs -u -k all"
> and "dpkg-reconfigure -plow mdadm". Isn't the second command
> calling the first? Because I had tried the 2nd command already
> without success... But maybe I did forgot something else at that
> time...

dpkg-reconfigure calls update-initramfs, that's correct.

-- 
 .''`.     martin f. krafft <madduck at debian.org>
: :'  :    proud Debian developer, author, administrator, and user
`. `'`     http://people.debian.org/~madduck http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature (GPG/PGP)
Url : http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20060913/47d39138/attachment.pgp