This looks familiar. Didn't we run into this at a Linux clinic a
couple of months ago?
Yes, openSUSE defaults to grub. Here's a chunk of /boot/grub/menu.lst
from my machine
title openSUSE 11.1 - 2.6.27.21-0.1
root (hd0,1)
kernel /boot/vmlinuz-2.6.27.21-0.1-default
root=/dev/disk/by-id/ata-ST3160811AS_5PT10CJZ-part2
resume=/dev/disk/by-id/ata-ST3160811AS_5PT10CJZ-part1 splash=silent
showopts vga=0x317
initrd /boot/initrd-2.6.27.21-0.1-default
When openSUSE boots, you need to hit "ESC" to get into the Grub menu.
Then you can edit the line to point to actual devices. Once you get
the machine booted up, you can edit /boot/grub/menu.lst and change the
line so it always boots that way.
On 5/27/09, Matt McKenzie <[email protected]> wrote:
> On Wed, May 27, 2009 at 9:21 PM, Wayne E. Van Loon Sr.
> <[email protected]>wrote:
>
>> I seems if you move a openSuse 11.1 hard disk to another computer, it
>> starts booting up, hangs for a bit, and then switches to black and white
>> console and gives the message:
>> Could not find /dev/disk/by-id/ata_WDC_WD800JB-OOJJCO_WD-WMAM bla bla bla.
>>
>> If you wait a bit, it will start a bash shell. It obviously found the
>> disk and booted something. You can then do a ls command, change
>> directories etc., but you can't do much.
>>
>> If you take the disk back to the computer on which you made the
>> installation, it boots up fine.
>>
>> Searching for the first part of the error string "Could not find
>> /dev/disk/by-id/" finds several folks having the same problem moving or
>> duplicating openSuse Installations. Most of them had to resort to
>> booting the install CD and repairing or reinstalling (Beginning to sound
>> a little like Windows??).
>>
>> A customer of mine runs some flavor of a SuSE server in their back room
>> and therefore would like to deploy openSuse based systems in one of
>> their industrial control system products. However, if a system located
>> in Rusia, Japan or even Alabama should have a disk failure and need a
>> new disk, or should the main board die, having to make the new disk on
>> the target hardware would be a pain.
>>
>> Has anyone on this list encountered this problem?
>> Is there a simple way to reconfigure something and get openSuSE to run
>> on multiple machines?
>> Do you think not being able to run on any hardware other than the
>> installation hardware is a good idea?
>>
>> Wayne
>>
>>
>>
>>
> This is a bit of a shot in the dark, but I may have run into something
> similar, although with Ubuntu.
> It may be that OpenSuSE uses UUID of the disk to determine what to boot,
> instead of a pathname like /dev/hda or /dev/sda. Moving the disk to a
> different computer, causes that disk to have a different UUID since it is on
> a different IDE/SATA controller. UUID is said to remain constant across
> reboots, but only on the same computer. If you move the drive to another
> computer (and thus another IDE/SATA controller) the UUID is not guaranteed
> and likely not going to be the same.
>
> One thing you can do, is when the system boots, interrupt the automated
> countdown, and go into GRUB and edit the kernel line (use arrow keys to
> hightlight the line that has "kernel" and hit "e" to edit) so that it points
> to /dev/hda1 or /dev/sda1 (depending on your disk) instead of the UUID, and
> see if it boots. If it does, you can then get the UUID of the disk in the
> new computer on the command line (I forget the exact command offhand,
> perhaps someone else can chip in with it...), and edit /boot/grub.conf and
> change it to point to the new UUID to boot to it each time.
>
> I am pretty sure OpenSuSE uses GRUB now yes?
>
> This is a guess but an educated guess... ;)
>
> ----------
> Matt M.
> LinuxKnight
> _______________________________________________
> PLUG mailing list
> [email protected]
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
--
M. Edward (Ed) Borasky
http://www.linkedin.com/in/edborasky
I've never met a happy clam. In fact, most of them were pretty steamed.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
