ubuntu9 works for me now, thank you.
On Wed, Oct 8, 2008 at 1:07 AM, Chris <[EMAIL PROTECTED]> wrote:
> Hi,
> I believe I had checked that. The default build turns out to be
> non-local. When linux failed to boot, it dropped to the initram
> prompt, where I did a dmraid --version (or similar) an
Hi,
I believe I had checked that. The default build turns out to be
non-local. When linux failed to boot, it dropped to the initram
prompt, where I did a dmraid --version (or similar) and it gave rc15.
It was a static build I believe.
When it failed I was able to boot one of my older kernels tha
Ok, when you built dmraid there was probably a chance that dmraid ended
up in /usr/local/bin. If so, move /usr/local/bin/dmraid to
/usr/bin/dmraid, and regenerate the initramfs.
I am interested in whether rc15 fixes your problem.
Luke
--
Debian patch for bug #494278 removes intel raid 10 suppor
Thank you for the response.
I did generate a new initramfs, this packs the modules and necessary
dmraid into the initram file for when the kernel loads. Unfortunately
this rc15 dmraid did not work. (Could not find metadata). I did not
apply any dmraid "debian" patches to it, I thought that was th
Compiling and installing a newer version of dmraid is not enough for the
newer dmraid to help your system boot. You need to generate a new
initramfs to include the new dmraid executable.
If I get time in the coming days, I will make an rc15 package for you to
test.
For now, I'll consider re-enabl
Public bug reported:
My intel raid 10 (0+1) used to use fine, but the recent dmraid package
removed dmraid 10 support because of debian bug #494278. I was told to
wait for rc15. I downloaded rc15 myself, and it cannot find meta data.
(Maybe it needs a patch?) Please support my system, otherwise
