DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

surister · 2020-03-10 16:04:54

Hello there, my current installation is the following:

- Dual bot arch + Windows 10 with systemd-boot both on different SSDs.

Back in the day to make systemd-boot aware of windows I copied from the Windows EFI partition

to

/boot/EFI/Microsoft

Everything worked fine, I'd boot the pc and get two options, Arch and Windows, but today for some reason, it would boot directly to arch.

I didn't do/touch anything that could result into this

--------------------------------------------------------------------------------------------------

- I tested that the WIndows disk worked properly, I went into the bios changed the boot order to any of the Windows boot manager option (with disk name, the middle one doesn't boot to anything) and I booted into windows, it worked finely.

https://media.discordapp.net/attachment … height=684

- I updated the the system with

sudo pacman -Syu

- I copied again the windows efi partition into

/boot/EFI/Microsoft

- I checked that my loader.conf was Intact

# cat /boot/loader/loader.conf
timeout 30

I don't know what to do so I am once again asking for your wisdom.

bootctl status

System:
     Firmware: UEFI 2.60 (American Megatrends 5.12)
  Secure Boot: disabled
   Setup Mode: setup

Current Boot Loader:
      Product: systemd-boot 243.162-2-arch
     Features: ✓ Boot counting
               ✓ Menu timeout control
               ✓ One-shot menu timeout control
               ✓ Default entry control
               ✓ One-shot entry control
               ✓ Support for XBOOTLDR partition
               ✓ Support for passing random seed to OS
               ✓ Boot loader sets ESP partition information
          ESP: /dev/disk/by-partuuid/d819b24d-dfbe-a64f-ba0f-05fa05958002
         File: └─/EFI/BOOT/BOOTX64.EFI

Random Seed:
 Passed to OS: yes
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/d819b24d-dfbe-a64f-ba0f-05fa05958002)
         File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 243.162-2-arch)
         File: └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 243.162-2-arch)

Boot Loaders Listed in EFI Variables:
        Title: UEFI OS
           ID: 0x0008
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/d819b24d-dfbe-a64f-ba0f-05fa05958002
         File: └─/EFI/BOOT/BOOTX64.EFI

        Title: Windows Boot Manager
           ID: 0x0004
       Status: inactive, boot-order
    Partition: /dev/disk/by-partuuid/d819b24d-dfbe-a64f-ba0f-05fa05958002
         File: └─/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI

        Title: Windows Boot Manager
           ID: 0x0000
       Status: inactive, boot-order
    Partition: /dev/disk/by-partuuid/e57c2d3b-7064-4b70-bd59-ced503eedfa6
         File: └─/EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI

        Title: Windows Boot Manager
           ID: 0x0005
       Status: inactive, boot-order
    Partition: /dev/disk/by-partuuid/e57c2d3b-7064-4b70-bd59-ced503eedfa6
         File: └─/EFI/MICROSOFT/BOOT/BOOTMGFW.EFI

Boot Loader Entries:
        $BOOT: /boot (/dev/disk/by-partuuid/d819b24d-dfbe-a64f-ba0f-05fa05958002)

gparted --list

Model: ATA ST1000DM003-1CH1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size   Type     File system  Flags
 1      1049kB  374MB   373MB  primary  ntfs         boot
 2      374MB   899GB   899GB  primary  ntfs
 3      1000GB  1000GB  471MB  primary  ntfs         msftres


Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system  Name                          Flags
 1      1049kB  556MB  555MB   ntfs         Basic data partition          hidden, diag
 2      556MB   661MB  105MB   fat32        EFI system partition          boot, esp
 3      661MB   677MB  16.8MB               Microsoft reserved partition  msftres
 4      677MB   500GB  499GB   ntfs         Basic data partition          msftdata


Model: ATA PNY CS900 480GB (scsi)
Disk /dev/sdc: 480GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  538MB   537MB   fat32                 boot, esp
 2      538MB   10.5GB  10.0GB  linux-swap(v1)        swap
 3      10.5GB  480GB   470GB   ext4


Model: Kingston DataTraveler 3.0 (scsi)
Disk /dev/sdd: 15.5GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  15.5GB  15.5GB  primary  fat32        boot, lba

Mod note: Replaced oversized image with URL. Please read the Code of Conduct regarding acceptable image sizes. -- WorMzy

Last edited by WorMzy (2020-03-10 21:07:04)

Steo · 2020-03-10 16:39:25

