Public bug reported:

System is currently running SUSE 10.1 (updated to 2.6.20) with software
raid enabled.

I'm using the alternative Ubuntu Feisty 4 setup.

There are several SATA disks fitted, all connected to an Intel SATA
Controller.

Two of the disks are currently used in Software RAID 1 as follows.

10.5 GB RAID ( OS )
3.2 GB SWAP
136.4 GB RAID ( DATA)

I choose manual partitioning.

These are detected by the setup correctly as SDC and SDE.

I go into "Configure Software RAID" and confirm that I wish to use two
of the partitions for swap. I then try to exit Software RAID
configuration, with the intention that the existing RAID partitions will
be visable on the partitioning screen (as usually happens).

If I try to exit either via Finish or Cancel I get the error "Could not
stat device /dev/md/1 - No such file or directory"

If I press Retry on the error nothing happens. If I press cancel the
"Setting up the Partitioner" progress dialog hangs at 44%.

If I look in the console there are messages to say

md: md0 stopped.
md: bind<sde1>
md: bind<sdc1>
raid1: raid set md0 active with 2 out of 2 mirrors
md: md1 stopped.
md: bind<sde3>
md: bind<sdc3>
raid1: raid set md1 active with 2 out of 2 mirrors

using "mdadm -D" on either array doesn't show any problems.

There is a /dev/md directory which is empty.
There are /dev/md0 and /dev/md1 devices present.

I've tried a couple of times and the same thing happens each time.

** Affects: Ubuntu
     Importance: Undecided
         Status: Unconfirmed

-- 
Software RAID Problem during Install
https://launchpad.net/bugs/88977

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to