Thanks for the kick to look at this again. In fact, it's caused by an earlier Edgy problem that, alas I didn't report (mea culpa).
* With the 2.6.17-5, boot.lst was changed to use UUID (vice device names). * This caused the machine not to boot as init could not find the root device from the UUID. * I booted manually with root=/dev/md0 (replacing the Ubuntu modified root=UUID=....) * I manually edited boot.lst to make this permanent, only I put "/dev/md0" instead of "root=/dev/md0" in the kopt line. * My typo broke the subsequent boot with 2.6.17-6 (don't know how 2.6.17-5 manged). Summary: real problem is that root=UUID=..... failed for my raid1 setup (and still does). -jonathan -- Edgy updates of 2006-08-12 render machine unbootable https://launchpad.net/bugs/56155 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
