Comment 24 for bug 102973

Revision history for this message
Chad Bernier (berniercr) wrote : Re: [Bug 102973] Re: dmraid looking for raid45 when kernel uses raid456
  • unnamed Edit (2.3 KiB, text/html; charset=ISO-8859-1)

no one in the ubuntu community seems to care. They don't aim it towards the
people who use raid5. they aim it towards the people who can't even
diagnose a compiz problem with their video driver.

There was that one guy working on the bug before. I was helping him, but i
lost access to the hardware. It wasn't my computer. He was unable to finish
working on it because the new software wasn't ready.

It sounds like all the hard work has been done, the software is ready, but
it still isn't working. it's quite hard to understand. I wish i could
help, but I don't have the hardware.

the state of this bug in ubuntu is absolutely ridiculous. Gentoo and fedora
have had this working for a long time now. I might stop using ubuntu
someday, because it bores me.

If you can afford it, you might want to get a hardware raid card. It will
be much easier to get to work, and it will be much safer. I will seriously
consider that option myself whenever i finally build a new desktop. The
problem is finding an affordable one with more than 4 ports.

On Wed, Apr 23, 2008 at 3:32 PM, Jochen Schneider <email address hidden>
wrote:

> Let me try to summarize what has happened so far:
> - this bug has been posted more than one year ago
> - Feisty has come and gone
> - so has Gutsy
> - Hardy is one day before release, with this problem still being unsolved
>
> I have been using Ubuntu now for almost one year. So far, I've been
> pleasantly surprised. But this issue is really worrying me, since I rely
> on the RAID feature for my new machine.
>
> I can only second the comment about most of today's motherboards being
> equipped with RAID (5) functionality.
> Does anyone have a honest clue when we can except a fix?
>
> --
> dmraid looking for raid45 when kernel uses raid456
> https://bugs.launchpad.net/bugs/102973
> You received this bug notification because you are a direct subscriber
> of the bug.
>