how to reboot in another os just once?

[john_hudson]

@aperali

pc reboots in windows as expected but without passing through the boot loader screen anymore and after I reboot from W10 it is always keeping booting into W10 with no boot loader screen options to choose.

Is this really a Windows 10 issue? My understanding is that Windows 10 never shuts down unless you force it; so a normal ‘shutdown’ is really a hibernation and a reboot never takes you back to the boot process; it simply reloads Windows.

[gogalthorp]

Maybe and Windows Fast Boot does mess thing up but the grub no write to BTRFS is real

As to the OP You have a LVM partition which can contain other partitions so are you sure that there are not multiple partition in the LVM?? We can’t tell from the data provided to date

This is the kind of situation that makes having a separate home partition for your personal stuff make sense. If you have to reinstall you end up wiping your data. With a separate home you can just wipe the root and leave your data and settings safe.

[aperali]

@john_hudson

Is this really a Windows 10 issue? My understanding is that Windows 10 never shuts down unless you force it; so a normal ‘shutdown’ is really a hibernation and a reboot never takes you back to the boot process; it simply reloads Windows.

I dont think it is a w10 issue as when using GRUB2_SET_DEFAULT everything works as expected

[aperali]

@gogalthorp

Maybe and Windows Fast Boot does mess thing up but the grub no write to BTRFS is real

As to the OP You have a LVM partition which can contain other partitions so are you sure that there are not multiple partition in the LVM?? We can’t tell from the data provided to date

This is the kind of situation that makes having a separate home partition for your personal stuff make sense. If you have to reinstall you end up wiping your data. With a separate home you can just wipe the root and leave your data and settings safe.

I’ve just rebooted in opensuse using grub2-once 0 and got the same behavior, no bootloader options screen.

[terjejh]

I have not read everything above and am not sure I understand the real issue, so use my comment just for what it is worth or not. I myself have an ultrabook with a grub2 tripple-boot linux installation: Ubuntu factory installed, Leap and Tumbleweed add-installed. That is no Windows.

Let us say Tumbleweed was installed last, and so is located on top of the grub2 boot menu and boot as default after a short break. If I use Leap mostly I want Leap to boot default by bringing it on top of the menu. I’ve found out a simple way to fix this, is to select Leap once from the menu and boot it. Then from running Leap I start YasT2 > Bootloader and just OK to finish. This will bring Leap on top of the menu and boot it default after this.

[aperali]

@nrickert

As far as I know, “grub2-once” works by storing information in “/boot/grub2/grubenv”. And grub2 is supposed to remove that information on the next boot. But grub2 is unable to write to “grubenv” if it is on a “btrfs” file system.

Or, at least, that used to be the problem. I don’t know whether it is still a problem.

I think you were right! After reinstalling suse in an ext4 partition with no LVM support everything works as expected.
I’m not sure about file system but LVM does’t work wirh grub2-once acording GNU GRUB Manual 2.12
Thank you all

[terjejh]

@aperali

Hi
I’m trying to figure out how to reboot just once in a different OS (Windows 10) and after rebooting from W10 it automatically comes back to opensuse at the boot screen order as default.

I’ve tried some methods like these (no matter if the GRUB2_DEFAULT=0 or saved - 0 is the TW:

Method 1:

sudo grub2-set-default 2

which is the W10 place at the boot order and then

sudo reboot

but it fixed the boot order to always boot on W10 although I have an option to manually change it in the boot loader screen.

If you are on the console display and select W10 boot from the grub2 menu, does the boot order change also then after restart from W10?

Terje H.

[aperali]

@terjejh

If you are on the console display and select W10 boot from the grub2 menu, does the boot order change also then after restart from W10?

Terje H.

If I had used grub2-set-default to reboot from suse to w10 yes it was changed to win10 after rebooting from it.
Fortunately after reinstalling suse problem was solved!

[terjejh]

@aperali

If I had used grub2-set-default to reboot from suse to w10 yes it was changed to win10 after rebooting from it.
Fortunately after reinstalling suse problem was solved!

Just to clarify:
If you have Tumbleweed set as default boot and from a Tw session enter just the “reboot” command or the “DE | Restart”, this bring up the grub2 menu.
Select W10 from this menu, this boot W10
From the W10 session, select Restart

Is the grub2 boot menu that now come up re-ordered so that W10 is on top (the default)?

At least this procedure works flawless in my case between Leap 15.1, Tumbleweed and Ubuntu 18.04.
I had Windows installed earlier, but can’t remember it caused the mentioned issue.

Terje H.

[oldcpu]

I’m a bit late coming to this thread.

For EXT4 format, I blogged about this topic here: oldcpu’s meandering thoughts on Computers, GNU/Linux and openSUSE (which has already been noted - and solved in this thread).

I found it very useful, when maintaining a relative’s GNU/Linux PC from distances very far away. If one’s relative mistakenly trashed one of their boot partitions, I could have them boot into one of the other GNU/Linux partitions, which would allow me to externally access the broken partition and repair such.
.