Hi,
Though I'm currently not using md, I have done so in the past, and it
has always worked well for me. I saw this bug report and thought that
I might try to reproduce it. Here's what I did:
1. retrieved debian-5010-i386-netinst.iso from
http://cdimage.debian.org/mirror/cdimage/archive/5.0.1.0/i386/iso-cd/
2. created a new VMware virtual machine with two 1GB IDE virtual disks
3. started a text-based install
4. created partitions manually using the installer menus:
hda1: 98.7 MB, ext3, /boot
hda2: 970.6 MB, raid
hdb1: 98.7 MB, swap
hdb2: 970.6 MB, raid
md0: RAID1, hda2 and hdb2, ext3, / (root filesystem)
5. received an error message about failing to read the partition table
on md0, which is odd, but apparently harmless. Running "mount" in the
2nd virtual console showed md0 mounted as "/target", so I continued
installation.
6. installation completed, booting from hard drive succeeded
7. removed lenny from sources.list, added squeeze, ran apt-get update
&& apt-get dist-upgrade
8. MD arrays needed for the root filesystem: "all"
9. rebooted successfully with new kernel
Things to try:
* start with Debian 5.0.0 (outdated oldstable)
* upgrade to 6.0.0 (outdated stable)
* upgrade to wheezy (current testing)
* create the md array manually using old superblocks or whatever if possible?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
