Comment 3 for bug 380138

HPA ignore by default is a DISGRACE decision, basically what it does, is if you are already using DMRAID for MatrixRAID, NVRAID, etc, etc, it simply destroys the hpa information on boot, and this cannot be fixed.

After tedious testing I found out that, once a single boot is made with HPA ignoring on the kernel, the HPA information is totally destroyed, the only way the RAID can be used is by booting into Ubuntu every time you start the PC THEN going to Windows te recover the RAID, in Intel Matrix RAID, once you boot up to a linux kernel in HPA ignoring state you never get the HPA information back and the PC will always fail with "Offline Member" even after powering down and up, I already tried this numerous times.. so, One little error on your part of not setting libata ignore_hpa=0 on kernel and that's it, you have to rebuild your entire array for it to be working again without you having to boot into linux every time you want to put Online the disks again.

This is a disaster, I've been reporting this problem, which could be considered a SERIOUS BUG for us, users with RAID and to this day, there is no solution, even on Karmic.

A simple "Boot into RAID system" in the welcome screen at boot could fix this horrendous problem, at least give us a choice without users having to resort to put kernel commands.

Before jaunty it was move back from kernel to libata module in modprobe.d, from jaunty and back on, it was move back to kernel libata ignore, this situation cannot be further delayed, with each change, it means that the user has to be aware Ubuntu internal desicions prior to booting a LiveCD or else, deactivate it's raid system and be sure the option is introduced correctly BEFORE booting the livecd, checking the option once the liveCD is loaded, rebooting with the option enabled and then installing, this hussle should NOT be there for the majority of us, RAID users, which are ever increasing in the desktop space.

Could my post be considered? Did you realize the level in which this situation has escalated and that could be so easily fixed with a simple "kernel option" at boot ?

Could anyone tell me how to do it myself and propose it back to the ubuntu guys for consideration?

I do not want to suffer anymore from this, and I'm prepared to help in any way possible.

PLEASE DO SOMETHING about it :(