Comment 10 for bug 107249

So I added sdc1 back to the md0 array. This was enough to get me past the errors in the upgrade and everything checks out ok. I guess I'll really know when I next try to reboot.

It is not clear to me why sdc1 was dropped from the array ... I will look for a log to see if I can find an explanation. sdc2 remained in the second array so I know that the drive itself is functional.

here is the output from apt-get install:

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libgoffice-0-common gdesklets-data gnome-cups-manager
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up linux-image-2.6.20-16-generic (2.6.20-16.29) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.20-16-generic
Warning: '/proc/partitions' does not match '/dev' directory structure.
    Name change: '/dev/dm-0' -> '/dev/horizon/swp'
Added Linux *
Added LinuxOLD
Added Windows
The Master boot record of /dev/sdc has been updated.
Warning: /dev/sdd is not on the first disk
The Master boot record of /dev/sdd has been updated.
Warning: /dev/sdb is not on the first disk
The Master boot record of /dev/sdb has been updated.
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.20-16.28 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.20-16.28 was configured last, according to dpkg)
You already have a LILO configuration in /etc/lilo.conf
Running boot loader as requested
Testing lilo.conf ...
Testing successful.
Installing the partition boot sector...
Running /sbin/lilo ...
Installation successful.