*** This bug is a duplicate of bug 141435 ***
https://bugs.launchpad.net/bugs/141435
I'm having the same problem with a Nvidia Fakeraid configuration. Under
Feisty (with kernel 2.6.20-16) during boot, two devices are discovered
under /dev/mapper :
/dev/mapper/nvidia_blah
/dev/mapper/nvidia_blah1
However, after upgrading to Gutsy, these are missing. Normally, these are
coupled to become /dev/md1 ....
Interestingly I also have a Silicon Image Controller with a Softraid
configuration, and these devices are discovered correctly with both Kernels.
During boot time with Kernel, errors are reported as:
device-mapper: table: 253:0: mirror: Device lookup failure
device-mapper: ioctl: error adding target to table
I know there are a couple of Bugs relating to EVMS - this is definitely
something different, as EVMS was never installed on my system.
Could this be something specific with dmraid/dmsetup/udev relating to the
Nvidia Nforce4 chipset ?
Luckily, the Raid mirror I'm having problems with isn't the boot device,
however I can't access the data (obviously).
Rebooting to the old Kernel kinda works, but introduces other problems with the
Nvidia linux restricted graphics driver.
The partitions look fine from fdisk, but the discovery issue would
appear to be the main problem.
Any help would be appreciated ... I'd hate to have to downgrade.
--
Unable to boot after linux-image-2.6.22-11.33 rt or generic after upgrade
https://bugs.launchpad.net/bugs/140748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
