Intel Matrix RAID (on ICH9R) created on Windows. 3 HDD-
0 - SATA320GB (3 partitions) Non-RAID = 1-windows (16Gb) 2 linux ext3 (16gb) 3 - ntfs (backup win/linux) 1- SATA320GB (RAID0) - NTFS 2- SATA320GB (RAID0) - NTFS The linux boot disk is recognized as /dev/sda2 of course and this setup was already working as this since Feisty Fawn. This problem just appears to be in Hardy as soon as I do "apt-get install dmraid" and reboot the machine. /boot/menu.lst already reflect the disk as being hd0,2 which corresponds to /dev/sda2 and nothing happens. I also tried to reasign disk to /dev/mapper/isw_iwjidjqwMAIN1 or whatever name it was for the RAID thinking DMRAID could take over normal naming and that should be the problema but no, if I manually mount /dev/mapper or /dev/sda2 in busybox I am always receiving the message "device is bussy" Also, this is the problem, of course, initram is always reporting "device is busy" after installing dmraid and rebooting the system. :( -- dmraid package destroys initrd and render system unbooteable (ubuntu Hardy) https://bugs.launchpad.net/bugs/245842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
