[opensuse] Windows 10 apparently destroyed my bootloader
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up? Thanks for any advise and help... Marc -- --... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-. *Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! * -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 18. Januar 2020 07:49:12 schrieb Marc Chamberlin <marc@marcchamberlin.com>:
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up?
Thanks for any advise and help... Marc
--
--... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-.
*Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! *
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org Hi Marc,
this procedure should help: https://en.opensuse.org/SDB:Repair_MBR_after_Windows_install Regards, vinz. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 18 januari 2020 09:09:46 CET schreef Vinzenz Vietzke:
Am 18. Januar 2020 07:49:12 schrieb Marc Chamberlin <marc@marcchamberlin.com>:
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up?
Thanks for any advise and help... Marc
--
--... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-.
*Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! *
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Marc,
this procedure should help: https://en.opensuse.org/SDB:Repair_MBR_after_Windows_install
Regards, vinz. Vinz, that looks outdated. Specially on modern ( Win 10...) systems.
Marc, find the /dev/sdX# entry that has your openSUSE install, and replace the X and # to the appropriate values, then do: mount /dev/sdX# /mnt mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt mount -a yast Then open the bootloader modules ( in System ), make sure that "Probe for other OS" is checked and hit OK. Reboot and you should be fine. FYI: the 'mount -a' is needed in case of btrfs, to make sure the subvolumes are mounted ( at least, that's what I'm told ). -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 18. Januar 2020 09:21:23 schrieb Knurpht-openSUSE <knurpht@opensuse.org>:
Op zaterdag 18 januari 2020 09:09:46 CET schreef Vinzenz Vietzke:
Am 18. Januar 2020 07:49:12 schrieb Marc Chamberlin <marc@marcchamberlin.com>:
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up?
Thanks for any advise and help... Marc
--
--... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-.
*Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! *
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Marc,
this procedure should help: https://en.opensuse.org/SDB:Repair_MBR_after_Windows_install
Regards, vinz. Vinz, that looks outdated. Specially on modern ( Win 10...) systems.
Marc, find the /dev/sdX# entry that has your openSUSE install, and replace the X and # to the appropriate values, then do:
mount /dev/sdX# /mnt mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt mount -a yast
Then open the bootloader modules ( in System ), make sure that "Probe for other OS" is checked and hit OK. Reboot and you should be fine.
FYI: the 'mount -a' is needed in case of btrfs, to make sure the subvolumes are mounted ( at least, that's what I'm told ).
One crucial part is still relevant: "You have to make sure to be able to boot into openSUSE. You can do this either by using the Rescue System mode on the installation DVD or by using a CD with Plop Boot Manager or Super Grub Disk, for example." Regards, vinz. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 18 januari 2020 10:31:45 CET schreef Vinzenz Vietzke:
Am 18. Januar 2020 09:21:23 schrieb Knurpht-openSUSE <knurpht@opensuse.org>:
Op zaterdag 18 januari 2020 09:09:46 CET schreef Vinzenz Vietzke:
Am 18. Januar 2020 07:49:12 schrieb Marc Chamberlin
<marc@marcchamberlin.com>:
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up?
Thanks for any advise and help... Marc
--
--... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-.
*Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! *
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi Marc,
this procedure should help: https://en.opensuse.org/SDB:Repair_MBR_after_Windows_install
Regards, vinz.
Vinz, that looks outdated. Specially on modern ( Win 10...) systems.
Marc, find the /dev/sdX# entry that has your openSUSE install, and replace the X and # to the appropriate values, then do:
mount /dev/sdX# /mnt mount --bind /dev /mnt/dev, mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt mount -a yast
Then open the bootloader modules ( in System ), make sure that "Probe for other OS" is checked and hit OK. Reboot and you should be fine.
FYI: the 'mount -a' is needed in case of btrfs, to make sure the subvolumes are mounted ( at least, that's what I'm told ).
One crucial part is still relevant:
"You have to make sure to be able to boot into openSUSE. You can do this either by using the Rescue System mode on the installation DVD or by using a CD with Plop Boot Manager or Super Grub Disk, for example."
Regards, vinz. You are of course 100% right
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 18 Jan 2020 09:21:03 +0100 Knurpht-openSUSE Knurpht-openSUSE wrote:
Vinz, that looks outdated. Specially on modern ( Win 10...) systems.
Marc, find the /dev/sdX# entry that has your openSUSE install, and replace the X and # to the appropriate values, then do:
mount /dev/sdX# /mnt mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt
Hi Knurpht, Out of curiosity and for posterity, my empirically derived, long term proven 'just works' DR procedure comports with the above steps, up to and including the 'chroot /mnt'. I also grasp why the next line could be necessary / useful (in case of btrfs):
mount -a
Continuing with your nomenclature, my next steps are as follows: grub2-install /dev/sdX# then grub2-mkconfig -o /boot/grub2/grub.cfg then poweroff Are these last steps still valid? TIA & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 18/01/2020 à 11:08, Carl Hartung a écrit :
mount /dev/sdX# /mnt mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt
a bit simpler: mount /dev/sdX# /mnt cd /mnt mount --bind /dev dev mount --bind /proc proc mount --bind /sys sys chroot . using history (up arrow) for the --bind lines makes it very fast then simply use yast... and the new language menu of rescue is very handy, it save us typing "loadkeys <LANG> :-) jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 18 januari 2020 11:08:08 CET schreef Carl Hartung:
On Sat, 18 Jan 2020 09:21:03 +0100
Knurpht-openSUSE Knurpht-openSUSE wrote:
Vinz, that looks outdated. Specially on modern ( Win 10...) systems.
Marc, find the /dev/sdX# entry that has your openSUSE install, and replace the X and # to the appropriate values, then do:
mount /dev/sdX# /mnt mount --bind /dev /mnt/dev mount --bind /proc /mnt/proc mount --bind /sys /mnt/sys chroot /mnt
Hi Knurpht,
Out of curiosity and for posterity, my empirically derived, long term proven 'just works' DR procedure comports with the above steps, up to and including the 'chroot /mnt'. I also grasp why the next line could
be necessary / useful (in case of btrfs):
mount -a
Continuing with your nomenclature, my next steps are as follows:
grub2-install /dev/sdX#
then
grub2-mkconfig -o /boot/grub2/grub.cfg
then
poweroff
Are these last steps still valid?
TIA & regards,
Carl Hi Carl,
I just copied the code from my notes..... -- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/01/2020 07.48, Marc Chamberlin wrote: | I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and | it looks like some freaking Windows update has destroyed my | bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise | now my system will only boot up Windows 10 and I no longer have the | option to boot up OpenSuSE. What is the best way to restore the | boot loader on my system so I can get the GRUB menu back to select | what operating system I want to boot up? | | Thanks for any advise and help... Marc People, the first thing to do before jumping to give instructions to reinstall grub, the bootloader, is diagnose what happened. For example, one thing I have heard windows 10 update did to people recently is add a new partition; thus partition number changes and Linux, usually installed after Windows, can not boot. So one thing to do is verify that with a rescue system. The repair needs modifying fstab, grub entries, bootloader, initrd, and efi "code". Another typical cause, in an EFI system like this, is very that the efi entries are correct, because either the UEFI (aka BIOS) may have deleted the Linux entry. Running "efibootmgr" in a rescue system would tell. If opensuse entry is missing, I have doubts about the next step. Now grub itself destroyed in a non MBR system after a Windows update would be very rare. Unless grub had been installed to the MBR in an EFI system, which is WRONG, but there may be reasons for it. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXiLw2gAKCRC1MxgcbY1H 1clkAJsEZu5AonwJM+U9N8mBc4pi64jpxQCfQoYTGmTCUQZhpaKxY0p+bN9SucQ= =ibkm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-01-18 06:49 AM, Carlos E. R. wrote:
People, the first thing to do before jumping to give instructions to reinstall grub, the bootloader, is diagnose what happened.
That's why I suggested that fast boot issue. It's easy to check and fix. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-01-18 01:48 AM, Marc Chamberlin wrote:
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up?
Thanks for any advise and help... Marc
There's a "feature" with Windows 10, where it doesn't fully shut down a drive, when shutting down. This prevents the boot manager from working. There's a setting that disables that, but I don't recall the details. A bit of Googling should find it though. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-01-18 07:05 AM, James Knott wrote:
On 2020-01-18 01:48 AM, Marc Chamberlin wrote:
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up?
Thanks for any advise and help... Marc
There's a "feature" with Windows 10, where it doesn't fully shut down a drive, when shutting down. This prevents the boot manager from working. There's a setting that disables that, but I don't recall the details. A bit of Googling should find it though.
It's the fast boot option, which has to be turned off. Here's some info: https://lifehacker.com/enable-this-setting-to-make-windows-10-boot-up-faster... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 18/01/2020 à 13:17, James Knott a écrit :
It's the fast boot option, which has to be turned off.
faster way is to reboot instead of switch off, and press the button after that jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 18/01/2020 13.17, James Knott wrote:
On 2020-01-18 07:05 AM, James Knott wrote:
On 2020-01-18 01:48 AM, Marc Chamberlin wrote:
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up?
Thanks for any advise and help... Marc
There's a "feature" with Windows 10, where it doesn't fully shut down a drive, when shutting down. This prevents the boot manager from working. There's a setting that disables that, but I don't recall the details. A bit of Googling should find it though.
It's the fast boot option, which has to be turned off.
Here's some info:
https://lifehacker.com/enable-this-setting-to-make-windows-10-boot-up-faster...
It should not impede booting, unless they have changed it. It impedes accessing the windows partitions from Linux, because they are "open" or "mounted". -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 2020-01-18 11:45 AM, Carlos E. R. wrote:
It's the fast boot option, which has to be turned off.
Here's some info:
https://lifehacker.com/enable-this-setting-to-make-windows-10-boot-up-faster...
It should not impede booting, unless they have changed it. It impedes accessing the windows partitions from Linux, because they are "open" or "mounted".
I've experienced that a couple of times. You don't even get to the grub boot loader. It goes right into Windows. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2020-01-18 a las 12:07 -0500, James Knott escribió:
On 2020-01-18 11:45 AM, Carlos E. R. wrote:
It's the fast boot option, which has to be turned off.
Here's some info:
https://lifehacker.com/enable-this-setting-to-make-windows-10-boot-up-faster...
It should not impede booting, unless they have changed it. It impedes accessing the windows partitions from Linux, because they are "open" or "mounted".
I've experienced that a couple of times. You don't even get to the grub boot loader. It goes right into Windows.
Thats when the machine is hibernated. Linux does the same, but it is currently broken. - -- Cheers Carlos E. R. (from openSUSE 15.1 (Legolas)) -----BEGIN PGP SIGNATURE----- iHIEARECADIWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXiOn/hQccm9iaW4ubGlz dGFzQGdteC5lcwAKCRC1MxgcbY1H1auQAKCX1r0v0GoAxvxBDVfj2X88UmD+8gCe MIyJbc8oA9Lk9SNjEwxeha791UU= =PY/5 -----END PGP SIGNATURE-----
On 2020-01-18 07:51 PM, Carlos E. R. wrote:
I've experienced that a couple of times. You don't even get to the grub boot loader. It goes right into Windows.
Thats when the machine is hibernated. Linux does the same, but it is currently broken.
No, it wasn't in hibernation. It would run Windows and when I tried to reboot, it would boot back into Windows, not the grub menu. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-01-18 08:04 PM, James Knott wrote:
On 2020-01-18 07:51 PM, Carlos E. R. wrote:
I've experienced that a couple of times. You don't even get to the grub boot loader. It goes right into Windows.
Thats when the machine is hibernated. Linux does the same, but it is currently broken.
No, it wasn't in hibernation. It would run Windows and when I tried to reboot, it would boot back into Windows, not the grub menu.
I just turned on that option again. When I turn the computer off, from Windows, and then turn it on again, it goes directly into Windows, without the grub menu appearing. However, if I restart, the menu appears. Based on the OP's description, this could be what he's experiencing. He doesn't say if he tried a restart. As I mentioned, I've been hit with this a couple of times. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 18 Jan 2020 21:34:38 -0500 James Knott wrote:
I just turned on that option again. When I turn the computer off, from Windows, and then turn it on again, it goes directly into Windows, without the grub menu appearing. However, if I restart, the menu appears. Based on the OP's description, this could be what he's experiencing. He doesn't say if he tried a restart. As I mentioned, I've been hit with this a couple of times.
I seem to recall three methods for instructing Win10 to not use fastboot: The first method is to explicitly turn it off. This setting is permanent until you enable it again. The second is to hold the shift key down and restart the system. This method only disables it for one Win10 boot cycle. The third is to restart Win10 two times in rapid succession. This method also only disables it for one Win10 boot cycle. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-01-18 09:53 PM, Carl Hartung wrote:
I seem to recall three methods for instructing Win10 to not use fastboot:
The first method is to explicitly turn it off. This setting is permanent until you enable it again.
That setting in the Control Panel > Power Options is what does it permanently, at least until some update enables it again. I remember this so well, because it initially took some effort to find the cause. The next time I was a bit wiser. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19/01/2020 03.34, James Knott wrote: | On 2020-01-18 08:04 PM, James Knott wrote: |> On 2020-01-18 07:51 PM, Carlos E. R. wrote: |>>> I've experienced that a couple of times. You don't even get |>>> to the grub boot loader. It goes right into Windows. |>> |>> Thats when the machine is hibernated. Linux does the same, but |>> it is currently broken. |> |> No, it wasn't in hibernation. It would run Windows and when I |> tried to reboot, it would boot back into Windows, not the grub |> menu. |> | | | I just turned on that option again. When I turn the computer off, | from Windows, and then turn it on again, it goes directly into | Windows, without the grub menu appearing. However, if I restart, | the menu > appears. Based on the OP's description, this could be | what he's experiencing. He doesn't say if he tried a restart. As | I mentioned, I've been hit with this a couple of times. With fast boot activated, "off" is understood as (another kind of) hibernate. Mind, if the system was updating itself, a reboot might go into windows too. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXiQHWAAKCRC1MxgcbY1H 1Ve4AJ9mBiKG9/s3MOKDq3aYRabGR8xnNgCcCLdYxy+uTzNxE8t7E2dXOqVV4Ho= =LCdk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-01-19 02:38 AM, Carlos E. R. wrote:
Mind, if the system was updating itself, a reboot might go into windows too.
With those updates, I have to use fdisk to change which partition is booted from, so that it goes right into Windows. Otherwise, the update will fail. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19/01/2020 13.37, James Knott wrote: | On 2020-01-19 02:38 AM, Carlos E. R. wrote: |> Mind, if the system was updating itself, a reboot might go into |> windows too. | | With those updates, I have to use fdisk to change which partition | is booted from, so that it goes right into Windows. Otherwise, the | update will fail. That's on BIOS booting, not on UEFI with gpt disks. - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXiSGOgAKCRC1MxgcbY1H 1XsRAJ0dRcn2g0w0MaXlibrsmYwkz3zawQCfazADihMTL2WStoanRRVRNhQufbw= =TUOG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
There's a "feature" with Windows 10, where it doesn't fully shut down a drive, when shutting down. This prevents the boot manager from working. There's a setting that disables that, but I don't recall the details. A bit of Googling should find it though. It's called FastBoot. But I've never seen it affecting a linux bootloader.
Op zaterdag 18 januari 2020 13:05:21 CET schreef James Knott: - Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-01-18 07:18 AM, Knurpht-openSUSE wrote:
erdag 18 januari 2020 13:05:21 CET schreef James Knott:
There's a "feature" with Windows 10, where it doesn't fully shut down a drive, when shutting down. This prevents the boot manager from working. There's a setting that disables that, but I don't recall the details. A bit of Googling should find it though. It's called FastBoot. But I've never seen it affecting a linux bootloader.
I've experienced it a couple of times. That's why I know about it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Samstag, 18. Januar 2020, 07:48:54 CET schrieb Marc Chamberlin:
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up?
Thanks for any advise and help... Marc
Did you already look into the BIOS/UEFI entries for boot order ? Make sure that grub is there at first place. And not windows bootmanager. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 1/17/20 10:48 PM, Marc Chamberlin wrote:
I have a dual boot system for both OpenSuSE 15.1 and Windows 10 and it looks like some freaking Windows update has destroyed my bootloader (I believe it was EFI Grub 2 but I am not sure) Anywise now my system will only boot up Windows 10 and I no longer have the option to boot up OpenSuSE. What is the best way to restore the boot loader on my system so I can get the GRUB menu back to select what operating system I want to boot up?
Thanks for any advise and help... Marc
Wow! Thanks everyone for all your replies and helpful suggestions! I certainly kicked off a lot more discussion than I had expected, so wanted to wait until the dust had settled before attempting anything serious. But I am a bit sheepish in my report back, I had jumped to an erroneous conclusion because all I had done was to boot up the Windows 10 side of my system to set a configuration in one of my security cameras (It only has a Windows interface.) While I was configuring the camera I noted that Windows wanted to do a lot of updated so I let it. But when I tried to reboot back into my SuSE system it failed and only allowed me to boot up Windows 10. So I swore at Microsoft and came here for help.... But on further investigating I discovered that the drive itself, on which my SuSE system is installed, had failed! So Microsoft's updates were only a coincidence with the drive failure. Taking the drive itself out (a Black WD 750GB drive) I can hear it making ticking sounds and the drive does not spin up. So I am going to have to get a new drive, install OpenSuSE on it and try to recover all the bits from my backups. What fun! Sigh, got a lot of work ahead of me! Again many thanks for all your responses and taking the time to try and help. Marc... -- --... ...-- .----. ... -.. . .-- .- --... .--. -..- .-- -- .- .-. -.-. *Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! * -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19/01/2020 22.59, Marc Chamberlin wrote: | On 1/17/20 10:48 PM, Marc Chamberlin wrote: |> I have a dual boot system for both OpenSuSE 15.1 and Windows 10 |> and it looks like some freaking Windows update has destroyed my |> bootloader (I believe it was EFI Grub 2 but I am not sure) |> Anywise now my system will only boot up Windows 10 and I no |> longer have the option to boot up OpenSuSE. What is the best way |> to restore the boot loader on my system so I can get the GRUB |> menu back to select what operating system I want to boot up? |> |> Thanks for any advise and help... Marc |> | Wow! Thanks everyone for all your replies and helpful suggestions! | I certainly kicked off a lot more discussion than I had expected, | so wanted to wait until the dust had settled before attempting | anything serious. But I am a bit sheepish in my report back, I had | jumped to an erroneous conclusion because all I had done was to | boot up the Windows 10 side of my system to set a configuration in | one of my security cameras (It only has a Windows interface.) You might consider installing a virtual machine with a Windows with the sole purpose of handling the cameras when needed. | While I was configuring the camera I noted that Windows wanted to | do a lot of updated so I let it. But when I tried to reboot back | into my SuSE system it failed and only allowed me to boot up | Windows 10. So I swore at Microsoft and came here for help.... | | But on further investigating I discovered that the drive itself, on | which my SuSE system is installed, had failed! So Microsoft's | updates were only a coincidence with the drive failure. Taking the | drive itself out (a Black WD 750GB drive) I can hear it making | ticking sounds and the drive does not spin up. So I am going to | have to get a new drive, install OpenSuSE on it and try to recover | all the bits from my backups. What fun! Yeah :-( Well, it does show that first thing is diagnosis ;-) | | Sigh, got a lot of work ahead of me! Again many thanks for all | your responses and taking the time to try and help. Marc... Welcome - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXiTS0gAKCRC1MxgcbY1H 1ThXAKCRsmQNRXjcIHcmLxMHS+cPn9jxmACaAoAcrFonkq7KP0583pD1qBUNSm4= =qyF3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2020-01-19 04:59 PM, Marc Chamberlin wrote:
But on further investigating I discovered that the drive itself, on which my SuSE system is installed, had failed! So Microsoft's updates were only a coincidence with the drive failure. Taking the drive itself out (a Black WD 750GB drive) I can hear it making ticking sounds and the drive does not spin up. So I am going to have to get a new drive, install OpenSuSE on it and try to recover all the bits from my backups. What fun!
WOW!!! That's the first time I've heard of a Windows update killing a drive! ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Carl Hartung -
Carlos E. R. -
Carlos E. R. -
James Knott -
jdd＠dodin.org -
Knurpht-openSUSE -
Marc Chamberlin -
Markus Koßmann -
Vinzenz Vietzke