booting raid volume with LVM cant boot my server.. haalp!

[dirtbag]

ok, folks, I have a gentoo server (2.6.26 kernel) thats got 2 disks which are mirrored with software raid.
smartd was telling me that one of the disks (sdb) was going bad.. so, I fail it and remove it..
I reboot the box to try to make sure that things will boot right before I go any further, but I get boot errors..
cant remember which now, but I cannot get it booted. what I finally did, was replaced that bad sdb disk, and boot up systemrescue cd
and got my raid and lvm devices noticed.. I mirrored the partitions with sfdisk.. thats fine.
I add the new partitions to the raid and during the sync, it craps out cause of read errors on sda?!?!? wtf?!
so I end up fscking my root volume on sda (the supposedly good disk) and its kicking out some errors.. great
so on the new disk (sdb) i created a new raid device and lvm and did an rsync of the root partition to the new disk..
that all worked fine except for some files in /proc of course..

ok, so now, when I boot up the system with the NEW raid on the new lvm root partition, I get the following error and cant figure out why..
It seems udev is crapping out on me somehow..
*mounting sysfs at /sys ...
* you eed at least Linux kernel 2.6.27 for reliable operation of udev.
* mounting /dev ...
/etc/init.udev: line 40: /proc/sys/kernel/hotplug: Read-only file system
* starting udevd ...
/sbin/udevd already running.
start-stop-daemon: warning: failed to kill 9079: no such process
start-stop-daemon: warning: failed to kill 9080: no such process
start-stop-daemon: warning: failed to kill 3569: no such process
3 pids were not killed
No /sbin/udevd found rnning; none killed.
*checking root filesystem ...
fsck.ext3: No such file for directory while trying to open /dev/volgroup/rootvol/volgroup/rootvol:
The superblock could not be read or does not describe a correct ext2...

*Filesystem couldn't be fixed
give root password for maintenace
(or Ctrl-D to continue):

when I give the root password and look at
/dev/ all I see is
console core fd kmsg null pts shm stderr stdin stdout tty tty1

note... the NEW volume is /dev/volgroup2/rootvol2..
when I boot, it complains that it cant find root, so I tell it /dev/volgroup2/rootvol2
and it seems to take it, but then i eventually get the error above..

and ideas on what to do?

-db

[dirtbag]

ok folks, after many hours of spinning my wheels and failing .. I finally came across this bug..
https://bugs.gentoo.org/show_bug.cgi?id=291916

I cleared out my old array entries in /etc/mdadm..conf and
I had to clear out /proc/* on the disk that I was working with and now things boot fine..

*whew*

-db