DANGER!!! Problems with 10.04 installer (RAID devices *will* get corrupted)

[Rashkae]

Christopher Chan wrote:
> On Thursday, April 22, 2010 02:24 AM, J wrote:
>> On Wed, Apr 21, 2010 at 12:41, Alvin Thompson<alvin at thompsonlogic.com>  wrote:
>>> On 04/21/2010 12:23 PM, Brian McKee wrote:
>>>> Jeez, thousands of people donate thousands of hours of time to give
>>>> you an OS and you can't fill in a bug report?  For shame....
>>> I have literally lost about 10 years worth of work (well, half of it).
>>> And most of the replies I get are from people smugly saying that I
>>> should have also backed up my data (true, but it doesn't help).  I've
>>> used ubuntu since Hoary Hedgehog, but right now I'm so sick of their
>>> current
>>> get-it-out-the-door-on-time-with-too-many-new-features-to-properly-test-and-to-hell-with-quality
>>> attitude that I want nothing to do with them.  You're lucky I
>>> investigated this problem and wrote this warning.
>> Problem is, no one in a position to fix or even look into this issue
>> you have officially is going to do so if you don't file a bug.
> 
> HA!
> 
> 
>> Coming here (or any other mailing list) and providing the info you
>> have (which is EXCELLENT info, I might add) is no different than just
>> running outside and telling your neighbor about your RAID issues.
> 
> His RAID issues? Cool, his issues eh? Not ubuntu-installer's issues. 
> Nice. I, for one, appreciate the heads up.
> 
> 
>> I understand your frustration, but really, no one here can fix the
>> installer.  The people who can find out about these things from bugs
>> filed in Launchpad.
>>
> 
> Really, you understand his frustation eh? What about mine (there is a 
> reason why I am still on Hardy at work and Jaunty at home)? As in maybe 
> developers need to learn to keep in touch with their users then. For an 
> issue with such ramifications such as this, I'd say filing a bug report 
> is the least of the problem. Why? Because it shows that the developer(s) 
> failed to even to some basic testing and just let their code out in the 
> wild and wait to see if problems occur. If not, great, if so, too bad. 
> That kind of attitude plus a 'customer must file complaint via the {name 
> your favourite pain in the neck dept}' mentality will only lead to the 
> inevitable. Poor product.
> 

This might well be true, and god knows I have my own issues with Ubuntu 
quality control  (Smart monitoring service that bricks SSD's anyone?)

However, you are jumping some pretty large conclusions based on a, so 
far, unsubstantiated claim by someone who has demonstrated lack of basic 
understanding of how hard drives and raid arrays are created/accessed by 
the OS.  Who can say what really happened? Until someone can re-create 
the scenario and actually test it.