GRUB _ *only* displayed after zypper dup:
Hi, I am using Tumbleweed with KDE 6 on a machine here. I decide to update the machine today by passing 'zypper dup' into Konsole. After a bit the update completed and 'zypper ps -s' said there were no core libraries updated but I proceeded to powercycle the machine. After doing this the machine is stuck at the following displayed on screen > GRUB _ Can you tell me what may have happened and the steps to try to attempt to get this repaired?
On 24.05.2024 20:19, -pj wrote:
Hi, I am using Tumbleweed with KDE 6 on a machine here. I decide to update the machine today by passing 'zypper dup' into Konsole. After a bit the update completed and 'zypper ps -s' said there were no core libraries updated but I proceeded to powercycle the machine.
After doing this the machine is stuck at the following displayed on screen > GRUB _
Can you tell me what may have happened and the steps to try to attempt to get this repaired?
Boot from live image, run https://github.com/arvidjaar/bootinfoscript, provide RESULTS.txt.
I have booted from a live image on the machine. Here are bootinfoscript RESULTS > https://paste.opensuse.org/pastes/d5b9e3d7a46c On 05-24-2024 12:33PM, Andrei Borzenkov wrote:
On 24.05.2024 20:19, -pj wrote:
Hi, I am using Tumbleweed with KDE 6 on a machine here. I decide to update the machine today by passing 'zypper dup' into Konsole. After a bit the update completed and 'zypper ps -s' said there were no core libraries updated but I proceeded to powercycle the machine.
After doing this the machine is stuck at the following displayed on screen > GRUB _
Can you tell me what may have happened and the steps to try to attempt to get this repaired?
Boot from live image, run https://github.com/arvidjaar/bootinfoscript, provide RESULTS.txt.
On 24.05.2024 20:57, -pj wrote:
I have booted from a live image on the machine.
Here are bootinfoscript RESULTS > https://paste.opensuse.org/pastes/d5b9e3d7a46c
=> Grub2 (v1.99-2.00) is installed in the MBR of /dev/sdb and looks at sector 2048 of the same hard drive for core.img, but core.img can not be found at this location. GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sdb1 2,048 18,431 16,384 BIOS Boot partition /dev/sdb2 B 18,432 1,953,523,711 1,953,505,280 Logical Volume Manager (LVM) partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set sdb1: __________________________________________________________________________ File system: BIOS Boot partition Boot sector type: - Boot sector info: Well, it seems that grub is gone from BIOS boot partition. Mount root and show the content of /etc/default/grub_installdevice and /etc/sysconfig/bootloader.
On 05-24-2024 12:33PM, Andrei Borzenkov wrote:
On 24.05.2024 20:19, -pj wrote:
Hi, I am using Tumbleweed with KDE 6 on a machine here. I decide to update the machine today by passing 'zypper dup' into Konsole. After a bit the update completed and 'zypper ps -s' said there were no core libraries updated but I proceeded to powercycle the machine.
After doing this the machine is stuck at the following displayed on screen > GRUB _
Can you tell me what may have happened and the steps to try to attempt to get this repaired?
Boot from live image, run https://github.com/arvidjaar/bootinfoscript, provide RESULTS.txt.
On 05-24-2024 01:26PM, Andrei Borzenkov wrote:
On 24.05.2024 20:57, -pj wrote:
I have booted from a live image on the machine.
Here are bootinfoscript RESULTS > https://paste.opensuse.org/pastes/d5b9e3d7a46c
=> Grub2 (v1.99-2.00) is installed in the MBR of /dev/sdb and looks at sector 2048 of the same hard drive for core.img, but core.img can not be found at this location.
GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sdb1 2,048 18,431 16,384 BIOS Boot partition /dev/sdb2 B 18,432 1,953,523,711 1,953,505,280 Logical Volume Manager (LVM) partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
sdb1: __________________________________________________________________________ File system: BIOS Boot partition Boot sector type: - Boot sector info:
Well, it seems that grub is gone from BIOS boot partition. Mount root and show the content of /etc/default/grub_installdevice and /etc/sysconfig/bootloader.
Contents of /etc/default/grub_installdevice /dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_1909AF805062 - Contents of /etc/sysconfig/bootloader ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: list(grub,grub2,grub2-efi,none) ## Default: grub2 # # Type of bootloader in use. # For making the change effect run bootloader configuration tool # and configure newly selected bootloader # # LOADER_TYPE="grub2" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: "no" # # Enable Secure Boot support # Only available on UEFI systems and IBM z15+. # # SECURE_BOOT="yes" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: "no" # # Enable Trusted Boot support # Only available on hardware with a Trusted Platform Module. # TRUSTED_BOOT="no" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: "yes" # # Update nvram boot settings (UEFI, OF) # Unset to preserve specific settings or workaround firmware issues. # UPDATE_NVRAM="yes" The entry line above "(SECURE_BOOT="yes")" may not be correct because the machine in question does not have UEFI capability. I believe the machine is a Legacy BIOS hardware. What are your thoughts? -Best regards
On 05-24-2024 12:33PM, Andrei Borzenkov wrote:
On 24.05.2024 20:19, -pj wrote:
Hi, I am using Tumbleweed with KDE 6 on a machine here. I decide to update the machine today by passing 'zypper dup' into Konsole. After a bit the update completed and 'zypper ps -s' said there were no core libraries updated but I proceeded to powercycle the machine.
After doing this the machine is stuck at the following displayed on screen > GRUB _
Can you tell me what may have happened and the steps to try to attempt to get this repaired?
Boot from live image, run https://github.com/arvidjaar/bootinfoscript, provide RESULTS.txt.
On 24.05.2024 21:45, -pj wrote:
On 05-24-2024 01:26PM, Andrei Borzenkov wrote:
On 24.05.2024 20:57, -pj wrote:
I have booted from a live image on the machine.
Here are bootinfoscript RESULTS > https://paste.opensuse.org/pastes/d5b9e3d7a46c
=> Grub2 (v1.99-2.00) is installed in the MBR of /dev/sdb and looks at sector 2048 of the same hard drive for core.img, but core.img can not be found at this location.
GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sdb1 2,048 18,431 16,384 BIOS Boot partition /dev/sdb2 B 18,432 1,953,523,711 1,953,505,280 Logical Volume Manager (LVM) partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
sdb1: __________________________________________________________________________ File system: BIOS Boot partition Boot sector type: - Boot sector info:
Well, it seems that grub is gone from BIOS boot partition. Mount root and show the content of /etc/default/grub_installdevice and /etc/sysconfig/bootloader.
Contents of /etc/default/grub_installdevice
/dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_1909AF805062 - Contents of /etc/sysconfig/bootloader
## Path: System/Bootloader ## Description: Bootloader configuration ## Type: list(grub,grub2,grub2-efi,none) ## Default: grub2 # # Type of bootloader in use. # For making the change effect run bootloader configuration tool # and configure newly selected bootloader # # LOADER_TYPE="grub2" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: "no" # # Enable Secure Boot support # Only available on UEFI systems and IBM z15+. # # SECURE_BOOT="yes" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: "no" # # Enable Trusted Boot support # Only available on hardware with a Trusted Platform Module. # TRUSTED_BOOT="no" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: "yes" # # Update nvram boot settings (UEFI, OF) # Unset to preserve specific settings or workaround firmware issues. # UPDATE_NVRAM="yes"
The entry line above "(SECURE_BOOT="yes")" may not be correct because the machine in question does not have UEFI capability. I believe the machine is a Legacy BIOS hardware.
What are your thoughts?
So far not much. Could you show (better on paste.opensuse.org) hexdump -C -n 512 /dev/sdb hexdump -C -n 512 /dev/sdb1
-Best regards
On 05-24-2024 12:33PM, Andrei Borzenkov wrote:
On 24.05.2024 20:19, -pj wrote:
Hi, I am using Tumbleweed with KDE 6 on a machine here. I decide to update the machine today by passing 'zypper dup' into Konsole. After a bit the update completed and 'zypper ps -s' said there were no core libraries updated but I proceeded to powercycle the machine.
After doing this the machine is stuck at the following displayed on screen > GRUB _
Can you tell me what may have happened and the steps to try to attempt to get this repaired?
Boot from live image, run https://github.com/arvidjaar/bootinfoscript, provide RESULTS.txt.
On 05-24-2024 02:24PM, Andrei Borzenkov wrote:
On 24.05.2024 21:45, -pj wrote:
On 05-24-2024 01:26PM, Andrei Borzenkov wrote:
On 24.05.2024 20:57, -pj wrote:
I have booted from a live image on the machine.
Here are bootinfoscript RESULTS > https://paste.opensuse.org/pastes/d5b9e3d7a46c
=> Grub2 (v1.99-2.00) is installed in the MBR of /dev/sdb and looks at sector 2048 of the same hard drive for core.img, but core.img can not be found at this location.
GUID Partition Table detected. Partition Attrs Start Sector End Sector # of Sectors System /dev/sdb1 2,048 18,431 16,384 BIOS Boot partition /dev/sdb2 B 18,432 1,953,523,711 1,953,505,280 Logical Volume Manager (LVM) partition (Linux) Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
sdb1: __________________________________________________________________________
File system: BIOS Boot partition Boot sector type: - Boot sector info:
Well, it seems that grub is gone from BIOS boot partition. Mount root and show the content of /etc/default/grub_installdevice and /etc/sysconfig/bootloader.
Contents of /etc/default/grub_installdevice
/dev/disk/by-id/ata-WDC_WDS100T2B0A-00SM50_1909AF805062 - Contents of /etc/sysconfig/bootloader
## Path: System/Bootloader ## Description: Bootloader configuration ## Type: list(grub,grub2,grub2-efi,none) ## Default: grub2 # # Type of bootloader in use. # For making the change effect run bootloader configuration tool # and configure newly selected bootloader # # LOADER_TYPE="grub2" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: "no" # # Enable Secure Boot support # Only available on UEFI systems and IBM z15+. # # SECURE_BOOT="yes" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: "no" # # Enable Trusted Boot support # Only available on hardware with a Trusted Platform Module. # TRUSTED_BOOT="no" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: "yes" # # Update nvram boot settings (UEFI, OF) # Unset to preserve specific settings or workaround firmware issues. # UPDATE_NVRAM="yes"
The entry line above "(SECURE_BOOT="yes")" may not be correct because the machine in question does not have UEFI capability. I believe the machine is a Legacy BIOS hardware.
What are your thoughts?
So far not much. Could you show (better on paste.opensuse.org)
hexdump -C -n 512 /dev/sdb hexdump -C -n 512 /dev/sdb1
Thank you for asking, of course. #hexdump -C -n 512 /dev/sdb 00000000 eb 63 90 90 90 90 90 90 90 90 90 90 90 90 90 90 |.c..............| 00000010 90 90 90 90 90 90 90 90 90 90 eb 49 24 12 0f 09 |...........I$...| 00000020 00 52 be 1b 7c 31 c0 cd 13 46 8a 0c 84 c9 75 10 |.R..|1...F....u.| 00000030 be 39 7c e8 74 01 e9 3d 01 46 6c 6f 70 70 79 00 |.9|.t..=.Floppy.| 00000040 bb 00 70 8e c3 31 db b8 01 02 b5 00 b6 00 cd 13 |..p..1..........| 00000050 72 d3 b6 01 b5 4f e9 98 00 00 00 80 00 00 00 00 |r....O..........| 00000060 00 00 00 00 ff fa eb 05 f6 c2 80 74 05 f6 c2 70 |...........t...p| 00000070 74 02 b2 80 ea 79 7c 00 00 31 c0 8e d8 8e d0 bc |t....y|..1......| 00000080 00 20 fb a0 64 7c 3c ff 74 02 88 c2 52 be 80 7d |. ..d|<.t...R..}| 00000090 e8 17 01 be bf 7d b4 41 bb aa 55 cd 13 5a 52 72 |.....}.A..U..ZRr| 000000a0 3d 81 fb 55 aa 75 37 83 e1 01 74 32 31 c0 89 44 |=..U.u7...t21..D| 000000b0 04 40 88 44 ff 89 44 02 c7 04 10 00 66 8b 1e b0 |.@.D..D.....f...| 000000c0 7d 66 89 5c 08 66 8b 1e b4 7d 66 89 5c 0c c7 44 |}f.\.f...}f.\..D| 000000d0 06 00 70 b4 42 cd 13 72 05 bb 00 70 eb 76 b4 08 |..p.B..r...p.v..| 000000e0 cd 13 73 0d 5a 84 d2 0f 83 36 ff be 8b 7d e9 82 |..s.Z....6...}..| 000000f0 00 66 0f b6 c6 88 64 ff 40 66 89 44 04 0f b6 d1 |.f....d.@f.D....| 00000100 c1 e2 02 88 e8 88 f4 40 89 44 08 0f b6 c2 c0 e8 |.......@.D......| 00000110 02 66 89 04 66 a1 b4 7d 66 09 c0 75 4e 66 a1 b0 |.f..f..}f..uNf..| 00000120 7d 66 31 d2 66 f7 34 88 d1 31 d2 66 f7 74 04 3b |}f1.f.4..1.f.t.;| 00000130 44 08 7d 37 fe c1 88 c5 30 c0 c1 e8 02 08 c1 88 |D.}7....0.......| 00000140 d0 5a 88 c6 bb 00 70 8e c3 31 db b8 01 02 cd 13 |.Z....p..1......| 00000150 72 1e 8c c3 60 1e b9 00 01 8e db 31 f6 bf 00 80 |r...`......1....| 00000160 8e c6 fc f3 a5 1f 61 ff 26 5a 7c be 86 7d eb 03 |......a.&Z|..}..| 00000170 be 95 7d e8 34 00 be 9a 7d e8 2e 00 cd 18 eb fe |..}.4...}.......| 00000180 47 52 55 42 20 00 47 65 6f 6d 00 48 61 72 64 20 |GRUB .Geom.Hard | 00000190 44 69 73 6b 00 52 65 61 64 00 20 45 72 72 6f 72 |Disk.Read. Error| 000001a0 0d 0a 00 bb 01 00 b4 0e cd 10 ac 3c 00 75 f4 c3 |...........<.u..| 000001b0 38 03 00 00 00 00 00 00 00 00 00 00 00 00 80 02 |8...............| 000001c0 01 00 cd 3b d0 95 40 00 00 00 30 af 1c 00 00 3b |...;..@...0....;| 000001d0 d1 95 ef 3b d0 a9 70 af 1c 00 00 a0 00 00 00 00 |...;..p.........| 000001e0 c1 aa 83 3f e0 ff 00 50 1d 00 00 70 d1 00 00 00 |...?...P...p....| 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 00000200 - #hexdump -C -n 512 /dev/sdb1 00000000 01 43 44 30 30 31 01 00 20 20 20 20 20 20 20 20 |.CD001.. | 00000010 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | 00000020 20 20 20 20 20 20 20 20 6f 70 65 6e 53 55 53 45 | openSUSE| 00000030 5f 54 75 6d 62 6c 65 77 65 65 64 5f 4b 44 45 5f |_Tumbleweed_KDE_| 00000040 4c 69 76 65 20 20 20 20 00 00 00 00 00 00 00 00 |Live ........| 00000050 dc 53 07 00 00 07 53 dc 00 00 00 00 00 00 00 00 |.S....S.........| 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000070 00 00 00 00 00 00 00 00 01 00 00 01 01 00 00 01 |................| 00000080 00 08 08 00 c2 00 00 00 00 00 00 c2 75 00 00 00 |............u...| 00000090 00 00 00 00 00 00 00 76 00 00 00 00 22 00 53 00 |.......v....".S.| 000000a0 00 00 00 00 00 53 00 08 00 00 00 00 08 00 7c 01 |.....S........|.| 000000b0 10 09 30 15 00 02 00 00 01 00 00 01 01 00 20 20 |..0........... | 000000c0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | * 00000130 20 20 20 20 20 20 20 20 20 20 20 20 20 20 53 55 | SU| 00000140 53 45 20 4c 49 4e 55 58 20 47 4d 42 48 20 20 20 |SE LINUX GMBH | 00000150 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | * 000001b0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 4b 49 | KI| 000001c0 57 49 20 2d 20 48 54 54 50 53 3a 2f 2f 47 49 54 |WI - HTTPS://GIT| 000001d0 48 55 42 2e 43 4f 4d 2f 4f 53 49 4e 53 49 44 45 |HUB.COM/OSINSIDE| 000001e0 2f 4b 49 57 49 20 20 20 20 20 20 20 20 20 20 20 |/KIWI | 000001f0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | 00000200
-Best regards
On 05-24-2024 12:33PM, Andrei Borzenkov wrote:
On 24.05.2024 20:19, -pj wrote:
Hi, I am using Tumbleweed with KDE 6 on a machine here. I decide to update the machine today by passing 'zypper dup' into Konsole. After a bit the update completed and 'zypper ps -s' said there were no core libraries updated but I proceeded to powercycle the machine.
After doing this the machine is stuck at the following displayed on screen > GRUB _
Can you tell me what may have happened and the steps to try to attempt to get this repaired?
Boot from live image, run https://github.com/arvidjaar/bootinfoscript, provide RESULTS.txt.
On 05-24-2024 02:51PM, Andrei Borzenkov wrote:
On 24.05.2024 22:48, -pj wrote:
#hexdump -C -n 512 /dev/sdb1 00000000 01 43 44 30 30 31 01 00 20 20 20 20 20 20 20 20 |.CD001.. |
Is it really your HDD (or SSD)? Not your live USB?
Sorry to have not pasted in susepaste, I realized and was preparing a susepaste when your message came in here. The OS SDD is at /dev/sda *not* /dev/sdb . /dev/sdb is the Live OS on USB Flashdrive. See this susepaste > https://paste.opensuse.org/pastes/db65b16ca38c
On 24.05.2024 23:01, -pj wrote:
On 05-24-2024 02:51PM, Andrei Borzenkov wrote:
On 24.05.2024 22:48, -pj wrote:
#hexdump -C -n 512 /dev/sdb1 00000000 01 43 44 30 30 31 01 00 20 20 20 20 20 20 20 20 |.CD001.. |
Is it really your HDD (or SSD)? Not your live USB?
Sorry to have not pasted in susepaste, I realized and was preparing a susepaste when your message came in here.
The OS SDD is at /dev/sda *not* /dev/sdb . /dev/sdb is the Live OS on USB Flashdrive.
Well, in the RESULTS.txt you posted earlier it was exactly the other way riund. Anyway
See this susepaste > https://paste.opensuse.org/pastes/db65b16ca38c
# hexdump -C -n 512 /dev/sda1 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200 There is no bootloader where it was supposed to be according to RESULTS.txt. Try chrooting into your root and running "update-bootloader --reinit". You will need to bind mount /dev, /sys, /proc and /run into chroot.
On 05-24-2024 03:08PM, Andrei Borzenkov wrote:
On 24.05.2024 23:01, -pj wrote:
On 05-24-2024 02:51PM, Andrei Borzenkov wrote:
On 24.05.2024 22:48, -pj wrote:
#hexdump -C -n 512 /dev/sdb1 00000000 01 43 44 30 30 31 01 00 20 20 20 20 20 20 20 20 |.CD001.. |
Is it really your HDD (or SSD)? Not your live USB?
Sorry to have not pasted in susepaste, I realized and was preparing a susepaste when your message came in here.
The OS SDD is at /dev/sda *not* /dev/sdb . /dev/sdb is the Live OS on USB Flashdrive.
Well, in the RESULTS.txt you posted earlier it was exactly the other way riund. Anyway
See this susepaste > https://paste.opensuse.org/pastes/db65b16ca38c
# hexdump -C -n 512 /dev/sda1 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200
There is no bootloader where it was supposed to be according to RESULTS.txt.
Try chrooting into your root and running "update-bootloader --reinit". You will need to bind mount /dev, /sys, /proc and /run into chroot.
Thank you for your message. I will do as you suggest above. I have not done this before. Could you explain in more detail at all perhaps? I will have to look at how to do this . How to "bind mount /dev, /sys, /proc, and /run into chroot"? I will return to this machine in a while. I must work on another project for a few hours now. -Greatest Hopes
This <https://www.suse.com/support/kb/doc/?id=000018770> is a good starting point. On 24/05/2024 22:16, -pj wrote:
On 05-24-2024 03:08PM, Andrei Borzenkov wrote:
On 24.05.2024 23:01, -pj wrote:
On 05-24-2024 02:51PM, Andrei Borzenkov wrote:
On 24.05.2024 22:48, -pj wrote:
#hexdump -C -n 512 /dev/sdb1 00000000 01 43 44 30 30 31 01 00 20 20 20 20 20 20 20 20 |.CD001.. |
Is it really your HDD (or SSD)? Not your live USB?
Sorry to have not pasted in susepaste, I realized and was preparing a susepaste when your message came in here.
The OS SDD is at /dev/sda *not* /dev/sdb . /dev/sdb is the Live OS on USB Flashdrive.
Well, in the RESULTS.txt you posted earlier it was exactly the other way riund. Anyway
See this susepaste > https://paste.opensuse.org/pastes/db65b16ca38c
# hexdump -C -n 512 /dev/sda1 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200
There is no bootloader where it was supposed to be according to RESULTS.txt.
Try chrooting into your root and running "update-bootloader --reinit". You will need to bind mount /dev, /sys, /proc and /run into chroot.
Thank you for your message. I will do as you suggest above. I have not done this before. Could you explain in more detail at all perhaps? I will have to look at how to do this .
How to "bind mount /dev, /sys, /proc, and /run into chroot"?
I will return to this machine in a while. I must work on another project for a few hours now.
-Greatest Hopes
On 05-24-2024 03:29PM, Andreas Croci wrote:
This <https://www.suse.com/support/kb/doc/?id=000018770> is a good starting point.
Thank you very much for suggesting this link above. I have had success with this, it seems now from what I can tell. I passed '# mount /dev/mapper/system-root /mnt' and the rest I was able to follow without alot of difficulty. Can you tell me briefly how this happened or may have happened? Is there a way I could have prevented this from happening after the 'zypper dup' was displayed as completed in Konsole? -Regards
On 24/05/2024 22:16, -pj wrote:
On 05-24-2024 03:08PM, Andrei Borzenkov wrote:
On 24.05.2024 23:01, -pj wrote:
On 05-24-2024 02:51PM, Andrei Borzenkov wrote:
On 24.05.2024 22:48, -pj wrote:
#hexdump -C -n 512 /dev/sdb1 00000000 01 43 44 30 30 31 01 00 20 20 20 20 20 20 20 20 |.CD001.. |
Is it really your HDD (or SSD)? Not your live USB?
Sorry to have not pasted in susepaste, I realized and was preparing a susepaste when your message came in here.
The OS SDD is at /dev/sda *not* /dev/sdb . /dev/sdb is the Live OS on USB Flashdrive.
Well, in the RESULTS.txt you posted earlier it was exactly the other way riund. Anyway
See this susepaste > https://paste.opensuse.org/pastes/db65b16ca38c
# hexdump -C -n 512 /dev/sda1 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200
There is no bootloader where it was supposed to be according to RESULTS.txt.
Try chrooting into your root and running "update-bootloader --reinit". You will need to bind mount /dev, /sys, /proc and /run into chroot.
Thank you for your message. I will do as you suggest above. I have not done this before. Could you explain in more detail at all perhaps? I will have to look at how to do this .
How to "bind mount /dev, /sys, /proc, and /run into chroot"?
I will return to this machine in a while. I must work on another project for a few hours now.
-Greatest Hopes
On 24.05.2024 23:16, -pj wrote:
On 05-24-2024 03:08PM, Andrei Borzenkov wrote:
On 24.05.2024 23:01, -pj wrote:
On 05-24-2024 02:51PM, Andrei Borzenkov wrote:
On 24.05.2024 22:48, -pj wrote:
#hexdump -C -n 512 /dev/sdb1 00000000 01 43 44 30 30 31 01 00 20 20 20 20 20 20 20 20 |.CD001.. |
Is it really your HDD (or SSD)? Not your live USB?
Sorry to have not pasted in susepaste, I realized and was preparing a susepaste when your message came in here.
The OS SDD is at /dev/sda *not* /dev/sdb . /dev/sdb is the Live OS on USB Flashdrive.
Well, in the RESULTS.txt you posted earlier it was exactly the other way riund. Anyway
See this susepaste > https://paste.opensuse.org/pastes/db65b16ca38c
# hexdump -C -n 512 /dev/sda1 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200
There is no bootloader where it was supposed to be according to RESULTS.txt.
Try chrooting into your root and running "update-bootloader --reinit". You will need to bind mount /dev, /sys, /proc and /run into chroot.
Thank you for your message. I will do as you suggest above. I have not done this before. Could you explain in more detail at all perhaps? I will have to look at how to do this .
How to "bind mount /dev, /sys, /proc, and /run into chroot"?
Are you using btrfs?
I will return to this machine in a while. I must work on another project for a few hours now.
-Greatest Hopes
On 05-24-2024 03:29PM, Andrei Borzenkov wrote:
On 24.05.2024 23:16, -pj wrote:
On 05-24-2024 03:08PM, Andrei Borzenkov wrote:
On 24.05.2024 23:01, -pj wrote:
On 05-24-2024 02:51PM, Andrei Borzenkov wrote:
On 24.05.2024 22:48, -pj wrote:
#hexdump -C -n 512 /dev/sdb1 00000000 01 43 44 30 30 31 01 00 20 20 20 20 20 20 20 20 |.CD001.. |
Is it really your HDD (or SSD)? Not your live USB?
Sorry to have not pasted in susepaste, I realized and was preparing a susepaste when your message came in here.
The OS SDD is at /dev/sda *not* /dev/sdb . /dev/sdb is the Live OS on USB Flashdrive.
Well, in the RESULTS.txt you posted earlier it was exactly the other way riund. Anyway
See this susepaste > https://paste.opensuse.org/pastes/db65b16ca38c
# hexdump -C -n 512 /dev/sda1 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200
There is no bootloader where it was supposed to be according to RESULTS.txt.
Try chrooting into your root and running "update-bootloader --reinit". You will need to bind mount /dev, /sys, /proc and /run into chroot.
Thank you for your message. I will do as you suggest above. I have not done this before. Could you explain in more detail at all perhaps? I will have to look at how to do this .
How to "bind mount /dev, /sys, /proc, and /run into chroot"?
Are you using btrfs?
Yes, the drive has an *encrypted* btrfs filesystem. In this instance from live OS, I used '# cryptsetup luksOpen /dev/sda2 Clean' using Clean as the drives arbitrary name. This is the '# fdisk -l' output displayed for the disk (/dev/sda). > https://paste.opensuse.org/pastes/f4e8a6982d5c I would like to thank you for your responses. I will read the link from Andreas Croci. Do you have any more advice? -Regards
I will return to this machine in a while. I must work on another project for a few hours now.
-Greatest Hopes
On 25.05.2024 04:02, -pj wrote:
On 05-24-2024 03:29PM, Andrei Borzenkov wrote:
On 24.05.2024 23:16, -pj wrote:
On 05-24-2024 03:08PM, Andrei Borzenkov wrote:
On 24.05.2024 23:01, -pj wrote:
On 05-24-2024 02:51PM, Andrei Borzenkov wrote:
On 24.05.2024 22:48, -pj wrote: > > #hexdump -C -n 512 /dev/sdb1 > 00000000 01 43 44 30 30 31 01 00 20 20 20 20 20 20 20 20 > |.CD001.. > |
Is it really your HDD (or SSD)? Not your live USB?
Sorry to have not pasted in susepaste, I realized and was preparing a susepaste when your message came in here.
The OS SDD is at /dev/sda *not* /dev/sdb . /dev/sdb is the Live OS on USB Flashdrive.
Well, in the RESULTS.txt you posted earlier it was exactly the other way riund. Anyway
See this susepaste > https://paste.opensuse.org/pastes/db65b16ca38c
# hexdump -C -n 512 /dev/sda1 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200
There is no bootloader where it was supposed to be according to RESULTS.txt.
Try chrooting into your root and running "update-bootloader --reinit". You will need to bind mount /dev, /sys, /proc and /run into chroot.
Thank you for your message. I will do as you suggest above. I have not done this before. Could you explain in more detail at all perhaps? I will have to look at how to do this .
How to "bind mount /dev, /sys, /proc, and /run into chroot"?
Are you using btrfs?
Yes, the drive has an *encrypted* btrfs filesystem.
In this instance from live OS, I used '# cryptsetup luksOpen /dev/sda2 Clean' using Clean as the drives arbitrary name.
This is the '# fdisk -l' output displayed for the disk (/dev/sda). > https://paste.opensuse.org/pastes/f4e8a6982d5c
I would like to thank you for your responses. I will read the link from Andreas Croci. Do you have any more advice?
This KB looks OK and already handles btrfs. I usually do mount -t -t btrfs instead of mount -a to avoid remote filesystem. I wish mount command had some "local only" flag.
participants (3)
-
-pj -
Andreas Croci -
Andrei Borzenkov