On Tue, Jan 13, 2009 at 9:41 AM, Christopher Sawtell <[email protected]>wrote:
> On Tuesday 13 January 2009 08:59:02 Steve wrote: > > Looking at your setup, I'd say that you put the drives back in in the > wrong > > order, so that sda - with the bootstrap - is now sdb. Whether you can > > recover from this now, I'm not too sure. Still worth a try though (: > > If that were the case wouldn't the BIOS report that there was no operating > system? But he's getting as far as getting the boot loader to execute > because > it's saying 'GRUB'. > > There is a _very_ comprehensive list of GRUB error problems and their > solutions here:- > > http://www.gentoo.org/doc/en/grub-error-guide.xml > Problem #11 looks like the one I had, I'll try the suggested solution tonight when I get home :) > IMHO David should attempt to boot his machine using a rescue CD/DVD/USB > drive. > > Possible bootable rescue disk images can be found at:- > > http://www.sysresccd.org/Download > http://www.giannone.eu/rescue/current/ > http://www.toms.net/rb/download.html > > Note that last time I tried toms root and boot it would not execute the > chroot > command correctly. > > To the best of my knowledge, almost every Linux distro available now-a-days > has a rescue system built-in. If that's available to you, you can, may, and > should use that. > > imho, to start with you should boot your machine using a rescue system and > check the state of the grub config file. It's usually > at:-/boot/grub/menu.lst > some distros use a different file name such as /boot/grub/grub.conf which > might be linked to menu.lst . > Yes... Unfortunately, as I mentioned, using the rescue system on the SuSE DVD was partly what got me into this mess in the first place :D Still, I'll have another try. Thanks, David
