Juergen Keil wrote:
2009/5/3 Matt Ingenthron <[email protected]>:
This assumes the upgrade from 2008.11 to build 111a did not
install the new grub bits, but the menu.lst file was rewritten
and now uses those zfs gang blocks, and the old grub cannot
read the file any more? What kind of error is reported by the
grub console when you try a "cat /boot/grub/menu.lst" ?
No error. I see the file on the screen. This is, of course, after I've
done the findroot.
Hmm, with a VirtualBox 2.2.2 guest install and build 111a,
I can enter the grub console and cat /boot/grub/menu.lst,
without having to use findroot!
Well, in my case, grub is loaded but presumably doesn't even know which
of the partitions on the disk to operate with, right? In your case,
you've dropped to the grub menu after loading a number of parameters,
including that there is this thing called rpool on a particular disk.
Maybe I misunderstand what the findroot is doing and prematurely did the
findroot.
I tried just now and got "Error 25: Disk read error"
Did you get an error before you used findroot? Which one?
I didn't even try.
The other file that is loaded before the grub menu is displayed
is the file /boot/grub/splash.xpm.gz. IIRC a failure to load it
is not fatal and results in a grub menu without splashimage.
But, in the past there had been bugs in that area, e.g. 6775099
and 6779852.
Does a cat on that splash.xpm.gz file work from grub console, too?
I can try that, but if it's failing and dropping to a grub> prompt
because of that, there's a bug there. :)
I've just tried and yes, I can cat the splash.xpm.gz. Any thoughts on
how to get grub back in shape on this box?
- Matt
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
