system crashed during upgrade--HELP
OpenSUSE TW. System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at 966/2162 Installing shim _15 + git47-222222222.2.x86_64 Rebooted to blank (black) screen with message as follows: GNU GRUB VERSION 2.04 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completion. Anywhere else TAB lists possible device file completetions. grub _ Is it possible to save this, and if so, how? Have left computer in this condition awaiting answer. --doug
On 2/23/21 4:44 PM, Doug McGarrett wrote:
OpenSUSE TW.
System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
Rebooted to blank (black) screen with message as follows:
GNU GRUB VERSION 2.04 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completion. Anywhere else TAB lists possible device file completetions. grub _
Is it possible to save this, and if so, how? Have left computer in this condition awaiting answer.
--doug
While you're waiting for someone who knows this better than I do . . . This was after a zypper up or zypper dup? Or are you using snapshot media? The shim is bootstrap code used with EFI/UEFI firmware. It sounds like you are using EFI/UEFI and possibly Secure Boot. (I don't suppose you've been twiddling with this in your BIOS or recently installed a different linux distro or a different non-openSUSE kernel?) Your description sounds like grub2 was not properly installed. Could be a number of reasons. Here is a forum thread which dealt with that problem. https://forums.opensuse.org/showthread.php/534275-How-to-reinstall-grub2-efi... Or this from the SUSE doc's . . . https://www.suse.com/support/kb/doc/?id=000019196 More background: https://doc.opensuse.org/documentation/leap/reference/html/book-opensuse-ref... https://en.opensuse.org/openSUSE:UEFI --dg
On 23/02/2021 22.44, Doug McGarrett wrote:
OpenSUSE TW.
System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
Rebooted to blank (black) screen with message as follows:
GNU GRUB VERSION 2.04 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completion. Anywhere else TAB lists possible device file completetions. grub _
Is it possible to save this, and if so, how? Have left computer in this condition awaiting answer.
Ow :-/ On another computer, download the current Tumbleweed DVD. Put it on a DVD or and USB stick following the instructions at the wiki. Boot that DVD or USB stick on the failed computer, and choose "upgrade system". Notice: I have never tested this procedure with Tumbleweed, and it is drastic. Another possibility. Download a Grub rescue distribution and put in DVD or USB stick following their instructions, and use it to try repair your GRUB. I can not help with this from here. Else, reinstall. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
* Carlos E.R.
On 23/02/2021 22.44, Doug McGarrett wrote:
OpenSUSE TW.
System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
Rebooted to blank (black) screen with message as follows:
GNU GRUB VERSION 2.04 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completion. Anywhere else TAB lists possible device file completetions. grub _
Is it possible to save this, and if so, how? Have left computer in this condition awaiting answer.
Ow :-/
On another computer, download the current Tumbleweed DVD. Put it on a DVD or and USB stick following the instructions at the wiki.
Boot that DVD or USB stick on the failed computer, and choose "upgrade system".
Notice: I have never tested this procedure with Tumbleweed, and it is drastic.
Another possibility.
Download a Grub rescue distribution and put in DVD or USB stick following their instructions, and use it to try repair your GRUB.
I can not help with this from here.
Else, reinstall.
yes, and if reinstall, LEAP not Tw. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On 2/23/21 6:12 PM, Carlos E.R. wrote:
On 23/02/2021 22.44, Doug McGarrett wrote:
OpenSUSE TW.
System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
Rebooted to blank (black) screen with message as follows:
GNU GRUB VERSION 2.04 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completion. Anywhere else TAB lists possible device file completetions. grub _
Is it possible to save this, and if so, how? Have left computer in this condition awaiting answer. Ow :-/
On another computer, download the current Tumbleweed DVD. Put it on a DVD or and USB stick following the instructions at the wiki.
Boot that DVD or USB stick on the failed computer, and choose "upgrade system".
Notice: I have never tested this procedure with Tumbleweed, and it is drastic.
Another possibility.
Download a Grub rescue distribution and put in DVD or USB stick following their instructions, and use it to try repair your GRUB.
I can not help with this from here.
Else, reinstall.
With the caveat that I'm really rusty about this . . . It's possible to fix this in a chroot from the rescue disc. The first thing to determine is whether the shim exists and whether Secure Boot is turned on. If the problem is with the latter, that may mean disabling it (which will upset W$) or possibly working on MOK. Running YaST Bootloader from within the chroot will, with luck, get grub installed. IIRC YaST will install the shim package if it sees its necessary, but if it doesn't, that may need to be done first. I think the links I posted cover how to do all this. Gotta do everything exactly right. Snapshot upgrade might be simpler. And it might catch the bootloader installation problem it ran into? -dg --dg
On 2/23/21 6:12 PM, Carlos E.R. wrote:
On 23/02/2021 22.44, Doug McGarrett wrote:
OpenSUSE TW.
System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
Rebooted to blank (black) screen with message as follows:
GNU GRUB VERSION 2.04 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completion. Anywhere else TAB lists possible device file completetions. grub _
Is it possible to save this, and if so, how? Have left computer in this condition awaiting answer. Ow :-/
On another computer, download the current Tumbleweed DVD. Put it on a DVD or and USB stick following the instructions at the wiki.
Boot that DVD or USB stick on the failed computer, and choose "upgrade system".
Notice: I have never tested this procedure with Tumbleweed, and it is drastic.
Another possibility.
Download a Grub rescue distribution and put in DVD or USB stick following their instructions, and use it to try repair your GRUB.
I can not help with this from here.
Else, reinstall.
Temporary update: While trying to get the machine to boot on a DVD in order to run GParted and see exactly what and where the partitions are, I accidentally made the machine completely unbootable altogether. (It does not look for the external DVD drive, altho the drive does come alive on switch-on. This was my error in trying to set the bios boot sequence. (Don't buy a machine with an ASRock MOBO!) I hope that clearing the CMOS with get the machine back to life, at least. That's pain. Tomorrow, Thanx for the inputs from a couple of you! --doug
On 2/24/21 12:01 AM, Doug McGarrett wrote:
On 2/23/21 6:12 PM, Carlos E.R. wrote:
On 23/02/2021 22.44, Doug McGarrett wrote:
OpenSUSE TW.
System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
/snip/ Long story short: System became completely unusable. Wound up trying to clean ssd and repartition, then load Windows and Linux again. Found that the crash--which occurred again with new software--is due to the computer, not the software. However, in the course of reformatting got message from gparted: "Invalid partition table - recursive partition on /dev/sr0." Option provided: ignore. In the course of things, I cleaned the entire ssd with gparted and repartitioned from scratch, including the entire drive. Still get message. Loaded Windows, loaded latest TW. Now do not have dual boot--Windows ignored. Possibly due to format problem? (Windows ran before installing Linux. Second problem, for now.) Obviously cannot live this way--system crashed again after about 6 hours running. Suspect overheating. 1. How can I measure cpu temperature and record it? Is there any other likely component that would cause the crash? 2. Anyone have a fix for the invalid partition table, short of replacing the drive? --doug
On 16/05/2021 19.57, Doug McGarrett wrote:
On 2/24/21 12:01 AM, Doug McGarrett wrote:
On 2/23/21 6:12 PM, Carlos E.R. wrote:
On 23/02/2021 22.44, Doug McGarrett wrote:
OpenSUSE TW.
System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
/snip/
Long story short:
System became completely unusable. Wound up trying to clean ssd and repartition, then load Windows and Linux again. Found that the crash--which occurred again with new software--is due to the computer, not the software. However, in the course of reformatting got message from gparted: "Invalid partition table - recursive partition on /dev/sr0."
/dev/sr0 is the DVD, not the harddisk. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Installed OS-TW after Win 10. Version is 2021-0513. Earlier versions automatically picked up Windows and set up dual boot. This time starting computer only goes to TW; Windows is not accessible. Can this be fixed, and if so, how? Thanx--doug
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how?
Make sure that Windows is actually installed. You could run this: lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
somefile.txt
and then attach that "somefile.txt" to your reply. Mind, attach, do not paste. Menu File/attach/File(s). If Windows is installed, you could run yast2 as root, then "boot loader" module, then "Bootloader options" tab. Here, make sure that [X] Probe Foreign OS is marked, then change the timeout one second up or down on the left of the screen, Then click [OK]. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how?
Make sure that Windows is actually installed. You could run this:
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
somefile.txt
and then attach that "somefile.txt" to your reply. Mind, attach, do not paste. Menu File/attach/File(s).
Hope that this worked OK. I'll get to the rest of the instructions (below) right after I send this. --doug
If Windows is installed, you could run yast2 as root, then "boot loader" module, then "Bootloader options" tab. Here, make sure that
[X] Probe Foreign OS
is marked, then change the timeout one second up or down on the left of the screen, Then click [OK].
On 17/05/2021 02.29, Douglas McGarrett wrote:
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how?
Make sure that Windows is actually installed. You could run this:
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
somefile.txt
and then attach that "somefile.txt" to your reply. Mind, attach, do not paste. Menu File/attach/File(s).
Hope that this worked OK. I'll get to the rest of the instructions (below) right after I send this.
Perfect. Yes, Windows is installed. I see 3 small vfat partitions, two unknown and one EFI (#1, #2 and #5) I see one small NTFS partition, probably the windows boot. (#4) I see one big NTFS partition, #3 Then there is swap (#6) and linux (#7) I guess. I suspect you did not fully erase the disk before starting the installation of the first system (#1 and #2). And maybe Linux did not like the result and created yet another EFI partition. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 5/16/21 9:26 PM, Carlos E. R. wrote:
On 17/05/2021 02.29, Douglas McGarrett wrote:
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how?
Make sure that Windows is actually installed. You could run this:
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
somefile.txt
and then attach that "somefile.txt" to your reply. Mind, attach, do not paste. Menu File/attach/File(s).
Hope that this worked OK. I'll get to the rest of the instructions (below) right after I send this.
Perfect.
Yes, Windows is installed.
I see 3 small vfat partitions, two unknown and one EFI (#1, #2 and #5) I see one small NTFS partition, probably the windows boot. (#4) I see one big NTFS partition, #3
Then there is swap (#6) and linux (#7) I guess.
I suspect you did not fully erase the disk before starting the installation of the first system (#1 and #2). And maybe Linux did not like the result and created yet another EFI partition.
Yes I fully erase the disk. As I mentioned, I completely cleaned it and made new partitions. Suse changed its partitions to the unique ones it likes, but everything else is the same. Here goes to attempt to reboot.--doug
On 5/16/21 9:26 PM, Carlos E. R. wrote:
On 17/05/2021 02.29, Douglas McGarrett wrote:
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how?
Make sure that Windows is actually installed. You could run this:
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
somefile.txt
and then attach that "somefile.txt" to your reply. Mind, attach, do not paste. Menu File/attach/File(s).
Hope that this worked OK. I'll get to the rest of the instructions (below) right after I send this.
Perfect.
Yes, Windows is installed.
I see 3 small vfat partitions, two unknown and one EFI (#1, #2 and #5) I see one small NTFS partition, probably the windows boot. (#4) I see one big NTFS partition, #3
Then there is swap (#6) and linux (#7) I guess.
I suspect you did not fully erase the disk before starting the installation of the first system (#1 and #2). And maybe Linux did not like the result and created yet another EFI partition.
In another post I admitted that I had formatted partitions for Windows and TW after I had cleaned the entire drive by erasing and removing all partitions using gparted. Before I installed TW, I installed and ran Windows, as I mentioned, and installed just a few apps to make it not suck so much. Then I installed TW. The system has crashed about three times since then, but I did run s-tui and watched it for some time while I ran some other stuff. I did not see anything suspicious. Of course I monitored the fan on the CPU--it ran all the time. Perhaps it needs to run faster? It seems to run silently. But the CPU also remains about 30°C or so--hardly working up a sweat. Someone posted a line for monitoring cpu temperatures but I can't find it. Perhaps I can write a short app to monitor the temperatures and record them. If I can find a Pascal compiler. Or if I could find my notes on writing BASH. Then I also need some kind of routine that will keep the processor busy. (It is only about 30 years since I wrote any code!) What else could make the system crash? --doug
On 19/05/2021 07.35, Douglas McGarrett wrote:
On 5/16/21 9:26 PM, Carlos E. R. wrote:
On 17/05/2021 02.29, Douglas McGarrett wrote:
In another post I admitted that I had formatted partitions for Windows and TW after I had cleaned the entire drive by erasing and removing all partitions using gparted. Before I installed TW, I installed and ran Windows, as I mentioned, and installed just a few apps to make it not suck so much. Then I installed TW. The system has crashed about three times since then, but I did run s-tui and watched it for some time while I ran some other stuff. I did not see anything suspicious. Of course I monitored the fan on the CPU--it ran all the time. Perhaps it needs to run faster? It seems to run silently. But the CPU also remains about 30°C or so--hardly working up a sweat.
You can start gkrellm, and tell it to display temperatures and fan speeds - what it can display depends on the machine (run sensors-detect as root to find and enable them). But it does not graph those.
Someone posted a line for monitoring cpu temperatures but I can't find it. Perhaps I can write a short app to monitor the temperatures and record them. If I can find a Pascal compiler. Or if I could find my notes on writing BASH. Then I also need some kind of routine that will keep the processor busy. (It is only about 30 years since I wrote any code!)
What else could make the system crash?
Many things. Very difficult to say. You have to watch the logs. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.1 x86_64 (Minas Tirith))
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how?
Make sure that Windows is actually installed. You could run this:
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
somefile.txt
and then attach that "somefile.txt" to your reply. Mind, attach, do not paste. Menu File/attach/File(s).
Could not run the following. Don't know how to add "boot loader module" to yast2. /If Windows is installed, you could run yast2 as root, then "boot loader" module, then "Bootloader options" tab. Here, make sure that // //// // [X] Probe Foreign OS // //// //is marked, then change the timeout one second up or down on the left of the screen, Then click [OK]./ /Computer output:/ DESKTOP-4FSTN3U:~ # yast2 QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' boot loader ^C DESKTOP-4FSTN3U:~ # boot loader module If 'boot' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf boot DESKTOP-4FSTN3U:~ # bootloader If 'bootloader' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf bootloader
On 17/05/2021 02.53, Douglas McGarrett wrote:
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how?
Make sure that Windows is actually installed. You could run this:
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
somefile.txt
and then attach that "somefile.txt" to your reply. Mind, attach, do not paste. Menu File/attach/File(s).
Could not run the following. Don't know how to add "boot loader module"
to yast2.
You don't need to add anything, it is there. If you don't see it, look again. If you don't see it, look again. If you don't see it, look again. If you don't see it, look again. If you don't see it, look again.
/If Windows is installed, you could run yast2 as root, then "boot loader" module, then "Bootloader options" tab. Here, make sure that // //// // [X] Probe Foreign OS // //// //is marked, then change the timeout one second up or down on the left of the screen, Then click [OK]./
/Computer output:/
DESKTOP-4FSTN3U:~ # yast2
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' boot loader ^C DESKTOP-4FSTN3U:~ # boot loader module
¡¡¡¡NO!!!! JUST CLICK ON THE DAMN ICON! Look at the photo. https://susepaste.org/66062360 -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 5/16/21 9:26 PM, Carlos E. R. wrote:
On 17/05/2021 02.53, Douglas McGarrett wrote:
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how?
Make sure that Windows is actually installed. You could run this:
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
somefile.txt
and then attach that "somefile.txt" to your reply. Mind, attach, do not paste. Menu File/attach/File(s).
Could not run the following. Don't know how to add "boot loader module"
to yast2.
You don't need to add anything, it is there.
If you don't see it, look again. If you don't see it, look again. If you don't see it, look again. If you don't see it, look again. If you don't see it, look again.
/If Windows is installed, you could run yast2 as root, then "boot loader" module, then "Bootloader options" tab. Here, make sure that // //// // [X] Probe Foreign OS // //// //is marked, then change the timeout one second up or down on the left of the screen, Then click [OK]./
/Computer output:/
DESKTOP-4FSTN3U:~ # yast2
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' boot loader ^C DESKTOP-4FSTN3U:~ # boot loader module
¡¡¡¡NO!!!!
JUST CLICK ON THE DAMN ICON!
Look at the photo.
OK, OK! I wasn't looking at that yast picture, I was opening yast2 from sudo as instructed. I have now the picture yu want me to have. I did that. Got a blue-background screen. It asked me if it was OK and I said yes. If nothing boots now, I'll know why! Gonna shut down now and try and restart and see what happens. Might have to answer from the Mageia machine! Let's see. . . .Doug
On 5/16/21 10:12 PM, Douglas McGarrett wrote:
On 5/16/21 9:26 PM, Carlos E. R. wrote:
On 17/05/2021 02.53, Douglas McGarrett wrote:
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how?
Make sure that Windows is actually installed. You could run this:
lsblk --output NAME,KNAME,RA,RM,RO,PARTFLAGS,SIZE,TYPE,FSTYPE,LABEL,PARTLABEL,PTTYPE,MOUNTPOINT,UUID,PARTUUID,WWN,MODEL,ALIGNMENT
somefile.txt
and then attach that "somefile.txt" to your reply. Mind, attach, do not paste. Menu File/attach/File(s).
Could not run the following. Don't know how to add "boot loader module"
to yast2.
You don't need to add anything, it is there.
If you don't see it, look again. If you don't see it, look again. If you don't see it, look again. If you don't see it, look again. If you don't see it, look again.
/If Windows is installed, you could run yast2 as root, then "boot loader" module, then "Bootloader options" tab. Here, make sure that // //// // [X] Probe Foreign OS // //// //is marked, then change the timeout one second up or down on the left of the screen, Then click [OK]./
/Computer output:/
DESKTOP-4FSTN3U:~ # yast2
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' boot loader ^C DESKTOP-4FSTN3U:~ # boot loader module
¡¡¡¡NO!!!!
JUST CLICK ON THE DAMN ICON!
Look at the photo.
OK, OK! I wasn't looking at that yast picture, I was opening yast2 from sudo as instructed. I have now the picture yu want me to have.
I did that. Got a blue-background screen. It asked me if it was OK and I said yes. If nothing boots now, I'll know why! Gonna
shut down now and try and restart and see what happens. Might have to answer from the Mageia machine!
Let's see. . . .Doug
Almost had to answer from Mageia machine. It doesn't like to boot anything, but after several hits and misses, I found a version that boots TW. No Windows. I hope I don't have to start over, but it's beginning to look that way. I put about 5 apps on Windows, just so I could use it at all, and I put 17 on TW, and even if I start over, I might wind up right back where I started yesterday! Is it possible that the 2021-0513 system is defective in this area? I still have the disk from last fall, but that would be a lot of upgrades--where I came in! --doug
On 5/16/21 9:26 PM, Carlos E. R. wrote:
On 17/05/2021 02.53, Douglas McGarrett wrote:
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how? /big snip/
I admit that I lied a little. I did not install Windows from a blank slate, I formatted the first four windows partitions in accordance with some information as to what they should be, file type and size. Windows was happy. I also formatted what became Linux with ext4, but Suse changed that. I forgot about that until just now. I don't know why it matters, but if it does, I confess. Mea culpa! --doug
On 17/05/2021 04.53, Douglas McGarrett wrote:
On 5/16/21 9:26 PM, Carlos E. R. wrote:
On 17/05/2021 02.53, Douglas McGarrett wrote:
On 5/16/21 6:21 PM, Carlos E.R. wrote:
On 17/05/2021 00.13, Douglas McGarrett wrote:
Installed OS-TW after Win 10. Version is 2021-0513. Earlier
versions automatically picked up Windows and set up
dual boot. This time starting computer only goes to TW;
Windows is not accessible. Can this be fixed, and if so, how? /big snip/
I admit that I lied a little. I did not install Windows from a blank slate, I formatted the first four windows partitions
in accordance with some information as to what they should be, file type and size. Windows was happy. I also formatted
what became Linux with ext4, but Suse changed that. I forgot about that
until just now. I don't know why it matters, but if it does,
I confess. Mea culpa!
It matters because it explains why you have the partitions that you have. If you use the correct windows installation disk, you can tell Windows the percent of the hard disk to use. As to why your system doesn't boot now and doesn't find Windows, I have no idea. The problems you have do not happen to other people. You also know we told you not to use tumbleweed. You have to be an expert to use tumbleweed, and you are not. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Douglas McGarrett composed on 2021-05-16 20:53 (UTC-0400):
DESKTOP-4FSTN3U:~ # yast2
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' boot loader ^C DESKTOP-4FSTN3U:~ # boot loader module If 'boot' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf boot DESKTOP-4FSTN3U:~ # bootloader If 'bootloader' is not a typo you can use command-not-found to lookup the package that contains it, like this: cnf bootloader
# sudo yast2 bootloader -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 5/16/21 9:36 PM, Felix Miata wrote: Found _sensors_ routine finds and outputs cpu temps. Can someone suggest a simple closed-form equation that will keep all the cores of the cpu busy? I will try and write some kind of routine that will output temps vs. time elapsed and see what happens. --doug
Am 19.05.21 um 08:03 schrieb Douglas McGarrett:
On 5/16/21 9:36 PM, Felix Miata wrote:
Found _sensors_ routine finds and outputs cpu temps. Can someone suggest a simple
closed-form equation that will keep all the cores of the cpu busy? I will try and write some
kind of routine that will output temps vs. time elapsed and see what happens.
--doug
you could use pbzip2 (parallel bzip2 compressor) and compress large files (in a small shell script, and decompress it and do it again) or you use the "kill ryzon script" this is originally written to compile kernel and heat up amd ryzon cpu's to show a problem inside some of the batches. i did not know if it will work with intel processors. and maybe you have to modify it a little bit to run under recent tumbleweed. (two years before i have to modify to make sure kernel will compile) simoN -- www.becherer.de
On 2021-05-19 12:03 a.m., Douglas McGarrett wrote:
On 5/16/21 9:36 PM, Felix Miata wrote:
Found _sensors_ routine finds and outputs cpu temps. Can someone suggest a simple
closed-form equation that will keep all the cores of the cpu busy? I will try and write some
kind of routine that will output temps vs. time elapsed and see what happens.
--doug
"md5sum /dev/zero" run one instance per core will max out any CPU. Use gkrellm to monitor temperatures in real time. Don't blame us if you fry your CPU.
On 5/19/21 2:03 AM, Douglas McGarrett wrote:
On 5/16/21 9:36 PM, Felix Miata wrote:
Found _sensors_ routine finds and outputs cpu temps. Can someone suggest a simple
closed-form equation that will keep all the cores of the cpu busy? I will try and write some
kind of routine that will output temps vs. time elapsed and see what happens.
--doug
Write something in Pascal??? Why must you always make everything harder? Sensors takes readings from the heat/voltage sensors that are on the mobo and/or on the cpu. There needs to be a configuration clause in its config file specific to the sensor devices. The sensors app can set that up for you, or at least the bare structure which you can edit, add labels to, etc. Some boards do not have such devices, on others the sensors app may not be able to find the chips. #man sensors #man sensors-detect #man sensors-conf Do not confuse monitoring readings with stress testing. Stress testing is a technique used in overclocking and to burn in new hardware, etc. My preference is mprime (prime95 on W$), but there are others . . . https://wiki.archlinux.org/title/Stress_testing https://linuxhint.com/useful_linux_stress_test_benchmark_cpu_perf/ https://www.mersenne.org/download/ https://www.unixmen.com/how-to-test-system-stability-using-mprime/ I presume you are doing this because you've had several crashes and you think the problem may be hardware, e.g., overheating. Monitoring the temps can easily be done in an app like KsysGuard (which also allows the user to graph the sensor devices). 'Keeping all cores busy' essentially means nothing; busy at what, how busy, what thresholds, etc.? Do you even understand power throttling? It's one thing to monitor the system, another to use stress-test tools, yet another to know how to interpret results. So another safe assumption is that you don't really know what you're doing (watching the fan speed? calculate time elapsed? you gotta be kidding). You are venturing into dangerous waters, pal. --dg
On 19/05/2021 21.03, DennisG wrote:
On 5/19/21 2:03 AM, Douglas McGarrett wrote:
On 5/16/21 9:36 PM, Felix Miata wrote:
Found _sensors_ routine finds and outputs cpu temps. Can someone suggest a simple
closed-form equation that will keep all the cores of the cpu busy? I will try and write some
kind of routine that will output temps vs. time elapsed and see what happens.
Write something in Pascal??? Why must you always make everything harder?
I do things in Pascal on Linux, but I don't see the point for this. Bash scripts are good enough and easy. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.1 x86_64 (Minas Tirith))
On 5/16/21 12:57 PM, Doug McGarrett wrote:
On 2/24/21 12:01 AM, Doug McGarrett wrote:
On 2/23/21 6:12 PM, Carlos E.R. wrote:
On 23/02/2021 22.44, Doug McGarrett wrote:
OpenSUSE TW.
System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
/snip/
Long story short:
System became completely unusable. Wound up trying to clean ssd and repartition, then load Windows and Linux again. Found that the crash--which occurred again with new software--is due to the computer, not the software. However, in the course of reformatting got message from gparted: "Invalid partition table - recursive partition on /dev/sr0." Option provided: ignore. In the course of things, I cleaned the entire ssd with gparted and repartitioned from scratch, including the entire drive. Still get message. Loaded Windows, loaded latest TW. Now do not have dual boot--Windows ignored. Possibly due to format problem? (Windows ran before installing Linux. Second problem, for now.) Obviously cannot live this way--system crashed again after about 6 hours running. Suspect overheating. 1. How can I measure cpu temperature and record it? Is there any other likely component that would cause the crash?
2. Anyone have a fix for the invalid partition table, short of replacing the drive? I would like to possibly suggest using "dd" -dubbed- data destroyer. You must be very careful and know the specific drive label e.g. /dev/sda you wish to clear/wipe fresh. The following utilities can help you determine
I think you can use the inxi utility to monitor your systems temperature also you can install sensors to get more specifics. Pass the following command "inxi -Fxz" and towards the bottom of the report you will see CPU temperature. Open up your case and carefully verify that fans are functioning also visually is not a bad idea either. this: "fdisk -l", "gparted". I am not certain of Windows based utilities. Then you could boot with a live-cd or rescue-cd and perform the following on the appropriate drive. You can, however, use dd to make it a whole lot more difficult for the bad guys to get at your old data. This command will spend some time writing millions and millions of zeros over every nook and cranny of the /dev/sda1 partition: # dd if=/dev/zero of=/dev/sda1 Then perhaps you could install Windows followed by openSUSE TDE once again afterwards. May go smoother with a perfectly clear drive. --Regards
On 17/05/2021 00.34, -pj wrote:
On 5/16/21 12:57 PM, Doug McGarrett wrote:
...
2. Anyone have a fix for the invalid partition table, short of replacing the drive? I would like to possibly suggest using "dd" -dubbed- data destroyer. You must be very careful and know the specific drive label e.g. /dev/sda you wish to clear/wipe fresh. The following utilities can help you determine this: "fdisk -l", "gparted". I am not certain of Windows based utilities. Then you could boot with a live-cd or rescue-cd and perform the following on the appropriate drive.
You can, however, use dd to make it a whole lot more difficult for the bad guys to get at your old data. This command will spend some time writing millions and millions of zeros over every nook and cranny of the /dev/sda1 partition:
# dd if=/dev/zero of=/dev/sda1
Then perhaps you could install Windows followed by openSUSE TDE once again afterwards. May go smoother with a perfectly clear drive.
NO! For one thing, it is an SSD and you kill one life. It has limited lives. For another, it is Doug you are trying to help. :-| -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2/23/21 6:12 PM, Carlos E.R. wrote:
On 23/02/2021 22.44, Doug McGarrett wrote:
OpenSUSE TW.
System crashed during the second part of upgrade, where files were reporting "done." Crash occurred at
966/2162 Installing shim _15 + git47-222222222.2.x86_64
Rebooted to blank (black) screen with message as follows:
GNU GRUB VERSION 2.04 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completion. Anywhere else TAB lists possible device file completetions. grub _
Is it possible to save this, and if so, how? Have left computer in this condition awaiting answer. Ow :-/
On another computer, download the current Tumbleweed DVD. Put it on a DVD or and USB stick following the instructions at the wiki.
Boot that DVD or USB stick on the failed computer, and choose "upgrade system".
Notice: I have never tested this procedure with Tumbleweed, and it is drastic.
Another possibility.
Download a Grub rescue distribution and put in DVD or USB stick following their instructions, and use it to try repair your GRUB.
I can not help with this from here.
Multiple problems, apparently. I took the computer apart and reset the CMOS a couple of times. One of the problems was that I seem to have picked a bad option to reset the DVD boot procedure, and it blew up on me. By some stroke of luck, I got the thing to boot back into Suse, where I am now. It seemed that some combination of things kept the cpu from outputting video on the HDMI port that was going to the monitor. I went round and round before figuring this out, and finally connected an "old fashioned" multi-pin video cable between the computer and the monitor and got video back, and then by some stroke of luck, I got into the cmos setup again and told it to boot OpenSUSE TW from the ssd, and it did. The cmos setup on this ASRock mobo is video, not like the old system we're all used to, and it is a bit confusing. (Was trying to get the machine to boot from a DVD and I blew it, somehow.) If you should have one of these boards, F10 will save your desired setting. Not obvious. (Altho, I think F10 worked on the old system, too, now that I think of it.) Now, I'm wondering whether the attempted zypper dup caused the system to crash, or if it was just a perversion, or what. --doug
Doug McGarrett writes:
966/2162 Installing shim _15 + git47-222222222.2.x86_64
Rebooted to blank (black) screen with message as follows:
If the shim is missing Grub will not be able to load a kernel. You should in principle be able to boot from a rescue system (it needs to be new enough to has a shim that's been signed recently if you use secure boot). The other option is to drop a shim from the rescue medium into the EFI partition and then retry the boot. You may find other things missing, though, depending on where exactly things crashed.
Is it possible to save this, and if so, how? Have left computer in this condition awaiting answer.
You can mount the system and boot partitions from a rescue system into a chroot environment and then run the part of the install that was incomplete if it's not just the shim that is missing. You should find some information in both the openSUSE forums and elsewhere on the wen on how to do it. I've had to do that about half a year ago, look for a post from me "NVMe drive setup on system w/o NVMe BIOS support" on this very list. Regards Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
participants (11)
-
-pj -
Achim Gratz -
Carlos E. R. -
Carlos E.R. -
Darryl Gregorash -
DennisG -
Doug McGarrett -
Douglas McGarrett
-
Felix Miata -
Patrick Shanahan -
Simon Becherer