raid config fails with debian-installer/mdadm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Using the alternative cd I have been trying to install ubuntu on 2 disks in a raid 1 linux software raid configuration. I would like 1 raid device for boot and 1 for the rest(actually I would have the rest used by LVM, but haven't got that far)
Something is confusing the partitioner or mdadm about my disks. It is 2 maxtor Diamondmax plus 9 120GB disks.
I can create the partitions fine. But when I then enter the raid configuration. And choose to create a new raid 1...I get a message about that no raid are available. If I then go to the terminal I can see that it somehow has put all 4 raid partitions in one md device
I have 2 different controllers on my motherboard and have tried it on each of them...with the same result.
I have also tried to install just normally on one disk, and then convert it to raid...I cannot boot after I install mdadm
On the other hand I have tried the same alternate install cd on 2 old ibm disks I had around where it works perfectly
I don't know, but what I can imagine is that somehow maybe the kernel doesn't get the correct geometry of the disks? but that is just a wild guess
I can install fedora core9 in the same raid configuration which are failing with ubuntu. I have actually tried both 7.04,7.10,8.04 alfa 1 & 3 and also Debian etch. All of these versions fail with the maxtor disks
I will see if I can find out if there is any differences in kernel parameters at boot time and/or kernel configuration
Regards
Hasse
Ok. I have tried to see if I could find any differences in the kernel config, but haven't been very good at it. I have tried opensuse also. It also is creating Software raid successfully. I have attached then kernel config from Ubuntu 8.04 alpha 3 and fedora core8 if anyone have a good way to diff these