Cannot complete install with software RAID 0! (with Lucid Lynx beta 1, was fine with alpha 3)

Bug #549258 reported by RJARRRPCGP
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: debian-installer

Affects: Lucid Lynx beta 1.

----------------------------------

I created /boot on /dev/sda1.

I created a 1.5 GB RAID partition on /dev/sda2 and a 1.5 GB RAID partition on /dev/sdb1.

I created an MD RAID 0, which gives me a 3 GB partition.

The symptoms:

Then, when I tell the installer to write the changes, I get a message that's not normal, claiming the kernel can't reread the disk.

Then it displays an error about an attempt to mount /dev/sda3, the swap partition on the first HDD, failing!

This is the same partition setup I have been using with alpha 3.

It did seem to give me a nonsense message about the attempt to mount a filesystem at mountpoint "none" and the attempt failing. (This didn't occur before)

Then it offers me to go back to the partitioning screen, but then it displays "Detecting filesystems" (or similar) and stayed there! (freezed!)

I had to hold down the power button!

I could see nothing that I forgot. And, the CD integrity check passed.

Looks like it's possibly giving up before it can even add a file system!

Revision history for this message
Russell Green (r.green) wrote :

Duplicate of 527401[1].
Its been fixed already aswell.

[1]https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/527401

Changed in debian-installer (Ubuntu):
status: New → Invalid
Revision history for this message
RJARRRPCGP (rjarrrpcgp) wrote :

The duplicate status is wrong. The problem is before the GRUB installation stage.

Revision history for this message
Colin Watson (cjwatson) wrote :

I agree, your problem doesn't seem to have anything to do with bug 527401. Russell, please be more careful. It looks more like what I'm currently investigating as bug 539324 (although I realise that's LVM/crypto not RAID), although I'm not sure yet since I have not yet fully understood what's causing that bug.

Changed in debian-installer (Ubuntu):
status: Invalid → New
Revision history for this message
Colin Watson (cjwatson) wrote :

Also, Russell, please don't mark bugs as invalid while duplicating them. The duplication is quite sufficient, and by changing the status as well you just create additional work if and when the duplication needs to be reverted.

Revision history for this message
Maxim Wirt (mvirt) wrote :

I have the same problem. Installation of beta1 / beta2 on raid0 fails during partitioning stage with "unable to create ext4 filesystem on defice #0" message

Revision history for this message
RJARRRPCGP (rjarrrpcgp) wrote :

I didn't get that error.

Revision history for this message
Sergei Ianovich (ynvich-gmail) wrote :

I've attempted to install 10.04 beta 2 server with RAID1 today. On installer start-up, it complained about missing kernel modules, but offered to go on. After I created partitions, I chose 'Configure RAID' from partition manager menu. It offered to create arrays, but never put anything on disk.

Apparently, this problem is caused by missing kernel modules, because it doesn't appear with daily install image. It may be a good idea to serve installer kernel modules for beta2 until the the next beta or rc comes out.

With the daily image, I got the error Maxim describes in comment 5 for "mounting / on device 0". I was able to proceed by changing fs type to "ext4", but I'm not sure it is obvious.

Revision history for this message
NewTesla (newtesla-gmail) wrote :

Also, same problem here.
2x WD500AAKS (sata) on Amd S780/S880 (that`s how ubuntu sees it) fakeraid. Desktop (live) just returns me two steps back when I click finish, to install. Alternate cd keeps saying "unable to create ext4 filesystem...". Tried Softraid, no luck. Even tried setting harddrives to AHCI (not fakeraid) in BIOS, and then choosing softraid - no luck either.

Is there a workaround for this? Same computer had 9.10 a day ago, and worked flawlessly with raid1.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.