[opensuse] Interesting Boot Problem
I've just installed openSuSE 10.2, everything went fine, all hardware was identified, my primary hard drive mapped to sda, my ARECA raid neatly mapped to sdb, all was right in the world... Then, for some reason, today when I rebooted the system my primary drive mapped to sdb and my raid array mapped to sda... I've changed nothing since the last boot except trivial stuff like adding user accounts etc. Naturally the boot process now fails as it can't mount the root file system, as it's looking for it on sda2 which as I said now points to my big empty raid array. Several hours of web searching has left me with the impression that I should be able to force the physical devices (some sort of BIOS naming) to map to a static logical device (sda...), but I'm not sure what files to edit and what the syntax would be??? Any help would be greatly appreciated. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stuart Knock wrote:
I've just installed openSuSE 10.2, everything went fine, all hardware was identified, my primary hard drive mapped to sda, my ARECA raid neatly mapped to sdb, all was right in the world... Then, for some reason, today when I rebooted the system my primary drive mapped to sdb and my raid array mapped to sda... I've changed nothing since the last boot except trivial stuff like adding user accounts etc. Naturally the boot process now fails as it can't mount the root file system, as it's looking for it on sda2 which as I said now points to my big empty raid array. Several hours of web searching has left me with the impression that I should be able to force the physical devices (some sort of BIOS naming) to map to a static logical device (sda...), but I'm not sure what files to edit and what the syntax would be??? Any help would be greatly appreciated.
This sounds like a BIOS problem to me. Does your BIOS allow you to set the order of which drives to boot? Do you reach the GRUB boot menu? How do you know how the drives are now mapped? Is the RAID you have using the fake raid setup in your BIOS or an actual RAID controller? It sounds like your BIOS switched the drives on GRUB (but if so, since I assume grub was only installed on the MBR of sda it would no longer even try to boot). -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-01-31 18:03, Stuart Knock wrote:
<snip> searching has left me with the impression that I should be able to force the physical devices (some sort of BIOS naming) to map to a static logical device (sda...), .... I think this can only be handled in the BIOS itself, probably in the boot order settings. Make sure your primary is set as the first boot device. You probably don't want the RAID array mapped as a possible boot device (not sure, I don't use RAID here, so could be wrong).
-- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-01-31 18:43, Darryl Gregorash wrote:
On 2007-01-31 18:03, Stuart Knock wrote:
<snip> searching has left me with the impression that I should be able to force the physical devices (some sort of BIOS naming) to map to a static logical device (sda...), ....
I think this can only be handled in the BIOS itself, probably in the boot order settings. Make sure your primary is set as the first boot device. You probably don't want the RAID array mapped as a possible boot device (not sure, I don't use RAID here, so could be wrong).
OP replies (offlist):
BIOS settings are fine, the system had booted a few times already, without a problem. Since this issue I have tried completely removing the RAID array from the boot sequence but somehow GRUB seems to find it and assign it to sda... which I thought wasn't possible as GRUB supposedly assigns logical naming based on the boot order... guess there is some magic in the code somewhere.
Then check /boot/grub/device.map to make sure the proper devices are mapped to the proper grub device names. Grub isn't assigning any names to anything, it is simply using what the BIOS reports following POST, and there is *no* "magic code" anywhere. -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 31 January 2007 18:03, Stuart Knock wrote:
I've changed nothing since the last boot except This is user lie #742.
Well, when I was on the service desk and somebody tried to feed me lie #742 I would always say, "That's great... 'cause if you changed nothing since the last time it worked... it still works... have a nice day". Almost invariably they would admit that there were a couple of hundred insignificant things that they changed... but really they are certain NONE of them have anything to do with this 'cause nothing else has been changed! Outside of a massive illogical hardware failure (probably BIOS related) there is no way that what is being described happened. This kind of stuff always rips my heart out. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 31 January 2007 17:00, M Harris wrote:
On Wednesday 31 January 2007 18:03, Stuart Knock wrote:
I've changed nothing since the last boot except
This is user lie #742.
Well, when I was on the service desk and somebody tried to feed me lie #742 I would always say, "That's great... 'cause if you changed nothing since the last time it worked... it still works... have a nice day". Almost invariably they would admit that there were a couple of hundred insignificant things that they changed... but really they are certain NONE of them have anything to do with this 'cause nothing else has been changed!
Outside of a massive illogical hardware failure (probably BIOS related) there is no way that what is being described happened. This kind of stuff always rips my heart out.
-- Kind regards,
M Harris <><
This one CAN happen without operator intervention. What grub sees as hd0 can be changed through the "hard drive boot priority list", accessible through the bios settings. If there is a power failure or some other abrupt interruption of the system, the bios can reset to "default" settings, which can be different from the working setup. I believe the standard default is that hda is what grub calls hd0. The reason I know this is because it has happened in my biostar 3800+ mobo. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
kanenas wrote:
that hda is what grub calls hd0. The reason I know this is because it has happened in my biostar 3800+ mobo.
and anytime grub can itself start, don't forget you can use the mini grub console to boot whatever you want, or simply know what grub see this is documented in the wiki jdd -- http://www.dodin.net Votez pour nous, merci - vote for us, thanks :-) http://musique.sfrjeunestalents.fr/artiste/Magic-Alliance/ http://photo.sfrjeunestalents.fr/artiste/jddphoto/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Darryl Gregorash -
jdd -
Joe Morris (NTM) -
kanenas -
M Harris -
Stuart Knock