[opensuse] 15.1 Installation
Hi, I'm not sure if this is the correct forum for 15.1, but since I don't know I thought I would give it a try. I'm trying to install 15.1 on a computer on the second hard drive. That is /dev/sdb. In the installation readout for booting, the mbr keeps on coming up as /dev/sdb. But my mbr is esconsced in /dev/sda. I can't find a way to change the installation to boot from the mbr in /dev/sda. Everything I have tried reports to me that the 15.1 installation won't boot. No surprise, it doesn't. Any ideas how to change this? Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/2019 01.34, Mark Misulich wrote:
Hi, I'm not sure if this is the correct forum for 15.1, but since I don't know I thought I would give it a try.
I'm trying to install 15.1 on a computer on the second hard drive. That is /dev/sdb. In the installation readout for booting, the mbr keeps on coming up as /dev/sdb. But my mbr is esconsced in /dev/sda. I can't find a way to change the installation to boot from the mbr in /dev/sda. Everything I have tried reports to me that the 15.1 installation won't boot. No surprise, it doesn't.
Any ideas how to change this?
Don't. Simply change the computer bios order to boot from sdb instead. Not the only way to do it, though. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/25/19 6:34 PM, Mark Misulich wrote:
I'm trying to install 15.1 on a computer on the second hard drive. That is /dev/sdb. In the installation readout for booting, the mbr keeps on coming up as /dev/sdb. But my mbr is esconsced in /dev/sda. I can't find a way to change the installation to boot from the mbr in /dev/sda. Everything I have tried reports to me that the 15.1 installation won't boot. No surprise, it doesn't.
In the boot settings, check the box for "Custom boot partition" and then enter "/dev/sda" in the space provided. If you are able to boot your installed system, you can use Yast bootloader to make that change. Maybe booting the installer to the rescue system or using it to boot your system can work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/2019 05.20, Neil Rickert wrote:
On 4/25/19 6:34 PM, Mark Misulich wrote:
I'm trying to install 15.1 on a computer on the second hard drive. That is /dev/sdb. In the installation readout for booting, the mbr keeps on coming up as /dev/sdb. But my mbr is esconsced in /dev/sda. I can't find a way to change the installation to boot from the mbr in /dev/sda. Everything I have tried reports to me that the 15.1 installation won't boot. No surprise, it doesn't.
In the boot settings, check the box for "Custom boot partition" and then enter "/dev/sda" in the space provided.
However, this destroys whatever boot system might already exist on sda. Is it another Linux, a Windows...? -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2019-04-25 at 22:20 -0500, Neil Rickert wrote:
On 4/25/19 6:34 PM, Mark Misulich wrote:
I'm trying to install 15.1 on a computer on the second hard drive. That is /dev/sdb. In the installation readout for booting, the mbr keeps on coming up as /dev/sdb. But my mbr is esconsced in /dev/sda. I can't find a way to change the installation to boot from the mbr in /dev/sda. Everything I have tried reports to me that the 15.1 installation won't boot. No surprise, it doesn't.
In the boot settings, check the box for "Custom boot partition" and then enter "/dev/sda" in the space provided.
If you are able to boot your installed system, you can use Yast bootloader to make that change. Maybe booting the installer to the rescue system or using it to boot your system can work.
I did try to make the changes you suggested, but the installion software kept giving me a message that the system wouldn't boot with that configuration. So I didn't execute the change. Maybe it would have worked, or not, in spite of the warning message, I don't know. I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition. I booted into 15.0, and used yast to rewrite the grub menu. It picked up the installed 15.1 system which I couldn't boot, and wrote it into the mbr on /dev/sda. I can boot the 15.1 system now. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before. Booting two different Linux on the same disk is not plug and play, you have to do work yourself. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 26 Apr 2019 19:49:32 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself.
That seems counter-intuitive. I'd have thought that scenario was: - at least as common as dual-boot with e.g. windows, especially among developers/testers - more fully controllable - easier to fix in the case of problems So I'm curious if there are reasons why, or if it's just lack of bandwidth? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/2019 21.28, Dave Howorth wrote:
On Fri, 26 Apr 2019 19:49:32 +0200 "Carlos E. R." <> wrote:
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself.
That seems counter-intuitive. I'd have thought that scenario was: - at least as common as dual-boot with e.g. windows, especially among developers/testers
Certainly.
- more fully controllable
It is, manually :-)
- easier to fix in the case of problems
It is and it ain't :-)
So I'm curious if there are reasons why, or if it's just lack of bandwidth?
It just is. It is easier if the machine is UEFI, because UEFI does contemplate multiple bootable systems. But BIOS was designed for a single operating system: to boot "others" hacks had to be designed. LILO, GRUB... Possibilities - the one I prefer: Install generic boot code on MBR (preferably from syslinux) Install each LINUX system with GRUB on the "/" or root partition. Mark the main one as "bootable" in the partition table (classic or GPT). Changing which is the main one is as simple as putting the boot mark on another partition. Each Linux must "probe" for other systems to be able to load the "other". Alternatively, edit manually "/boot/grub2/custom.cfg" to chain load the other grubs. The other method, is to have a system as main, with grub in the MBR. The second system must be told to install Grub into root (and it will complain that it is not bootable). Then probing on the first system will locate the second. Or, edit manually "/boot/grub2/custom.cfg". Notice that letting one system find the other must be repeated each time the kernel in the second system changes. If each system is told to install on MBR, each time grub is updated may take away booting from the other system. This is not tidy. There is no option to tell YaST that you are installing a second Linux. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself. Eh, I have both Leap 15.0 and TW on the same SSD, never had any issues. The only thing I did, since TW is my workhorse, have TW have control over GRUB. I wouldn't call that work.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/2019 21.32, Knurpht-openSUSE wrote:
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself. Eh, I have both Leap 15.0 and TW on the same SSD, never had any issues. The only thing I did, since TW is my workhorse, have TW have control over GRUB. I wouldn't call that work.
You have to know that the second install must not install GRUB on the MBR or it destroys the boot of the first install. And YaST will complain that the system is not bootable, has to be booted from the first system. That's a bit of work. To improve it you must do further work :-) -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-04-26 01:41 PM, Carlos E. R. wrote:
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition. You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself. Eh, I have both Leap 15.0 and TW on the same SSD, never had any issues. The only thing I did, since TW is my workhorse, have TW have control over GRUB. I wouldn't call that work. You have to know that the second install must not install GRUB on the MBR or it destroys the boot of the first install. And YaST will complain
On 26/04/2019 21.32, Knurpht-openSUSE wrote: that the system is not bootable, has to be booted from the first system.
That's a bit of work. To improve it you must do further work :-)
Is anyone even installing the boot loader into the MBR anymore? (well, except for Windows, of course) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op vrijdag 26 april 2019 21:49:44 CEST schreef Darryl Gregorash:
On 2019-04-26 01:41 PM, Carlos E. R. wrote:
On 26/04/2019 21.32, Knurpht-openSUSE wrote:
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself.
Eh, I have both Leap 15.0 and TW on the same SSD, never had any issues. The only thing I did, since TW is my workhorse, have TW have control over GRUB. I wouldn't call that work.
You have to know that the second install must not install GRUB on the MBR or it destroys the boot of the first install. And YaST will complain that the system is not bootable, has to be booted from the first system.
That's a bit of work. To improve it you must do further work :-)
Is anyone even installing the boot loader into the MBR anymore? (well, except for Windows, of course) Not me.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/2019 21.49, Darryl Gregorash wrote:
On 2019-04-26 01:41 PM, Carlos E. R. wrote:
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition. You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself. Eh, I have both Leap 15.0 and TW on the same SSD, never had any issues. The only thing I did, since TW is my workhorse, have TW have control over GRUB. I wouldn't call that work. You have to know that the second install must not install GRUB on the MBR or it destroys the boot of the first install. And YaST will complain
On 26/04/2019 21.32, Knurpht-openSUSE wrote: that the system is not bootable, has to be booted from the first system.
That's a bit of work. To improve it you must do further work :-)
Is anyone even installing the boot loader into the MBR anymore? (well, except for Windows, of course)
I don't know, or don't remember. I always watch for it and change it if so. On a BIOS machine with Windows any automatic setup will have problems, IMHO. The /correct/ way is described here: <https://nwrickert2.wordpress.com/2015/06/15/generic-boot-code/> -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op vrijdag 26 april 2019 21:58:20 CEST schreef Carlos E. R.:
On 26/04/2019 21.49, Darryl Gregorash wrote:
On 2019-04-26 01:41 PM, Carlos E. R. wrote:
On 26/04/2019 21.32, Knurpht-openSUSE wrote:
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself.
Eh, I have both Leap 15.0 and TW on the same SSD, never had any issues. The only thing I did, since TW is my workhorse, have TW have control over GRUB. I wouldn't call that work.
You have to know that the second install must not install GRUB on the MBR or it destroys the boot of the first install. And YaST will complain that the system is not bootable, has to be booted from the first system.
That's a bit of work. To improve it you must do further work :-)
Is anyone even installing the boot loader into the MBR anymore? (well, except for Windows, of course)
I don't know, or don't remember. I always watch for it and change it if so.
On a BIOS machine with Windows any automatic setup will have problems, IMHO. The /correct/ way is described here:
<https://nwrickert2.wordpress.com/2015/06/15/generic-boot-code/> From 2015, and nothing changed since then ...... These days most machines are UEFI based. Why do you stick to outdated methods. Installing multiple linuces on one system, one disk are not an issue. Sticking to old methods is.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/2019 22.02, Knurpht-openSUSE wrote:
Op vrijdag 26 april 2019 21:58:20 CEST schreef Carlos E. R.:
On 26/04/2019 21.49, Darryl Gregorash wrote:
On 2019-04-26 01:41 PM, Carlos E. R. wrote:
On 26/04/2019 21.32, Knurpht-openSUSE wrote:
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
On 26/04/2019 15.56, Mark Misulich wrote: > I did find a way to resolve this problem, however. The computer > is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself.
Eh, I have both Leap 15.0 and TW on the same SSD, never had any issues. The only thing I did, since TW is my workhorse, have TW have control over GRUB. I wouldn't call that work.
You have to know that the second install must not install GRUB on the MBR or it destroys the boot of the first install. And YaST will complain that the system is not bootable, has to be booted from the first system.
That's a bit of work. To improve it you must do further work :-)
Is anyone even installing the boot loader into the MBR anymore? (well, except for Windows, of course)
I don't know, or don't remember. I always watch for it and change it if so.
On a BIOS machine with Windows any automatic setup will have problems, IMHO. The /correct/ way is described here:
<https://nwrickert2.wordpress.com/2015/06/15/generic-boot-code/> From 2015, and nothing changed since then ...... These days most machines are UEFI based. Why do you stick to outdated methods.
Well, this machine is not UEFI, nor is my main laptop. And I suspect that the OP's is neither. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 2019-04-26 at 21:32 +0200, Knurpht-openSUSE wrote:
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
On 26/04/2019 15.56, Mark Misulich wrote:
I did find a way to resolve this problem, however. The computer is a multiboot, with Opensuse 15.0 on a separate partition.
You failed to say that before.
Booting two different Linux on the same disk is not plug and play, you have to do work yourself.
Eh, I have both Leap 15.0 and TW on the same SSD, never had any issues. The only thing I did, since TW is my workhorse, have TW have control over GRUB. I wouldn't call that work.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team
Carlos, you're right, I didn't say that before. I didn't realize that it was an issue, or I could have mentioned it. Anyways, thanks for providing your input to help me out. But more precisely I didn't mention it because the two opensuse systems aren't on the same disk, they are on the same computer. Opensuse 15.0 is on /dev/sda, and I installed Opensuse 15.1 on /dev/sdb. That caused the problem I was trying to solicit help on the mail list to resolve. Opensuse 15.1 designated /dev/sdb as the default place to store the mbr, and I couldn't find a way to change that during installation to /dev/sda. What was an issue for me here was that I couldn't write the 15.1 boot to the mbr on /dev/sda when I was installing the 15.1 operating system on the dev/sdb disk. I still don't know how to accomplish that, other than the way I found around the problem. Kind of a lucky guess that got me out of the difficulty. Maybe the warnings from the installation software that the system wouldn't boot if I selected /dev/sda as the boot partition were wrong and I should have disregarded them. If there was only one hard drive, there wouldn't have been any issue. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/2019 22.08, Mark Misulich wrote:
On Fri, 2019-04-26 at 21:32 +0200, Knurpht-openSUSE wrote:
Op vrijdag 26 april 2019 19:49:32 CEST schreef Carlos E. R.:
Carlos, you're right, I didn't say that before. I didn't realize that it was an issue, or I could have mentioned it. Anyways, thanks for providing your input to help me out.
But more precisely I didn't mention it because the two opensuse systems aren't on the same disk, they are on the same computer.
Ok, then that's another important thing to know about, it changes things again :-) Another question: is your machine UEFI or BIOS?
Opensuse 15.0 is on /dev/sda, and I installed Opensuse 15.1 on /dev/sdb. That caused the problem I was trying to solicit help on the mail list to resolve. Opensuse 15.1 designated /dev/sdb as the default place to store the mbr, and I couldn't find a way to change that during installation to /dev/sda.
I would have to try an install to see, but what you were attempting would break the 15.0 boot.
What was an issue for me here was that I couldn't write the 15.1 boot to the mbr on /dev/sda when I was installing the 15.1 operating system on the dev/sdb disk. I still don't know how to accomplish that, other than the way I found around the problem. Kind of a lucky guess that got me out of the difficulty. Maybe the warnings from the installation software that the system wouldn't boot if I selected /dev/sda as the boot partition were wrong and I should have disregarded them. If there was only one hard drive, there wouldn't have been any issue.
The /correct/ way to install is what yast suggested, Grub on MBR of /dev/sdb (by the way, that YaST suggests this, is what makes me think it is not UEFI system). As I mentioned on another post: Generic boot code on MBR of /dev/sdb Grub on "/" partition (or separate /boot if it exists). Mark "/" as bootable in partition table. or Grub on MBR of /dev/sdb Then, two procedures. Change boot order in BIOS: sdb must boot first. or Boot sda and make grub to probe for other systems. Note that this must be repeated if second system updates the kernel. Third procedure: Edit "/boot/grub2/custom.cfg" to add an entry to the second grub. If you are interested in this one, I'll post details. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/25/2019 06:34 PM, Mark Misulich wrote:
Hi, I'm not sure if this is the correct forum for 15.1, but since I don't know I thought I would give it a try.
I'm trying to install 15.1 on a computer on the second hard drive. That is /dev/sdb. In the installation readout for booting, the mbr keeps on coming up as /dev/sdb. But my mbr is esconsced in /dev/sda. I can't find a way to change the installation to boot from the mbr in /dev/sda. Everything I have tried reports to me that the 15.1 installation won't boot. No surprise, it doesn't.
Any ideas how to change this?
Mark
Strange, If I understand you are installing to /dev/sdb (with normal partitions) and you have an existing OS on /dev/sda, if os-prober is installed (generally is by default), the installer, in the past, would see and setup grub to provide boot options for your existing OS as well as your install on /dev/sdb. (which did produce some unwanted modificaitons of /dev/sda in the past, setup all OSs to boot) If that is no longer occurring, you can tell grub to use /dev/sdb as the first drive in the system by creating a /boot/grub2/device.map which allows you to tell grup which to use as hd0 and hd1. For example: (hd0) /dev/sdb (hd1) /dev/sda would order the drives so grub uses /dev/sdb as the first drive and /dev/sda as the second. See: https://www.gnu.org/software/grub/manual/grub/grub.html#Device-syntax -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Carlos E. R. -
Darryl Gregorash -
Dave Howorth -
David C. Rankin -
Knurpht-openSUSE -
Mark Misulich -
Neil Rickert