bootctl install - non-responsive drive

WickedWizard · 2023-12-16 19:12:37

Hello all, if nothing else I hope someone has a good laugh at my stupidity.

Scenario: dual boot setup, Window 11 on on SSD, Linux on another SSD. systemd-boot was set up to select the OS upon boot, and the Linux SSD prioritized in the UEFI boot order.

Fast forward to a few days ago, Windows did an update and systemd-boot was bypassed and my system booted straight to Windows. I was sort of mentally prepared for this eventuality, though I thought separated disks might prevent it.

So after booting in with Arch on a USB key and running efibootmgr -v I noticed that the EFI on my Linux SSD was pointing to the Windows bootloader.

Here's where my folly began: after consulting the wiki I noted that Fast Start and Secure boot were both disabled on my system so ruled those out. I was a little intimidated with correcting the boot path using efibootmgr so after doing some google searched someone reported success chrooting into the disk and running

bootctl install

.

I mounted both the boot and main parititions of my SSD to the USB key and chrooted in, but when I attempted

bootlctl install

it complained that the boot partitiion wasn't found in /efi or /boot. So without thinking I ran

mount /dev/nvme01pn1 /boot

bootctl install

Success was reported, however after logging out of the session and rebooting the disk is now invisible. Not showing up in the bios, Windows disk management, fdisk -l, lsblk... all completely invisible. Definitely not a case of the disk suddenly being detached (it's an M.2 securely installed).

So sadly my practically brand new SSD seems to be a hunk of silicon garbage :'(

I'm going to try installing on another system to see if it's recognized there.

So please, at least have a nice laugh at my expense, so I can get some value of it.

Head_on_a_Stick · 2023-12-16 20:05:06

I very much doubt `bootctl install` has trashed your disk. All it does is copy the systemd-boot loader to the EFI system partition and make a new boot entry.

WickedWizard · 2023-12-16 22:24:38

@Head_on_a_Stick well that's a relief, that's what I thought it did too. I wonder why my system can't see it then?

WickedWizard · 2023-12-16 23:56:24

Hey @Head_on_a_Stick you were right, I plugged it into another computer and it was fine. I went ahead and formatted it and plugged back into mine, and it's showing up again.

No clue what I did, but at least I didn't lose any data.

Boo to Windows and their boot overwriting!

Head_on_a_Stick · 2023-12-17 10:16:24

WickedWizard wrote:

Boo to Windows and their boot overwriting!

https://wiki.archlinux.org/title/Unifie … boot_order

Arch Linux

#1 2023-12-16 19:12:37

bootctl install - non-responsive drive

#2 2023-12-16 20:05:06

Re: bootctl install - non-responsive drive

#3 2023-12-16 22:24:38

Re: bootctl install - non-responsive drive

#4 2023-12-16 23:56:24

Re: bootctl install - non-responsive drive

#5 2023-12-17 10:16:24

Re: bootctl install - non-responsive drive

Board footer