[opensuse] OpenSUSE and disk boot order
Hello I remember on previous openSUSE installs (e.g., 10.0), one could select the disk boot order in the BIOS. I do not mean if it is in a partition or the MBR. I mean which disk. All disks are present in the install so all info is there to do this, as it did in 10.0. For the life of me, I do not see this in 10.3. I am guessing it is moved or traveling incognito. Anyone know where this is now located? -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hmm this is interesting. I maintain a separate bootable windoze image on my laptop which I also run under vmware. In vmware I have to use the whole physical disk as the vmware disk so that the init loader and bootup stuff works. That exposes me to accidentally booting linux under linux and wrecking my filesystems. However if the vmware bios could be made to boot a different partition than the native linux boot this exposure would disappear. Anyone have ideas about that? wcn Roger Oberholtzer wrote:
Hello
I remember on previous openSUSE installs (e.g., 10.0), one could select the disk boot order in the BIOS. I do not mean if it is in a partition or the MBR. I mean which disk. All disks are present in the install so all info is there to do this, as it did in 10.0. For the life of me, I do not see this in 10.3. I am guessing it is moved or traveling incognito. Anyone know where this is now located?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-03-04 at 07:38 -0700, Wendell Nichols wrote:
Hmm this is interesting. I maintain a separate bootable windoze image on my laptop which I also run under vmware. In vmware I have to use the whole physical disk as the vmware disk so that the init loader and bootup stuff works. That exposes me to accidentally booting linux under linux and wrecking my filesystems. However if the vmware bios could be made to boot a different partition than the native linux boot this exposure would disappear. Anyone have ideas about that?
An idea (not tested): Create a boot manager in another disk, which can be virtual. This boot manager should be responsible of booting the partition you need. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHzXAftTMYHG2NR9URAjDMAJ9knRYKbr2+jS4ZUfnEEP7ObPTt2gCfVObD TGdMLLtO1vJcd53QcebCaF0= =mnLN -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-03-04 at 15:23 +0100, Roger Oberholtzer wrote:
I remember on previous openSUSE installs (e.g., 10.0), one could select the disk boot order in the BIOS. I do not mean if it is in a partition or the MBR. I mean which disk. All disks are present in the install so all info is there to do this, as it did in 10.0. For the life of me, I do not see this in 10.3. I am guessing it is moved or traveling incognito. Anyone know where this is now located?
AFAIK “the disk boot order in the BIOS” is selected in the BIOS, obviously. Or are you asking about something different? :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHzV/BtTMYHG2NR9URAsAQAJ9oxtuEwCPerPntGUddNt3VatTpqQCfXsQL BRlgI1QCtbnv6xJt0zaRcj8= =/IS4 -----END PGP SIGNATURE-----
On Tue, 2008-03-04 at 15:42 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Tuesday 2008-03-04 at 15:23 +0100, Roger Oberholtzer wrote:
I remember on previous openSUSE installs (e.g., 10.0), one could select the disk boot order in the BIOS. I do not mean if it is in a partition or the MBR. I mean which disk. All disks are present in the install so all info is there to do this, as it did in 10.0. For the life of me, I do not see this in 10.3. I am guessing it is moved or traveling incognito. Anyone know where this is now located?
AFAIK “the disk boot order in the BIOS” is selected in the BIOS, obviously.
Or are you asking about something different? :-?
Yes. The BIOS is involved, up to a point. But if there are two disks in the system during install, and one later gets removed, something important may may go missing. In 10.0, you could select which disk was going to be the boot disk, and then the install made sure all things boot related were set up for this. In my case, there is a removable disk that shows up as /dev/sda during install (no matter where it is in the BIOS boot order), and the disk I want to install on is /dev/sdb. In 10.0 I could, in a menu available during install, tell the install that /dev/sdb is the boot disk. Removing /dev/sda has no effect. The boot always works. I am looking for this functionality in 10.3 that worked great for me in 10.0. As I wrote, perhaps it is now done via different information. I am trying to find out what that is. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-03-04 at 16:21 +0100, Roger Oberholtzer wrote:
Yes. The BIOS is involved, up to a point. But if there are two disks in the system during install, and one later gets removed, something important may may go missing. In 10.0, you could select which disk was going to be the boot disk, and then the install made sure all things boot related were set up for this. In my case, there is a removable disk that shows up as /dev/sda during install (no matter where it is in the BIOS boot order), and the disk I want to install on is /dev/sdb. In 10.0 I could, in a menu available during install, tell the install that /dev/sdb is the boot disk. Removing /dev/sda has no effect. The boot always works. I am looking for this functionality in 10.3 that worked great for me in 10.0. As I wrote, perhaps it is now done via different information. I am trying to find out what that is.
Maybe the information you need is the file /boot/grub/device.map. Which is the boot disk depends entirely on the bios, then on whatever program that disk MBR contains. This program can then boot another disk or partition. If what worries you is the change of name when removing/adding a drive, then simply do not use those names. Edit grub so that instead of '/dev/sda' it uses labels or ids, for instance. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHzW0dtTMYHG2NR9URAgg+AJ9vx3FemW+OIntjiFNZXJVrliIBwACgiIGg 5duiTBJcaGU4xzHQP1dKQpA= =CaRd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 04 March 2008 15:39:08 Carlos E. R. wrote:
The Tuesday 2008-03-04 at 16:21 +0100, Roger Oberholtzer wrote:
Yes. The BIOS is involved, up to a point. But if there are two disks in the system during install, and one later gets removed, something important may may go missing. In 10.0, you could select which disk was going to be the boot disk, and then the install made sure all things boot related were set up for this. In my case, there is a removable disk that shows up as /dev/sda during install (no matter where it is in the BIOS boot order), and the disk I want to install on is /dev/sdb. In 10.0 I could, in a menu available during install, tell the install that /dev/sdb is the boot disk. Removing /dev/sda has no effect. The boot always works. I am looking for this functionality in 10.3 that worked great for me in 10.0. As I wrote, perhaps it is now done via different information. I am trying to find out what that is.
Maybe the information you need is the file /boot/grub/device.map.
Which is the boot disk depends entirely on the bios, then on whatever program that disk MBR contains. This program can then boot another disk or partition.
If what worries you is the change of name when removing/adding a drive, then simply do not use those names. Edit grub so that instead of '/dev/sda' it uses labels or ids, for instance.
Are you talking about the location of /boot? You can set this up at installation time in the Partitioning wizard. -- Bob Registered Linux User #463880 openSUSE 10.3, Kernel 2.6.22.13-0.3-default, KDE 3.5.9 Intel Celeron 2.53GB, 2GB DDR RAM, nVidia GeForce 7600GS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2008-03-04 at 19:09 +0000, Bob wrote:
On Tuesday 04 March 2008 15:39:08 Carlos E. R. wrote:
The Tuesday 2008-03-04 at 16:21 +0100, Roger Oberholtzer wrote:
Yes. The BIOS is involved, up to a point. But if there are two disks in the system during install, and one later gets removed, something important may may go missing. In 10.0, you could select which disk was going to be the boot disk, and then the install made sure all things boot related were set up for this. In my case, there is a removable disk that shows up as /dev/sda during install (no matter where it is in the BIOS boot order), and the disk I want to install on is /dev/sdb. In 10.0 I could, in a menu available during install, tell the install that /dev/sdb is the boot disk. Removing /dev/sda has no effect. The boot always works. I am looking for this functionality in 10.3 that worked great for me in 10.0. As I wrote, perhaps it is now done via different information. I am trying to find out what that is.
Maybe the information you need is the file /boot/grub/device.map.
Which is the boot disk depends entirely on the bios, then on whatever program that disk MBR contains. This program can then boot another disk or partition.
If what worries you is the change of name when removing/adding a drive, then simply do not use those names. Edit grub so that instead of '/dev/sda' it uses labels or ids, for instance.
Are you talking about the location of /boot? You can set this up at installation time in the Partitioning wizard.
It could be /boot. But it is not the just files themselves (I think). It is the boot tracks that can be written either to the MBR or to a partition. It must ALL (all stages) be written to the same disk (/dev/sdb). In 10.0, there was a little pop-up menu available in the install that listed all found disks. You just moved the one you wanted to contain all this information to the top of the list. There is no such popup in 10.3. There is a "more verbose and less obvious about the intent" choice of things like described here: http://www.novell.com/documentation/opensuse103/opensuse103_reference/index.... in section 13.3.2. I am guessing this accomplishes the EXACT same thing, but presented in a totally different way. (Sorry about the long URL - that is what the Novell site made as I moved through the document.) I guess my question was just wanting to confirm this. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Tuesday 2008-03-04 at 16:21 +0100, Roger Oberholtzer wrote:
Yes. The BIOS is involved, up to a point. But if there are two disks in the system during install, and one later gets removed, something important may may go missing. In 10.0, you could select which disk was going to be the boot disk, and then the install made sure all things boot related were set up for this. In my case, there is a removable disk that shows up as /dev/sda during install (no matter where it is in the BIOS boot order), and the disk I want to install on is /dev/sdb. In 10.0 I could, in a menu available during install, tell the install that /dev/sdb is the boot disk. Removing /dev/sda has no effect. The boot always works. I am looking for this functionality in 10.3 that worked great for me in 10.0. As I wrote, perhaps it is now done via different information. I am trying to find out what that is.
Maybe the information you need is the file /boot/grub/device.map.
Which is the boot disk depends entirely on the bios, then on whatever program that disk MBR contains. This program can then boot another disk or partition.
If what worries you is the change of name when removing/adding a drive, then simply do not use those names. Edit grub so that instead of '/dev/sda' it uses labels or ids, for instance.
In v10.2 during the installation process there was an entry in the grub setup sequence where you could choose which HD was going to be the first HD and be "the booter". In 10.3 this is no longer available and the installation process decides where the boot info will be placed, and it can stuff it up by putting it on the second HD - which it did in my case and it took me a while to figure why the system wouldn't boot. After altering the device.map and the entries in menu.lst I got the thing going. Ciao. -- A fanatic is one who can't change his mind and won't change the subject. Sir Winston Churchill -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin a écrit :
In v10.2 during the installation process there was an entry in the grub setup sequence where you could choose which HD was going to be the first HD and be "the booter".
you can still choose where you setup the grub, but only the bios can choose which drive is the first (this is done _before_ grub launch and of course before any linux) In 10.3 this is no longer available and the
installation process decides where the boot info will be placed
not at all, I played a lot with this on 10.3 (to boot from usb) many things are done on unexpected places and when the GUI changes it's sometime difficult to find where they are gone :-) when a disk swap is necessary to boot, usually yast is very good. (I always begin to set grup on the root partition, before any mbr) jdd -- http://www.dodin.net http://clairedodin.voices.com/ http://www.clairedodin.com/ http://claire.dodin.net/
participants (6)
-
Basil Chupin -
Bob -
Carlos E. R. -
jdd -
Roger Oberholtzer -
Wendell Nichols