Boot Problem after Crash

[Lennart Sorensen]

On Fri, Mar 07, 2008 at 06:30:04PM -0400, Tony Abou-Assaleh wrote:
> Here is the item from my menu.lst from grub that I've been using:
> 
> title           Ubuntu, kernel 2.6.22-14-generic, UUID root
> root            (hd0,0)
> kernel          /vmlinuz-2.6.22-14-generic \
> 		root=UUID=28fd2317-9996-4c22-8e16-32e3e7c5c393 ro quiet 
> 		splash
> initrd          /initrd.img-2.6.22-14-generic
> quiet
> savedefault
> 
> Previously, it was:
> 
> title           Ubuntu, kernel 2.6.22-14-generic
> root            (hd0,0)
> kernel          /vmlinuz-2.6.22-14-generic \
> 		root=/dev/mapper/raid250-root  ro quiet splash
> initrd          /initrd.img-2.6.22-14-generic
> quiet
> savedefault
> 
> Both give the same result. I added \ to indicate long lines, they're one 
> liners in the file.

You weren't by any chance trying to use one of those fakeraid onboard
raid controllers along with dmraid were you?

I have never seen /dev/mapper/raid250-root before, only ever when using
LVM stuff.  If it is just LVM then I am really puzzeld as to what it's
issue is.

Of course it would be much simpler if you could capture the console
output during the boot that fails since it usually gives useful clues as
to why it can't load certain drivers or can't find certain devices.

The most likely problem is that your initrd is rather minimal and didn't
include drivers for the other system you moved the drives to.

--
Len Sorensen
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists