[opensuse] Computer won't boot OS
Hi, after a recent update, I noticed on the grub screen that my multiboot with Win was no longer present, and the only option for boot was Opensuse 15.2, followed by the next line of Advanced options for boot Opensuse 15.2. I didn't consider that too much of an issue, as this has happened occasionally, and I just boot Opensuse, open Yast, and rerun the bootloader setup. I did this, and now I can't boot my laptop into either operating system. When I try to boot up, the computer boots to the password screen for the bios, then when I input the password, I get into the bios setup program. But things aren't right there, and I have no boot device setup menu in the boot configuration screen. I can't move around all the options in the bios, as the cursor won't move to the normal items in the menus. Once I save the settings to move beyond the bios setup screens in the boot process, the computer reboots to the bios password screen again. The process of saving the bios settings brings me back to the bios password screen each time the computer reboots. I can never get to the grub menu screen. If I try to boot into the shortcut boot device selection menu, using the appropriate key when I boot the computer, I can't get to that menu. The boot process takes me to the bios password input screen again. It seems that the bios may not be recognizing any options of boot devices, as it isn't listing any. I hope that I have described this using correct terminology so that the members of the list can understand the problem. The computer is a ASUS Q303 laptop. What I have tried to fix the problem: 1. I tried to boot using Supergrub2 disc via a usb connected external drive. But the drive never gets recognized, and I can't get to the Supergrub program. 2. I downloaded the bios software on another computer, and loaded it to a USB stick. Then I inserted the USB stick into the laptop and booted into the bios setup, where there is a selection for one to reflash the bios program. But the cursor won't move to that selection in the bios menu, so I can't reflash the bios. I had hoped that by reflashing the bios it might resolve the booting problem I would appreciate some help to resolve this problem. Thanks, Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/08/2020 21.27, Mark Misulich wrote:
2. I downloaded the bios software on another computer, and loaded it to a USB stick. Then I inserted the USB stick into the laptop and booted into the bios setup, where there is a selection for one to reflash the bios program. But the cursor won't move to that selection in the bios menu, so I can't reflash the bios. I had hoped that by reflashing the bios it might resolve the booting problem
I would appreciate some help to resolve this problem.
Could it be a keyboard issue? CMOS battery? Tried booting any rescue media on USB stick? -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 16/08/2020 21.27, Mark Misulich wrote:
2. I downloaded the bios software on another computer, and loaded it to a USB stick. Then I inserted the USB stick into the laptop and booted into the bios setup, where there is a selection for one to reflash the bios program. But the cursor won't move to that selection in the bios menu, so I can't reflash the bios. I had hoped that by reflashing the bios it might resolve the booting problem
I would appreciate some help to resolve this problem.
Could it be a keyboard issue? Hi Carlos, I don't think it is a keyboard issue. I had no problems before the attempt to reinstall the bootloader, and the keys allow me to move the cursor (highlighting) around the bios menu. But some parts of the bios
On Sun, 2020-08-16 at 21:45 +0200, Carlos E. R. wrote: menu don't seem to be active all of the sudden, that's what I mean when I write that I can't access them. It's what led me to think that the bootloader software must have messed up the bios software. But, I have to say that I'm not Mr. Computer Surgeon, so I could be all wrong about that. I should be able to access the function in the bios menu that allows me to reflash the bios, but the highlighting won't move to that and several other functions in the list. Other functions in that menu are accessible as I can move the highlighting up and down in the list to those functions, but they are of no use in resolving this problem. The keyboard itself had a bad key manifest itself about a year ago, so I bought a used serviceable keyboard and installed it in place of the malfunctioning keyboard. It has been working fine since, and seems to be working normally now.
CMOS battery?
I don't know specifically how to troubleshoot for a bad battery, but when I have had one go bad on a desktop motherboard on a desktop computer, the symptom was that it wouldn't hold computer time. I had to reset the date and time each time I booted the computer. My laptop hasn't had any such problem, and it has been booting normally even after the glitch with the grub menu not showing the second operating system. I have used it on opensuse alone for the last week, and had some time to try to resolve what I thought was a minor issue this afternoon by rerunning the boot loader software via yast. That was when the present problem occured.
Tried booting any rescue media on USB stick?
I haven't tried to boot any rescue media on USB, other than the external drive running the most current stable Supergrub2 disc. The external disc drive connects via USB. I have some things to attend at present, later this evening when I am free I will download the Supergrub software for USB stick and try it.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/08/2020 23.37, Mark Misulich wrote:
On 16/08/2020 21.27, Mark Misulich wrote:
2. I downloaded the bios software on another computer, and loaded it to a USB stick. Then I inserted the USB stick into the laptop and booted into the bios setup, where there is a selection for one to reflash the bios program. But the cursor won't move to that selection in the bios menu, so I can't reflash the bios. I had hoped that by reflashing the bios it might resolve the booting problem
I would appreciate some help to resolve this problem.
Could it be a keyboard issue? Hi Carlos, I don't think it is a keyboard issue. I had no problems before the attempt to reinstall the bootloader, and the keys allow me to move the cursor (highlighting) around the bios menu. But some parts of the bios
On Sun, 2020-08-16 at 21:45 +0200, Carlos E. R. wrote: menu don't seem to be active all of the sudden, that's what I mean when I write that I can't access them. It's what led me to think that the bootloader software must have messed up the bios software. But, I have to say that I'm not Mr. Computer Surgeon, so I could be all wrong about that. I should be able to access the function in the bios menu that allows me to reflash the bios, but the highlighting won't move to that and several other functions in the list. Other functions in that menu are accessible as I can move the highlighting up and down in the list to those functions, but they are of no use in resolving this problem.
The keyboard itself had a bad key manifest itself about a year ago, so I bought a used serviceable keyboard and installed it in place of the malfunctioning keyboard. It has been working fine since, and seems to be working normally now.
On desktops machines there can be a hidden button where the back connectors are to reset the BIOS. It is that accessible if the motherboard is designed for overclocking. Otherwise, there would be a jumper on the board to do it. You would have to see the documentation of the board to find it. Flashing the BIOS should be a last resource. More difficult if it is a laptop. Maybe what you are seeing is the BIOS mode for a plain user, not the admin. There would be two different passwords.
CMOS battery?
I don't know specifically how to troubleshoot for a bad battery, but when I have had one go bad on a desktop motherboard on a desktop computer, the symptom was that it wouldn't hold computer time.
That's the typical one, but can also corrupt the configuration. Although in that case the corruption should be detected and it would do a full self reset.
I had to reset the date and time each time I booted the computer. My laptop hasn't had any such problem, and it has been booting normally even after the glitch with the grub menu not showing the second operating system. I have used it on opensuse alone for the last week, and had some time to try to resolve what I thought was a minor issue this afternoon by rerunning the boot loader software via yast. That was when the present problem occured.
Tried booting any rescue media on USB stick?
I haven't tried to boot any rescue media on USB, other than the external drive running the most current stable Supergrub2 disc. The external disc drive connects via USB. I have some things to attend at present, later this evening when I am free I will download the Supergrub software for USB stick and try it.
I would try the openSUSE rescue image. <http://download.opensuse.org/distribution/leap/15.2/live/openSUSE-Leap-15.2-Rescue-CD-x86_64-Build31.142-Media.iso> -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 16/08/2020 23.37, Mark Misulich wrote:
On 16/08/2020 21.27, Mark Misulich wrote:
Tried booting any rescue media on USB stick? I haven't tried to boot any rescue media on USB, other than the external drive running the most current stable Supergrub2 disc. The external disc drive connects via USB. I have some things to attend at
On Sun, 2020-08-16 at 21:45 +0200, Carlos E. R. wrote: present, later this evening when I am free I will download the Supergrub software for USB stick and try it.
I would try the openSUSE rescue image.
< http://download.opensuse.org/distribution/leap/15.2/live/openSUSE-Leap-15.2-...
I tried to run the Supergrub2 software which I copied to a USB stick. When I booted the computer the bios recognized the USB stick, but I wasn't able to access the USB stick and the software after I selected
On Sun, 2020-08-16 at 23:50 +0200, Carlos E. R. wrote: the USB stick. It just went back to the password screen for the bios. Next, I downloaded the opensuse rescue cd for which you provided the link above. I wrote it to the USB stick and made it a bootable image using Suse Studio Imagewriter. When I put it in the USB port of the laptop and booted the laptop, I was able to boot the rescue software from the USB stick. After booting up the rescue system, I opened Yast and tried to run the bootloader software. The software ran to the point that an error window popped up. It says: YaST2 (on localhost.localdomain) Error Execution of command "[["/usr/bin/grub2-editnv","list"]]" failed. Exit code: 1 Error output: /usr/bin/grub2-editnv: error: failed to get canonical path of 'LiveOS_rootfs' When I clicked on "OK", another dialog box popped up. YaST2(on loacalhost.localdomain) Error YaST cannot configure the bootloader because it failed to find the root file system. OK I ran the boot loader software on my desktop for a comparison to see if I could remember any differences from the configuration presented on the laptop when I ran the bootloader software in yast on that machine. On the Boot Code Options tab, the desktop software has checked: Boot from Master Boot Record and below it the following two options are checked: Set active Flag in Partition Table for Boot Partition Write generic Boot Code to MBR On the laptop, I vaguely remember that it had the following selected Boot from Master Boot Record and below it Write generic Boot Code to MBR Could it be that the laptop Bootloader software should have also presented as checked, the option Set active Flag in Partition Table for Boot Partition If it wasn't checked, could that be the source of my present problem in booting, and how do I fix it? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 17/08/2020 04.43, Mark Misulich wrote:
On 16/08/2020 23.37, Mark Misulich wrote:
On 16/08/2020 21.27, Mark Misulich wrote:
Tried booting any rescue media on USB stick? I haven't tried to boot any rescue media on USB, other than the external drive running the most current stable Supergrub2 disc. The external disc drive connects via USB. I have some things to attend at
On Sun, 2020-08-16 at 21:45 +0200, Carlos E. R. wrote: present, later this evening when I am free I will download the Supergrub software for USB stick and try it.
I would try the openSUSE rescue image.
< http://download.opensuse.org/distribution/leap/15.2/live/openSUSE-Leap-15.2-...
I tried to run the Supergrub2 software which I copied to a USB stick. When I booted the computer the bios recognized the USB stick, but I wasn't able to access the USB stick and the software after I selected
On Sun, 2020-08-16 at 23:50 +0200, Carlos E. R. wrote: the USB stick. It just went back to the password screen for the bios.
Next, I downloaded the opensuse rescue cd for which you provided the link above. I wrote it to the USB stick and made it a bootable image using Suse Studio Imagewriter.
Nonono.... don't do anything. Just write the image to the USB as is. The image is already bootable. dd if=openSUSE-...iso of=/dev/sdX oflag=direct bs=16M or cp openSUSE-...iso /dev/sdX or cat openSUSE-...iso > /dev/sdX
When I put it in the USB port of the laptop and booted the laptop, I was able to boot the rescue software from the USB stick.
Ok, good.
After booting up the rescue system, I opened Yast and tried to run the bootloader software. The software ran to the point that an error window popped up. It says:
YaST2 (on localhost.localdomain)
Error
Execution of command "[["/usr/bin/grub2-editnv","list"]]" failed.
Exit code: 1
Error output: /usr/bin/grub2-editnv: error: failed to get canonical path of 'LiveOS_rootfs'
When I clicked on "OK", another dialog box popped up.
YaST2(on loacalhost.localdomain)
Error
YaST cannot configure the bootloader because it failed to find the root file system.
OK
I ran the boot loader software on my desktop for a comparison to see if I could remember any differences from the configuration presented on the laptop when I ran the bootloader software in yast on that machine. On the Boot Code Options tab, the desktop software has checked:
Boot from Master Boot Record
and below it the following two options are checked:
Set active Flag in Partition Table for Boot Partition
Write generic Boot Code to MBR
On the laptop, I vaguely remember that it had the following selected
Boot from Master Boot Record
and below it
Write generic Boot Code to MBR
Could it be that the laptop Bootloader software should have also presented as checked, the option
Set active Flag in Partition Table for Boot Partition
If it wasn't checked, could that be the source of my present problem in booting, and how do I fix it?
You mention the MBR, but I thought you were using UEFI? The system to boot is very different. The generic procedure to repair a system, would be (mutandis mutandi): mount /dev/sda3 /mnt # assuming sda3 is the faulty root system mount /dev/sda2 /mnt/boot # assuming sda2 is the separate # boot partition if it exists mount /dev/sda1 /mnt/boot/efi # assuming sda1 has the efi fat part, # if it exists. It doesn't if your # boot is "Classic" mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys mount --bind /dev /mnt/dev chroot /mnt You might have to edit /etc/mtab to match. If you need network, it might fail and you would have to edit some files. yast # Not yast2. You need the text version of yast, # running from the failed system, not from the # rescue system. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 8/16/20 10:43 PM, Mark Misulich wrote:
I ran the boot loader software on my desktop for a comparison to see if I could remember any differences from the configuration presented on the laptop when I ran the bootloader software in yast on that machine. On the Boot Code Options tab, the desktop software has checked:
Boot from Master Boot Record
and below it the following two options are checked:
Set active Flag in Partition Table for Boot Partition
Write generic Boot Code to MBR
On the laptop, I vaguely remember that it had the following selected
Boot from Master Boot Record
and below it
Write generic Boot Code to MBR
Could it be that the laptop Bootloader software should have also presented as checked, the option
Set active Flag in Partition Table for Boot Partition
If it wasn't checked, could that be the source of my present problem in booting, and how do I fix it?
Those sound like instructions if you want to enable "legacy" booting. It used to be that you could set the bootable flag in "fdisk". Like much else, this has been changed. Still, at a command line you'd go into fdisk -- like (as root) "fdisk /dev/sda" (or whatever your boot drive is mounted as) -- then hit "x" to get into the "expert" menu, then "A" to "toggle the legacy BIOS bootable flag". If you've never used fdisk before, use "p" to print the partition table (mentioned in the output you included above) and use "m" to bring up the menus in fdisk. If you aren't absolutely sure about what you've done in fdisk, you can always hit "q" to quite without writing any of the changes you've made. hth. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 2020-08-16 at 23:50 +0200, Carlos E. R. wrote:
On 16/08/2020 23.37, Mark Misulich wrote:
On 16/08/2020 21.27, Mark Misulich wrote: I haven't tried to boot any rescue media on USB, other than the external drive running the most current stable Supergrub2 disc. The external disc drive connects via USB. I have some things to attend at
On Sun, 2020-08-16 at 21:45 +0200, Carlos E. R. wrote: present, later this evening when I am free I will download the Supergrub software for USB stick and try it.
Here's an update. After I sent the previous message with details about using the opensuse rescue CD software, I realized that maybe I could make the Supergrub2 software bootable on the USB stick, so that is what I did. I used the USB stick with the bootable Supergrub software to boot into my opensuse 15.2 system located on my laptop's harddrive. I then opened Yast and ran the bootloader software, marking Set active Flag in Partition Table for Boot Partition I rebooted, and still have the issue where the password dialogue box presents, then I have to save bios settings and exit. It won't boot into the installed opensuse system unless I use the hot key to go to boot options menu when the bios starts to boot, and then select the USB stick with the bootable Supergrub2 software on the next screen after the password screen. Once the Supergrub menu presents, I can select and boot my opensuse system, but not Windows.
I would try the openSUSE rescue image.
< http://download.opensuse.org/distribution/leap/15.2/live/openSUSE-Leap-15.2-...
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 17/08/2020 à 05:29, Mark Misulich a écrit :
Set active Flag in Partition Table for Boot Partition
this is only necessary if you have "BIOS" system (AKA not UEFI)
I would try the openSUSE rescue image.
if you boot a rescue system, you can go root in your openSUSE install with the commands given here: http://www.dodin.org/wiki/pmwiki.php?n=Doc.AccesRootAvecOpensuseRescue using the keyboard arrows makes it very easy to type but the persistence of your problem make me wondering of the state of your computer mobo or hdd :-( *Some* laptops are very easy to disassemble, some are very difficult. I published some video showing that here: https://www.culte.org/pmwiki/?n=Rubriques.CommentDMonterUnPCPortable the video are in french, but are self-explanatory. They are *not* a tutorial, only a way to understand the rationale behind the dismounting, every laptop is special :-(. jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 8/16/20 11:29 PM, Mark Misulich wrote:
On Sun, 2020-08-16 at 23:50 +0200, Carlos E. R. wrote:
On 16/08/2020 23.37, Mark Misulich wrote:
On 16/08/2020 21.27, Mark Misulich wrote: I haven't tried to boot any rescue media on USB, other than the external drive running the most current stable Supergrub2 disc. The external disc drive connects via USB. I have some things to attend at
On Sun, 2020-08-16 at 21:45 +0200, Carlos E. R. wrote: present, later this evening when I am free I will download the Supergrub software for USB stick and try it. Here's an update. After I sent the previous message with details about using the opensuse rescue CD software, I realized that maybe I could make the Supergrub2 software bootable on the USB stick, so that is what I did.
I used the USB stick with the bootable Supergrub software to boot into my opensuse 15.2 system located on my laptop's harddrive. I then opened Yast and ran the bootloader software, marking
Set active Flag in Partition Table for Boot Partition
I rebooted, and still have the issue where the password dialogue box presents, then I have to save bios settings and exit. It won't boot into the installed opensuse system unless I use the hot key to go to boot options menu when the bios starts to boot, and then select the USB stick with the bootable Supergrub2 software on the next screen after the password screen. Once the Supergrub menu presents, I can select and boot my opensuse system, but not Windows.
I would try the openSUSE rescue image.
< http://download.opensuse.org/distribution/leap/15.2/live/openSUSE-Leap-15.2-...
In the manpage for efibootmgr it talks a little about creating an entry for booting, though it doesn't give enough detail to actually do it. Maybe the web has more info. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 8/16/20 3:27 PM, Mark Misulich wrote:
after a recent update, I noticed on the grub screen that my multiboot with Win was no longer present, and the only option for boot was Opensuse 15.2, followed by the next line of Advanced options for boot Opensuse 15.2. I didn't consider that too much of an issue, as this has happened occasionally, and I just boot Opensuse, open Yast, and rerun the bootloader setup.
For this part of the problem, I find running Grub Customizer helps. https://software.opensuse.org/download.html?project=home%3Aecsos&package=grub-customizer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
16.08.2020 22:27, Mark Misulich пишет:
Hi,
after a recent update, I noticed on the grub screen that my multiboot with Win was no longer present, and the only option for boot was Opensuse 15.2, followed by the next line of Advanced options for boot Opensuse 15.2. I didn't consider that too much of an issue, as this has happened occasionally, and I just boot Opensuse, open Yast, and rerun the bootloader setup.
I did this, and now I can't boot my laptop into either operating system. When I try to boot up, the computer boots to the password screen for the bios, then when I input the password, I get into the bios setup program. But things aren't right there, and I have no boot device setup menu in the boot configuration screen. I can't move around all the options in the bios, as the cursor won't move to the normal items in the menus. Once I save the settings to move beyond the bios setup screens in the boot process, the computer reboots to the bios password screen again. The process of saving the bios settings brings me back to the bios password screen each time the computer reboots. I can never get to the grub menu screen.
If I try to boot into the shortcut boot device selection menu, using the appropriate key when I boot the computer, I can't get to that menu. The boot process takes me to the bios password input screen again. It seems that the bios may not be recognizing any options of boot devices, as it isn't listing any.
I hope that I have described this using correct terminology so that the members of the list can understand the problem.
The computer is a ASUS Q303 laptop.
What I have tried to fix the problem: 1. I tried to boot using Supergrub2 disc via a usb connected external drive. But the drive never gets recognized, and I can't get to the Supergrub program.
2. I downloaded the bios software on another computer, and loaded it to a USB stick. Then I inserted the USB stick into the laptop and booted into the bios setup, where there is a selection for one to reflash the bios program. But the cursor won't move to that selection in the bios menu, so I can't reflash the bios. I had hoped that by reflashing the bios it might resolve the booting problem
I would appreciate some help to resolve this problem.
You have much more chance on support forums of your laptop, there is nothing that can be done from openSUSE side. If your laptop is still under warranty, do not waste your time and ask for replacement. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 2020-08-17 at 09:11 +0300, Andrei Borzenkov wrote:
16.08.2020 22:27, Mark Misulich пишет:
Hi,
after a recent update, I noticed on the grub screen that my multiboot with Win was no longer present, and the only option for boot was Opensuse 15.2, followed by the next line of Advanced options for boot Opensuse 15.2. I didn't consider that too much of an issue, as this has happened occasionally, and I just boot Opensuse, open Yast, and rerun the bootloader setup.
I did this, and now I can't boot my laptop into either operating system. When I try to boot up, the computer boots to the password screen for the bios, then when I input the password, I get into the bios setup program. But things aren't right there, and I have no boot device setup menu in the boot configuration screen. I can't move around all the options in the bios, as the cursor won't move to the normal items in the menus. Once I save the settings to move beyond the bios setup screens in the boot process, the computer reboots to the bios password screen again. The process of saving the bios settings brings me back to the bios password screen each time the computer reboots. I can never get to the grub menu screen.
If I try to boot into the shortcut boot device selection menu, using the appropriate key when I boot the computer, I can't get to that menu. The boot process takes me to the bios password input screen again. It seems that the bios may not be recognizing any options of boot devices, as it isn't listing any.
I hope that I have described this using correct terminology so that the members of the list can understand the problem.
The computer is a ASUS Q303 laptop.
What I have tried to fix the problem: 1. I tried to boot using Supergrub2 disc via a usb connected external drive. But the drive never gets recognized, and I can't get to the Supergrub program.
2. I downloaded the bios software on another computer, and loaded it to a USB stick. Then I inserted the USB stick into the laptop and booted into the bios setup, where there is a selection for one to reflash the bios program. But the cursor won't move to that selection in the bios menu, so I can't reflash the bios. I had hoped that by reflashing the bios it might resolve the booting problem
I would appreciate some help to resolve this problem.
You have much more chance on support forums of your laptop, there is nothing that can be done from openSUSE side. If your laptop is still under warranty, do not waste your time and ask for replacement.
Hi, I want to thank those on the list that have posted information to try and help me resolve this problem that I have described above. I recognize that the members of this list are exceptionally knowledgeable and insightful to deal with the occasional problems that pop up running opensuse. You are all very gracious to allow me access to your expertise. I am happy to report that I was able to finally get Win10 to boot this morning, and used the Asus program it contained to update and reflash the bios. I again used Supergrub2 then on a bootable USB stick to boot opensuse, and then used yast to run the bootloader software to reinstall the bootloader. It was succesful, and the multiboot grub screen appears as normal, and the problems with the bios are resolved. Everything works like its supposed to now, and its like the problem never happened. I feel like I lucked into resolving this, and can't offer a reason as to why it happened. But thanks to everyone for trying to help. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
James Knott -
jdd＠dodin.org -
ken -
Mark Misulich