Raid Installation Hoary Hedgehog 5.04

The intallation go straight forward. After the first reboot, the boot stop and ask for "do e2fsk manualy". With mount -a and CTRL-d the boot continue. There are two error, one in /etc/fstab (doesn't find /dev/md3) and the same error in /etc/mdadm/mdadm.conf. Another problem is a kernel upgrade, because the mkinitrd fails (details see below). There is now a Ubuntu BugNr 12191

The following two changes solve the problem:

1. Using LABEL= statements in /etc/fstab:

         LABEL=/  /  ext3  defaults,errors=remount-ro  0  1
         LABEL=/var  /var  ext3  defaults  0  2
   

2. Removing DEVICE statement and adding auto=md in /etc/mdadm/mdadm.conf:

         ARRAY /dev/md3 level=raid1 num-devices=2
            UUID=72950ff5:90036b68:5751e315:c2df18f8 auto=md
   

3. Change the ROOT parameter in /etc/mkinitrd/mkinitrd.conf:

         #ROOT=probe
         # --to--
         ROOT=/dev/md0
   

This is the boot error situation:

        * Starting RAID devices...
        mdadm: error opening /dev/md3: No such file or directory
        mdadm: error opening /dev/md2: No such file or directory
        mdadm: error opening /dev/md1: No such file or directory   [fail]
        * Setting up LVM Volume Management system...               [ ok ]
        md: md2: read array is not clean -- starting background reconstruction
        * Checking all file systems...
        fsck.ext3: No such file or directory whie trying to open /dev/md3
        /dev/md3:
        The superblock could not be read or does not describe a correcrt ext2
        filesystem. If the device is valid and it really contains an ext2
        fileystem (and not swap of ufs or someting else), then the superblock
        is corrupt, and you might try running e2fsck with an alternate superblock:
                e2fsck -b 8193 <device>

        * fsck failed. Please repair manually.

        * CONTROL-D will exit from this shell and continue system startup.

        root@(none): #

This is the kernel update situation (in detail a mkinitrd error situation). I simulate a kernel update with mkinitrd:

        root@fugazzi:~# mkinitrd -o /tmp/mkinird
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        dpkg: warning, architecture `amd64' not in remapping table
        File descriptor 3 left open
        File descriptor 4 left open
        File descriptor 5 left open
        File descriptor 6 left open
        File descriptor 7 left open
                Finding all volume groups
          No volume groups found
        /usr/sbin/mkinitrd: 253:0: Cannot find LVM device
        root@fugazzi:~#