According to your bootctl status, UEFI OS is Arch.

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/d819b24d-dfbe-a64f-ba0f-05fa05958002)
         File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 243.162-2-arch)
         File: └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 243.162-2-arch)

        Title: UEFI OS
           ID: 0x0008
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/d819b24d-dfbe-a64f-ba0f-05fa05958002
         File: └─/EFI/BOOT/BOOTX64.EFI

I usually run bootctl update after making any changes.

surister · 2020-03-10 18:10:04

Steo wrote:

According to your bootctl status, UEFI OS is Arch.

Available Boot Loaders on ESP:
          ESP: /boot (/dev/disk/by-partuuid/d819b24d-dfbe-a64f-ba0f-05fa05958002)
         File: └─/EFI/systemd/systemd-bootx64.efi (systemd-boot 243.162-2-arch)
         File: └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 243.162-2-arch)

        Title: UEFI OS
           ID: 0x0008
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/d819b24d-dfbe-a64f-ba0f-05fa05958002
         File: └─/EFI/BOOT/BOOTX64.EFI

I usually run bootctl update after making any changes.

I do know it takes me to arch, before when everything worked, it'd take me to the bootloader. The other entries windows one, take me to windows.

Steo · 2020-03-10 18:52:42

Oh I see, you're not getting the systemd boot screen anymore, it's just booting Arch. What are the contents of "/boot/loader/loader.conf"?

surister · 2020-03-10 19:26:10

Steo wrote:

Oh I see, you're not getting the systemd boot screen anymore, it's just booting Arch. What are the contents of "/boot/loader/loader.conf"?

timeout 30

jasonwryan · 2020-03-10 19:36:19

https://bugs.archlinux.org/task/65726

qinohe · 2020-03-10 19:46:16

jasonwryan wrote:

https://bugs.archlinux.org/task/65726

That was I was thinking too at first...
But OP is running 'systemd-boot 243.162-2-arch'

Steo · 2020-03-10 19:49:19

I'm not having this issue on 245. My output of "/sbin/init --version" is

systemd 245 (245-1-arch)

When I reboot, I still get my boot menu with Arch, Debian and Windows.

EDIT: The other thing the wiki says is that there are EFI overrides where loader.conf will be ignored:

Tip:
default and timeout can be changed in the boot menu itself and changes will be stored as EFI variables, overriding these options.
bootctl set-default "" can be used to clear the EFI variable overriding the default option.
A basic loader configuration file is located at /usr/share/systemd/bootctl/loader.conf.

Last edited by Steo (2020-03-10 19:56:23)

qinohe · 2020-03-10 20:04:03

@Steo , still, could be your loader.conf is wrong, unless you reacted to #6

Steo · 2020-03-10 20:11:59

qinohe wrote:

@Steo , still, could be your loader.conf is wrong, unless you reacted to #6

I was reacting to #6, but I just ran bootctl update there and rebooted, the systemd boot screen was highlighting Debian by default instead of Arch.

qinohe · 2020-03-10 20:15:44

Well there you are;)

edit: I was running into this (nasty) new feature earlier today https://bbs.archlinux.org/viewtopic.php?id=253501

Last edited by qinohe (2020-03-10 20:18:07)

Steo · 2020-03-10 20:27:54

Well at least we all know we didn't do anything to mess up our systems then.

In my case, it's not a big deal. I can just press up during boot to select Arch until it's resolved.

qinohe · 2020-03-10 20:36:29

Read the bug report again than read the github page (#3 in bug report).
And, see you won't recover until you act to it.

But hey we may get besides OP's topic here..
@surister, please replace your huge picture with a link; https://wiki.archlinux.org/index.php/Co … s_and_code

Steo · 2020-03-11 14:19:54

qinohe wrote:

Read the bug report again than read the github page (#3 in bug report).
And, see you won't recover until you act to it.

Thanks for that, I had missed that. All I'll have to do is replace mine with "default arch.conf" then.

Arch Linux

#1 2020-03-10 16:04:54

DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#2 2020-03-10 16:39:25

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#3 2020-03-10 18:10:04

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#4 2020-03-10 18:52:42

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#5 2020-03-10 19:26:10

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#6 2020-03-10 19:36:19

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#7 2020-03-10 19:46:16

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#8 2020-03-10 19:49:19

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#9 2020-03-10 20:04:03

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#10 2020-03-10 20:11:59

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#11 2020-03-10 20:15:44

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#12 2020-03-10 20:27:54

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#13 2020-03-10 20:36:29

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

#14 2020-03-11 14:19:54

Re: DUAL BOOT | ARCH + W10 | SYSTEMD-BOOT | Suddenly stops working.

Board footer