[opensuse] grub2 enigma

newer
[opensuse] DHCP server, VLAN and...

older
[opensuse] cups and init open port...

Basil Chupin

20 Aug 2013 20 Aug '13

12:03

Can anyone please provide an answer or suggest some doc. to read (but NOT a manual :-( ) which would provide me with the answer. Searching the web has not really provided an answer. The problem is with grub2. To begin: I have 2 HDDs - sda and sdb - both sitting in mobile racks. I have the following systems installed on these 2 drives: sda3 openSUSE 12.2 sda5 opensuse 12.3 sda6 Tumbleweed (12.3) sda7 Ubuntu 13.04 sda8 openSUSE 13.1 Milestone #4 sdb1 Windows #7 In addition I have a separate bootloader which contained/contains grub.cfg which will boot (or did boot) all and any of the above. This bootloader is sitting in sda1 and I mount it manually in /mnt/btldr when required. I orginally installed 12.2 on sda3 and then installed Windows on sdb1 (to do this Win installation I removed sda from the box and Windows was able to install its bootloader in the MBR for sdb). After this was done I mounted sda1 - the btldr partition - and ran: grub2-install --root-directory=/mnt/btldr /dev/sda followed by (2) grub2-mkconfig -o /mnt/btldr/boot/grub2/grub.cfg to populate the grub.cfg in the /btldr/boot/grub2/. This was working fine for months even after I added 12.3, Tumbleweed, Ubuntu, and Milestone 1, 2, and 3. However, something went dodgy and now if I boot into 12.2 and run (2) above oS 12.3 on sda5 is not recognised in the btldr; yet running grub2-mkconfig -o /boot/grub2/grub.cfg in 12.2 does see sda5 - but is left out in btldr. The "reverse" happens if I manage (using smoke and mirrors) to boot into 12.3 and then 12.2 (on sda3) is omitted from btldr when I run (2). I have used the Ubuntu's Boot Rescue Disk and while the first time I used it (a couple of weeks ago) it recognised all of the systems but when I ran it again earlier tonight it did not recognise 12.3 on sda5. I really wish I knew what to do to get back to where I was before this dodgy-thing struck and therefore be able to boot into all of the systems I have currently installed. So if anyone can throw some light on how to overcome this dilemma please advise me. (The inability to create the correct grub menu by running grub2-mkconfig -o /mnt/btldr/boot/grub2/grub.cfg is preventing the upgrading of new versions of the kernel because I need to boot into level 3 in order to compile the nvidia driver for the new kernel.) BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Show replies by date

Andrey Borzenkov

20 Aug 20 Aug

12:22

On Tue, Aug 20, 2013 at 4:03 PM, Basil Chupin wrote:

...

The "reverse" happens if I manage (using smoke and mirrors) to boot into 12.3 and then 12.2 (on sda3) is omitted from btldr when I run (2).

Boot into 12.3, run os-prober (literal command), paste output and also paste messages in /var/log/messages during os-prober run (you can notice time before and time after and cut lines in between). Or simply upload full /var/log/message to susepaste.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin

12:29

On 20/08/13 22:22, Andrey Borzenkov wrote:

...

On Tue, Aug 20, 2013 at 4:03 PM, Basil Chupin wrote:

...
The "reverse" happens if I manage (using smoke and mirrors) to boot into 12.3 and then 12.2 (on sda3) is omitted from btldr when I run (2).

Boot into 12.3, run os-prober (literal command), paste output and also paste messages in /var/log/messages during os-prober run (you can notice time before and time after and cut lines in between). Or simply upload full /var/log/message to susepaste.org

Unfortunately, this time 'round it is 12.3 which I cannot boot into so will booting into 12.2 do? BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov

12:35

On Tue, Aug 20, 2013 at 4:29 PM, Basil Chupin wrote:

...

On 20/08/13 22:22, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 4:03 PM, Basil Chupin wrote:

...
The "reverse" happens if I manage (using smoke and mirrors) to boot into 12.3 and then 12.2 (on sda3) is omitted from btldr when I run (2).

Boot into 12.3, run os-prober (literal command), paste output and also paste messages in /var/log/messages during os-prober run (you can notice time before and time after and cut lines in between). Or simply upload full /var/log/message to susepaste.org

Unfortunately, this time 'round it is 12.3 which I cannot boot into so will booting into 12.2 do?

Yes. It is just that there were quite a number of fixes in 12.3, but let's do it first. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin

13:06

On 20/08/13 22:35, Andrey Borzenkov wrote:

...

On Tue, Aug 20, 2013 at 4:29 PM, Basil Chupin wrote:

...
On 20/08/13 22:22, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 4:03 PM, Basil Chupin wrote:

...
The "reverse" happens if I manage (using smoke and mirrors) to boot into 12.3 and then 12.2 (on sda3) is omitted from btldr when I run (2).

Boot into 12.3, run os-prober (literal command), paste output and also paste messages in /var/log/messages during os-prober run (you can notice time before and time after and cut lines in between). Or simply upload full /var/log/message to susepaste.org

Unfortunately, this time 'round it is 12.3 which I cannot boot into so will booting into 12.2 do?

Yes. It is just that there were quite a number of fixes in 12.3, but let's do it first.

(I suspected that there were some changes between 12.2 and 12.3.) Here is the link to the output of os-prober and section of /log/messages: http://susepaste.org/83010800 BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov

13:25

On Tue, Aug 20, 2013 at 5:06 PM, Basil Chupin wrote:

...

(I suspected that there were some changes between 12.2 and 12.3.)

Here is the link to the output of os-prober and section of /log/messages:

http://susepaste.org/83010800

It shows /dev/sda5:openSUSE 12.3 (x86_64):SUSE:linux /dev/sda6:openSUSE 12.3 (x86_64):SUSE1:linux So it is obvuiouly is detected by os-prober. Now could you explain what exactly "if I boot into 12.2 and run (2) above oS 12.3 on sda5 is not recognised in the btldr" means? You do not get openSUSE 12.3 in boot menu? You get it in boot menu but it does not boot or it boots wrong OS? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin

13:46

On 20/08/13 23:25, Andrey Borzenkov wrote:

...

On Tue, Aug 20, 2013 at 5:06 PM, Basil Chupin wrote:

...
(I suspected that there were some changes between 12.2 and 12.3.)

Here is the link to the output of os-prober and section of /log/messages:

http://susepaste.org/83010800 It shows

/dev/sda5:openSUSE 12.3 (x86_64):SUSE:linux /dev/sda6:openSUSE 12.3 (x86_64):SUSE1:linux

So it is obvuiouly is detected by os-prober. Now could you explain what exactly

"if I boot into 12.2 and run (2) above oS 12.3 on sda5 is not recognised in the btldr"

means? You do not get openSUSE 12.3 in boot menu? You get it in boot menu but it does not boot or it boots wrong OS?

In 12.2 I can run grub2-mkconfig -o /boot/etc and I can see that both versions of 12.3 (on sda5 and on sda6) are recognised and are in the grub.cfg but sda5 does not show in the menu when the computer is booted. Copy of grub.cfg which is generated by grub2-mkconfig -o /mnt/btldr/boot/grub2/grub.cfg (and from which the menu is created) is: http://susepaste.org/21776310 BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov

13:58

On Tue, Aug 20, 2013 at 5:46 PM, Basil Chupin wrote:

...

On 20/08/13 23:25, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 5:06 PM, Basil Chupin wrote:

...
(I suspected that there were some changes between 12.2 and 12.3.)

Here is the link to the output of os-prober and section of /log/messages:

http://susepaste.org/83010800

It shows

/dev/sda5:openSUSE 12.3 (x86_64):SUSE:linux /dev/sda6:openSUSE 12.3 (x86_64):SUSE1:linux

So it is obvuiouly is detected by os-prober. Now could you explain what exactly

"if I boot into 12.2 and run (2) above oS 12.3 on sda5 is not recognised in the btldr"

means? You do not get openSUSE 12.3 in boot menu? You get it in boot menu but it does not boot or it boots wrong OS?

In 12.2 I can run grub2-mkconfig -o /boot/etc and I can see that both versions of 12.3 (on sda5 and on sda6) are recognised and are in the grub.cfg

No. What you see for /dev/sda5 is part of Ubuntu menu (and should have been skipped but that's another story). Could you please show what linux-boot-prober /dev/sda5 linux-boot-prober /dev/sda6 output? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin

14:06

On 20/08/13 23:58, Andrey Borzenkov wrote:

...

On Tue, Aug 20, 2013 at 5:46 PM, Basil Chupin wrote:

...
On 20/08/13 23:25, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 5:06 PM, Basil Chupin wrote:

...
(I suspected that there were some changes between 12.2 and 12.3.)

Here is the link to the output of os-prober and section of /log/messages:

http://susepaste.org/83010800 It shows

/dev/sda5:openSUSE 12.3 (x86_64):SUSE:linux /dev/sda6:openSUSE 12.3 (x86_64):SUSE1:linux

So it is obvuiouly is detected by os-prober. Now could you explain what exactly

"if I boot into 12.2 and run (2) above oS 12.3 on sda5 is not recognised in the btldr"

means? You do not get openSUSE 12.3 in boot menu? You get it in boot menu but it does not boot or it boots wrong OS?

In 12.2 I can run grub2-mkconfig -o /boot/etc and I can see that both versions of 12.3 (on sda5 and on sda6) are recognised and are in the grub.cfg No. What you see for /dev/sda5 is part of Ubuntu menu (and should have been skipped but that's another story).

Could you please show what

linux-boot-prober /dev/sda5 linux-boot-prober /dev/sda6

output?

Probing sda5 produces a NIL output but sda6 produces: /dev/sda6:/dev/sda6::/boot/vmlinuz-3.9.2-8.g04040b9-desktop:/boot/initrd-3.9.2-8.g04040b9-desktop:root=/dev/sda6 /dev/sda6:/dev/sda6::/boot/vmlinux-3.9.2-8.g04040b9-desktop.gz::root=/dev/sda6 BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov

14:14

On Tue, Aug 20, 2013 at 6:06 PM, Basil Chupin wrote:

...

...
Could you please show what

linux-boot-prober /dev/sda5 linux-boot-prober /dev/sda6

output?

Probing sda5 produces a NIL output

Which is the reason why you do not see it in menu. Could you paste /var/log/messages related to this run? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin

14:36

On 21/08/13 00:14, Andrey Borzenkov wrote:

...

On Tue, Aug 20, 2013 at 6:06 PM, Basil Chupin wrote:

...
...
Could you please show what

linux-boot-prober /dev/sda5 linux-boot-prober /dev/sda6

output?

Probing sda5 produces a NIL output Which is the reason why you do not see it in menu. Could you paste /var/log/messages related to this run?

The extract from 'messages' from around the time I ran the probes on sda5 and sda6: http://susepaste.org/64565242 BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov

14:40

On Tue, Aug 20, 2013 at 6:36 PM, Basil Chupin wrote:

...

On 21/08/13 00:14, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 6:06 PM, Basil Chupin wrote:

...
...
Could you please show what

linux-boot-prober /dev/sda5 linux-boot-prober /dev/sda6

output?

Probing sda5 produces a NIL output

Which is the reason why you do not see it in menu. Could you paste /var/log/messages related to this run?

The extract from 'messages' from around the time I ran the probes on sda5 and sda6:

50mounted-tests: debug: found boot partition /dev/sda1 for linux system on /dev/sda5 Is it correct? As far as I understood you, your /dev/sda1 is "special" standalone partition that normally is not mounted anywhere? What *is* in this partition? mount -r /dev/sda1 /mnt ls -lR /mnt ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin

14:51

On 21/08/13 00:40, Andrey Borzenkov wrote:

...

On Tue, Aug 20, 2013 at 6:36 PM, Basil Chupin wrote:

...
On 21/08/13 00:14, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 6:06 PM, Basil Chupin wrote:

...
...
Could you please show what

linux-boot-prober /dev/sda5 linux-boot-prober /dev/sda6

output?

Probing sda5 produces a NIL output Which is the reason why you do not see it in menu. Could you paste /var/log/messages related to this run?

The extract from 'messages' from around the time I ran the probes on sda5 and sda6:

50mounted-tests: debug: found boot partition /dev/sda1 for linux system on /dev/sda5

Is it correct? As far as I understood you, your /dev/sda1 is "special" standalone partition that normally is not mounted anywhere? What *is* in this partition?

mount -r /dev/sda1 /mnt ls -lR /mnt

? Output:

http://susepaste.org/77298057 The /boot_br is the directory which Boot Rescue Disk creates and the /boot is one I created from a backup of /btldr. BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov

16:09

В Wed, 21 Aug 2013 00:51:56 +1000 Basil Chupin пишет:

...

On 21/08/13 00:40, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 6:36 PM, Basil Chupin wrote:

...
On 21/08/13 00:14, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 6:06 PM, Basil Chupin wrote:

...
...
Could you please show what

linux-boot-prober /dev/sda5 linux-boot-prober /dev/sda6

output?

Probing sda5 produces a NIL output Which is the reason why you do not see it in menu. Could you paste /var/log/messages related to this run?

The extract from 'messages' from around the time I ran the probes on sda5 and sda6:

50mounted-tests: debug: found boot partition /dev/sda1 for linux system on /dev/sda5

Is it correct? As far as I understood you, your /dev/sda1 is "special" standalone partition that normally is not mounted anywhere? What *is* in this partition?

mount -r /dev/sda1 /mnt ls -lR /mnt

? Output:

http://susepaste.org/77298057

The /boot_br is the directory which Boot Rescue Disk creates and the /boot is one I created from a backup of /btldr.

Please show /etc/fstab from /dev/sda5. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin

21 Aug 21 Aug

00:18

On 21/08/13 02:09, Andrey Borzenkov wrote:

...

� Wed, 21 Aug 2013 00:51:56 +1000 Basil Chupin ��:

...
On 21/08/13 00:40, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 6:36 PM, Basil Chupin wrote:

...
On 21/08/13 00:14, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 6:06 PM, Basil Chupin wrote:

...
> Could you please show what > > linux-boot-prober /dev/sda5 > linux-boot-prober /dev/sda6 > > output? Probing sda5 produces a NIL output Which is the reason why you do not see it in menu. Could you paste /var/log/messages related to this run? The extract from 'messages' from around the time I ran the probes on sda5 and sda6:

50mounted-tests: debug: found boot partition /dev/sda1 for linux system on /dev/sda5

Is it correct? As far as I understood you, your /dev/sda1 is "special" standalone partition that normally is not mounted anywhere? What *is* in this partition?

mount -r /dev/sda1 /mnt ls -lR /mnt

? Output:

http://susepaste.org/77298057

The /boot_br is the directory which Boot Rescue Disk creates and the /boot is one I created from a backup of /btldr.

Please show /etc/fstab from /dev/sda5.

fstab on sda5 (12.3): http://susepaste.org/68134960 BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov

02:35

В Wed, 21 Aug 2013 10:18:09 +1000 Basil Chupin пишет:

...

On 21/08/13 02:09, Andrey Borzenkov wrote:

...
� Wed, 21 Aug 2013 00:51:56 +1000 Basil Chupin ��:

...
On 21/08/13 00:40, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 6:36 PM, Basil Chupin wrote:

...
On 21/08/13 00:14, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 6:06 PM, Basil Chupin wrote: >> Could you please show what >> >> linux-boot-prober /dev/sda5 >> linux-boot-prober /dev/sda6 >> >> output? > Probing sda5 produces a NIL output Which is the reason why you do not see it in menu. Could you paste /var/log/messages related to this run? The extract from 'messages' from around the time I ran the probes on sda5 and sda6:

50mounted-tests: debug: found boot partition /dev/sda1 for linux system on /dev/sda5

Is it correct? As far as I understood you, your /dev/sda1 is "special" standalone partition that normally is not mounted anywhere? What *is* in this partition?

mount -r /dev/sda1 /mnt ls -lR /mnt

? Output:

http://susepaste.org/77298057

The /boot_br is the directory which Boot Rescue Disk creates and the /boot is one I created from a backup of /btldr.

Please show /etc/fstab from /dev/sda5.

fstab on sda5 (12.3):

http://susepaste.org/68134960

Well ... UUID=979f1826-87bf-49e4-ac95-8726a2e1c9e4 /boot ext4 defaults 0 2 Aug 21 00:02:22 linux-860j 50mounted-tests: debug: mapped UUID=979f1826-87bf-49e4-ac95-8726a2e1c9e4 to /dev/sda1 So your system on /dev/sda5 is configured to use /dev/sda1 as /boot. But according to content of /dev/sda1 you provided this is wrong - /dev/sda1 does not have any vmlilnuz-* file to start with. So you need to decide what is /boot in this case and fix it. Probably by removing entry from fstab. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin

06:23

On 21/08/13 12:35, Andrey Borzenkov wrote:

...

В Wed, 21 Aug 2013 10:18:09 +1000 Basil Chupin пишет:

...
On 21/08/13 02:09, Andrey Borzenkov wrote:

...
� Wed, 21 Aug 2013 00:51:56 +1000 Basil Chupin ��:

...
On 21/08/13 00:40, Andrey Borzenkov wrote:

...
On Tue, Aug 20, 2013 at 6:36 PM, Basil Chupin wrote:

...
On 21/08/13 00:14, Andrey Borzenkov wrote: > On Tue, Aug 20, 2013 at 6:06 PM, Basil Chupin > wrote: >>> Could you please show what >>> >>> linux-boot-prober /dev/sda5 >>> linux-boot-prober /dev/sda6 >>> >>> output? >> Probing sda5 produces a NIL output > Which is the reason why you do not see it in menu. Could you paste > /var/log/messages related to this run? The extract from 'messages' from around the time I ran the probes on sda5 and sda6:

50mounted-tests: debug: found boot partition /dev/sda1 for linux system on /dev/sda5

Is it correct? As far as I understood you, your /dev/sda1 is "special" standalone partition that normally is not mounted anywhere? What *is* in this partition?

mount -r /dev/sda1 /mnt ls -lR /mnt

? Output:

http://susepaste.org/77298057

The /boot_br is the directory which Boot Rescue Disk creates and the /boot is one I created from a backup of /btldr.

Please show /etc/fstab from /dev/sda5. fstab on sda5 (12.3):

http://susepaste.org/68134960

Well ...

UUID=979f1826-87bf-49e4-ac95-8726a2e1c9e4 /boot ext4 defaults 0 2 Aug 21 00:02:22 linux-860j 50mounted-tests: debug: mapped UUID=979f1826-87bf-49e4-ac95-8726a2e1c9e4 to /dev/sda1

So your system on /dev/sda5 is configured to use /dev/sda1 as /boot. But according to content of /dev/sda1 you provided this is wrong - /dev/sda1 does not have any vmlilnuz-* file to start with. So you need to decide what is /boot in this case and fix it. Probably by removing entry from fstab.

Sheesh, is this the problem? There are 2 entries for this UUID in fstab: one is REMed out and the other active. I wonder what put that there in the first instance then REMed it out and then replaced it...... Damn little gremlins! I hate them! Anyway..... I have REMed out the second reference to that UUID (sda1) and reran grub2-mkconfig in 12.2 but of course I am still stuck with the (Ubuntu) Boot Repair Disk menu. I need to get rid of it and to do so I am proposing to do the following and would appreciate comment if what I want to do is the way to do it. In YaST>Bootloader I will alter the time delay figure which will trigger the replacement of the bootoader -- but here do I also rewrite the MBR or leave this alone? And I will use /boot where to boot from - correct? After doing the above I will run: grub2-install --root-directory=/mnt/btldr /dev/sda then (after mounting /sda1 [/btldr] and creating a blank grub.cfg in /mnt/btldr/grub2/) run: grub2-mkconfig -o /mnt/btldr/grub2/grub.cfg to populate the empty grub.cfg with the data for all the installed systems. Am I am on the right track, please, to get things back on track with getting rid of the Ubuntu menu, getting back to openSUSE boot time menu and having all the systems correctly listed for access? BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov

16:06

В Wed, 21 Aug 2013 16:23:41 +1000 Basil Chupin пишет:

...

I have REMed out the second reference to that UUID (sda1) and reran grub2-mkconfig in 12.2 but of course I am still stuck with the (Ubuntu) Boot Repair Disk menu. I need to get rid of it and to do so I am proposing to do the following and would appreciate comment if what I want to do is the way to do it.

In YaST>Bootloader I will alter the time delay figure which will trigger the replacement of the bootoader

Current openSUSE has a bug - it is impossible to reinstall grub2 (I cannot say to which extent it applies to other bootloaders) using YaST. It *never* reinstalls it, only changes grub.cfg https://bugzilla.novell.com/show_bug.cgi?id=819517 I wish it were fixed for 13.1 but judging by the total lack of activity it is unlikely.

...

-- but here do I also rewrite the MBR or leave this alone? And I will use /boot where to boot from - correct?

No idea. It is up to you. I'm not sure I understand your current or intended boot architecture so I'm not going to give advice what you need to do.

...

After doing the above I will run:

grub2-install --root-directory=/mnt/btldr /dev/sda

This should install grub2 on MBR of /dev/sda using filesystem on /mnt as module and configuration repository.

...

then (after mounting /sda1 [/btldr] and creating a blank grub.cfg in /mnt/btldr/grub2/) run:

grub2-mkconfig -o /mnt/btldr/grub2/grub.cfg

to populate the empty grub.cfg with the data for all the installed systems.

Am I am on the right track, please, to get things back on track with getting rid of the Ubuntu menu, getting back to openSUSE boot time menu and having all the systems correctly listed for access?

The obvious thing to check - whether /dev/sda your actual boot drive. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Andrey Borzenkov

16:15

В Wed, 21 Aug 2013 16:23:41 +1000 Basil Chupin пишет:

...

After doing the above I will run:

grub2-install --root-directory=/mnt/btldr /dev/sda

This installs grub into /mnt/btldr/boot/grub2

...

then (after mounting /sda1 [/btldr] and creating a blank grub.cfg in /mnt/btldr/grub2/) run:

grub2-mkconfig -o /mnt/btldr/grub2/grub.cfg

So it will expect /mnt/btldr/boot/grub2/grub.cfg, not path above. You probably want to use --boot-directory instead of --root-directory. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Basil Chupin

22 Aug 22 Aug

12:58

On 22/08/13 02:15, Andrey Borzenkov wrote:

...

� Wed, 21 Aug 2013 16:23:41 +1000 Basil Chupin ��:

...
After doing the above I will run:

grub2-install --root-directory=/mnt/btldr /dev/sda

This installs grub into /mnt/btldr/boot/grub2

...
then (after mounting /sda1 [/btldr] and creating a blank grub.cfg in /mnt/btldr/grub2/) run:

grub2-mkconfig -o /mnt/btldr/grub2/grub.cfg

So it will expect /mnt/btldr/boot/grub2/grub.cfg, not path above. You probably want to use --boot-directory instead of --root-directory.

'Spa-see-bo'. Thank you. Your help has now resulted in the system(s) coming back to normality. I have an openSUSE grub2 menu which shows all the bootable installed systems. The steps I took after I REMed out the reference to /dev/sda1 in fstab in oS 12.2 were: Taking into account the bug in YaST you mentioned, I altered the time out for the boot in the bootloader; this altered the grub.cfg as you mentioned. I did not select the option to rewrite the MBR, and left where grub2 should go as /boot. I then ran grub2-mkconfig -o /boot/grub2/grub.cfg Then I mounted /dev/sda1 to /mnt/btldr (which is the common bootloader for all systems) and deleted the /boot directory which was there (it will be recreated in the next step). Next I ran grub-install --root-directory=/mnt/btldr /dev/sda [**] which put grub2 into the MBR and in /mnt/btldr/ created /boot/grub2/ Following this I created an empty file called grub.cfg in /mnt/btldr/grub2/ and populated it by running grub2-mkconfig -o /mnt/btldr/boot/grub2/grub.cfg All this overwrote what the (Ubuntu) Boot Repair Disk produces and everything is now openSUSE-looking. Nice. Just for reference, I set up my grub2 for multi-system booting using this article: http://www.linuxidentity.com/us/down/articles/LSK_multi_distro_install_US.pd... but as it is written (again, grrrrrr..) with Ubuntu in mind one needs to adapt the grub commands used in the pdf for grub2 as used in oS (and Fedora?) [**] Using ".... --boot-directory=...." rather then "...-root-directory=...." created /mnt/btldr/grub2 and not what I had before /mnt/btldr/boot/grub2/ BC -- Using openSUSE 12.3, KDE 4.11.0 & kernel 3.10.5-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

3901

Age (days ago)

3903

Last active (days ago)

List overview

Download

19 comments

2 participants

participants (2)

Andrey Borzenkov
Basil Chupin

[opensuse] grub2 enigma

tags

participants (2)