[Bug 278176] Re: Intrepid ubuntu server won't boot RAID1

[Mike Hicks]

I saw this as well.  lspci reports that I have an Adaptec AHA-3960D
controller.  Since the device got detected a few seconds after the
"(initramfs)" prompt appeared, I was able to boot the system by just
typing "exit".  I guess the startup scripts will re-scan for the boot
device after the busybox shell exits (the first time, anyway).

Isn't the "correct" fix to add this to the commented "kopt=..." line
like this?

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
##      kopt_2_6_8=root=/dev/hdc1 ro 
##      kopt_2_6_8_2_686=root=/dev/hdc2 ro 
# kopt=root=UUID=d5373d24-cbe4-46be-a4cd-b3457985915a ro rootdelay=40

...and then, run the update-grub tool?  This way, the changes you've
made won't get overwritten the next time the update-grub script gets run
during a kernel install/upgrade.

-- 
Intrepid ubuntu server won't boot RAID1
https://bugs.launchpad.net/bugs/278176
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to initramfs-tools in ubuntu.